aboutsummaryrefslogtreecommitdiff
path: root/NOTICE
diff options
context:
space:
mode:
authorVenkata Ramana Gollamudi <ramana.gollamudi@huawei.com>2014-10-31 11:30:28 -0700
committerMichael Armbrust <michael@databricks.com>2014-10-31 11:30:28 -0700
commitfa712b309c0e59943aae289dab629b34a13fe20e (patch)
tree5f96444a74af45854723031f64af456e72681ab4 /NOTICE
parent7c41d135709c148d4fa3a1b06b5905715c970519 (diff)
downloadspark-fa712b309c0e59943aae289dab629b34a13fe20e.tar.gz
spark-fa712b309c0e59943aae289dab629b34a13fe20e.tar.bz2
spark-fa712b309c0e59943aae289dab629b34a13fe20e.zip
[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 <ramana.gollamudihuawei.com> Author: Venkata Ramana Gollamudi <ramana.gollamudi@huawei.com> Closes #3019 from gvramana/spark_4077 and squashes the following commits: 32d818f [Venkata Ramana Gollamudi] fixed check style fa01e71 [Venkata Ramana Gollamudi] cloned timestamp object as org.apache.hadoop.hive.serde2.io.TimestampWritable.set will reset current time object
Diffstat (limited to 'NOTICE')
0 files changed, 0 insertions, 0 deletions