jacobmarble commented on PR #9008: URL: https://github.com/apache/iceberg/pull/9008#issuecomment-2248517382
> > > Given that this type is for v3, wouldn't a v2 writer just blindly write this new type if it's being used anywhere and thus break forward compability? > > > > > > @nastra I don't think I understand your question, would you mind sharing an example? > > It seems to me that any writer that doesn't recognize a particular type (in this case `timestamp_ns` or `timestamptz_ns`) should fail when it reads the schema in the table metadata. How does the writer "blindly" write to an unimplemented type? > > @jacobmarble currently nothing is preventing this new type to be written with a V2 writer, meaning that one could use this new type in a schema and write it with a V2 writer. Now an older Iceberg client tries to read this using a V2 reader and will fail. @nastra I've opened a new issue. I tried to keep it simple; is it too simple? https://github.com/apache/iceberg/issues/10775 -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
