[
https://issues.apache.org/jira/browse/HIVE-21553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16805816#comment-16805816
]
Laszlo Bodor edited comment on HIVE-21553 at 3/31/19 11:17 AM:
---------------------------------------------------------------
cc: [~janulatha] , [~alangates] , what do you think about upgrading derby in
standalone-metastore to 10.14.1.0, or upgrade it in both hive +
standalone-metastore to the latest 10.15.1.3
UPDATE: seems like 10.15 is for Java9 and higher
([https://db.apache.org/derby/derby_downloads.html])
currently, I cannot prove that derby is the cause of failures in HIVE-21550
was (Author: abstractdog):
cc: [~janulatha] , [~alangates] , what do you think about upgrading derby in
standalone-metastore to 10.14.1.0, or upgrade it in both hive +
standalone-metastore to the latest 10.15.1.3
UPDATE1: seems like 10.15 is for Java9 and higher
([https://db.apache.org/derby/derby_downloads.html])
currently, I cannot prove that derby is the cause of failures in HIVE-21550
> Upgrade derby version in standalone-metastore
> ---------------------------------------------
>
> Key: HIVE-21553
> URL: https://issues.apache.org/jira/browse/HIVE-21553
> Project: Hive
> Issue Type: Bug
> Reporter: Laszlo Bodor
> Assignee: Laszlo Bodor
> Priority: Major
> Attachments: HIVE-21553.01.patch
>
>
> HIVE-17506 decoupled standalone metastore poms from hive, then HIVE-18586
> upgraded derby to 10.14.1.0 in hive's top level pom.xml. Maybe it could be
> useful to synchronize them.
> Current versions
> hive: 10.14.1.0
> standalone-metastore: 10.10.2.0
> This idea came up while investigating some derby lock issues in HIVE-21550.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
