-
Notifications
You must be signed in to change notification settings - Fork 0
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
[SUPPORT] How to store schema in schema registry for capturing nested arrays and JSONs with column names for Hudi table onboarding from Mongo data source? #253
Comments
Hello! 👋 Please wait while I generate the follow up questions; this usually takes about 30 seconds |
Based on the provided documentation snippets, in order to store the schema in a schema registry to capture all complex nested arrays and JSONs with column names for a Hudi table onboarding when the source is a Mongo data source with static schema nature data, you can follow these steps:
By following these steps and configurations, you can effectively store the schema in a schema registry to handle complex nested data structures in Hudi tables when onboarding data from a Mongo source. Sources:
|
Not satisfied with the answer. |
Ticket created successfully. Here is the link to the GitHub issue: #253 |
Tips before filing an issue
Have you gone through our FAQs?
Join the mailing list to engage in conversations and get faster support at dev-subscribe@hudi.apache.org.
If you have triaged this as a bug, then file an issue directly.
Describe the problem you faced
Can someone suggest how to store the schema in schema registry to capture all complex nested arrays and JSONs with column names for Hudi table onboarding when the source is a Mongo data source (e.g., when opting for a static schema nature data)?
To Reproduce
Steps to reproduce the behavior:
1.
2.
3.
4.
Expected behavior
A clear and concise description of what you expected to happen.
Environment Description
Hudi version :
Spark version :
Hive version :
Hadoop version :
Storage (HDFS/S3/GCS..) :
Running on Docker? (yes/no) :
Additional context
Add any other context about the problem here.
Stacktrace
Add the stacktrace of the error.
The text was updated successfully, but these errors were encountered: