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

Robert Hou commented on DRILL-7225:
-----------------------------------

I have not been able to reproduce the original problem.

I created three files in one directory.  File 1 and file 2 have the same column 
names, but for one of the columns, the data type is different for each file.  
Also, file 1 and file 3 have one column that has different names.  I could not 
get an error with both the new code and old code (before the commit).  Either 
way, the new code is working.

> Merging of columnTypeInfo for file with different schema throws 
> NullPointerException during refresh metadata
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: DRILL-7225
>                 URL: https://issues.apache.org/jira/browse/DRILL-7225
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Metadata
>    Affects Versions: 1.16.0
>            Reporter: Venkata Jyothsna Donapati
>            Assignee: Venkata Jyothsna Donapati
>            Priority: Major
>              Labels: ready-to-commit
>             Fix For: 1.17.0
>
>
> Merging of columnTypeInfo from two files with different schemas throws 
> nullpointerexception. For example if a directory Orders has two files:
>  * orders.parquet (with columns order_id, order_name, order_date)
>  * orders_with_address.parquet (with columns order_id, order_name, address)
> When refresh table metadata is triggered, metadata such as total_null_count 
> for columns in both the files is aggregated and updated in the 
> ColumnTypeInfo. Initially ColumnTypeInfo is initialized with the first file's 
> ColumnTypeInfo (i.e., order_id, order_name, order_date). While aggregating, 
> the existing ColumnTypeInfo is looked up for columns in the second file and 
> since some of them don't exist in the ColumnTypeInfo, a npe is thrown. This 
> can be fixed by initializing ColumnTypeInfo for columns that are not yet 
> present.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to