[HUDI-3264] Make schema registry configs more flexible with MultiTableDeltaStreamer

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.11.0
• Component/s: deltastreamer
• Labels: pull-request-available sev:normal
• Assignee: Pratyaksh Sharma Assign to me
• Reporter: sivabalan narayanan
• Created: 18/Jan/22 11:29
• Updated: 17/Aug/22 10:08
• Resolved: 08/Mar/22 14:09

Description

Ref issue: https://github.com/apache/hudi/issues/4585

Hi guys,

we ran into a problem setting the target schema of our Hudi table using the MultiTableDeltaStreamer.

Using a normal DeltaStreamer, we are able to set our source and target schemas using the properties:

• hoodie.deltastreamer.schemaprovider.registry.url
• hoodie.deltastreamer.schemaprovider.registry.targetUrl

We found that we are not able to set these properties on a table basis using the MultiTableDeltaStreamer, since the MTDS builds SchemaRegistry URLs for target and source schema using the properties:

• hoodie.deltastreamer.schemaprovider.registry.baseUrl
• hoodie.deltastreamer.schemaprovider.registry.sourceUrlSuffix
• hoodie.deltastreamer.schemaprovider.registry.targetUrlSuffix

Later the MultiTableDeltaStreamer uses the source Kafka Topic name also for setting the name of the target schema:

 
hudi/hudi-utilities/src/main/java/org/apache/hudi/utilities/deltastreamer/HoodieMultiTableDeltaStreamer.java

Line 167 in 9fe28e5

typedProperties.setProperty(Constants.TARGET_SCHEMA_REGISTRY_URL_PROP, schemaRegistryBaseUrl + typedProperties.getString(Constants.KAFKA_TOPIC_PROP) + targetSchemaRegistrySuffix);

 

We think, that schema names should be more configurable, like the origin DeltaStreamer would handle it. Actually the names of the schemas you want to use for reading or writing the data are very tight coupled to the name of the Kafka topic the data is loaded from.

 

 

 

Issue Links

• links to: GitHub Pull Request #4779