On Feb 3, 2014, at 5:29 PM, Xuefu Zhang wrote:
> I guess another point that I tried to make is that if sqlline fork is
> bundled with Hive, it defeats the purpose of allowing other projects to
> share the same code line. I'd like to see the possibility of fork sqlline
> to apache as an independen
I guess another point that I tried to make is that if sqlline fork is
bundled with Hive, it defeats the purpose of allowing other projects to
share the same code line. I'd like to see the possibility of fork sqlline
to apache as an independent module.
On Mon, Feb 3, 2014 at 5:18 PM, Julian Hyde
On Feb 3, 2014, at 11:15 AM, Xuefu Zhang wrote:
> I'm thinking if it makes more sense to fork sqlline
> directly into Apache. upon its completion, Hive gets rid of its copy of
> sqlline and creates a dependency on the forked sqlline instead. I guess
> this is a top-down approach and the benefits
Hi Julian,
Thanks for sharing your thought. I'm certainly on board on code sharing
among project. However, I don't see immediate benefits for Hive by
separating Beeline into two modules. Instead, it requires additional work
and potentially creates instability, while code sharing isn't achieved
unt
As you probably know, Hive’s SQL command-line interface Beeline was created by
forking Sqlline [1] [2]. At the time it was a useful but low-activity project
languishing on SourceForge without an active owner. Around the same time, I
independently picked up the Sqlline code, moved it to github [3
