[GitHub] [hudi] getniz commented on issue #2101: [SUPPORT]Unable to interpret Child JSON fields value as a separate columns rather it is loaded as one single field value. Any way to interpret that.

2020-09-29 Thread GitBox
getniz commented on issue #2101: URL: https://github.com/apache/hudi/issues/2101#issuecomment-700728117 Closing this issue as I could use KSQL to flatten the incoming Nested JSON and then consume in HUDI instantaneously without staging.

[GitHub] [hudi] getniz commented on issue #2101: [SUPPORT]Unable to interpret Child JSON fields value as a separate columns rather it is loaded as one single field value. Any way to interpret that.

2020-09-29 Thread GitBox
getniz commented on issue #2101: URL: https://github.com/apache/hudi/issues/2101#issuecomment-700727885 Closing this issue as I could use KSQL to flatten the incoming Nested JSON and then consume in HUDI instantaneously without staging.

[GitHub] [hudi] getniz commented on issue #2101: [SUPPORT]Unable to interpret Child JSON fields value as a separate columns rather it is loaded as one single field value. Any way to interpret that.

2020-09-28 Thread GitBox
getniz commented on issue #2101: URL: https://github.com/apache/hudi/issues/2101#issuecomment-699798342 @n3nash Thanks for your inputs, while I'm experimenting this on the other side I saw there is another easy way to achieve this using ksql from Kafka receiving side which flattens the

[GitHub] [hudi] getniz commented on issue #2101: [SUPPORT]Unable to interpret Child JSON fields value as a separate columns rather it is loaded as one single field value. Any way to interpret that.

2020-09-25 Thread GitBox
getniz commented on issue #2101: URL: https://github.com/apache/hudi/issues/2101#issuecomment-698761326 @n3nash thanks for the response with details, 1 & 3 option I may not be able to consider as I need to build this layer as immediate target tables for further consumption in Reporting

[GitHub] [hudi] getniz commented on issue #2101: [SUPPORT]Unable to interpret Child JSON fields value as a separate columns rather it is loaded as one single field value. Any way to interpret that.

2020-09-25 Thread GitBox
getniz commented on issue #2101: URL: https://github.com/apache/hudi/issues/2101#issuecomment-698761326 @n3nash thanks for the response with details, 1 & 3 option I may not be able to consider as I need to build this layer as immediate target tables for further consumption in Reporting