[jira] [Commented] (HIVE-21614) Derby does not support CLOB comparisons
[
https://issues.apache.org/jira/browse/HIVE-21614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17368778#comment-17368778
]
Piotr Findeisen commented on HIVE-21614:
[~hankfanchiu] , in Trino i worked around this limitation by issuing filter
with `LIKE` instead of `=` predicate.
The code is here
https://github.com/trinodb/trino/blob/d95eafe397fe4b476b2b1a73baeb7643349d4bdb/plugin/trino-hive/src/main/java/io/trino/plugin/hive/metastore/thrift/ThriftHiveMetastore.java#L973-L981
> Derby does not support CLOB comparisons
> ---
>
> Key: HIVE-21614
> URL: https://issues.apache.org/jira/browse/HIVE-21614
> Project: Hive
> Issue Type: Bug
> Components: Metastore
>Affects Versions: 2.3.4, 3.0.0
>Reporter: Vlad Rozov
>Priority: Major
>
> HiveMetaStoreClient.listTableNamesByFilter() with non empty filter causes
> exception with Derby DB:
> {noformat}
> Caused by: ERROR 42818: Comparisons between 'CLOB (UCS_BASIC)' and 'CLOB
> (UCS_BASIC)' are not supported. Types must be comparable. String types must
> also have matching collation. If collation does not match, a possible
> solution is to cast operands to force them to the default collation (e.g.
> SELECT tablename FROM sys.systables WHERE CAST(tablename AS VARCHAR(128)) =
> 'T1')
> at org.apache.derby.iapi.error.StandardException.newException(Unknown
> Source)
> at org.apache.derby.iapi.error.StandardException.newException(Unknown
> Source)
> at
> org.apache.derby.impl.sql.compile.BinaryComparisonOperatorNode.bindComparisonOperator(Unknown
> Source)
> at
> org.apache.derby.impl.sql.compile.BinaryComparisonOperatorNode.bindExpression(Unknown
> Source)
> at
> org.apache.derby.impl.sql.compile.BinaryOperatorNode.bindExpression(Unknown
> Source)
> at
> org.apache.derby.impl.sql.compile.BinaryLogicalOperatorNode.bindExpression(Unknown
> Source)
> at org.apache.derby.impl.sql.compile.AndNode.bindExpression(Unknown
> Source)
> at org.apache.derby.impl.sql.compile.SelectNode.bindExpressions(Unknown
> Source)
> at
> org.apache.derby.impl.sql.compile.DMLStatementNode.bindExpressions(Unknown
> Source)
> at org.apache.derby.impl.sql.compile.DMLStatementNode.bind(Unknown
> Source)
> at org.apache.derby.impl.sql.compile.CursorNode.bindStatement(Unknown
> Source)
> at org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown Source)
> at org.apache.derby.impl.sql.GenericStatement.prepare(Unknown Source)
> at
> org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(Unknown
> Source)
> ... 42 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HIVE-11266) count(*) wrong result based on table statistics for external tables
[
https://issues.apache.org/jira/browse/HIVE-11266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17245953#comment-17245953
]
Piotr Findeisen commented on HIVE-11266:
{quote}This is not just external tables - any tables where users are directly
modifying the underlying data can be impacted by this.
{quote}
{quote}Yes, I agree with you, external table is just my personal use
case.{quote}
[~tmgstev] [~simobatt] was there a follow-up issue to this?
>From the attached patch (same as
>[https://github.com/apache/hive/commit/a2dff9e13acc62ecc0388b3b2e221f26c9184dbb)]
> i see this was fixed for external tables only.
> count(*) wrong result based on table statistics for external tables
> ---
>
> Key: HIVE-11266
> URL: https://issues.apache.org/jira/browse/HIVE-11266
> Project: Hive
> Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Simone Battaglia
>Assignee: Jesus Camacho Rodriguez
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: HIVE-11266.01.patch, HIVE-11266.patch
>
>
> Hive returns wrong count result on an external table with table statistics if
> I change table data files.
> This is the scenario in details:
> 1) create external table my_table (...) location 'my_location';
> 2) analyze table my_table compute statistics;
> 3) change/add/delete one or more files in 'my_location' directory;
> 4) select count(\*) from my_table;
> In this case the count query doesn't generate a MR job and returns the result
> based on table statistics. This result is wrong because is based on
> statistics stored in the Hive metastore and doesn't take into account
> modifications introduced on data files.
> Obviously setting "hive.compute.query.using.stats" to FALSE this problem
> doesn't occur but the default value of this property is TRUE.
> I thinks that also this post on stackoverflow, that shows another type of bug
> in case of multiple insert, is related to the one that I reported:
> http://stackoverflow.com/questions/24080276/wrong-result-for-count-in-hive-table
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HIVE-24082) Expose information whether AcidUtils.ParsedDelta contains statementId
[
https://issues.apache.org/jira/browse/HIVE-24082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17191652#comment-17191652
]
Piotr Findeisen commented on HIVE-24082:
We call these methods today:
{code:java}
AcidUtils.isTransactionalTable
AcidUtils.isFullAcidTable
AcidUtils.getAcidState
AcidUtils.OrcAcidVersion.getAcidVersionFromMetaFile
AcidUtils.deleteDeltaSubdir
AcidUtils.createBucketFile{code}
I expect further usage as we advance Presto's support for ORC ACID /
Transactional tables.
I am aware AcidUtils is not public interface, so I am aware a breakage may
occur when we upgrade.
We chose to do this since the ACID handling logic has quite a few nuances that
are easy to overlook. Copying the logic over to Presto codebase would probably
be safer from code compilation perspective, but could cause trouble as ORC ACID
evolves.
{quote}we were planning to change things around that.
{quote}
sure! I am always curious so please CC me whenever you feel like I could be
interested.
> Expose information whether AcidUtils.ParsedDelta contains statementId
> -
>
> Key: HIVE-24082
> URL: https://issues.apache.org/jira/browse/HIVE-24082
> Project: Hive
> Issue Type: Improvement
>Reporter: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> In [Presto|https://prestosql.io] we support reading ORC ACID tables by
> leveraging AcidUtils rather than duplicate the file name parsing logic in our
> code.
> To do this fully correctly, we need information whether
> {{org.apache.hadoop.hive.ql.io.AcidUtils.ParsedDelta}} contains
> {{statementId}} information or not.
> Currently, a getter of that property does not allow us to access this
> information.
> [https://github.com/apache/hive/blob/468907eab36f78df3e14a24005153c9a23d62555/ql/src/java/org/apache/hadoop/hive/ql/io/AcidUtils.java#L804-L806]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HIVE-8648) numRows cannot be set by user
[
https://issues.apache.org/jira/browse/HIVE-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976372#comment-16976372
]
Piotr Findeisen commented on HIVE-8648:
---
Related to (solved by?) HIVE-12730.
> numRows cannot be set by user
> -
>
> Key: HIVE-8648
> URL: https://issues.apache.org/jira/browse/HIVE-8648
> Project: Hive
> Issue Type: Bug
>Affects Versions: 0.13.0, 0.14.0, 0.13.1
>Reporter: Brock Noland
>Assignee: Brock Noland
>Priority: Major
> Attachments: HIVE-8648.1.patch, HIVE-8648.patch
>
>
> Since HIVE-3777 users who want to set the number of rows for a table, must do
> as follows:
> {noformat}
> alter table ... set tblproperties ('numRows' = '12345',
> 'STATS_GENERATED_VIA_STATS_TASK' = 'true');
> {noformat}
> Which is strange because (1) users can know the numbers of rows and (2) the
> stat is not generated by a stats task.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HIVE-21436) "Malformed ORC file. Invalid postscript length 17" when only one data-file in external table directory
[
https://issues.apache.org/jira/browse/HIVE-21436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen resolved HIVE-21436.
Resolution: Fixed
Fixed by changing ORC writer in Presto (in 323 release) to avoid running into
this situation.
> "Malformed ORC file. Invalid postscript length 17" when only one data-file in
> external table directory
> --
>
> Key: HIVE-21436
> URL: https://issues.apache.org/jira/browse/HIVE-21436
> Project: Hive
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: archon gum
>Assignee: Piotr Findeisen
>Priority: Blocker
> Attachments: 1.jpg, 2.jpg, hive-insert-into.orc,
> org-apache-orc-java-code.orc, presto-insert-into.orc
>
>
> h1. env
> * Presto 305
> * Hive 3.1.0
>
> h1. step
>
> {code:java}
> -- create external table using hiveserver2
> CREATE EXTERNAL TABLE `dw.dim_date2`(
> `d` date
> )
> STORED AS ORC
> LOCATION
> 'hdfs://datacenter1:8020/user/hive/warehouse/dw.db/dim_date2'
> ;
> -- upload the 'presto-insert-into.orc' file from attachments
> -- OR
> -- insert one row using presto
> insert into dim_date2 values (current_date);
> {code}
>
>
> when using `hiveserver2` to query, it works only at the first query and error
> after then
> !1.jpg!
>
> If I insert another row, it works
> {code:java}
> -- upload the 'presto-insert-into.orc' file from attachments
> -- OR
> -- insert one row using presto
> insert into dim_date2 values (current_date);
> {code}
> !2.jpg!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (HIVE-21436) "Malformed ORC file. Invalid postscript length 17" when only one data-file in external table directory
[
https://issues.apache.org/jira/browse/HIVE-21436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen reassigned HIVE-21436:
--
Assignee: Piotr Findeisen
> "Malformed ORC file. Invalid postscript length 17" when only one data-file in
> external table directory
> --
>
> Key: HIVE-21436
> URL: https://issues.apache.org/jira/browse/HIVE-21436
> Project: Hive
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: archon gum
>Assignee: Piotr Findeisen
>Priority: Blocker
> Attachments: 1.jpg, 2.jpg, hive-insert-into.orc,
> org-apache-orc-java-code.orc, presto-insert-into.orc
>
>
> h1. env
> * Presto 305
> * Hive 3.1.0
>
> h1. step
>
> {code:java}
> -- create external table using hiveserver2
> CREATE EXTERNAL TABLE `dw.dim_date2`(
> `d` date
> )
> STORED AS ORC
> LOCATION
> 'hdfs://datacenter1:8020/user/hive/warehouse/dw.db/dim_date2'
> ;
> -- upload the 'presto-insert-into.orc' file from attachments
> -- OR
> -- insert one row using presto
> insert into dim_date2 values (current_date);
> {code}
>
>
> when using `hiveserver2` to query, it works only at the first query and error
> after then
> !1.jpg!
>
> If I insert another row, it works
> {code:java}
> -- upload the 'presto-insert-into.orc' file from attachments
> -- OR
> -- insert one row using presto
> insert into dim_date2 values (current_date);
> {code}
> !2.jpg!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (HIVE-21436) "Malformed ORC file. Invalid postscript length 17" when only one data-file in external table directory
[
https://issues.apache.org/jira/browse/HIVE-21436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16944357#comment-16944357
]
Piotr Findeisen edited comment on HIVE-21436 at 10/4/19 10:14 AM:
--
First-time select works:
{code:java}
jdbc:hive2://localhost:1/default> SELECT * FROM t;
...
+--+
| 42 |
+--+ {code}
But all subsequent fail:
{code:java}
jdbc:hive2://localhost:1/default> SELECT * FROM t;
going to print operations logs
printed operations logs
Getting log thread is interrupted, since query is done!
INFO : Compiling
command(queryId=hive_20191004151730_e7c48562-51c8-4d39-9622-62231a499768):
SELECT * FROM t
INFO : Semantic Analysis Completed (retrial = false)
INFO : Returning Hive schema: Schema(fieldSchemas:[FieldSchema(name:t.a,
type:bigint, comment:null)], properties:null)
INFO : Completed compiling
command(queryId=hive_20191004151730_e7c48562-51c8-4d39-9622-62231a499768); Time
taken: 0.24 seconds
INFO : Executing
command(queryId=hive_20191004151730_e7c48562-51c8-4d39-9622-62231a499768):
SELECT * FROM t
INFO : Completed executing
command(queryId=hive_20191004151730_e7c48562-51c8-4d39-9622-62231a499768); Time
taken: 0.0 seconds
INFO : OK
Error: java.io.IOException: java.lang.RuntimeException: ORC split generation
failed with exception: Malformed ORC file. Invalid postscript length 17
(state=,code=0)
org.apache.hive.service.cli.HiveSQLException: java.io.IOException:
java.lang.RuntimeException: ORC split generation failed with exception:
Malformed ORC file. Invalid postscript length 17
at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:300)
at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:286)
at
org.apache.hive.jdbc.HiveQueryResultSet.next(HiveQueryResultSet.java:379)
at org.apache.hive.beeline.BufferedRows.(BufferedRows.java:56)
at
org.apache.hive.beeline.IncrementalRowsWithNormalization.(IncrementalRowsWithNormalization.java:50)
at org.apache.hive.beeline.BeeLine.print(BeeLine.java:2305)
at org.apache.hive.beeline.Commands.executeInternal(Commands.java:1026)
at org.apache.hive.beeline.Commands.execute(Commands.java:1201)
at org.apache.hive.beeline.Commands.sql(Commands.java:1130)
at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1480)
at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1342)
at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1126)
at
org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:546)
at org.apache.hive.beeline.BeeLine.main(BeeLine.java:528)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.util.RunJar.run(RunJar.java:318)
at org.apache.hadoop.util.RunJar.main(RunJar.java:232)
Caused by: org.apache.hive.service.cli.HiveSQLException: java.io.IOException:
java.lang.RuntimeException: ORC split generation failed with exception:
Malformed ORC file. Invalid postscript length 17
at
org.apache.hive.service.cli.operation.SQLOperation.getNextRowSet(SQLOperation.java:478)
at
org.apache.hive.service.cli.operation.OperationManager.getOperationNextRowSet(OperationManager.java:328)
at
org.apache.hive.service.cli.session.HiveSessionImpl.fetchResults(HiveSessionImpl.java:952)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:78)
at
org.apache.hive.service.cli.session.HiveSessionProxy.access$000(HiveSessionProxy.java:36)
at
org.apache.hive.service.cli.session.HiveSessionProxy$1.run(HiveSessionProxy.java:63)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1730)
at
org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:59)
at com.sun.proxy.$Proxy50.fetchResults(Unknown Source)
at
org.apache.hive.service.cli.CLIService.fetchResults(CLIService.java:564)
at
org.apache.hive.service.cli.thrift.ThriftCLIService.FetchResults(ThriftCLIService.java:792)
at
org.apache.hive.service.rpc.thrift.TCLIService$Processor$FetchResults.getResult(TCLIService.java:1837)
[jira] [Commented] (HIVE-21436) "Malformed ORC file. Invalid postscript length 17" when only one data-file in external table directory
[
https://issues.apache.org/jira/browse/HIVE-21436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16944379#comment-16944379
]
Piotr Findeisen commented on HIVE-21436:
The {{org.apache.hadoop.hive.ql.io.orc.LocalCache#cache}} gets populated from
{{OrcTail}} objects in
{{org.apache.hadoop.hive.ql.io.orc.LocalCache#put(org.apache.hadoop.fs.Path,
org.apache.orc.impl.OrcTail)}}.
I don't see yet why the cache entries are re-validated checking whether they
are valid ORC footer/tail, but this is the place where the exception is thrown.
> "Malformed ORC file. Invalid postscript length 17" when only one data-file in
> external table directory
> --
>
> Key: HIVE-21436
> URL: https://issues.apache.org/jira/browse/HIVE-21436
> Project: Hive
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: archon gum
>Priority: Blocker
> Attachments: 1.jpg, 2.jpg, hive-insert-into.orc,
> org-apache-orc-java-code.orc, presto-insert-into.orc
>
>
> h1. env
> * Presto 305
> * Hive 3.1.0
>
> h1. step
>
> {code:java}
> -- create external table using hiveserver2
> CREATE EXTERNAL TABLE `dw.dim_date2`(
> `d` date
> )
> STORED AS ORC
> LOCATION
> 'hdfs://datacenter1:8020/user/hive/warehouse/dw.db/dim_date2'
> ;
> -- upload the 'presto-insert-into.orc' file from attachments
> -- OR
> -- insert one row using presto
> insert into dim_date2 values (current_date);
> {code}
>
>
> when using `hiveserver2` to query, it works only at the first query and error
> after then
> !1.jpg!
>
> If I insert another row, it works
> {code:java}
> -- upload the 'presto-insert-into.orc' file from attachments
> -- OR
> -- insert one row using presto
> insert into dim_date2 values (current_date);
> {code}
> !2.jpg!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (HIVE-21436) "Malformed ORC file. Invalid postscript length 17" when only one data-file in external table directory
[
https://issues.apache.org/jira/browse/HIVE-21436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16944357#comment-16944357
]
Piotr Findeisen edited comment on HIVE-21436 at 10/4/19 9:42 AM:
-
First-time select works:
{code:java}
jdbc:hive2://localhost:1/default> SELECT * FROM t;
...
+--+
| 42 |
+--+ {code}
But all subsequent fail:
{code:java}
jdbc:hive2://localhost:1/default> SELECT * FROM t;
going to print operations logs
printed operations logs
Getting log thread is interrupted, since query is done!
INFO : Compiling
command(queryId=hive_20191004151730_e7c48562-51c8-4d39-9622-62231a499768):
SELECT * FROM t
INFO : Semantic Analysis Completed (retrial = false)
INFO : Returning Hive schema: Schema(fieldSchemas:[FieldSchema(name:t.a,
type:bigint, comment:null)], properties:null)
INFO : Completed compiling
command(queryId=hive_20191004151730_e7c48562-51c8-4d39-9622-62231a499768); Time
taken: 0.24 seconds
INFO : Executing
command(queryId=hive_20191004151730_e7c48562-51c8-4d39-9622-62231a499768):
SELECT * FROM t
INFO : Completed executing
command(queryId=hive_20191004151730_e7c48562-51c8-4d39-9622-62231a499768); Time
taken: 0.0 seconds
INFO : OK
Error: java.io.IOException: java.lang.RuntimeException: ORC split generation
failed with exception: Malformed ORC file. Invalid postscript length 17
(state=,code=0)
org.apache.hive.service.cli.HiveSQLException: java.io.IOException:
java.lang.RuntimeException: ORC split generation failed with exception:
Malformed ORC file. Invalid postscript length 17
at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:300)
at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:286)
at
org.apache.hive.jdbc.HiveQueryResultSet.next(HiveQueryResultSet.java:379)
at org.apache.hive.beeline.BufferedRows.(BufferedRows.java:56)
at
org.apache.hive.beeline.IncrementalRowsWithNormalization.(IncrementalRowsWithNormalization.java:50)
at org.apache.hive.beeline.BeeLine.print(BeeLine.java:2305)
at org.apache.hive.beeline.Commands.executeInternal(Commands.java:1026)
at org.apache.hive.beeline.Commands.execute(Commands.java:1201)
at org.apache.hive.beeline.Commands.sql(Commands.java:1130)
at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1480)
at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1342)
at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1126)
at
org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:546)
at org.apache.hive.beeline.BeeLine.main(BeeLine.java:528)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.util.RunJar.run(RunJar.java:318)
at org.apache.hadoop.util.RunJar.main(RunJar.java:232)
Caused by: org.apache.hive.service.cli.HiveSQLException: java.io.IOException:
java.lang.RuntimeException: ORC split generation failed with exception:
Malformed ORC file. Invalid postscript length 17
at
org.apache.hive.service.cli.operation.SQLOperation.getNextRowSet(SQLOperation.java:478)
at
org.apache.hive.service.cli.operation.OperationManager.getOperationNextRowSet(OperationManager.java:328)
at
org.apache.hive.service.cli.session.HiveSessionImpl.fetchResults(HiveSessionImpl.java:952)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:78)
at
org.apache.hive.service.cli.session.HiveSessionProxy.access$000(HiveSessionProxy.java:36)
at
org.apache.hive.service.cli.session.HiveSessionProxy$1.run(HiveSessionProxy.java:63)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1730)
at
org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:59)
at com.sun.proxy.$Proxy50.fetchResults(Unknown Source)
at
org.apache.hive.service.cli.CLIService.fetchResults(CLIService.java:564)
at
org.apache.hive.service.cli.thrift.ThriftCLIService.FetchResults(ThriftCLIService.java:792)
at
org.apache.hive.service.rpc.thrift.TCLIService$Processor$FetchResults.getResult(TCLIService.java:1837)
[jira] [Commented] (HIVE-21436) "Malformed ORC file. Invalid postscript length 17" when only one data-file in external table directory
[
https://issues.apache.org/jira/browse/HIVE-21436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16944357#comment-16944357
]
Piotr Findeisen commented on HIVE-21436:
First-time select works:
{code:java}
jdbc:hive2://localhost:1/default> SELECT * FROM t;
...
+--+
| 42 |
+--+ {code}
But all subsequent fail:
{code:java}
jdbc:hive2://localhost:1/default> SELECT * FROM t;
going to print operations logs
printed operations logs
Getting log thread is interrupted, since query is done!
INFO : Compiling
command(queryId=hive_20191004151730_e7c48562-51c8-4d39-9622-62231a499768):
SELECT * FROM t
INFO : Semantic Analysis Completed (retrial = false)
INFO : Returning Hive schema: Schema(fieldSchemas:[FieldSchema(name:t.a,
type:bigint, comment:null)], properties:null)
INFO : Completed compiling
command(queryId=hive_20191004151730_e7c48562-51c8-4d39-9622-62231a499768); Time
taken: 0.24 seconds
INFO : Executing
command(queryId=hive_20191004151730_e7c48562-51c8-4d39-9622-62231a499768):
SELECT * FROM t
INFO : Completed executing
command(queryId=hive_20191004151730_e7c48562-51c8-4d39-9622-62231a499768); Time
taken: 0.0 seconds
INFO : OK
Error: java.io.IOException: java.lang.RuntimeException: ORC split generation
failed with exception: Malformed ORC file. Invalid postscript length 17
(state=,code=0)
org.apache.hive.service.cli.HiveSQLException: java.io.IOException:
java.lang.RuntimeException: ORC split generation failed with exception:
Malformed ORC file. Invalid postscript length 17
at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:300)
at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:286)
at
org.apache.hive.jdbc.HiveQueryResultSet.next(HiveQueryResultSet.java:379)
at org.apache.hive.beeline.BufferedRows.(BufferedRows.java:56)
at
org.apache.hive.beeline.IncrementalRowsWithNormalization.(IncrementalRowsWithNormalization.java:50)
at org.apache.hive.beeline.BeeLine.print(BeeLine.java:2305)
at org.apache.hive.beeline.Commands.executeInternal(Commands.java:1026)
at org.apache.hive.beeline.Commands.execute(Commands.java:1201)
at org.apache.hive.beeline.Commands.sql(Commands.java:1130)
at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1480)
at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1342)
at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1126)
at
org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:546)
at org.apache.hive.beeline.BeeLine.main(BeeLine.java:528)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.util.RunJar.run(RunJar.java:318)
at org.apache.hadoop.util.RunJar.main(RunJar.java:232)
Caused by: org.apache.hive.service.cli.HiveSQLException: java.io.IOException:
java.lang.RuntimeException: ORC split generation failed with exception:
Malformed ORC file. Invalid postscript length 17
at
org.apache.hive.service.cli.operation.SQLOperation.getNextRowSet(SQLOperation.java:478)
at
org.apache.hive.service.cli.operation.OperationManager.getOperationNextRowSet(OperationManager.java:328)
at
org.apache.hive.service.cli.session.HiveSessionImpl.fetchResults(HiveSessionImpl.java:952)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:78)
at
org.apache.hive.service.cli.session.HiveSessionProxy.access$000(HiveSessionProxy.java:36)
at
org.apache.hive.service.cli.session.HiveSessionProxy$1.run(HiveSessionProxy.java:63)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1730)
at
org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:59)
at com.sun.proxy.$Proxy50.fetchResults(Unknown Source)
at
org.apache.hive.service.cli.CLIService.fetchResults(CLIService.java:564)
at
org.apache.hive.service.cli.thrift.ThriftCLIService.FetchResults(ThriftCLIService.java:792)
at
org.apache.hive.service.rpc.thrift.TCLIService$Processor$FetchResults.getResult(TCLIService.java:1837)
at
[jira] [Updated] (HIVE-21436) "Malformed ORC file. Invalid postscript length 17" when only one data-file in external table directory
[
https://issues.apache.org/jira/browse/HIVE-21436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen updated HIVE-21436:
---
Summary: "Malformed ORC file. Invalid postscript length 17" when only one
data-file in external table directory (was: "Malformed ORC file" when only one
data-file in external table directory)
> "Malformed ORC file. Invalid postscript length 17" when only one data-file in
> external table directory
> --
>
> Key: HIVE-21436
> URL: https://issues.apache.org/jira/browse/HIVE-21436
> Project: Hive
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: archon gum
>Priority: Blocker
> Attachments: 1.jpg, 2.jpg, hive-insert-into.orc,
> org-apache-orc-java-code.orc, presto-insert-into.orc
>
>
> h1. env
> * Presto 305
> * Hive 3.1.0
>
> h1. step
>
> {code:java}
> -- create external table using hiveserver2
> CREATE EXTERNAL TABLE `dw.dim_date2`(
> `d` date
> )
> STORED AS ORC
> LOCATION
> 'hdfs://datacenter1:8020/user/hive/warehouse/dw.db/dim_date2'
> ;
> -- upload the 'presto-insert-into.orc' file from attachments
> -- OR
> -- insert one row using presto
> insert into dim_date2 values (current_date);
> {code}
>
>
> when using `hiveserver2` to query, it works only at the first query and error
> after then
> !1.jpg!
>
> If I insert another row, it works
> {code:java}
> -- upload the 'presto-insert-into.orc' file from attachments
> -- OR
> -- insert one row using presto
> insert into dim_date2 values (current_date);
> {code}
> !2.jpg!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (HIVE-21002) TIMESTAMP - Backwards incompatible change: Hive 3.1 reads back Avro and Parquet timestamps written by Hive 2.x incorrectly
[
https://issues.apache.org/jira/browse/HIVE-21002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919389#comment-16919389
]
Piotr Findeisen edited comment on HIVE-21002 at 9/3/19 10:59 AM:
-
[~klcopp] [~zi] this issue explicitly talks about Avro and Parquet, whereas the
same problem applies also to "RCBinary" ({{ROW FORMAT SERDE
'org.apache.hadoop.hive.serde2.columnar.LazyBinaryColumnarSerDe' STORED AS
RCFILE;}}).
-Has this been addressed too, or should I create a new issue?- created
HIVE-22167
was (Author: findepi):
[~klcopp] [~zi] this issue explicitly talks about Avro and Parquet, whereas
the same problem applies also to "RCBinary" ({{ROW FORMAT SERDE
'org.apache.hadoop.hive.serde2.columnar.LazyBinaryColumnarSerDe' STORED AS
RCFILE;}}).
Has this been addressed too, or should I create a new issue?
> TIMESTAMP - Backwards incompatible change: Hive 3.1 reads back Avro and
> Parquet timestamps written by Hive 2.x incorrectly
> --
>
> Key: HIVE-21002
> URL: https://issues.apache.org/jira/browse/HIVE-21002
> Project: Hive
> Issue Type: Bug
>Affects Versions: 3.1.0, 3.1.1
>Reporter: Zoltan Ivanfi
>Priority: Major
>
> Hive 3.1 reads back Avro and Parquet timestamps written by Hive 2.x
> incorrectly. As an example session to demonstrate this problem, create a
> dataset using Hive version 2.x in America/Los_Angeles:
> {code:sql}
> hive> create table ts_‹format› (ts timestamp) stored as ‹format›;
> hive> insert into ts_‹format› values (*‘2018-01-01 00:00:00.000’*);
> {code}
> Querying this table by issuing
> {code:sql}
> hive> select * from ts_‹format›;
> {code}
> from different time zones using different versions of Hive and different
> storage formats gives the following results:
> |‹format›|Writer time zone (in Hive 2.x)|Reader time zone|Result in Hive 2.x
> reader|Result in Hive 3.1 reader|
> |Avro and Parquet|America/Los_Angeles|America/Los_Angeles|2018-01-01
> *00*:00:00.0|2018-01-01 *08*:00:00.0|
> |Avro and Parquet|America/Los_Angeles|Europe/Paris|2018-01-01
> *09*:00:00.0|2018-01-01 *08*:00:00.0|
> |Textfile and ORC|America/Los_Angeles|America/Los_Angeles|2018-01-01
> 00:00:00.0|2018-01-01 00:00:00.0|
> |Textfile and ORC|America/Los_Angeles|Europe/Paris|2018-01-01
> 00:00:00.0|2018-01-01 00:00:00.0|
> *Hive 3.1 clearly gives different results than Hive 2.x for timestamps stored
> in Avro and Parquet formats.* Apache ORC behaviour has not changed because it
> was modified to adjust timestamps to retain backwards compatibility. Textfile
> behaviour has not changed, because its processing involves parsing and
> formatting instead of proper serializing and deserializing, so they
> inherently had LocalDateTime semantics even in Hive 2.x.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HIVE-21002) TIMESTAMP - Backwards incompatible change: Hive 3.1 reads back Avro and Parquet timestamps written by Hive 2.x incorrectly
[
https://issues.apache.org/jira/browse/HIVE-21002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919389#comment-16919389
]
Piotr Findeisen commented on HIVE-21002:
[~klcopp] [~zi] this issue explicitly talks about Avro and Parquet, whereas
the same problem applies also to "RCBinary" ({{ROW FORMAT SERDE
'org.apache.hadoop.hive.serde2.columnar.LazyBinaryColumnarSerDe' STORED AS
RCFILE;}}).
Has this been addressed too, or should I create a new issue?
> TIMESTAMP - Backwards incompatible change: Hive 3.1 reads back Avro and
> Parquet timestamps written by Hive 2.x incorrectly
> --
>
> Key: HIVE-21002
> URL: https://issues.apache.org/jira/browse/HIVE-21002
> Project: Hive
> Issue Type: Bug
>Affects Versions: 3.1.0, 3.1.1
>Reporter: Zoltan Ivanfi
>Priority: Major
>
> Hive 3.1 reads back Avro and Parquet timestamps written by Hive 2.x
> incorrectly. As an example session to demonstrate this problem, create a
> dataset using Hive version 2.x in America/Los_Angeles:
> {code:sql}
> hive> create table ts_‹format› (ts timestamp) stored as ‹format›;
> hive> insert into ts_‹format› values (*‘2018-01-01 00:00:00.000’*);
> {code}
> Querying this table by issuing
> {code:sql}
> hive> select * from ts_‹format›;
> {code}
> from different time zones using different versions of Hive and different
> storage formats gives the following results:
> |‹format›|Writer time zone (in Hive 2.x)|Reader time zone|Result in Hive 2.x
> reader|Result in Hive 3.1 reader|
> |Avro and Parquet|America/Los_Angeles|America/Los_Angeles|2018-01-01
> *00*:00:00.0|2018-01-01 *08*:00:00.0|
> |Avro and Parquet|America/Los_Angeles|Europe/Paris|2018-01-01
> *09*:00:00.0|2018-01-01 *08*:00:00.0|
> |Textfile and ORC|America/Los_Angeles|America/Los_Angeles|2018-01-01
> 00:00:00.0|2018-01-01 00:00:00.0|
> |Textfile and ORC|America/Los_Angeles|Europe/Paris|2018-01-01
> 00:00:00.0|2018-01-01 00:00:00.0|
> *Hive 3.1 clearly gives different results than Hive 2.x for timestamps stored
> in Avro and Parquet formats.* Apache ORC behaviour has not changed because it
> was modified to adjust timestamps to retain backwards compatibility. Textfile
> behaviour has not changed, because its processing involves parsing and
> formatting instead of proper serializing and deserializing, so they
> inherently had LocalDateTime semantics even in Hive 2.x.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Assigned] (HIVE-1010) Implement INFORMATION_SCHEMA in Hive
[ https://issues.apache.org/jira/browse/HIVE-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Findeisen reassigned HIVE-1010: - Assignee: Piotr Findeisen (was: Gunther Hagleitner) > Implement INFORMATION_SCHEMA in Hive > > > Key: HIVE-1010 > URL: https://issues.apache.org/jira/browse/HIVE-1010 > Project: Hive > Issue Type: New Feature > Components: Metastore, Query Processor, Server Infrastructure >Reporter: Jeff Hammerbacher >Assignee: Piotr Findeisen >Priority: Major > Labels: TODOC3.0 > Fix For: 3.0.0 > > Attachments: HIVE-1010.10.patch, HIVE-1010.11.patch, > HIVE-1010.12.patch, HIVE-1010.13.patch, HIVE-1010.14.patch, > HIVE-1010.15.patch, HIVE-1010.16.patch, HIVE-1010.7.patch, HIVE-1010.8.patch, > HIVE-1010.9.patch > > > INFORMATION_SCHEMA is part of the SQL92 standard and would be useful to > implement using our metastore. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HIVE-22130) Incorrect data inserted when CTAS or INS from TEXTFILE to ORC with nested collection types
[
https://issues.apache.org/jira/browse/HIVE-22130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16912142#comment-16912142
]
Piotr Findeisen commented on HIVE-22130:
Similarly there are problems when doing CTAS or INS from TEXTFILE to
SEQUENCEFILE or textual RCFILE.
> Incorrect data inserted when CTAS or INS from TEXTFILE to ORC with nested
> collection types
> --
>
> Key: HIVE-22130
> URL: https://issues.apache.org/jira/browse/HIVE-22130
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Affects Versions: 3.1.0
>Reporter: Piotr Findeisen
>Priority: Major
>
> {code}
> CREATE TABLE ttf (t_complex MAP s_double:DOUBLE>>>) STORED AS TEXTFILE;
> CREATE TABLE tor (t_complex MAP s_double:DOUBLE>>>) STORED AS ORC;
> INSERT INTO ttf VALUES (map(1, array(named_struct('s_string', 'test abc',
> 's_double', 1e-1), named_struct('s_string' , 'test xyz', 's_double', 2e-1;
> INSERT INTO tor VALUES (map(1, array(named_struct('s_string', 'test abc',
> 's_double', 1e-1), named_struct('s_string' , 'test xyz', 's_double', 2e-1;
> SELECT * FROM ttf;
> SELECT * FROM tor;
> {code}
> outputs
> {code}
> ++
> | ttf.t_complex|
> ++
> | {1:[{"s_string":"test abc","s_double":0.1},{"s_string":"test
> xyz","s_double":0.2}]} |
> ++
> ++
> | tor.t_complex|
> ++
> | {1:[{"s_string":"test abc","s_double":0.1},{"s_string":"test
> xyz","s_double":0.2}]} |
> ++
> {code}
> But now when I do {{INSERT INTO .. SELECT}}:
> {code}
> INSERT INTO tor SELECT * FROM ttf;
> SELECT * FROM tor;
> {code}
> the data gets inserted incorrectly.
> {code}
> ++
> | tor.t_complex|
> ++
> | {1:[{"s_string":"test abc","s_double":0.1},{"s_string":"test
> xyz","s_double":0.2}]} |
> | {1:[{"s_string":"test abc\u00050.1","s_double":null}]} |
> ++
> {code}
> Same happens when I {{CREATE TABLE .. STORED AS ORC AS SELECT ttf}}.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (HIVE-22130) Incorrect data inserted when CTAS or INS from TEXTFILE to ORC with nested collection types
[
https://issues.apache.org/jira/browse/HIVE-22130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen updated HIVE-22130:
---
Summary: Incorrect data inserted when CTAS or INS from TEXTFILE to ORC with
nested collection types (was: Incorrect data inserted when CTAS or INS from
TEXTFILE to ORC)
> Incorrect data inserted when CTAS or INS from TEXTFILE to ORC with nested
> collection types
> --
>
> Key: HIVE-22130
> URL: https://issues.apache.org/jira/browse/HIVE-22130
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Affects Versions: 3.1.0
>Reporter: Piotr Findeisen
>Priority: Major
>
> {code}
> CREATE TABLE ttf (t_complex MAP s_double:DOUBLE>>>) STORED AS TEXTFILE;
> CREATE TABLE tor (t_complex MAP s_double:DOUBLE>>>) STORED AS ORC;
> INSERT INTO ttf VALUES (map(1, array(named_struct('s_string', 'test abc',
> 's_double', 1e-1), named_struct('s_string' , 'test xyz', 's_double', 2e-1;
> INSERT INTO tor VALUES (map(1, array(named_struct('s_string', 'test abc',
> 's_double', 1e-1), named_struct('s_string' , 'test xyz', 's_double', 2e-1;
> SELECT * FROM ttf;
> SELECT * FROM tor;
> {code}
> outputs
> {code}
> ++
> | ttf.t_complex|
> ++
> | {1:[{"s_string":"test abc","s_double":0.1},{"s_string":"test
> xyz","s_double":0.2}]} |
> ++
> ++
> | tor.t_complex|
> ++
> | {1:[{"s_string":"test abc","s_double":0.1},{"s_string":"test
> xyz","s_double":0.2}]} |
> ++
> {code}
> But now when I do {{INSERT INTO .. SELECT}}:
> {code}
> INSERT INTO tor SELECT * FROM ttf;
> SELECT * FROM tor;
> {code}
> the data gets inserted incorrectly.
> {code}
> ++
> | tor.t_complex|
> ++
> | {1:[{"s_string":"test abc","s_double":0.1},{"s_string":"test
> xyz","s_double":0.2}]} |
> | {1:[{"s_string":"test abc\u00050.1","s_double":null}]} |
> ++
> {code}
> Same happens when I {{CREATE TABLE .. STORED AS ORC AS SELECT ttf}}.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (HIVE-21376) Incompatible change in Hive bucket computation
[
https://issues.apache.org/jira/browse/HIVE-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16901291#comment-16901291
]
Piotr Findeisen edited comment on HIVE-21376 at 8/6/19 7:52 PM:
bq. If bucketed data with those types has been written in 3.0 using v2, a user
should recreate those bucketed tables using a more recent Hive version.
To me that means there is a disincentive to deploying Hive 3 in production
until this issue is fixed.
It's fixed in 3.1.2, but the latest available from HDP is 3.1.0.
[~jcamachorodriguez] do you have a timeline when 3.1.2 will be available in HDP?
was (Author: findepi):
bq. If bucketed data with those types has been written in 3.0 using v2, a user
should recreate those bucketed tables using a more recent Hive version.
To me that means Hive 3 should not be deployed on production until this issue
is fixed.
It's fixed in 3.1.2, but the latest available from HDP is 3.1.0.
[~jcamachorodriguez] do you have a timeline when 3.1.2 will be available in HDP?
> Incompatible change in Hive bucket computation
> --
>
> Key: HIVE-21376
> URL: https://issues.apache.org/jira/browse/HIVE-21376
> Project: Hive
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: David Phillips
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
> Fix For: 4.0.0, 3.2.0, 3.1.2
>
> Attachments: HIVE-21376.01.patch, HIVE-21376.patch
>
>
> HIVE-20007 seems to have inadvertently changed the bucket hash code
> computation via {{ObjectInspectorUtils.getBucketHashCodeOld()}} for the
> {{DATE}} and {{TIMESTAMP}} data type2.
> {{DATE}} was previously computed using {{DateWritable}}, which uses
> {{daysSinceEpoch}} as the hash code. It is now computed using
> {{DateWritableV2}}, which uses the hash code of {{java.time.LocalDate}}
> (which is not days since epoch).
> {{TIMESTAMP}} was previous computed using {{TimestampWritable}} and now uses
> {{TimestampWritableV2}}. They ostensibly use the same hash code computation,
> but there are two important differences:
> # {{TimestampWritable}} rounds the number of milliseconds into the seconds
> portion of the computation, but {{TimestampWritableV2}} does not.
> # {{TimestampWritable}} gets the epoch time from {{java.sql.Timestamp}},
> which returns it relative to the JVM time zone, not UTC.
> {{TimestampWritableV2}} uses a {{LocalDateTime}} relative to UTC.
> I was unable to get Hive 3.1 running in order to verify if this actually
> causes data to be read or written incorrectly (there may be code above this
> library method which makes things work correctly). However, if my
> understanding is correct, this means Hive 3.1 is both forwards and backwards
> incompatible with bucketed tables using either of these data types. It also
> indicates that Hive needs tests to verify that the hash code does not change
> between releases.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (HIVE-21376) Incompatible change in Hive bucket computation
[
https://issues.apache.org/jira/browse/HIVE-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16901291#comment-16901291
]
Piotr Findeisen commented on HIVE-21376:
bq. If bucketed data with those types has been written in 3.0 using v2, a user
should recreate those bucketed tables using a more recent Hive version.
To me that means Hive 3 should not be deployed on production until this issue
is fixed.
It's fixed in 3.1.2, but the latest available from HDP is 3.1.0.
[~jcamachorodriguez] do you have a timeline when 3.1.2 will be available in HDP?
> Incompatible change in Hive bucket computation
> --
>
> Key: HIVE-21376
> URL: https://issues.apache.org/jira/browse/HIVE-21376
> Project: Hive
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: David Phillips
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
> Fix For: 4.0.0, 3.2.0, 3.1.2
>
> Attachments: HIVE-21376.01.patch, HIVE-21376.patch
>
>
> HIVE-20007 seems to have inadvertently changed the bucket hash code
> computation via {{ObjectInspectorUtils.getBucketHashCodeOld()}} for the
> {{DATE}} and {{TIMESTAMP}} data type2.
> {{DATE}} was previously computed using {{DateWritable}}, which uses
> {{daysSinceEpoch}} as the hash code. It is now computed using
> {{DateWritableV2}}, which uses the hash code of {{java.time.LocalDate}}
> (which is not days since epoch).
> {{TIMESTAMP}} was previous computed using {{TimestampWritable}} and now uses
> {{TimestampWritableV2}}. They ostensibly use the same hash code computation,
> but there are two important differences:
> # {{TimestampWritable}} rounds the number of milliseconds into the seconds
> portion of the computation, but {{TimestampWritableV2}} does not.
> # {{TimestampWritable}} gets the epoch time from {{java.sql.Timestamp}},
> which returns it relative to the JVM time zone, not UTC.
> {{TimestampWritableV2}} uses a {{LocalDateTime}} relative to UTC.
> I was unable to get Hive 3.1 running in order to verify if this actually
> causes data to be read or written incorrectly (there may be code above this
> library method which makes things work correctly). However, if my
> understanding is correct, this means Hive 3.1 is both forwards and backwards
> incompatible with bucketed tables using either of these data types. It also
> indicates that Hive needs tests to verify that the hash code does not change
> between releases.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (HIVE-21349) TIMESTAMP WITHOUT TIME ZONE
[
https://issues.apache.org/jira/browse/HIVE-21349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898722#comment-16898722
]
Piotr Findeisen commented on HIVE-21349:
Do i understand correctly that {{TIMESTAMP WITHOUT TIME ZONE}} is going to be
an alias for {{TIMESTAMP}}?
I.e. it's not going to be distinguishable whether I declared a column as
"{{TIMESTAMP}}" or "{{TIMESTAMP WITHOUT TIME ZONE}}"?
> TIMESTAMP WITHOUT TIME ZONE
> ---
>
> Key: HIVE-21349
> URL: https://issues.apache.org/jira/browse/HIVE-21349
> Project: Hive
> Issue Type: Task
>Reporter: Zoltan Ivanfi
>Priority: Major
>
> As specified in the [design doc for TIMESTAMP
> types|https://cwiki.apache.org/confluence/display/Hive/Different+TIMESTAMP+types],
> the TIMESTAMP WITHOUT TIME ZONE type shall behave like the
> [LocalDateTime|https://docs.oracle.com/javase/8/docs/api/java/time/LocalDateTime.html]
> class of Java, i.e., each value is a recording of what can be seen on a
> calendar and a clock hanging on the wall, for example "1969-07-20 16:17:39".
> It can be decomposed into year, month, day, hour, minute and seconds fields,
> but with no time zone information available, it does not correspond to any
> specific point in time.
> This behaviour is consistent with the SQL standard (revisions 2003 and
> higher).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Comment Edited] (HIVE-22073) SQL Injection in TxnHandler#enqueueLockWithRetry
[
https://issues.apache.org/jira/browse/HIVE-22073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898351#comment-16898351
]
Piotr Findeisen edited comment on HIVE-22073 at 8/1/19 8:52 PM:
In {{master}} this seems fixed already by HIVE-20607.
It might be sufficient to backport that change to 3.1 branch
(For context: I'm using Hive 3.1 because this is the version available in
latest HDP (HDP 3.1)).
was (Author: findepi):
In {{master}} this seems fixed already by HIVE-20607.
It might be sufficient to backport that change to 3.1 branch
> SQL Injection in TxnHandler#enqueueLockWithRetry
>
>
> Key: HIVE-22073
> URL: https://issues.apache.org/jira/browse/HIVE-22073
> Project: Hive
> Issue Type: Bug
>Affects Versions: 3.1.1
>Reporter: Piotr Findeisen
>Priority: Critical
>
> The {{org.apache.hadoop.hive.metastore.txn.TxnHandler#enqueueLockWithRetry}}
> method gets called for Thrift {{lock}} API call with input passed from the
> user.
> Within that method there is SQL injection possible:
> [https://github.com/apache/hive/blob/774a8ef7a6e92c8a43cad2fa66bd944e666f75f0/standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/txn/TxnHandler.java#L1987-L1991]
> for example, when partition name contains an apostrophe.
>
> Impact:
> * vulnerability: privilege escalation possible
> * availability: user cannot query ACID table where string/varchar partition
> key contains an apostrophe
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (HIVE-22073) SQL Injection in TxnHandler#enqueueLockWithRetry
[
https://issues.apache.org/jira/browse/HIVE-22073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898351#comment-16898351
]
Piotr Findeisen commented on HIVE-22073:
In {{master}} this seems fixed already by HIVE-20607.
It might be sufficient to backport that change to 3.1 branch
> SQL Injection in TxnHandler#enqueueLockWithRetry
>
>
> Key: HIVE-22073
> URL: https://issues.apache.org/jira/browse/HIVE-22073
> Project: Hive
> Issue Type: Bug
>Affects Versions: 3.1.1
>Reporter: Piotr Findeisen
>Priority: Critical
>
> The {{org.apache.hadoop.hive.metastore.txn.TxnHandler#enqueueLockWithRetry}}
> method gets called for Thrift {{lock}} API call with input passed from the
> user.
> Within that method there is SQL injection possible:
> [https://github.com/apache/hive/blob/774a8ef7a6e92c8a43cad2fa66bd944e666f75f0/standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/txn/TxnHandler.java#L1987-L1991]
> for example, when partition name contains an apostrophe.
>
> Impact:
> * vulnerability: privilege escalation possible
> * availability: user cannot query ACID table where string/varchar partition
> key contains an apostrophe
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (HIVE-21859) Backport HIVE-17466 (get_partition_values) to branch-2.3
[
https://issues.apache.org/jira/browse/HIVE-21859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870366#comment-16870366
]
Piotr Findeisen commented on HIVE-21859:
Thanks [~alangates] for merging this!
For context – we determined this Thrift API is necessary to improve performance
of Presto for certain query types
([https://github.com/prestosql/presto/issues/611]).
> Backport HIVE-17466 (get_partition_values) to branch-2.3
>
>
> Key: HIVE-21859
> URL: https://issues.apache.org/jira/browse/HIVE-21859
> Project: Hive
> Issue Type: Improvement
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Fix For: 2.3.6
>
> Attachments: HIVE-21859-branch-2.3.patch
>
>
> Please backport HIVE-17466 that adds {{get_partition_values}} to
> {{branch-2.3}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21859) Backport HIVE-17466 (get_partition_values) to branch-2.3
[
https://issues.apache.org/jira/browse/HIVE-21859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863732#comment-16863732
]
Piotr Findeisen commented on HIVE-21859:
[~ashutoshc] can you help me move this forward?
> Backport HIVE-17466 (get_partition_values) to branch-2.3
>
>
> Key: HIVE-21859
> URL: https://issues.apache.org/jira/browse/HIVE-21859
> Project: Hive
> Issue Type: Improvement
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Fix For: 2.3.6
>
> Attachments: HIVE-21859-branch-2.3.patch
>
>
> Please backport HIVE-17466 that adds {{get_partition_values}} to
> {{branch-2.3}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21859) Backport HIVE-17466 (get_partition_values) to branch-2.3
[
https://issues.apache.org/jira/browse/HIVE-21859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863099#comment-16863099
]
Piotr Findeisen commented on HIVE-21859:
[~alangates] can you possibly help with understand the test failures?
> Backport HIVE-17466 (get_partition_values) to branch-2.3
>
>
> Key: HIVE-21859
> URL: https://issues.apache.org/jira/browse/HIVE-21859
> Project: Hive
> Issue Type: Improvement
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Fix For: 2.3.6
>
> Attachments: HIVE-21859-branch-2.3.patch
>
>
> Please backport HIVE-17466 that adds {{get_partition_values}} to
> {{branch-2.3}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21859) Backport HIVE-17466 (get_partition_values) to branch-2.3
[
https://issues.apache.org/jira/browse/HIVE-21859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861953#comment-16861953
]
Piotr Findeisen commented on HIVE-21859:
[~alangates] it's named appropriately to the best of my knowledge, but the QA
job did not run.
What am I doing wrong?
> Backport HIVE-17466 (get_partition_values) to branch-2.3
>
>
> Key: HIVE-21859
> URL: https://issues.apache.org/jira/browse/HIVE-21859
> Project: Hive
> Issue Type: Improvement
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Fix For: 2.3.6
>
> Attachments: HIVE-21859-branch-2.3.patch
>
>
> Please backport HIVE-17466 that adds {{get_partition_values}} to
> {{branch-2.3}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21859) Backport HIVE-17466 (get_partition_values) to branch-2.3
[
https://issues.apache.org/jira/browse/HIVE-21859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen updated HIVE-21859:
---
Assignee: Piotr Findeisen
Fix Version/s: 2.3.6
Status: Patch Available (was: Open)
> Backport HIVE-17466 (get_partition_values) to branch-2.3
>
>
> Key: HIVE-21859
> URL: https://issues.apache.org/jira/browse/HIVE-21859
> Project: Hive
> Issue Type: Improvement
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Fix For: 2.3.6
>
> Attachments: HIVE-21859-branch-2.3.patch
>
>
> Please backport HIVE-17466 that adds {{get_partition_values}} to
> {{branch-2.3}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21859) Backport HIVE-17466 (get_partition_values) to branch-2.3
[
https://issues.apache.org/jira/browse/HIVE-21859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861120#comment-16861120
]
Piotr Findeisen commented on HIVE-21859:
[~ashutoshc] how should I name the patch to let the [~hiveqa] do its job?
> Backport HIVE-17466 (get_partition_values) to branch-2.3
>
>
> Key: HIVE-21859
> URL: https://issues.apache.org/jira/browse/HIVE-21859
> Project: Hive
> Issue Type: Improvement
>Reporter: Piotr Findeisen
>Priority: Major
> Attachments: HIVE-21859-branch-2.3.patch
>
>
> Please backport HIVE-17466 that adds {{get_partition_values}} to
> {{branch-2.3}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21859) Backport HIVE-17466 (get_partition_values) to branch-2.3
[
https://issues.apache.org/jira/browse/HIVE-21859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861028#comment-16861028
]
Piotr Findeisen commented on HIVE-21859:
I've cherry picked the commit from {{master}} into {{branch-2.3}} and
regenerated all the thrift bindings appropriately.
> Backport HIVE-17466 (get_partition_values) to branch-2.3
>
>
> Key: HIVE-21859
> URL: https://issues.apache.org/jira/browse/HIVE-21859
> Project: Hive
> Issue Type: Improvement
>Reporter: Piotr Findeisen
>Priority: Major
> Attachments: HIVE-21859-branch-2.3.patch
>
>
> Please backport HIVE-17466 that adds {{get_partition_values}} to
> {{branch-2.3}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21859) Backport HIVE-17466 (get_partition_values) to branch-2.3
[
https://issues.apache.org/jira/browse/HIVE-21859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen updated HIVE-21859:
---
Attachment: HIVE-21859-branch-2.3.patch
> Backport HIVE-17466 (get_partition_values) to branch-2.3
>
>
> Key: HIVE-21859
> URL: https://issues.apache.org/jira/browse/HIVE-21859
> Project: Hive
> Issue Type: Improvement
>Reporter: Piotr Findeisen
>Priority: Major
> Attachments: HIVE-21859-branch-2.3.patch
>
>
> Please backport HIVE-17466 that adds {{get_partition_values}} to
> {{branch-2.3}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21859) Backport HIVE-17466 (get_partition_values) to branch-2.3
[
https://issues.apache.org/jira/browse/HIVE-21859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen updated HIVE-21859:
---
Summary: Backport HIVE-17466 (get_partition_values) to branch-2.3 (was:
Backport HIVE-17466 (get_partition_values ) to branch-2.3)
> Backport HIVE-17466 (get_partition_values) to branch-2.3
>
>
> Key: HIVE-21859
> URL: https://issues.apache.org/jira/browse/HIVE-21859
> Project: Hive
> Issue Type: Improvement
>Reporter: Piotr Findeisen
>Priority: Major
>
> Please backport HIVE-17466 that adds {{get_partition_values}} to
> {{branch-2.3}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21859) Backport HIVE-17466 (get_partition_values ) to branch-2.3
[
https://issues.apache.org/jira/browse/HIVE-21859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen updated HIVE-21859:
---
Summary: Backport HIVE-17466 (get_partition_values ) to branch-2.3 (was:
Backport HIVE-17466 to branch-2.3)
> Backport HIVE-17466 (get_partition_values ) to branch-2.3
> -
>
> Key: HIVE-21859
> URL: https://issues.apache.org/jira/browse/HIVE-21859
> Project: Hive
> Issue Type: Improvement
>Reporter: Piotr Findeisen
>Priority: Major
>
> Please backport HIVE-17466 that adds {{get_partition_values}} to
> {{branch-2.3}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (HIVE-21614) Derby does not support CLOB comparisons
[
https://issues.apache.org/jira/browse/HIVE-21614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849571#comment-16849571
]
Piotr Findeisen edited comment on HIVE-21614 at 5/28/19 10:23 AM:
--
This breaks {{get_table_names_by_filter}} Metastore thrift call when using
{{hive_filter_field_params__}} prefix ({{HIVE_FILTER_FIELD_PARAMS}})
Like in
https://github.com/apache/hive/blob/fcd4721591e0ba7d9ba24821f9528dadb7ec16fd/standalone-metastore/metastore-common/src/main/thrift/hive_metastore.thrift#L2019-L2020
This probably affects Metastore running on Oracle too.
was (Author: findepi):
This breaks {{get_table_names_by_filter}} Metastore thrift call when using
{{hive_filter_field_params__}} prefix ({{HIVE_FILTER_FIELD_PARAMS}})
Like in
https://github.com/apache/hive/blob/fcd4721591e0ba7d9ba24821f9528dadb7ec16fd/standalone-metastore/metastore-common/src/main/thrift/hive_metastore.thrift#L2019-L2020
> Derby does not support CLOB comparisons
> ---
>
> Key: HIVE-21614
> URL: https://issues.apache.org/jira/browse/HIVE-21614
> Project: Hive
> Issue Type: Bug
> Components: Metastore
>Affects Versions: 3.0.0, 2.3.4
>Reporter: Vlad Rozov
>Priority: Major
>
> HiveMetaStoreClient.listTableNamesByFilter() with non empty filter causes
> exception with Derby DB:
> {noformat}
> Caused by: ERROR 42818: Comparisons between 'CLOB (UCS_BASIC)' and 'CLOB
> (UCS_BASIC)' are not supported. Types must be comparable. String types must
> also have matching collation. If collation does not match, a possible
> solution is to cast operands to force them to the default collation (e.g.
> SELECT tablename FROM sys.systables WHERE CAST(tablename AS VARCHAR(128)) =
> 'T1')
> at org.apache.derby.iapi.error.StandardException.newException(Unknown
> Source)
> at org.apache.derby.iapi.error.StandardException.newException(Unknown
> Source)
> at
> org.apache.derby.impl.sql.compile.BinaryComparisonOperatorNode.bindComparisonOperator(Unknown
> Source)
> at
> org.apache.derby.impl.sql.compile.BinaryComparisonOperatorNode.bindExpression(Unknown
> Source)
> at
> org.apache.derby.impl.sql.compile.BinaryOperatorNode.bindExpression(Unknown
> Source)
> at
> org.apache.derby.impl.sql.compile.BinaryLogicalOperatorNode.bindExpression(Unknown
> Source)
> at org.apache.derby.impl.sql.compile.AndNode.bindExpression(Unknown
> Source)
> at org.apache.derby.impl.sql.compile.SelectNode.bindExpressions(Unknown
> Source)
> at
> org.apache.derby.impl.sql.compile.DMLStatementNode.bindExpressions(Unknown
> Source)
> at org.apache.derby.impl.sql.compile.DMLStatementNode.bind(Unknown
> Source)
> at org.apache.derby.impl.sql.compile.CursorNode.bindStatement(Unknown
> Source)
> at org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown Source)
> at org.apache.derby.impl.sql.GenericStatement.prepare(Unknown Source)
> at
> org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(Unknown
> Source)
> ... 42 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21614) Derby does not support CLOB comparisons
[
https://issues.apache.org/jira/browse/HIVE-21614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849571#comment-16849571
]
Piotr Findeisen commented on HIVE-21614:
This breaks {{get_table_names_by_filter}} Metastore thrift call when using
{{hive_filter_field_params__}} prefix ({{HIVE_FILTER_FIELD_PARAMS}})
Like in
https://github.com/apache/hive/blob/fcd4721591e0ba7d9ba24821f9528dadb7ec16fd/standalone-metastore/metastore-common/src/main/thrift/hive_metastore.thrift#L2019-L2020
> Derby does not support CLOB comparisons
> ---
>
> Key: HIVE-21614
> URL: https://issues.apache.org/jira/browse/HIVE-21614
> Project: Hive
> Issue Type: Bug
> Components: Metastore
>Affects Versions: 3.0.0, 2.3.4
>Reporter: Vlad Rozov
>Priority: Major
>
> HiveMetaStoreClient.listTableNamesByFilter() with non empty filter causes
> exception with Derby DB:
> {noformat}
> Caused by: ERROR 42818: Comparisons between 'CLOB (UCS_BASIC)' and 'CLOB
> (UCS_BASIC)' are not supported. Types must be comparable. String types must
> also have matching collation. If collation does not match, a possible
> solution is to cast operands to force them to the default collation (e.g.
> SELECT tablename FROM sys.systables WHERE CAST(tablename AS VARCHAR(128)) =
> 'T1')
> at org.apache.derby.iapi.error.StandardException.newException(Unknown
> Source)
> at org.apache.derby.iapi.error.StandardException.newException(Unknown
> Source)
> at
> org.apache.derby.impl.sql.compile.BinaryComparisonOperatorNode.bindComparisonOperator(Unknown
> Source)
> at
> org.apache.derby.impl.sql.compile.BinaryComparisonOperatorNode.bindExpression(Unknown
> Source)
> at
> org.apache.derby.impl.sql.compile.BinaryOperatorNode.bindExpression(Unknown
> Source)
> at
> org.apache.derby.impl.sql.compile.BinaryLogicalOperatorNode.bindExpression(Unknown
> Source)
> at org.apache.derby.impl.sql.compile.AndNode.bindExpression(Unknown
> Source)
> at org.apache.derby.impl.sql.compile.SelectNode.bindExpressions(Unknown
> Source)
> at
> org.apache.derby.impl.sql.compile.DMLStatementNode.bindExpressions(Unknown
> Source)
> at org.apache.derby.impl.sql.compile.DMLStatementNode.bind(Unknown
> Source)
> at org.apache.derby.impl.sql.compile.CursorNode.bindStatement(Unknown
> Source)
> at org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown Source)
> at org.apache.derby.impl.sql.GenericStatement.prepare(Unknown Source)
> at
> org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(Unknown
> Source)
> ... 42 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-20098) Statistics: NPE when getting Date column partition statistics
[
https://issues.apache.org/jira/browse/HIVE-20098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590767#comment-16590767
]
Piotr Findeisen commented on HIVE-20098:
[~ashutoshc] will this fix be backported to earlier Hive releases?
> Statistics: NPE when getting Date column partition statistics
> -
>
> Key: HIVE-20098
> URL: https://issues.apache.org/jira/browse/HIVE-20098
> Project: Hive
> Issue Type: Bug
> Components: Metastore, Standalone Metastore
>Affects Versions: 1.2.1, 4.0.0
> Environment: Tested on versions `1.2.1` and the latest 4.0.0-SNAPSHOT
>Reporter: Andy Rosa
>Assignee: Andy Rosa
>Priority: Major
> Labels: Branch3Candidate
> Fix For: 4.0.0
>
> Attachments:
> 0001-Fix-NPE-when-getting-statistics-for-date-column.patch, HIVE-20098.1.patch
>
>
> The issue reproduces only for a date column for a partitioned table. It
> reproduces only if the date column has all the values set to null, and if the
> partition is not empty.
> Here is a quick reproducer:
>
>
> {code:java}
> CREATE TABLE dummy_table (
> c_date DATE,
> c_bigint BIGINT
> )
> PARTITIONED BY (ds STRING);
> INSERT OVERWRITE TABLE dummy_table PARTITION (ds='2018-01-01') SELECT
> CAST(null AS DATE), CAST(null AS BIGINT) FROM ;
> ANALYZE TABLE dummy_table COMPUTE STATISTICS FOR COLUMNS;
> DESCRIBE FORMATTED dummy_table.c_bigint PARTITION (ds='2018-01-01');
> DESCRIBE FORMATTED dummy_table.c_date PARTITION (ds='2018-01-01');
> {code}
>
>
> The first `DESCRIBE FORMATTED` statement succeeds, when the second fails with
> an `NPE`
>
> It happens because the null check is missing when converting Object from the
> ObjectStore to the Thrift object. The null check is missing only in the date
> statistics conversion for the partitioned table.
> Missing:
> [https://github.com/apache/hive/blob/master/standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/StatObjectConverter.java#L469]
> Present:
> https://github.com/apache/hive/blob/master/standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/StatObjectConverter.java#L298
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-12192) Hive should carry out timestamp computations in UTC
[
https://issues.apache.org/jira/browse/HIVE-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522801#comment-16522801
]
Piotr Findeisen commented on HIVE-12192:
hi [~jcamachorodriguez],
i guess [~haozhun]'s comment got lost among the comments by [~hiveqa], so let
me bump the question --
https://issues.apache.org/jira/browse/HIVE-12192?focusedCommentId=16520636=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16520636
Does [~haozhun]'s table represent the semantics of TIMESTAMP, TIMESTAMP WITH
LOCAL TIME ZONE? Note, since other products cannot be made dependent on single
Hive version, it's critical to understand semantics differences introduced by
this issue, if any.
Were there any semantics differences in DATE type?
Looking forward for clarification.
> Hive should carry out timestamp computations in UTC
> ---
>
> Key: HIVE-12192
> URL: https://issues.apache.org/jira/browse/HIVE-12192
> Project: Hive
> Issue Type: Sub-task
> Components: Hive
>Reporter: Ryan Blue
>Assignee: Jesus Camacho Rodriguez
>Priority: Blocker
> Labels: timestamp
> Fix For: 3.1.0
>
> Attachments: HIVE-12192.01.patch, HIVE-12192.02.patch,
> HIVE-12192.03.patch, HIVE-12192.04.patch, HIVE-12192.05.patch,
> HIVE-12192.06.patch, HIVE-12192.07.patch, HIVE-12192.08.patch,
> HIVE-12192.09.patch, HIVE-12192.10.patch, HIVE-12192.11.patch,
> HIVE-12192.12.patch, HIVE-12192.13.patch, HIVE-12192.14.patch,
> HIVE-12192.15.patch, HIVE-12192.16.patch, HIVE-12192.17.patch,
> HIVE-12192.18.patch, HIVE-12192.19.patch, HIVE-12192.20.patch,
> HIVE-12192.21.patch, HIVE-12192.22.patch, HIVE-12192.23.patch,
> HIVE-12192.24.patch, HIVE-12192.25.patch, HIVE-12192.patch
>
>
> Hive currently uses the "local" time of a java.sql.Timestamp to represent the
> SQL data type TIMESTAMP WITHOUT TIME ZONE. The purpose is to be able to use
> {{Timestamp#getYear()}} and similar methods to implement SQL functions like
> {{year}}.
> When the SQL session's time zone is a DST zone, such as America/Los_Angeles
> that alternates between PST and PDT, there are times that cannot be
> represented because the effective zone skips them.
> {code}
> hive> select TIMESTAMP '2015-03-08 02:10:00.101';
> 2015-03-08 03:10:00.101
> {code}
> Using UTC instead of the SQL session time zone as the underlying zone for a
> java.sql.Timestamp avoids this bug, while still returning correct values for
> {{getYear}} etc. Using UTC as the convenience representation (timestamp
> without time zone has no real zone) would make timestamp calculations more
> consistent and avoid similar problems in the future.
> Notably, this would break the {{unix_timestamp}} UDF that specifies the
> result is with respect to ["the default timezone and default
> locale"|https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF#LanguageManualUDF-DateFunctions].
> That function would need to be updated to use the
> {{System.getProperty("user.timezone")}} zone.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-12192) Hive should carry out timestamp computations in UTC
[
https://issues.apache.org/jira/browse/HIVE-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426109#comment-16426109
]
Piotr Findeisen commented on HIVE-12192:
Few clarifying questions
bq. The type is not really an instant, even before HIVE-12192. Semantics from
querying perspective are similar to SQL timestamp.
How much similar? Is it really the same as SQL (standard) timestamp, i.e. a
"Record" of year/month/day/hour/minute/second[/fraction] ?
Did this semantics change over time? ([~haozhun] and I work on Presto and we
would like Presto's Hive connector to work appropriately with different
versions of Hive)
bq. it uses java.sql.timestamp class to store the value
What about values that cannot be represented using {{java.sql.Timestamp}}?
(i.e. whenever there's a forward offset change in JVM's zone)
Did you also consider using a different representation, like
{{java.time.LocalDateTime}}? (if this representation is indeed applicable)
bq. How does ORC fix this? \[...]
Do you happen to know it is handled for other file types? Parquet, RC binary,
RC text, textfile?
> Hive should carry out timestamp computations in UTC
> ---
>
> Key: HIVE-12192
> URL: https://issues.apache.org/jira/browse/HIVE-12192
> Project: Hive
> Issue Type: Sub-task
> Components: Hive
>Reporter: Ryan Blue
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
> Labels: timestamp
> Attachments: HIVE-12192.patch
>
>
> Hive currently uses the "local" time of a java.sql.Timestamp to represent the
> SQL data type TIMESTAMP WITHOUT TIME ZONE. The purpose is to be able to use
> {{Timestamp#getYear()}} and similar methods to implement SQL functions like
> {{year}}.
> When the SQL session's time zone is a DST zone, such as America/Los_Angeles
> that alternates between PST and PDT, there are times that cannot be
> represented because the effective zone skips them.
> {code}
> hive> select TIMESTAMP '2015-03-08 02:10:00.101';
> 2015-03-08 03:10:00.101
> {code}
> Using UTC instead of the SQL session time zone as the underlying zone for a
> java.sql.Timestamp avoids this bug, while still returning correct values for
> {{getYear}} etc. Using UTC as the convenience representation (timestamp
> without time zone has no real zone) would make timestamp calculations more
> consistent and avoid similar problems in the future.
> Notably, this would break the {{unix_timestamp}} UDF that specifies the
> result is with respect to ["the default timezone and default
> locale"|https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF#LanguageManualUDF-DateFunctions].
> That function would need to be updated to use the
> {{System.getProperty("user.timezone")}} zone.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-16614) Support "set local time zone" statement
[ https://issues.apache.org/jira/browse/HIVE-16614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425288#comment-16425288 ] Piotr Findeisen commented on HIVE-16614: bq. Finally, I will create a follow-up to fix 'TIMESTAMP' type semantics so they are not dependent on the system timezone anymore. While 'TIMESTAMP' type will be compliant with SQL semantics, I will also take care that we are backwards compatible and old 'TIMESTAMP' typed values continue being accessible in the same way. (More in the issue to come) [~jcamachorodriguez], i tried to find the issue. Did you abandon the idea, or i'm just searching the wrong way? > Support "set local time zone" statement > --- > > Key: HIVE-16614 > URL: https://issues.apache.org/jira/browse/HIVE-16614 > Project: Hive > Issue Type: Improvement >Reporter: Carter Shanklin >Assignee: Jesus Camacho Rodriguez >Priority: Major > Labels: TODOC3.0 > Fix For: 3.0.0 > > Attachments: HIVE-16614.01.patch, HIVE-16614.02.patch, > HIVE-16614.03.patch, HIVE-16614.04.patch, HIVE-16614.05.patch, > HIVE-16614.patch > > > HIVE-14412 introduces a timezone-aware timestamp. > SQL has a concept of default time zone displacements, which are transparently > applied when converting between timezone-unaware types and timezone-aware > types and, in Hive's case, are also used to shift a timezone aware type to a > different time zone, depending on configuration. > SQL also provides that the default time zone displacement be settable at a > session level, so that clients can access a database simultaneously from > different time zones and see time values in their own time zone. > Currently the time zone displacement is fixed and is set based on the system > time zone where the Hive client runs (HiveServer2 or Hive CLI). It will be > more convenient for users if they have the ability to set their time zone of > choice. > SQL defines "set time zone" with 2 ways of specifying the time zone, first > using an interval and second using the special keyword LOCAL. > Examples: > • set time zone '-8:00'; > • set time zone LOCAL; > LOCAL means to set the current default time zone displacement to the > session's original default time zone displacement. > Reference: SQL:2011 section 19.4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412816#comment-16412816
]
Piotr Findeisen edited comment on HIVE-18925 at 3/26/18 4:20 PM:
-
[~lirui] ,
- [~ashutoshc] expressed thought that `TimestampParser` is supposed to parse
timestamps, so the {{"MM:dd:ss"}} pattern may actually be an invalid use case
- anyway, i attached [^HIVE-18925.2.patch] -- this is slightly more intrusive,
but makes tests pass in all zones
-- except, of course, the test case which tries to parse
{{1970-01-01T00:00:00}} -- such a timestamp cannot be represented using
{{java.sql.Timestamp}} when JVM zone didn't observe such local time, thus
{{TimestampParser#parseTimestamp(String)}} cannot succeed
was (Author: findepi):
[~lirui] ,
- [~ashutoshc] expressed thought that `TimestampParser` is supposed to parse
timestamps, so the {{"MM:dd:ss"}} pattern may actually be an invalid use case
- anyway, i attached [^HIVE-18925-2.patch] -- this is slightly more intrusive,
but makes tests pass in all zones
-- except, of course, the test case which tries to parse
{{1970-01-01T00:00:00}} -- such a timestamp cannot be represented using
{{java.sql.Timestamp}} when JVM zone didn't observe such local time, thus
{{TimestampParser#parseTimestamp(String)}} cannot succeed
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18925.2.patch, HIVE-18925.patch
>
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at
[jira] [Updated] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen updated HIVE-18925:
---
Attachment: (was: HIVE-18925-2.patch)
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18925.2.patch, HIVE-18925.patch
>
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:211)
> ... 21 more{noformat}
> From the above stacktrace it's not visible what is the cause, but i think
> it's initialization of
> {{org.apache.hive.common.util.TimestampParser#startingDateValue}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16414081#comment-16414081
]
Piotr Findeisen commented on HIVE-18925:
thanks [~lirui]! I deleted the wrongly named file to avoid confusion.
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18925.2.patch, HIVE-18925.patch
>
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:211)
> ... 21 more{noformat}
> From the above stacktrace it's not visible what is the cause, but i think
> it's initialization of
> {{org.apache.hive.common.util.TimestampParser#startingDateValue}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen updated HIVE-18925:
---
Attachment: HIVE-18925.2.patch
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18925-2.patch, HIVE-18925.2.patch, HIVE-18925.patch
>
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:211)
> ... 21 more{noformat}
> From the above stacktrace it's not visible what is the cause, but i think
> it's initialization of
> {{org.apache.hive.common.util.TimestampParser#startingDateValue}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412816#comment-16412816
]
Piotr Findeisen edited comment on HIVE-18925 at 3/24/18 10:17 PM:
--
[~lirui] ,
- [~ashutoshc] expressed thought that `TimestampParser` is supposed to parse
timestamps, so the {{"MM:dd:ss"}} pattern may actually be an invalid use case
- anyway, i attached [^HIVE-18925-2.patch] -- this is slightly more intrusive,
but makes tests pass in all zones
-- except, of course, the test case which tries to parse
{{1970-01-01T00:00:00}} -- such a timestamp cannot be represented using
{{java.sql.Timestamp}} when JVM zone didn't observe such local time, thus
{{TimestampParser#parseTimestamp(String)}} cannot succeed
was (Author: findepi):
[~lirui] ,
- [~ashutoshc] expressed thought that `TimestampParser` is supposed to parse
timestamps, so the {{"MM:dd:ss"}} pattern may not be a valid use case
- anyway, i attached [^HIVE-18925-2.patch] -- this is slightly more intrusive,
but makes tests pass in all zones
-- except, of course, the test case which tries to parse
{{1970-01-01T00:00:00}} -- such a timestamp cannot be represented using
{{java.sql.Timestamp}} when JVM zone didn't observe such local time, thus
{{TimestampParser#parseTimestamp(String)}} cannot succeed
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18925-2.patch, HIVE-18925.patch
>
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at
[jira] [Commented] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412816#comment-16412816
]
Piotr Findeisen commented on HIVE-18925:
[~lirui] ,
- [~ashutoshc] expressed thought that `TimestampParser` is supposed to parse
timestamps, so the {{"MM:dd:ss"}} pattern may not be a valid use case
- anyway, i attached [^HIVE-18925-2.patch] -- this is slightly more intrusive,
but makes tests pass in all zones
-- except, of course, the test case which tries to parse
{{1970-01-01T00:00:00}} -- such a timestamp cannot be represented using
{{java.sql.Timestamp}} when JVM zone didn't observe such local time, thus
{{TimestampParser#parseTimestamp(String)}} cannot succeed
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18925-2.patch, HIVE-18925.patch
>
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at
>
[jira] [Updated] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen updated HIVE-18925:
---
Attachment: HIVE-18925-2.patch
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18925-2.patch, HIVE-18925.patch
>
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:211)
> ... 21 more{noformat}
> From the above stacktrace it's not visible what is the cause, but i think
> it's initialization of
> {{org.apache.hive.common.util.TimestampParser#startingDateValue}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16410156#comment-16410156
]
Piotr Findeisen commented on HIVE-18925:
if this all is ok, how do i proceed to have the patch merged?
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18925.patch
>
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:211)
> ... 21 more{noformat}
> From the above stacktrace it's not visible what is the cause, but i think
> it's initialization of
> {{org.apache.hive.common.util.TimestampParser#startingDateValue}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406534#comment-16406534
]
Piotr Findeisen commented on HIVE-18925:
oh, thanks!
should {{org.apache.hive.common.util.TestTimestampParser#testPattern2}} be
updated then? It tests usage of a pattern {{MM:dd:ss}}. Parsing result is off
by 1 hour when the test is run in {{America/Bahia_Banderas}} zone.
btw. {{org.apache.hive.common.util.TestTimestampParser#testPattern1}} fails
when run in {{America/Bahia_Banderas}} zone but this is actually good. The test
tries to parse {{1970-01-01T00:00:00}} as local time and this is not possible
({{Illegal instant due to time zone offset transition
(America/Bahia_Banderas)}}). This is the expected behavior.
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18925.patch
>
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at
>
[jira] [Commented] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405524#comment-16405524
]
Piotr Findeisen commented on HIVE-18925:
[~sershe] could you please check if this is a correct fix for
{{TimestampParser#startingDateValue}}?
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18925.patch
>
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:211)
> ... 21 more{noformat}
> From the above stacktrace it's not visible what is the cause, but i think
> it's initialization of
> {{org.apache.hive.common.util.TimestampParser#startingDateValue}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401241#comment-16401241
]
Piotr Findeisen commented on HIVE-18925:
[~hiveqa] ,
i think all you're saying is that the test are failing even before my change.
[~sershe] , [~lirui],
i do not fully understand what are the duties of {{TimestampParser}}, so please
double check me.
In {{America/Bahia_Banderas}} zone, the first local time observed in 1970 was
{{1970-01-01 01:00:00}}, so with this patch,
{{TimestampParser#startingDateValue}} will be set to {{1970-01-01 01:00:00
America/Bahia_Banderas}}.
If {{TimestampParser}} is used to parse timestamps (as it seems), this is
alright. If, however, it can be used to parse _dates_ represented as midnights,
it might return {{ Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18925.patch
>
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
[jira] [Updated] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen updated HIVE-18925:
---
Status: Patch Available (was: Open)
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18925.patch
>
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:211)
> ... 21 more{noformat}
> From the above stacktrace it's not visible what is the cause, but i think
> it's initialization of
> {{org.apache.hive.common.util.TimestampParser#startingDateValue}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16398216#comment-16398216
]
Piotr Findeisen commented on HIVE-18925:
I'm concerned that the patch (diff) doesn't convey the commit message. I wanted
the commit message to be somewhat explanatory, e.g.
{noformat}
HIVE-18925: Prevent failure when JVM zone had change on 1970-01-01
This prevents static initializer failure if JVM zone did not observe
1970-01-01 00:00:00, while retaining original behavior for all other
zones.
{noformat}
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18925.patch
>
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:211)
> ... 21 more{noformat}
> From the above stacktrace it's not visible what is the cause, but i think
> it's initialization of
>
[jira] [Commented] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16398215#comment-16398215
]
Piotr Findeisen commented on HIVE-18925:
Thanks [~sershe], [^HIVE-18925.patch] attached
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18925.patch
>
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:211)
> ... 21 more{noformat}
> From the above stacktrace it's not visible what is the cause, but i think
> it's initialization of
> {{org.apache.hive.common.util.TimestampParser#startingDateValue}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen updated HIVE-18925:
---
Attachment: HIVE-18925.patch
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18925.patch
>
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:211)
> ... 21 more{noformat}
> From the above stacktrace it's not visible what is the cause, but i think
> it's initialization of
> {{org.apache.hive.common.util.TimestampParser#startingDateValue}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393721#comment-16393721
]
Piotr Findeisen commented on HIVE-18925:
i created a PR with this change. https://github.com/apache/hive/pull/319
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:211)
> ... 21 more{noformat}
> From the above stacktrace it's not visible what is the cause, but i think
> it's initialization of
> {{org.apache.hive.common.util.TimestampParser#startingDateValue}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen updated HIVE-18925:
---
Comment: was deleted
(was: i created a PR with this change. https://github.com/apache/hive/pull/319)
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Priority: Major
> Labels: pull-request-available
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:211)
> ... 21 more{noformat}
> From the above stacktrace it's not visible what is the cause, but i think
> it's initialization of
> {{org.apache.hive.common.util.TimestampParser#startingDateValue}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393711#comment-16393711
]
Piotr Findeisen commented on HIVE-18925:
I think it should be sufficient to replace
{code:java}
protected final static DateTime startingDateValue = new DateTime(1970, 1, 1, 0,
0, 0, 0);{code}
with
{code:java}
protected final static DateTime startingDateValue = new DateTime(1970, 1, 1, 0,
0, 0, 0, DateTimeZone.UTC)
.withZoneRetainFields(DateTimeZone.getDefault());{code}
This is equivalent to the former for any normal zone, but doesn't fail for
"odd" zone that skipped 1970-01-01 00:00:00 in its local time.
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Priority: Major
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:211)
> ... 21 more{noformat}
> From the above stacktrace it's not visible what is the cause, but i think
> it's initialization of
>
[jira] [Updated] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen updated HIVE-18925:
---
Description:
Hive Server2 doesn't work if started with
{{-Duser.timezone=America/Bahia_Banderas}}
Steps to reproduce
# use [https://github.com/big-data-europe/docker-hive]
# Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
{{hive-server}} docker container environment configuration
# {{docker-compose up}}
#
{code:java}
host# docker-compose exec hive-server bash
container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1 --verbose=true
...
jdbc:hive2://localhost:1> select 1;{code}
The above fails and prints
{noformat}
Error: java.lang.IllegalStateException: Can't overwrite cause with
org.joda.time.IllegalInstantException: Illegal instant due to time zone offset
transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
(America/Bahia_Banderas) (state=08S01,code=0)
java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause
with org.joda.time.IllegalInstantException: Illegal instant due to time zone
offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
(America/Bahia_Banderas)
at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
Caused by: java.lang.IllegalStateException: Can't overwrite cause with
org.joda.time.IllegalInstantException: Illegal instant due to time zone offset
transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
(America/Bahia_Banderas)
at java.lang.Throwable.initCause(Throwable.java:457)
at
org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
at
org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
at
org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
at
org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
... 15 more
Caused by: java.lang.ExceptionInInitializerError: null
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at
org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
at
org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:211)
... 21 more{noformat}
>From the above stacktrace it's not visible what is the cause, but i think it's
>initialization of
>{{org.apache.hive.common.util.TimestampParser#startingDateValue}}
was:
Hive Server2 doesn't work if started with
{{-Duser.timezone=America/Bahia_Banderas}}
Steps to reproduce
# use [https://github.com/big-data-europe/docker-hive]
# Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
{{hive-server}} docker container environment configuration
# {{docker-compose up}}
#
{code:java}
host# docker-compose exec hive-server bash
container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
...
jdbc:hive2://localhost:1> select 1;
Error: java.lang.IllegalStateException: Can't overwrite cause with
org.joda.time.IllegalInstantException: Illegal instant due to time zone offset
transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
(America/Bahia_Banderas) (state=08S01,code=0){code}
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
>
[jira] [Updated] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone
[
https://issues.apache.org/jira/browse/HIVE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Findeisen updated HIVE-18925:
---
Summary: Hive doesn't work when JVM is America/Bahia_Banderas time zone
(was: Hive doesn't start when JVM is America/Bahia_Banderas time zone)
> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
> Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Priority: Major
>
> Hive Server2 doesn't work if started with
> {{-Duser.timezone=America/Bahia_Banderas}}
>
> Steps to reproduce
> # use [https://github.com/big-data-europe/docker-hive]
> # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to
> {{hive-server}} docker container environment configuration
> # {{docker-compose up}}
> #
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1
> ...
> jdbc:hive2://localhost:1> select 1;
> Error: java.lang.IllegalStateException: Can't overwrite cause with
> org.joda.time.IllegalInstantException: Illegal instant due to time zone
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000
> (America/Bahia_Banderas) (state=08S01,code=0){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
