You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SchemaVersionLifecycleManager has all the required info but its not passed down to all SchemaProviders methods. some schema type like proto may require to have the schemaName or syntaxType while parsing or creating schema object internally. so its good to make such metadata accessible to schemaProvider.
some more context:
currently all methods within SchemaProvider are treated as kind of static methods where raw schema string are passed and its parsed and schema object or respective kind ( avro or proto or others) will be created on the fly to be able to perform the actual function ( like generateFields or checkCompatibility, etc...)
The above problems are surfaced when any of the methods requires access to additional metadata other than just the raw schemaText hope this explains the issue and it make sense.
The text was updated successfully, but these errors were encountered:
SchemaVersionLifecycleManager
has all the required info but its not passed down to allSchemaProviders
methods. some schema type like proto may require to have theschemaName
orsyntaxType
while parsing or creating schema object internally. so its good to make such metadata accessible to schemaProvider.some more context:
currently all methods within
SchemaProvider
are treated as kind of static methods where raw schema string are passed and its parsed and schema object or respective kind ( avro or proto or others) will be created on the fly to be able to perform the actual function ( likegenerateFields
orcheckCompatibility
, etc...)The above problems are surfaced when any of the methods requires access to additional metadata other than just the raw
schemaText
hope this explains the issue and it make sense.The text was updated successfully, but these errors were encountered: