GitHub user gvramana opened a pull request:
https://github.com/apache/spark/pull/3019
[SPARK-4077][SQL] Spark SQL return wrong values for valid string timestamp
values
In org.apache.hadoop.hive.serde2.io.TimestampWritable.set , if the next
entry is null then current time stamp object is being reset.
However because of this hiveinspectors:unwrap cannot use the same timestamp
object without creating a copy.
Author: Venkata Ramana G <[email protected]>
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gvramana/spark spark_4077
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/3019.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 #3019
----
commit fa01e71e5ba99b0906564b50f7b49fd8aa9ef0f0
Author: Venkata Ramana Gollamudi <[email protected]>
Date: 2014-10-30T18:06:30Z
cloned timestamp object as
org.apache.hadoop.hive.serde2.io.TimestampWritable.set will reset current time
object
commit 32d818f3e7df84996eb8c719ca21a8d4755de238
Author: Venkata Ramana Gollamudi <[email protected]>
Date: 2014-10-30T18:08:42Z
fixed check style
----
---
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]
