[ 
https://issues.apache.org/jira/browse/FLINK-13603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903432#comment-16903432
 ] 

Yu Du commented on FLINK-13603:
-------------------------------

hi, [~walterddr]

Thanks for reply .

yes,  I did a local flink-core build and change hashCode() do fix my issue  . I 
think those two issues are pretty similar as FlinkTypeFactory caching the 
TypeInfo and compare the hashcode() to check the if the TypeInfo in the cache.  
 if this change doesn't have side affect  to other Flink components will be 
happy to see next release fix .  

 

Will this change also be applied to Flink 1.6x and 1.7x ? 

 

> Flink Table ApI not working with nested Json schema starting From 1.6.x
> -----------------------------------------------------------------------
>
>                 Key: FLINK-13603
>                 URL: https://issues.apache.org/jira/browse/FLINK-13603
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / API
>    Affects Versions: 1.6.4, 1.7.2, 1.8.1
>            Reporter: Yu Du
>            Priority: Major
>              Labels: bug
>         Attachments: FlinkTableBugCode, jsonSchema.json, jsonSchema2.json, 
> schema_mapping_error_screenshot .png
>
>
> starting from Flink 1.6.2 , some schema not working when have nested object .
> issue like :  Caused by: 
> org.apache.calcite.sql.validate.SqlValidatorException: Column 
> 'data.interaction.action_type' not found in table 
> Even we can see that column from Table Schema .
> And the same schema and query working on 1.5.2 , but not working for 1.6.x , 
> 1.7.x and 1.8.x
>  
> I tried to dive into the bug, and found the root cause is calcite library 
> doesn't mapping the column name with the correct Row type . 
> I checked Flink 1.6 using the same version of Calcite as Flink 1.5 .  Not 
> sure if Calcite is the root cause of this issue .
> Attached with the code sample and two issue json schemas . both examples give 
> column not found exception .
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to