You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Yin Huai (JIRA)" <ji...@apache.org> on 2016/05/05 01:48:12 UTC

[jira] [Resolved] (SPARK-14993) Inconsistent behavior of partitioning discovery

     [ https://issues.apache.org/jira/browse/SPARK-14993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yin Huai resolved SPARK-14993.
------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

Issue resolved by pull request 12828
[https://github.com/apache/spark/pull/12828]

> Inconsistent behavior of partitioning discovery
> -----------------------------------------------
>
>                 Key: SPARK-14993
>                 URL: https://issues.apache.org/jira/browse/SPARK-14993
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>            Reporter: Yin Huai
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> When we load a dataset, if we set the path to {{/path/a=1}}, we will not take a as the partitioning column. However, if we set the path to {{/path/a=1/file.parquet}}, we take a as the partitioning column and it shows up in the schema. We should make the behaviors of these two cases consistent by not putting a into the schema for the second case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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