Re: schema compatibility check and change column type

Hi Ji,  Moving this discussion to https://github.com/apache/hudi/issues/2063 which you have opened. I have added a possible workaround in the comments. Please try it out and respond in the issue.  Thanks,Balaji.V On Monday, September 7, 2020, 10:11:13 AM PDT, Jl Liu (cadl) wrote:

Re: may i added as a contributor

Hi kai, Welcome and done! Looking forward to your contributions! Best, Vino 于2020年9月7日周一 下午9:16写道： > Hi, may i added as a contributor, and my ASF Jira username is: likai.yu > > Thanks > >

Re: schema compatibility check and change column type

Thanks~ I got another question about schema evolution. I don’t found document on homepage and wiki. If I change type from INT to LONG, will Audi overwrite total parquet files of the partition? I disable schema compatibility check and write LONG type data to existed INT type hudi table

Re: schema compatibility check and change column type

Actually, I guess it is a bug in hudi. reader and writer schema arguments are called wrongly. (reader is sent for writer and writer is sent for reader). Will file a bug. Then, as you expect, INT should be evolvable to LONG, where as vice versa is incompatible. On Mon, Sep 7, 2020 at 12:17 PM

Re: schema compatibility check and change column type

Hudi relies on avro's Schema compatability check. Looks like as per avro SchemaCompatability, INT can't be evolved to a LONG, but LONG to INT is allowed. Check line no 339 here .

Re: schema compatibility check and change column type

Yes, the schema change looks fine. That would mean its an issue with the schema compatibility checker. The are explicit checks for such cases so can't say where the issue lies. I am out on a vacation this week. I will look into this as soon as I am back. Thanks Prashant On Sun, Sep 6, 2020,

may i added as a contributor

Hi, may i added as a contributor, and my ASF Jira username is: likai.yu Thanks