You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/09/25 13:23:00 UTC

[jira] [Updated] (HUDI-279) Regression in Schema Evolution due to PR-755

     [ https://issues.apache.org/jira/browse/HUDI-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HUDI-279:
--------------------------------
    Labels: pull-request-available  (was: )

> Regression in Schema Evolution due to PR-755
> --------------------------------------------
>
>                 Key: HUDI-279
>                 URL: https://issues.apache.org/jira/browse/HUDI-279
>             Project: Apache Hudi (incubating)
>          Issue Type: Bug
>          Components: Common Core
>            Reporter: BALAJI VARADARAJAN
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.5.0
>
>
> Reported by Alex:
> [https://github.com/apache/incubator-hudi/blob/master/hudi-client/src/main/java/org/apache/hudi/table/HoodieCopyOnWriteTable.java#L200]
> this sets an Avro Schema on the config
>  
> but I see that AvroReadSupport.init is getting a different config instance, with avro schema set to null and falls back to what is in parquet. Which breaks during the old/new data merge. I’m pretty sure it worked before as we had successful schema evolutions. Any idea why it might be happening? 
>  
> Caused by changes in :
> [https://github.com/apache/incubator-hudi/pull/755]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)