[GitHub] [iceberg] rdblue commented on issue #2235: Flink schema validation always has checkNullability and checkOrdering set true. Any particular reason ?

[GitBox <gi...@apache.org>]

rdblue commented on issue #2235:
URL: https://github.com/apache/iceberg/issues/2235#issuecomment-878585949


   I disagree that there isn't a reason other than they aren't exposed. Originally, these weren't even options because the validation checks that the write is correct. Disabling the nullability check was added for cases where users wanted runtime failures because it was too hard to fix the schema that was being written. Disabling the order check was added because the Spark 2.4 planner wouldn't reorder columns automatically and users wanted to guarantee that the columns were correct without reordering.
   
   In both cases, users wanted to disable checks because they had more information than Iceberg did. For example, that a table contained no null values even though a field was optional.
   
   If someone wants to expose these, we should carefully consider the use case around it because not exposing these as options is the sensible default.


-- 
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-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org