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

Rong Rong commented on FLINK-13603:
-----------------------------------

Hi [[email protected]]. I wouldn't think they are necessarily the same. 
Does changing the {{hashCode()}} function resolve your issue? 

I just did a local change and run through the test on {{flink-core}} and it 
didn't affect any test committed with FLINK-9444. so I am assuming it is not 
necessary to change the haseCode function in that PR. This would be a much 
quicker fix (and I think easier to get this in 1.9 release) 

> 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