[ 
https://issues.apache.org/jira/browse/HIVE-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Hyde updated HIVE-6361:
------------------------------

    Status: Patch Available  (was: Open)

> Un-fork Sqlline
> ---------------
>
>                 Key: HIVE-6361
>                 URL: https://issues.apache.org/jira/browse/HIVE-6361
>             Project: Hive
>          Issue Type: Improvement
>          Components: CLI
>    Affects Versions: 0.12.0
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>         Attachments: HIVE-6361.patch
>
>
> I propose to merge the two development forks of sqlline: Hive's beeline 
> module, and the fork at https://github.com/julianhyde/sqlline.
> 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 Optiq.
> 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 Beeline.java (a derived 
> class of Sqlline.java) and Hive-specific extensions.
> 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
(v6.2#6252)

Reply via email to