Open vladimirivkovic opened 9 months ago
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io
The same behavior was noticed while using version 0.13.0.
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io
The same behavior was noticed while using version 0.13.1.
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io
The same behavior was noticed while using version 0.13.3.
Describe the bug A named type is used to specify the type for multiple fields in a record.
Sample AVRO schema:
After running Kafka ingestion with Schema Registry enabled, the following schema is shown in DataHub:
To Reproduce Steps to reproduce the behavior:
pyramid
with the AVRO schema specified abovepyramid
topic and open itExpected behavior It is expected that fields
b
andd
have the same structure as the fielda
- three sub-fields.Desktop (please complete the following information):
Additional context The same issue is noticed for both UI ingestion and custom ingestion using Python SDK and the
schema_util.avro_schema_to_mce_fields
method.For this case, it seems that commenting out the
else
statement here solves the problem.