hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Hyde (JIRA)" <>
Subject [jira] [Commented] (HIVE-6361) Un-fork Sqlline
Date Tue, 05 Aug 2014 18:34:12 GMT


Julian Hyde commented on HIVE-6361:

A lot more than a week so far... but making progress:

> Un-fork Sqlline
> ---------------
>                 Key: HIVE-6361
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: CLI
>    Affects Versions: 0.12.0
>            Reporter: Julian Hyde
> I propose to merge the two development forks of sqlline: Hive's beeline module, and the
fork at
> How did the forks come about? Hive’s SQL command-line interface Beeline was created
by forking Sqlline (see HIVE-987, HIVE-3100), which at the time it was a useful but low-activity
project languishing on SourceForge without an active owner. Around the same time, Julian Hyde
independently started a github repo based on the same code base. Now several projects are
using Julian Hyde's sqlline, including Apache Drill, Apache Phoenix, Cascading Lingual and
> Merging these two forks will allow us to pool our resources. (Case in point: Drill issue
DRILL-327 had already been fixed in a later version of sqlline; it still exists in beeline.)
> I propose the following steps:
> 1. Copy Julian Hyde's sqlline as a new Hive module, hive-sqlline.
> 2. Port fixes to hive-beeline into hive-sqlline.
> 3. Make hive-beeline depend on hive-sqlline, and remove code that is identical. What
remains in the hive-beeline module is (a derived class of and Hive-specific
> 4. Make the hive-sqlline the official successor to Julian Hyde's sqlline.
> This achieves continuity for Hive’s users, gives the users of the non-Hive sqlline
a version with minimal dependencies, unifies the two code lines, and brings everything under
the Apache roof.

This message was sent by Atlassian JIRA

View raw message