You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2019/02/01 02:07:00 UTC

[jira] [Commented] (SPARK-26808) Pruned schema should not change nullability

    [ https://issues.apache.org/jira/browse/SPARK-26808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757880#comment-16757880 ] 

Apache Spark commented on SPARK-26808:
--------------------------------------

User 'viirya' has created a pull request for this issue:
https://github.com/apache/spark/pull/23719

> Pruned schema should not change nullability
> -------------------------------------------
>
>                 Key: SPARK-26808
>                 URL: https://issues.apache.org/jira/browse/SPARK-26808
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 3.0.0
>            Reporter: Liang-Chi Hsieh
>            Priority: Minor
>
> We prune unnecessary nested fields from requested schema when reading Parquet. Now seems we don't keep original nullability in pruned schema. We should keep original nullability.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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