diff options
| author | Holden Karau <holden@us.ibm.com> | 2016-08-01 13:57:05 -0700 |
|---|---|---|
| committer | Sean Owen <sowen@cloudera.com> | 2016-08-01 13:57:05 -0700 |
| commit | ab1e761f9691b41385e2ed2202c5a671c63c963d (patch) | |
| tree | 11fa3ff20df539cd5cefbad4dc8442a2ae0ee96c /streaming/src | |
| parent | 338a98d65c8efe0c41f39a8dddeab7040dcda125 (diff) | |
| download | spark-ab1e761f9691b41385e2ed2202c5a671c63c963d.tar.gz spark-ab1e761f9691b41385e2ed2202c5a671c63c963d.tar.bz2 spark-ab1e761f9691b41385e2ed2202c5a671c63c963d.zip | |
[SPARK-16774][SQL] Fix use of deprecated timestamp constructor & improve timezone handling
## What changes were proposed in this pull request?
Removes the deprecated timestamp constructor and incidentally fixes the use which was using system timezone rather than the one specified when working near DST.
This change also causes the roundtrip tests to fail since it now actually uses all the timezones near DST boundaries where it didn't before.
Note: this is only a partial the solution, longer term we should follow up with https://issues.apache.org/jira/browse/SPARK-16788 to avoid this problem & simplify our timezone handling code.
## How was this patch tested?
New tests for two timezones added so even if user timezone happens to coincided with one, the other tests should still fail. Important note: this (temporarily) disables the round trip tests until we can fix the issue more thoroughly.
Author: Holden Karau <holden@us.ibm.com>
Closes #14398 from holdenk/SPARK-16774-fix-use-of-deprecated-timestamp-constructor.
Diffstat (limited to 'streaming/src')
0 files changed, 0 insertions, 0 deletions