GitHub user yhuai opened a pull request:
https://github.com/apache/spark/pull/12654
[SPARK-14885] [SQL] When creating a CatalogColumn, we should use the
catalogString of a DataType object.
## What changes were proposed in this pull request?
Right now, the data type field of a CatalogColumn is using the string
representation. When we create this string from a DataType object, there are
places where we use simpleString instead of catalogString. Although
catalogString is the same as simpleString right now, it is still good to use
catalogString. So, we will not silently introduce issues when we change the
semantic of simpleString or the implementation of catalogString.
## How was this patch tested?
Existing tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yhuai/spark useCatalogString
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/12654.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #12654
----
commit bc332555b4399ef65832328c0625749690f099a1
Author: Yin Huai <[email protected]>
Date: 2016-04-24T19:57:11Z
[SPARK-14885] [SQL] When creating a CatalogColumn, we should use the
catalogString of a DataType object.
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
