deepakpanda93 commented on issue #10533: URL: https://github.com/apache/hudi/issues/10533#issuecomment-4851676312
@imonteroq — the reason it looked unfixed on 1.1.0: the relevant fix, [#17776](https://github.com/apache/hudi/pull/17776) ("Ignore duplicate fields when merging schema in IncrementalRelation"), shipped in 1.2.0, not 1.1.0. It addresses exactly this — when the Hudi meta-field skeleton schema is merged with a data schema that already contains those fields, you'd get COLUMN_ALREADY_EXISTS; the merge now ignores the duplicate fields. (HUDI-9597 [#13731], in 1.1.0, also reduced unnecessary schema evolution under reconcile.) Could you retest ad1happy2go's [repro](https://gist.github.com/ad1happy2go/db5813b8bd8d5f7142c2f9b0b2f29922) on a 1.2.0 release? [#17776](https://github.com/apache/hudi/pull/17776) is scoped to the incremental-read relation, so if your read path is incremental it should be resolved. If you still hit COLUMN_ALREADY_EXISTS on 1.2.0 (or on a snapshot read), please share the exact read used and we'll dig in. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
