-
Notifications
You must be signed in to change notification settings - Fork 2.5k
[HUDI-3569] Introduce ChainedJsonKafkaSourePostProcessor to support setting multi processors at one time #4969
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Do we really see a need for chained post processor just for jsonKafkaSource. Unless or otherwise required, don't want to add them. if you know of valid use-case, let me know. |
@nsivabalan thanks for your review But, in our companay, we use maxwell to subscribe binlog,so I add a MaxwellJsonKafkaPostprocessor to extract the data we need. sometimes, there might be some data quality problems, for example, some not nullable fileds have null values, we have to fix it through processor, So I think somebody else who use maxwell may need this feature too |
|
@hudi-bot run azure |
1 similar comment
|
@hudi-bot run azure |
…etting multi processors at once
|
hi @nsivabalan can we add this processor ? it is very useful in scenarios with diversified data requirements.
with ChainedJsonKafkaSourcePostProcessor we can make data processing more flexible, it makes up for the lack of expression ability of |
|
sounds good 👍 |
…etting multi processors at once (apache#4969)
…etting multi processors at once (apache#4969)
…etting multi processors at once
Tips
What is the purpose of the pull request
Introduce ChainedJsonKafkaSourePostProcessor to support setting multi processors at once
Verify this pull request
This pull request is already covered by existing tests
org.apache.hudi.utilities.sources.TestJsonKafkaSourcePostProcessor#testChainedJsonKafkaSourcePostProcessor
Committer checklist
Has a corresponding JIRA in PR title & commit
Commit message is descriptive of the change
CI is green
Necessary doc changes done or have another open PR
For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.