Mailing-List: contact reviews-help@spark.apache.org; run by ezmlm
Precedence: bulk
From: viirya <git@git.apache.org>
To: reviews@spark.apache.org
Reply-To: reviews@spark.apache.org
References: <git-pr-14124-spark@git.apache.org>
In-Reply-To: <git-pr-14124-spark@git.apache.org>
Subject: [GitHub] spark issue #14124: [SPARK-16472][SQL] Inconsistent
 nullability in schema af...
Content-Type: text/plain
Message-Id: <20160711025445.10CA0E09C5@git1-us-west.apache.org>
Date: Mon, 11 Jul 2016 02:54:45 +0000 (UTC)

Github user viirya commented on the issue:

    https://github.com/apache/spark/pull/14124
  
    @HyukjinKwon Your patch solves this inconsistency by forcing schema as nullable at all. However,  looks like the parquet case is for compatibility, is this the same for json?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

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