hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Hillegas <>
Subject re: Derby version used by Hive
Date Mon, 28 Sep 2015 16:02:58 GMT

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 version
to, the new version being vetted by the Derby community right


> I am following the Hive build instructions here:
> .
> I noticed that Hive development seems to be using an old version of
> Is there some defect in the most recent Derby version
> ( which prevents Hive from upgrading to The only
> Hive-tagged Derby bug which I can find is
> That issue doesn't seem
> to be version-specific and it mentions a resolved Hive issue:
> Staying with makes sense if you need to run on some ancient
> Java SE 5 or Java ME CDC/Foundation Profile 1.1. Hadoop, however,
> at least Java 6 according to
> Note that the Derby community expects to release version soon:
> This might be
> good opportunity for Hive to upgrade to a more capable version of Derby.
> I mention this because the Derby version used by Hive ends up on the
> classpath used by downstream projects (like Spark). That makes it awkward
> for downstream projects to use more current Derby versions. Do you know
> any reason that downstream projects shouldn't override the Derby version
> currently preferred by Hive?
> Thanks,
> -Rick
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message