You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2019/05/23 03:36:51 UTC
[GitHub] [spark] dongjoon-hyun edited a comment on issue #24682:
[SPARK-27762][SQL] [FOLLOWUP] Add behavior change for Avro writer in
migration guide
dongjoon-hyun edited a comment on issue #24682: [SPARK-27762][SQL] [FOLLOWUP] Add behavior change for Avro writer in migration guide
URL: https://github.com/apache/spark/pull/24682#issuecomment-495054805
I understand the concern about the difference from our default `.schema` option. I believe this is the main reason why we add `.option("avroSchema", ...)`.
For Avro, `nullable` column type is `"type": ["int", "null"]` and non-nullable column type is `"type": "int"` explicitly.
For ORC/Parquet (DSv1/v2), everything is always nullable by default when reading. So, please don't worry about `.schema` use cases. This is a different use case.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org