Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Subject: re: Derby version used by Hive
To: dev@hive.apache.org
Message-ID: 
 <OF71EFF43E.69ACA89C-ON87257ECE.00577B89-88257ECE.00582984@us.ibm.com>
From: Richard Hillegas <rhilleg@us.ibm.com>
Date: Mon, 28 Sep 2015 09:02:58 -0700
MIME-Version: 1.0
Content-type: multipart/alternative;
	Boundary="0__=08BBF45DDFC4FD198f9e8a93df938690918c08BBF45DDFC4FD19"
Content-Disposition: inline

--0__=08BBF45DDFC4FD198f9e8a93df938690918c08BBF45DDFC4FD19
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable


I haven't received a response to the following message, which I posted =
last
week. Maybe my message rambled too much. Here is an attempt to pose my
question more succinctly:

Q: Does anyone know of any reason why we can't upgrade Hive's Derby ver=
sion
to 10.12.1.1, the new version being vetted by the Derby community right=

now?

Thanks,
-Rick

> I am following the Hive build instructions here:
>
https://cwiki.apache.org/confluence/display/Hive/GettingStarted#Getting=
Started-InstallationandConfiguration
> .
>
> I noticed that Hive development seems to be using an old version of
Derby:
> 10.10.2.0. Is there some defect in the most recent Derby version
> (10.11.1.1) which prevents Hive from upgrading to 10.11.1.1? The only=

> Hive-tagged Derby bug which I can find is
> https://issues.apache.org/jira/browse/DERBY-6358. That issue doesn't =
seem
> to be version-specific and it mentions a resolved Hive issue:
> https://issues.apache.org/jira/browse/HIVE-8739.
>
> Staying with 10.10.2.0 makes sense if you need to run on some ancient=

JVMs:
> Java SE 5 or Java ME CDC/Foundation Profile 1.1. Hadoop, however,
requires
> at least Java 6 according to
> https://wiki.apache.org/hadoop/HadoopJavaVersions.
>
> Note that the Derby community expects to release version 10.12.1.1 so=
on:
> https://wiki.apache.org/db-derby/DerbyTenTwelveOneRelease. This might=
 be
a
> good opportunity for Hive to upgrade to a more capable version of Der=
by.
>
> I mention this because the Derby version used by Hive ends up on the
> classpath used by downstream projects (like Spark). That makes it awk=
ward
> for downstream projects to use more current Derby versions. Do you kn=
ow
of
> any reason that downstream projects shouldn't override the Derby vers=
ion
> currently preferred by Hive?
>
> Thanks,
> -Rick=

--0__=08BBF45DDFC4FD198f9e8a93df938690918c08BBF45DDFC4FD19--