HIVE-18624 SQL parser performance bug

[Julian Hyde]

HIVE-18624 [1] is a serious performance bug in the SQL parser. It causes parse 
times that are literally exponential in the number of parentheses in the 
expression, thus parsing of a query that has complex expressions may take 
minutes or not terminate. According to JIRA, the bug was fixed on 2.4.0, 3.1.0, 
4.0.0 code lines in August but has not yet been released.

I work for Looker, a BI tool that generates SQL with deeply nested expressions, 
and therefore they hit this bug. Hive 2.2, 2.3 and 3.0 are unusable for our 
customers due to this bug.

I do not know the schedule for 2.4.0, 3.1.0 or 4.0.0 releases, but if they are 
a way off, would it be possible to fix this bug in a patch release?

Julian

[1] https://issues.apache.org/jira/browse/HIVE-18624 

[jira] [Created] (HIVE-20938) HiveResultSetMetaData.getColumnDisplaySize throws for SHORT column

[Julian Hyde (JIRA)]

Julian Hyde created HIVE-20938:
--

 Summary: HiveResultSetMetaData.getColumnDisplaySize throws for 
SHORT column
 Key: HIVE-20938
 URL: https://issues.apache.org/jira/browse/HIVE-20938
 Project: Hive
  Issue Type: Bug
Reporter: Julian Hyde


HiveResultSetMetaData.getColumnDisplaySize throws for SHORT column. Stack is as 
follows:

{noformat}
Error: Unrecognized column type: SHORT (state=,code=0)
java.sql.SQLException: Unrecognized column type: SHORT
at 
org.apache.hive.jdbc.JdbcColumn.typeStringToHiveType(JdbcColumn.java:164)
at 
org.apache.hive.jdbc.HiveResultSetMetaData.getHiveType(HiveResultSetMetaData.java:48)
at 
org.apache.hive.jdbc.HiveResultSetMetaData.getColumnDisplaySize(HiveResultSetMetaData.java:61)
at sqlline.IncrementalRows.(IncrementalRows.java:47)
at sqlline.SqlLine.print(SqlLine.java:1702)
at sqlline.Commands.metadata(Commands.java:207)
at sqlline.Commands.indexes(Commands.java:364)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:718)
at sqlline.SqlLine.begin(SqlLine.java:539)
at sqlline.SqlLine.start(SqlLine.java:264)
at sqlline.SqlLine.main(SqlLine.java:195)
{noformat}

We have worked around this in https://github.com/julianhyde/sqlline/issues/203. 
I believe the issue also exists in Beeline, which is a fork of SQLLine.

Seems similar to HIVE-7448, which related to BINARY type and was fixed a long 
time ago.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [DISCUSS] Separating out the metastore as its own TLP

[Julian Hyde]

+1

As a Calcite PMC member, I am very pleased to see this change. Calcite reads 
metadata from a variety of sources (including JDBC databases, NoSQL databases 
such as Cassandra and Druid, and streaming systems), and if more of those 
sources choose to store their metadata in the metastore it will make our lives 
easier.

Hive’s metastore has established a position as the place to go for metadata in 
the Hadoop ecosystem. Not all metadata is relational, or processed by Hive, so 
there are other parties using the metastore who justifiably would like to 
influence its direction. Opening up the metastore will help retain and extend 
this position.

Julian


On 2017-06-30 10:00 (-0700), "Dimitris ts...@apache.org> wrote: 
> 
> 
> On 2017-06-30 07:56 (-0700), Alan Gates  wrote: > 
> > A few of us have been talking and come to the conclussion that it would be> 
> > a good thing to split out the Hive metastore into its own Apache project.> 
> > Below and in the linked wiki page we explain what we see as the advantages> 
> > to this and how we would go about it.> 
> > > 
> > Hive’s metastore has long been used by other projects in the Hadoop> 
> > ecosystem to store and access metadata.  Apache Impala, Apache Spark,> 
> > Apache Drill, Presto, and other systems all use Hive’s metastore.  Some,> 
> > like Impala and Presto can use it as their own metadata system with the> 
> > rest of Hive not present.> 
> > > 
> > This sharing is excellent for the ecosystem.  Together with HDFS it allows> 
> > users to use the tool of their choice while still accessing the same 
> > shared> 
> > data.  But having this shared metadata inside the Hive project limits the> 
> > ability of other projects to contribute to the metastore.  It also makes 
> > it> 
> > harder for new systems that have similar but not identical metadata> 
> > requirements (for example, stream processing systems on top of Apache> 
> > Kafka) to use Hive’s metastore.  This difficulty for other systems comes> 
> > out in two ways.  One, it is hard for non-Hive community members to> 
> > participate in the project.  Second, it adds operational cost since users> 
> > are forced to deploy all of the Hive jars just to get the metastore to 
> > work.> 
> > > 
> > Therefore we propose to split Hive’s metastore out into a separate Apache> 
> > project.  This new project will continue to support the same Thrift API as> 
> > the current metastore.  It will continue to focus on being a high> 
> > performance, fault tolerant, large scale, operational metastore for SQL> 
> > engines and other systems that want to store schema information about 
> > their> 
> > data.> 
> > > 
> > By making it a separate project we will enable other projects to join us 
> > in> 
> > innovating on the metastore.  It will simplify operations for non-Hive> 
> > users that want to use the metastore as they will no longer need to 
> > install> 
> > Hive just to get the metastore.  And it will attract new projects that> 
> > might otherwise feel the need to solve their metadata problems on their 
> > own.> 
> > > 
> > Any Hive PMC member or committer will be welcome to join the new project 
> > at> 
> > the same level.  We propose this project go straight to a top level> 
> > project.  Given that the initial PMC will be formed from experienced Hive> 
> > PMC members we do not believe incubation will be necessary.  (Note that 
> > the> 
> > Apache board will need to approve this.)> 
> > > 
> > Obviously there a many details involved in a proposal like this.  Rather> 
> > than make this a ten page email we have filled out many of the details in 
> > a> 
> > wiki page:> 
> > https://cwiki.apache.org/confluence/display/Hive/Metastore+TLP+Proposal> 
> > > 
> > Yongzhi Chen> 
> > Vihang Karajgaonkar> 
> > Sergio Pena> 
> > Sahil Takiar> 
> > Aihua Xu> 
> > Gunther Hagleitner> 
> > Thejas Nair> 
> > Alan Gates> 
> > > 
> 
> +1 (from Apache Impala's (incubating) perspective)> 
> 
> Dimitris> 
> 

[jira] [Created] (HIVE-14217) Druid integration

[Julian Hyde (JIRA)]

Julian Hyde created HIVE-14217:
--

 Summary: Druid integration
 Key: HIVE-14217
 URL: https://issues.apache.org/jira/browse/HIVE-14217
 Project: Hive
  Issue Type: Bug
Reporter: Julian Hyde


Allow Hive to query data in Druid



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HIVE-11383) Upgrade Hive to Calcite 1.4

[Julian Hyde (JIRA)]

Julian Hyde created HIVE-11383:
--

 Summary: Upgrade Hive to Calcite 1.4
 Key: HIVE-11383
 URL: https://issues.apache.org/jira/browse/HIVE-11383
 Project: Hive
  Issue Type: Bug
Reporter: Julian Hyde


Upgrade Hive to Calcite 1.4.0-incubating.

There is currently a snapshot release, which is close to what will be in 1.4. I 
have checked that Hive compiles against the new snapshot, fixing one issue. The 
patch is attached.

Next step is to validate that Hive runs against the new Calcite, and post any 
issues to the Calcite list or log Calcite Jira cases. [~jcamachorodriguez], can 
you please do that.

[~pxiong], I gather you are dependent on CALCITE-814, which will be fixed in 
the new Calcite version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Building Hive-0.14 is failing because artifact pentaho-aggdesigner-algorithm-5.1.3-jhyde could not be resolved

[Julian Hyde]

I agree. Everything should come from the Apache repo or Maven central.

I logged https://issues.apache.org/jira/browse/CALCITE-605 to track it, and it 
is fixed except for pentaho-aggdesigner-algorithm. I am still working on that 
one (persuading the Pentaho folks to deploy to maven central); see 
https://issues.apache.org/jira/browse/CALCITE-756.

Julian


> On Jun 11, 2015, at 8:21 AM, Alan Gates  wrote:
> 
> To clarify, I didn't intend to say we shouldn't trust a repository like 
> conjars, I meant to say I don't know if we should.  I'll have to look into it.
> 
> Alan.
> 
> From: Ravi Prakash mailto:ravi...@ymail.com>>
> Reply-To: Ravi Prakash mailto:ravi...@ymail.com>>
> Date: Thursday, June 11, 2015 at 8:15
> To: Julian Hyde mailto:julianh...@gmail.com>>, 
> "d...@calcite.incubator.apache.org<mailto:d...@calcite.incubator.apache.org>" 
> mailto:d...@calcite.incubator.apache.org>>
> Cc: "hive-...@hadoop.apache.org<mailto:hive-...@hadoop.apache.org>" 
> mailto:hive-...@hadoop.apache.org>>, Alan Gates 
> mailto:ga...@hortonworks.com>>
> Subject: Re: Building Hive-0.14 is failing because artifact 
> pentaho-aggdesigner-algorithm-5.1.3-jhyde could not be resolved
> 
> Thanks Julian!
> 
> I talked to Alan at the Hadoop Summit on Tuesday and he agreed that 
> dependencies for Apache projects should be available via Maven Central (and 
> shouldn't require trusting other repositories like conjars).
> 
> This problem persists with the current Hive-1.2.0 release since it depends on 
> Calcite-1.3.0-incubating<https://github.com/apache/hive/blob/master/pom.xml#L104>
>  which in turn depends on artifacts like 
> pentaho-aggdesigner-algorithm-5.1.5-hyde<https://github.com/apache/incubator-calcite/blob/branch-1.3/pom.xml#L264>
>  , There are also licensing issues that I am not completely sure of. For 
> instance what is the license for pentaho-aggdesigner-algorithm ?
> 
> Thanks
> Ravi
> 
> 
> 
> 
> On Tuesday, January 6, 2015 5:13 PM, Julian Hyde 
> mailto:julianh...@gmail.com>> wrote:
> 
> 
> Conjars (http://conjars.org/) has all of these libraries. Calcite's pom uses 
> it:
> 
>  
>
>  
>true
>always
> warn
>  
>  conjars
>  Conjars
>  http://conjars.org/repo
>  default
>
>  
> 
> Julian
> 
> 
> On Jan 6, 2015, at 3:45 PM, Ravi Prakash 
> mailto:ravi...@ymail.com>> wrote:
> 
> Hi folks!
> I'm still stuck on this issue. Hopefully people are back from their vacations 
> and can now reply. Resending.
> 
> 
>On Monday, December 29, 2014 1:17 PM, Ravi Prakash 
> mailto:ravi...@ymail.com>> wrote:
> 
> 
> Hi folks!
> I'm still somewhat stuck on this issue. Could someone please guide me?
> I had to manually download these jars and put them into my ~/.m2/repository 
> from 
> http://repo.spring.io/libs-release/org/pentaho/pentaho-aggdesigner-algorithm/5.1.3-jhyde/
>  . (When I configured this repository, maven somehow still didn't find the 
> artifacts)
> I had to do this for the following 
> artifacts:http://repo.spring.io/libs-release/org/pentaho/pentaho-aggdesigner/5.1.3-jhyde/pentaho-aggdesigner-5.1.3-jhyde.pomhttp://repo.spring.io/libs-release/net/hydromatic/linq4j/0.4/linq4j-0.4.jarhttp://repo.spring.io/libs-release/net/hydromatic/quidem/0.1.1/quidem-0.1.1.pom
> Consequently I was able to build hive, however I don't believe this is a 
> kosher way of producing production binaries, so I am still waiting to hear 
> from you all. Is there another trusted repository I can try which has these 
> artifacts indexed?
> 
> ThanksRavi
> 
> 
>On Monday, December 22, 2014 2:14 PM, Ravi Prakash 
> mailto:ravi...@ymail.com>> wrote:
> 
> 
> Hi!
> Has anyone tried building Hive-0.14 from source? I'm using the tag for 
> release-0.14.0 https://github.com/apache/hive/releases/tag/release-0.14.0
> 
> The command I use is: mvn install -DskipTests -Phadoop-2 
> -DcreateChecksum=true -Dtez.version=0.5.3 -Dcalcite.version=0.9.2-incubating
> 
> The build fails for me with the following error:[ERROR] Failed to execute 
> goal on project hive-exec: Could not resolve dependencies for project 
> org.apache.hive:hive-exec:jar:0.14.0: The following artifacts could not be 
> resolved: org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.3-jhyde, 
> net.hydromatic:linq4j:jar:0.4, net.hydromatic:quidem:jar:0.1.1: Could not 
> find artifact org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.3-jhyde in 
> nexus (http://localhost:8081/nexus/content/groups/public) -> [Help 1]
> 
> This is a transitive dependency via the "calcite-0.9.2-incubating" artifact. 
> Is there a JIRA which someone can please point me to? It seems wrong that an 
> artifact with version "5.1.3-jhyde" is required to build Apache Hive, no 
> disrespect to Julian. Am I missing something?
> ThanksRavi
> 
> 
> 
> 
> 
> 
> 
> 

[jira] [Commented] (HIVE-9719) Up calcite version on cbo branch

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-9719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326850#comment-14326850
 ] 

Julian Hyde commented on HIVE-9719:
---

I just pushed the snapshot. It is based on 
https://github.com/apache/incubator-calcite/commit/f9db1ee9210a04f7a3ddae23e52e26be1669debb.

> Up calcite version on cbo branch
> 
>
> Key: HIVE-9719
> URL: https://issues.apache.org/jira/browse/HIVE-9719
> Project: Hive
>  Issue Type: Task
>  Components: CBO
>Affects Versions: cbo-branch
>Reporter: Ashutosh Chauhan
>Assignee: Ashutosh Chauhan
> Attachments: HIVE-9719.cbo.patch
>
>
> CALCITE-594 is now checked in calcite master.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-6173) Beeline doesn't accept --hiveconf option as Hive CLI does

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14323395#comment-14323395
 ] 

Julian Hyde commented on HIVE-6173:
---

In https://github.com/julianhyde/sqlline/issues/32, I have extended the output 
'!help set' to include all options, including showElapsedTime, maxHeight, 
maxWidth, timeout, trimScripts.

Those changes could be merged into Hive's fork of sqlline.

> Beeline doesn't accept --hiveconf option as Hive CLI does
> -
>
> Key: HIVE-6173
> URL: https://issues.apache.org/jira/browse/HIVE-6173
> Project: Hive
>  Issue Type: Improvement
>  Components: CLI
>Affects Versions: 0.10.0, 0.11.0, 0.12.0
>Reporter: Xuefu Zhang
>Assignee: Xuefu Zhang
>  Labels: TODOC13
> Fix For: 0.13.0
>
> Attachments: HIVE-6173.1.patch, HIVE-6173.2.patch, HIVE-6173.patch
>
>
> {code}
> > beeline -u jdbc:hive2:// --hiveconf a=b
> Usage: java org.apache.hive.cli.beeline.BeeLine 
> {code}
> Since Beeline is replacing Hive CLI, it should support this command line 
> option as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-9454) Test failures due to new Calcite version

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-9454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301877#comment-14301877
 ] 

Julian Hyde commented on HIVE-9454:
---

Calcite RC3 is looking good. With a little luck the RC3 vote will pass PPMC 
vote on Tuesday and IPMC vote on Friday.

> Test failures due to new Calcite version
> 
>
> Key: HIVE-9454
> URL: https://issues.apache.org/jira/browse/HIVE-9454
> Project: Hive
>  Issue Type: Bug
>Reporter: Brock Noland
>Assignee: Laljo John Pullokkaran
> Attachments: HIVE-9454.02.patch, HIVE-9454.03.patch, 
> HIVE-9454.04.patch, HIVE-9454.05.patch, HIVE-9454.1.patch
>
>
> A bunch of failures have started appearing in patches which seen unrelated. I 
> am thinking we've picked up a new version of Calcite. E.g.:
> http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/2488/testReport/org.apache.hadoop.hive.cli/TestCliDriver/testCliDriver_auto_join12/
> {noformat}
> Running: diff -a 
> /home/hiveptest/54.147.202.89-hiveptest-1/apache-svn-trunk-source/itests/qtest/../../itests/qtest/target/qfile-results/clientpositive/auto_join12.q.out
>  
> /home/hiveptest/54.147.202.89-hiveptest-1/apache-svn-trunk-source/itests/qtest/../../ql/src/test/results/clientpositive/auto_join12.q.out
> 32c32
> < $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> 35c35
> < $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:$hdt$_1:src 
> 39c39
> < $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> 54c54
> < $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:$hdt$_1:src 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-9510) Throwing null point exception , when get join distinct row count from RelMdUtil.java class

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-9510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298032#comment-14298032
 ] 

Julian Hyde commented on HIVE-9510:
---

In Calcite, metadata providers are adapters. The Calcite engine will call into 
the adapter, provided in this case by Hive, to get extra information. In this 
case it only asks for extra information when you increase the logging level. 
Calcite is assuming Hive implemented its metadata provider correctly but I am 
guessing that it did not -- in which case, the error is in Hive code.

> Throwing null point exception , when get join distinct row count from 
> RelMdUtil.java class
> --
>
> Key: HIVE-9510
> URL: https://issues.apache.org/jira/browse/HIVE-9510
> Project: Hive
>  Issue Type: Bug
>  Components: CBO
>Reporter: asko
>Assignee: Julian Hyde
> Attachments: log.txt, log3_cbo5
>
>
> Setting log level in logging.properties file as following:
> {noformat}
> handlers=java.util.logging.ConsoleHandler.level=INFO
> org.apache.calcite.plan.RelOptPlanner.level=ALL
> java.util.logging.ConsoleHandler.level=ALL
> {noformat}
> Running Q3 in TPCH-full  after modifying , in order to  test join reorder,
> but running  failed.
> QL:
> {code:sql}
> set  hive.cbo.enable=true;
> --ANALYZE TABLE customer COMPUTE STATISTICS for columns;
> --ANALYZE TABLE orders COMPUTE STATISTICS for columns;
> --ANALYZE TABLE lineitem COMPUTE STATISTICS for columns;
> --Q3
> -- the query
> select 
>   l_orderkey, sum(l_extendedprice*(1-l_discount)) as revenue, o_orderdate, 
> o_shippriority 
> from 
>   lineitem l join orders o 
> on l.l_orderkey = o.o_orderkey
>   join customer c
> on c.c_mktsegment = 'BUILDING' and c.c_custkey = o.o_custkey 
> where 
>   o_orderdate < '1995-03-15' and l_shipdate > '1995-03-15' 
> group by l_orderkey, o_orderdate, o_shippriority 
> order by revenue desc, o_orderdate 
> limit 10;
> {code}
> LOG:
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-9510) Throwing null point exception , when get join distinct row count from RelMdUtil.java class

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-9510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297412#comment-14297412
 ] 

Julian Hyde commented on HIVE-9510:
---

I moved this from CALCITE to HIVE because even though the error comes from 
Calcite code, it should be investigated as a Hive issue. The likely cause is 
that Hive did not set up its metadata provider correctly.

> Throwing null point exception , when get join distinct row count from 
> RelMdUtil.java class
> --
>
> Key: HIVE-9510
> URL: https://issues.apache.org/jira/browse/HIVE-9510
> Project: Hive
>  Issue Type: Bug
>Reporter: asko
>Assignee: Julian Hyde
> Attachments: log3_cbo5
>
>
> Setting log level in logging.properties file as following:
> handlers=java.util.logging.ConsoleHandler
> .level=INFO
> org.apache.calcite.plan.RelOptPlanner.level=ALL
> java.util.logging.ConsoleHandler.level=ALL
> Running Q3 in TPCH-full  after modifying , in order to  test join reorder,
> but running  failed.
> QL:
> set  hive.cbo.enable=true;
> --ANALYZE TABLE customer COMPUTE STATISTICS for columns;
> --ANALYZE TABLE orders COMPUTE STATISTICS for columns;
> --ANALYZE TABLE lineitem COMPUTE STATISTICS for columns;
> --Q3
> -- the query
> select 
>   l_orderkey, sum(l_extendedprice*(1-l_discount)) as revenue, o_orderdate, 
> o_shippriority 
> from 
>   lineitem l join orders o 
> on l.l_orderkey = o.o_orderkey
>   join customer c
> on c.c_mktsegment = 'BUILDING' and c.c_custkey = o.o_custkey 
> where 
>   o_orderdate < '1995-03-15' and l_shipdate > '1995-03-15' 
> group by l_orderkey, o_orderdate, o_shippriority 
> order by revenue desc, o_orderdate 
> limit 10;
> LOG:
> Jan 29, 2015 11:48:04 AM org.apache.calcite.plan.AbstractRelOptPlanner 
> fireRule
> FINE: call#15: Apply rule [FilterProjectTransposeRule] to 
> [rel#107:HiveFilter.HIVE.[](input=HepRelVertex#106,condition=<($2, 
> '1995-03-15')), 
> rel#105:HiveProject.HIVE.[](input=HepRelVertex#104,o_orderkey=$0,o_custkey=$1,o_orderdate=$4,o_shippriority=$7)]
> Jan 29, 2015 11:48:04 AM org.apache.calcite.rel.AbstractRelNode 
> FINEST: new HiveFilter#138
> Jan 29, 2015 11:48:04 AM org.apache.calcite.rel.AbstractRelNode 
> FINEST: new HiveProject#139
> Jan 29, 2015 11:48:04 AM org.apache.calcite.plan.AbstractRelOptPlanner 
> notifyTransformation
> FINE: call#15: Rule FilterProjectTransposeRule arguments 
> [rel#107:HiveFilter.HIVE.[](input=HepRelVertex#106,condition=<($2, 
> '1995-03-15')), 
> rel#105:HiveProject.HIVE.[](input=HepRelVertex#104,o_orderkey=$0,o_custkey=$1,o_orderdate=$4,o_shippriority=$7)]
>  produced HiveProject#139
> Jan 29, 2015 11:48:04 AM org.apache.calcite.rel.AbstractRelNode 
> FINEST: new HepRelVertex#140
> Jan 29, 2015 11:48:04 AM org.apache.calcite.rel.AbstractRelNode 
> FINEST: new HiveProject#141
> Jan 29, 2015 11:48:04 AM org.apache.calcite.rel.AbstractRelNode 
> FINEST: new HepRelVertex#142
> 15/01/29 11:48:04 [main]: DEBUG stats.HiveRelMdRowCount: Identified Primary - 
> Foreign Key relation:
> 15/01/29 11:48:04 [main]: DEBUG stats.HiveRelMdRowCount: 
> HiveJoin(condition=[=($0, $4)], joinType=[inner])
>   HiveProject(l_orderkey=[$0], l_extendedprice=[$5], l_discount=[$6], 
> l_shipdate=[$10])
> HiveFilter(condition=[>($10, '1995-03-15')])
>   HiveTableScan(table=[[default.lineitem]])
>   HiveProject(o_orderkey=[$0], o_custkey=[$1], o_orderdate=[$4], 
> o_shippriority=[$7])
> HiveFilter(condition=[<($4, '1995-03-15')])
>   HiveTableScan(table=[[default.orders]])
> 15/01/29 11:48:04 [main]: DEBUG stats.HiveRelMdRowCount: Primary - Foreign 
> Key join:
>   fkSide = 1
>   FKInfo:FKInfo(rowCount=1.00,ndv=-1.00)
>   PKInfo:PKInfo(rowCount=1.00,ndv=-1.00,selectivity=1.00)
>   isPKSideSimple:false
>   NDV Scaling Factor:1.00
> 15/01/29 11:48:04 [main]: DEBUG stats.HiveRelMdRowCount: Identified Primary - 
> Foreign Key relation:
> 15/01/29 11:48:04 [main]: DEBUG stats.HiveRelMdRowCount: 
> HiveJoin(condition=[=($8, $5)], joinType=[inner])
>   HiveJoin(condition=[=($0, $4)], joinType=[inner])
> HiveProject(l_orderkey=[$0], l_extendedprice=[$5], l_discount=[$6], 
> l_shipdate=[$10])
>   HiveFilter(condition=[>($10, '1995-03-15')])
> HiveTableScan(table=[[default.lineitem]])
> HiveProject(o_orderkey=[$0], o_custkey=[$1], o_orderdate=[$4], 
> o_shippriority=[$7])
>   HiveFil

[jira] [Moved] (HIVE-9510) Throwing null point exception , when get join distinct row count from RelMdUtil.java class

[Julian Hyde (JIRA)]

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

Julian Hyde moved CALCITE-578 to HIVE-9510:
---

Affects Version/s: (was: 1.0.0-incubating)
 Workflow: no-reopen-closed, patch-avail  (was: jira)
  Key: HIVE-9510  (was: CALCITE-578)
  Project: Hive  (was: Calcite)

> Throwing null point exception , when get join distinct row count from 
> RelMdUtil.java class
> --
>
> Key: HIVE-9510
> URL: https://issues.apache.org/jira/browse/HIVE-9510
> Project: Hive
>  Issue Type: Bug
>Reporter: asko
>    Assignee: Julian Hyde
> Attachments: log3_cbo5
>
>
> Setting log level in logging.properties file as following:
> handlers=java.util.logging.ConsoleHandler
> .level=INFO
> org.apache.calcite.plan.RelOptPlanner.level=ALL
> java.util.logging.ConsoleHandler.level=ALL
> Running Q3 in TPCH-full  after modifying , in order to  test join reorder,
> but running  failed.
> QL:
> set  hive.cbo.enable=true;
> --ANALYZE TABLE customer COMPUTE STATISTICS for columns;
> --ANALYZE TABLE orders COMPUTE STATISTICS for columns;
> --ANALYZE TABLE lineitem COMPUTE STATISTICS for columns;
> --Q3
> -- the query
> select 
>   l_orderkey, sum(l_extendedprice*(1-l_discount)) as revenue, o_orderdate, 
> o_shippriority 
> from 
>   lineitem l join orders o 
> on l.l_orderkey = o.o_orderkey
>   join customer c
> on c.c_mktsegment = 'BUILDING' and c.c_custkey = o.o_custkey 
> where 
>   o_orderdate < '1995-03-15' and l_shipdate > '1995-03-15' 
> group by l_orderkey, o_orderdate, o_shippriority 
> order by revenue desc, o_orderdate 
> limit 10;
> LOG:
> Jan 29, 2015 11:48:04 AM org.apache.calcite.plan.AbstractRelOptPlanner 
> fireRule
> FINE: call#15: Apply rule [FilterProjectTransposeRule] to 
> [rel#107:HiveFilter.HIVE.[](input=HepRelVertex#106,condition=<($2, 
> '1995-03-15')), 
> rel#105:HiveProject.HIVE.[](input=HepRelVertex#104,o_orderkey=$0,o_custkey=$1,o_orderdate=$4,o_shippriority=$7)]
> Jan 29, 2015 11:48:04 AM org.apache.calcite.rel.AbstractRelNode 
> FINEST: new HiveFilter#138
> Jan 29, 2015 11:48:04 AM org.apache.calcite.rel.AbstractRelNode 
> FINEST: new HiveProject#139
> Jan 29, 2015 11:48:04 AM org.apache.calcite.plan.AbstractRelOptPlanner 
> notifyTransformation
> FINE: call#15: Rule FilterProjectTransposeRule arguments 
> [rel#107:HiveFilter.HIVE.[](input=HepRelVertex#106,condition=<($2, 
> '1995-03-15')), 
> rel#105:HiveProject.HIVE.[](input=HepRelVertex#104,o_orderkey=$0,o_custkey=$1,o_orderdate=$4,o_shippriority=$7)]
>  produced HiveProject#139
> Jan 29, 2015 11:48:04 AM org.apache.calcite.rel.AbstractRelNode 
> FINEST: new HepRelVertex#140
> Jan 29, 2015 11:48:04 AM org.apache.calcite.rel.AbstractRelNode 
> FINEST: new HiveProject#141
> Jan 29, 2015 11:48:04 AM org.apache.calcite.rel.AbstractRelNode 
> FINEST: new HepRelVertex#142
> 15/01/29 11:48:04 [main]: DEBUG stats.HiveRelMdRowCount: Identified Primary - 
> Foreign Key relation:
> 15/01/29 11:48:04 [main]: DEBUG stats.HiveRelMdRowCount: 
> HiveJoin(condition=[=($0, $4)], joinType=[inner])
>   HiveProject(l_orderkey=[$0], l_extendedprice=[$5], l_discount=[$6], 
> l_shipdate=[$10])
> HiveFilter(condition=[>($10, '1995-03-15')])
>   HiveTableScan(table=[[default.lineitem]])
>   HiveProject(o_orderkey=[$0], o_custkey=[$1], o_orderdate=[$4], 
> o_shippriority=[$7])
> HiveFilter(condition=[<($4, '1995-03-15')])
>   HiveTableScan(table=[[default.orders]])
> 15/01/29 11:48:04 [main]: DEBUG stats.HiveRelMdRowCount: Primary - Foreign 
> Key join:
>   fkSide = 1
>   FKInfo:FKInfo(rowCount=1.00,ndv=-1.00)
>   PKInfo:PKInfo(rowCount=1.00,ndv=-1.00,selectivity=1.00)
>   isPKSideSimple:false
>   NDV Scaling Factor:1.00
> 15/01/29 11:48:04 [main]: DEBUG stats.HiveRelMdRowCount: Identified Primary - 
> Foreign Key relation:
> 15/01/29 11:48:04 [main]: DEBUG stats.HiveRelMdRowCount: 
> HiveJoin(condition=[=($8, $5)], joinType=[inner])
>   HiveJoin(condition=[=($0, $4)], joinType=[inner])
> HiveProject(l_orderkey=[$0], l_extendedprice=[$5], l_discount=[$6], 
> l_shipdate=[$10])
>   HiveFilter(condition=[>($10, '1995-03-15')])
> HiveTableScan(table=[[default.lineitem]])
> HiveProject(o_orderkey=[$0], o_custkey=[$1], o_orderdate=[$4], 
> o_shippriority=[$7])
>   HiveFilter(condition=[<($4, '1995-03-15')])
&

[jira] [Commented] (HIVE-9454) Test failures due to new Calcite version

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-9454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291459#comment-14291459
 ] 

Julian Hyde commented on HIVE-9454:
---

It's unfair to say I've been "using hive as a test bed". We have a test suite 
for Calcite that we're quite happy with. It serves its purpose -- it keeps 
Calcite from regressing.

You want to release Hive, so you need a release of Calcite. I am trying to do 
integration -- identify the incompatibilities between Hive and the new version 
of Calcite -- before we make that release. If that doesn't get done, you might 
well end up with a release of Calcite that is not suitable to make a release of 
Hive.

I have been telegraphing for some time on the Calcite dev list that a Calcite 
release is imminent. I made a release candidate on Thursday and started a vote. 
Given that Hive uses Calcite, at least one Hive committer ought to be actively 
participating on the Calcite dev list, participating in that vote, and doing 
integration testing.

The only integration testing that happened occurred because I pushed a new 
snapshot. That shit was going to hit the fan at some point between now and Hive 
15. It's actually a good thing that it happened now.

I'm coming round to the idea that it is a bad idea for Hive to develop on a 
snapshot of Calcite. But what are the alternatives? Given that it takes at 
least 6 days for an incubator project such as Calcite to make a release,  
development could very easily become stalled by a small bug or missing feature 
in Calcite. The ideal would be a Hive-specific snapshot of Calcite, controlled 
by Hive developers, but (a) Apache nexus doesn't seem to allow multiple 
versions of snapshots, (b) the Apache release process doesn't allow releases on 
snapshots, and (c) this would require proactive efforts by Hive committers to 
integrate with Calcite ahead of a Calcite release. Whatever we decide, it needs 
more proactive involvement from the Hive side.

There is an urgent need for a decision on the Calcite 1.0 release vote. We have 
sufficient votes for a release, and I could close the vote in just over an 
hour, but I won't. There is a non-binding -1 from [~jpullokkaran] due to 
incompatibilities but we haven't figured out whether the cause is on the Hive 
side or the Calcite side. I'd like to close the vote as soon as possible, but I 
need Hive developers to either log bugs or let the vote pass. "We haven't had 
time to do integration testing" (I'm paraphrasing a little) is not a valid 
reason for a -1.

> Test failures due to new Calcite version
> 
>
> Key: HIVE-9454
> URL: https://issues.apache.org/jira/browse/HIVE-9454
> Project: Hive
>  Issue Type: Bug
>Reporter: Brock Noland
> Attachments: HIVE-9454.1.patch
>
>
> A bunch of failures have started appearing in patches which seen unrelated. I 
> am thinking we've picked up a new version of Calcite. E.g.:
> http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/2488/testReport/org.apache.hadoop.hive.cli/TestCliDriver/testCliDriver_auto_join12/
> {noformat}
> Running: diff -a 
> /home/hiveptest/54.147.202.89-hiveptest-1/apache-svn-trunk-source/itests/qtest/../../itests/qtest/target/qfile-results/clientpositive/auto_join12.q.out
>  
> /home/hiveptest/54.147.202.89-hiveptest-1/apache-svn-trunk-source/itests/qtest/../../ql/src/test/results/clientpositive/auto_join12.q.out
> 32c32
> < $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> 35c35
> < $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:$hdt$_1:src 
> 39c39
> < $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> 54c54
> < $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:$hdt$_1:src 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-9454) Test failures due to new Calcite version

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-9454:
--
Attachment: HIVE-9454.1.patch

The attached patch (HIVE-9454.1.patch) works around CALCITE-566. It provides an 
executor so that constant-reduction rules can be executed.

The other test failures are, as far as I can tell, changes to generated plans 
and are either improvements or cosmetic changes. This patch does not fix those.

> Test failures due to new Calcite version
> 
>
> Key: HIVE-9454
> URL: https://issues.apache.org/jira/browse/HIVE-9454
> Project: Hive
>  Issue Type: Bug
>Reporter: Brock Noland
> Attachments: HIVE-9454.1.patch
>
>
> A bunch of failures have started appearing in patches which seen unrelated. I 
> am thinking we've picked up a new version of Calcite. E.g.:
> http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/2488/testReport/org.apache.hadoop.hive.cli/TestCliDriver/testCliDriver_auto_join12/
> {noformat}
> Running: diff -a 
> /home/hiveptest/54.147.202.89-hiveptest-1/apache-svn-trunk-source/itests/qtest/../../itests/qtest/target/qfile-results/clientpositive/auto_join12.q.out
>  
> /home/hiveptest/54.147.202.89-hiveptest-1/apache-svn-trunk-source/itests/qtest/../../ql/src/test/results/clientpositive/auto_join12.q.out
> 32c32
> < $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> 35c35
> < $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:$hdt$_1:src 
> 39c39
> < $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> 54c54
> < $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:$hdt$_1:src 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-9454) Test failures due to new Calcite version

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-9454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290207#comment-14290207
 ] 

Julian Hyde commented on HIVE-9454:
---

I've put back the old snapshot (from Dec 19th). So, these changes should go 
away.

These differences are a preview of what will happen when Hive moves to Calcite 
1.0.0. Calcite's RC1 vote is going on right now, and closes at 10pm Pacific on 
Sunday.

Can someone from Hive please evaluate the test failures and cast a 
(non-binding) vote? If you discover a show-stopper cast a -1 vote. I don't want 
to make a release that cannot be used. If issues are discovered after the vote 
has closed we won't be inclined to make a make a new release in a hurry. :)

> Test failures due to new Calcite version
> 
>
> Key: HIVE-9454
> URL: https://issues.apache.org/jira/browse/HIVE-9454
> Project: Hive
>  Issue Type: Bug
>Reporter: Brock Noland
>
> A bunch of failures have started appearing in patches which seen unrelated. I 
> am thinking we've picked up a new version of Calcite. E.g.:
> http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/2488/testReport/org.apache.hadoop.hive.cli/TestCliDriver/testCliDriver_auto_join12/
> {noformat}
> Running: diff -a 
> /home/hiveptest/54.147.202.89-hiveptest-1/apache-svn-trunk-source/itests/qtest/../../itests/qtest/target/qfile-results/clientpositive/auto_join12.q.out
>  
> /home/hiveptest/54.147.202.89-hiveptest-1/apache-svn-trunk-source/itests/qtest/../../ql/src/test/results/clientpositive/auto_join12.q.out
> 32c32
> < $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> 35c35
> < $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:$hdt$_1:src 
> 39c39
> < $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:$hdt$_0:src 
> 54c54
> < $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:src 
> ---
> > $hdt$_0:$hdt$_0:$hdt$_1:$hdt$_1:$hdt$_1:$hdt$_1:src 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-9441) Remove call to deprecated Calcite method

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288949#comment-14288949
 ] 

Julian Hyde commented on HIVE-9441:
---

Great. Now that patch is in, it should be trivial for Hive to upgrade from 
calcite-1.0-SNAPSHOT to calcite-1.0.0 when it is released. I started the PPMC 
vote today, so with luck 1.0 will be ready on 1/30.

> Remove call to deprecated Calcite method
> 
>
> Key: HIVE-9441
> URL: https://issues.apache.org/jira/browse/HIVE-9441
> Project: Hive
>  Issue Type: Bug
>    Reporter: Julian Hyde
>    Assignee: Julian Hyde
>Priority: Minor
> Fix For: 0.15.0
>
> Attachments: HIVE-9441.1.patch
>
>
> The method RexLiteral.byteValue() was deprecated and will be remove in 
> Calcite 1.0. The attached patch replaces it with a non-deprecated alternative.
> As soon as the patch is committed I will push to apache nexus a new 
> calcite-1.0.0-snapshot that will be very close to proposed calcite-1.0 
> release.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-9441) Remove call to deprecated Calcite method

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-9441:
--
Assignee: Ashutosh Chauhan
  Status: Patch Available  (was: Open)

> Remove call to deprecated Calcite method
> 
>
> Key: HIVE-9441
> URL: https://issues.apache.org/jira/browse/HIVE-9441
> Project: Hive
>  Issue Type: Bug
>    Reporter: Julian Hyde
>Assignee: Ashutosh Chauhan
>Priority: Minor
> Attachments: HIVE-9441.1.patch
>
>
> The method RexLiteral.byteValue() was deprecated and will be remove in 
> Calcite 1.0. The attached patch replaces it with a non-deprecated alternative.
> As soon as the patch is committed I will push to apache nexus a new 
> calcite-1.0.0-snapshot that will be very close to proposed calcite-1.0 
> release.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-9441) Remove call to deprecated Calcite method

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-9441:
--
Attachment: HIVE-9441.1.patch

> Remove call to deprecated Calcite method
> 
>
> Key: HIVE-9441
> URL: https://issues.apache.org/jira/browse/HIVE-9441
> Project: Hive
>  Issue Type: Bug
>    Reporter: Julian Hyde
>Priority: Minor
> Attachments: HIVE-9441.1.patch
>
>
> The method RexLiteral.byteValue() was deprecated and will be remove in 
> Calcite 1.0. The attached patch replaces it with a non-deprecated alternative.
> As soon as the patch is committed I will push to apache nexus a new 
> calcite-1.0.0-snapshot that will be very close to proposed calcite-1.0 
> release.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HIVE-9441) Remove call to deprecated Calcite method

[Julian Hyde (JIRA)]

Julian Hyde created HIVE-9441:
-

 Summary: Remove call to deprecated Calcite method
 Key: HIVE-9441
 URL: https://issues.apache.org/jira/browse/HIVE-9441
 Project: Hive
  Issue Type: Bug
Reporter: Julian Hyde
Priority: Minor


The method RexLiteral.byteValue() was deprecated and will be remove in Calcite 
1.0. The attached patch replaces it with a non-deprecated alternative.

As soon as the patch is committed I will push to apache nexus a new 
calcite-1.0.0-snapshot that will be very close to proposed calcite-1.0 release.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HIVE-9400) Upgrade parent POM

[Julian Hyde (JIRA)]

Julian Hyde created HIVE-9400:
-

 Summary: Upgrade parent POM
 Key: HIVE-9400
 URL: https://issues.apache.org/jira/browse/HIVE-9400
 Project: Hive
  Issue Type: Bug
Reporter: Julian Hyde


Upgrade Calcite's parent POM from apache-14 to apache-16. This will implicitly 
upgrade many of the dependencies, especially the maven plugins we use during 
the build process (e.g. surefire plugin).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Building Hive-0.14 is failing because artifact pentaho-aggdesigner-algorithm-5.1.3-jhyde could not be resolved

[Julian Hyde]

Conjars (http://conjars.org/) has all of these libraries. Calcite’s pom uses it:

  

  
true
always
warn
  
  conjars
  Conjars
  http://conjars.org/repo
  default

  

Julian


On Jan 6, 2015, at 3:45 PM, Ravi Prakash  wrote:

> Hi folks!
> I'm still stuck on this issue. Hopefully people are back from their vacations 
> and can now reply. Resending.
> 
> 
> On Monday, December 29, 2014 1:17 PM, Ravi Prakash  
> wrote:
> 
> 
> Hi folks!
> I'm still somewhat stuck on this issue. Could someone please guide me?
> I had to manually download these jars and put them into my ~/.m2/repository 
> from 
> http://repo.spring.io/libs-release/org/pentaho/pentaho-aggdesigner-algorithm/5.1.3-jhyde/
>  . (When I configured this repository, maven somehow still didn't find the 
> artifacts)
> I had to do this for the following 
> artifacts:http://repo.spring.io/libs-release/org/pentaho/pentaho-aggdesigner/5.1.3-jhyde/pentaho-aggdesigner-5.1.3-jhyde.pomhttp://repo.spring.io/libs-release/net/hydromatic/linq4j/0.4/linq4j-0.4.jarhttp://repo.spring.io/libs-release/net/hydromatic/quidem/0.1.1/quidem-0.1.1.pom
> Consequently I was able to build hive, however I don't believe this is a 
> kosher way of producing production binaries, so I am still waiting to hear 
> from you all. Is there another trusted repository I can try which has these 
> artifacts indexed?
> 
> ThanksRavi
> 
> 
> On Monday, December 22, 2014 2:14 PM, Ravi Prakash  
> wrote:
> 
> 
> Hi!
> Has anyone tried building Hive-0.14 from source? I'm using the tag for 
> release-0.14.0 https://github.com/apache/hive/releases/tag/release-0.14.0
> 
> The command I use is: mvn install -DskipTests -Phadoop-2 
> -DcreateChecksum=true -Dtez.version=0.5.3 -Dcalcite.version=0.9.2-incubating
> 
> The build fails for me with the following error:[ERROR] Failed to execute 
> goal on project hive-exec: Could not resolve dependencies for project 
> org.apache.hive:hive-exec:jar:0.14.0: The following artifacts could not be 
> resolved: org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.3-jhyde, 
> net.hydromatic:linq4j:jar:0.4, net.hydromatic:quidem:jar:0.1.1: Could not 
> find artifact org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.3-jhyde in 
> nexus (http://localhost:8081/nexus/content/groups/public) -> [Help 1]
> 
> This is a transitive dependency via the "calcite-0.9.2-incubating" artifact. 
> Is there a JIRA which someone can please point me to? It seems wrong that an 
> artifact with version "5.1.3-jhyde" is required to build Apache Hive, no 
> disrespect to Julian. Am I missing something?
> ThanksRavi
>  
> 
> 
> 
> 

[jira] [Commented] (HIVE-8988) Support advanced aggregation in Hive to Calcite path

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-8988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253730#comment-14253730
 ] 

Julian Hyde commented on HIVE-8988:
---

I've pushed a snapshot of Calcite that contains the fix to CALCITE-542.

> Support advanced aggregation in Hive to Calcite path 
> -
>
> Key: HIVE-8988
> URL: https://issues.apache.org/jira/browse/HIVE-8988
> Project: Hive
>  Issue Type: Improvement
>Affects Versions: 0.15.0
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>  Labels: grouping, logical, optiq
> Fix For: 0.15.0
>
> Attachments: HIVE-8988.01.patch, HIVE-8988.02.patch, 
> HIVE-8988.03.patch, HIVE-8988.04.patch, HIVE-8988.05.patch, 
> HIVE-8988.05.patch, HIVE-8988.patch
>
>
> CLEAR LIBRARY CACHE
> To close the gap between Hive and Calcite, we need to support the translation 
> of GroupingSets into Calcite; currently this is not implemented.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-9129) Migrate to newer Calcite snapshot, where ByteString is now in org.apache.calcite.avatica.util

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-9129:
--
Assignee: Ashutosh Chauhan
  Status: Patch Available  (was: Open)

> Migrate to newer Calcite snapshot, where ByteString is now in 
> org.apache.calcite.avatica.util
> -
>
> Key: HIVE-9129
> URL: https://issues.apache.org/jira/browse/HIVE-9129
> Project: Hive
>  Issue Type: Bug
>    Reporter: Julian Hyde
>Assignee: Ashutosh Chauhan
> Attachments: HIVE-9129.1.patch
>
>
> ByteString has moved from org.apache.calcite.avatica to 
> org.apache.calcite.avatica.util. To ease the migration, I have added a shim 
> method RexLiteral.byteValue(), so that ASTBuilder does not need to reference 
> ByteString explicitly.
> The attached patch allows Hive to run against 
> avatica-1.0.0-incubating-SNAPSHOT both before and after the change.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-9129) Migrate to newer Calcite snapshot, where ByteString is now in org.apache.calcite.avatica.util

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-9129:
--
Attachment: HIVE-9129.1.patch

> Migrate to newer Calcite snapshot, where ByteString is now in 
> org.apache.calcite.avatica.util
> -
>
> Key: HIVE-9129
> URL: https://issues.apache.org/jira/browse/HIVE-9129
> Project: Hive
>  Issue Type: Bug
>    Reporter: Julian Hyde
> Attachments: HIVE-9129.1.patch
>
>
> ByteString has moved from org.apache.calcite.avatica to 
> org.apache.calcite.avatica.util. To ease the migration, I have added a shim 
> method RexLiteral.byteValue(), so that ASTBuilder does not need to reference 
> ByteString explicitly.
> The attached patch allows Hive to run against 
> avatica-1.0.0-incubating-SNAPSHOT both before and after the change.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HIVE-9129) Migrate to newer Calcite snapshot, where ByteString is now in org.apache.calcite.avatica.util

[Julian Hyde (JIRA)]

Julian Hyde created HIVE-9129:
-

 Summary: Migrate to newer Calcite snapshot, where ByteString is 
now in org.apache.calcite.avatica.util
 Key: HIVE-9129
 URL: https://issues.apache.org/jira/browse/HIVE-9129
 Project: Hive
  Issue Type: Bug
Reporter: Julian Hyde


ByteString has moved from org.apache.calcite.avatica to 
org.apache.calcite.avatica.util. To ease the migration, I have added a shim 
method RexLiteral.byteValue(), so that ASTBuilder does not need to reference 
ByteString explicitly.

The attached patch allows Hive to run against avatica-1.0.0-incubating-SNAPSHOT 
both before and after the change.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-8988) Support advanced aggregation in Hive to Calcite path

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-8988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244585#comment-14244585
 ] 

Julian Hyde commented on HIVE-8988:
---

$Foo is probably not interesting to end-users, so let's keep it in Hive.  You 
should sub-class SqlInternalOperator. In SqlStdOperatorTable, you'll see 
$SLICE, $ELEMENT_SLICE, $SCALAR_QUERY and EXTEND are all examples of it.

> Support advanced aggregation in Hive to Calcite path 
> -
>
> Key: HIVE-8988
> URL: https://issues.apache.org/jira/browse/HIVE-8988
> Project: Hive
>  Issue Type: Improvement
>Affects Versions: 0.15.0
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>  Labels: grouping, logical, optiq
> Fix For: 0.15.0
>
> Attachments: HIVE-8988.01.patch, HIVE-8988.patch
>
>
> CLEAR LIBRARY CACHE
> To close the gap between Hive and Calcite, we need to support the translation 
> of GroupingSets into Calcite; currently this is not implemented.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-8988) Support advanced aggregation in Hive to Calcite path

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-8988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244535#comment-14244535
 ] 

Julian Hyde commented on HIVE-8988:
---

If I wrote {{select f(deptno, gender), count(*) from emp group by deptno, 
gender having f(deptno, gender) > 100}} and f was a "regular" function, then 
Calcite could push it down. And you'd probably want it to.

So we'd have to flag that "grouping_id" is not a regular function.

In my approach you apply the $Foo function to the indicator columns, which do 
not exist until the Aggregate creates them, hence the function cannot be pushed 
down. (The call to $Foo could still be pulled up.)

> Support advanced aggregation in Hive to Calcite path 
> -
>
> Key: HIVE-8988
> URL: https://issues.apache.org/jira/browse/HIVE-8988
> Project: Hive
>  Issue Type: Improvement
>Affects Versions: 0.15.0
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>  Labels: grouping, logical, optiq
> Fix For: 0.15.0
>
> Attachments: HIVE-8988.01.patch, HIVE-8988.patch
>
>
> CLEAR LIBRARY CACHE
> To close the gap between Hive and Calcite, we need to support the translation 
> of GroupingSets into Calcite; currently this is not implemented.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-8988) Support advanced aggregation in Hive to Calcite path

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-8988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244400#comment-14244400
 ] 

Julian Hyde commented on HIVE-8988:
---

It looks just like a function with no arguments, so Calcite will treat 
accordingly. 

You can't translate to grouping_id because that's a pseudo function too. Safest 
might be to translate it to {{$Foo(i0, i1, i2, i3, ...)}} where in are 
the indicator columns, and look for it afterwards. The column references will 
prevent it from being pushed down. Putatively $Foo would expand to {{i0 + 2 * 
i1 + 4 * i2 + ...}} (in fact the same logic that SqlToRelConverter translates 
GROUP_ID to) but it will be substituted before that ever happens.

> Support advanced aggregation in Hive to Calcite path 
> -
>
> Key: HIVE-8988
> URL: https://issues.apache.org/jira/browse/HIVE-8988
> Project: Hive
>  Issue Type: Improvement
>Affects Versions: 0.15.0
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>  Labels: grouping, logical, optiq
> Fix For: 0.15.0
>
> Attachments: HIVE-8988.01.patch, HIVE-8988.patch
>
>
> CLEAR LIBRARY CACHE
> To close the gap between Hive and Calcite, we need to support the translation 
> of GroupingSets into Calcite; currently this is not implemented.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-8988) Support advanced aggregation in Hive to Calcite path

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-8988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244310#comment-14244310
 ] 

Julian Hyde commented on HIVE-8988:
---

You'd better make sure that that function isn't pushed down.

> Support advanced aggregation in Hive to Calcite path 
> -
>
> Key: HIVE-8988
> URL: https://issues.apache.org/jira/browse/HIVE-8988
> Project: Hive
>  Issue Type: Improvement
>Affects Versions: 0.15.0
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>  Labels: grouping, logical, optiq
> Fix For: 0.15.0
>
> Attachments: HIVE-8988.01.patch, HIVE-8988.patch
>
>
> CLEAR LIBRARY CACHE
> To close the gap between Hive and Calcite, we need to support the translation 
> of GroupingSets into Calcite; currently this is not implemented.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-8988) Support advanced aggregation in Hive to Calcite path

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-8988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243533#comment-14243533
 ] 

Julian Hyde commented on HIVE-8988:
---

I am a bit surprised that translating GROUPING__ID to Calcite's GROUP_ID 
function works. The logic to expand it is in SqlToRelConverter, which Hive does 
not call (IIRC). How does it work?

You don't need to call BitSets.toIter anymore. ImmutableBitSet implements 
Iterable (BitSet, which we used to use for Aggregate.groupKeys, does not).

For {{ImmutableBitSet convert(int value)}}, I'll add 
ImmutableBitSet.valueOf(long...). valueOf(x) would be equivalent to convert(x). 
You can migrate to it in a future version of Calcite, if you like.

> Support advanced aggregation in Hive to Calcite path 
> -
>
> Key: HIVE-8988
> URL: https://issues.apache.org/jira/browse/HIVE-8988
> Project: Hive
>  Issue Type: Improvement
>Affects Versions: 0.15.0
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>  Labels: grouping, logical, optiq
> Fix For: 0.15.0
>
> Attachments: HIVE-8988.patch
>
>
> To close the gap between Hive and Calcite, we need to support the translation 
> of GroupingSets into Calcite; currently this is not implemented.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-8974) Upgrade to Calcite 1.0.0-SNAPSHOT (with lots of renames)

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-8974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233627#comment-14233627
 ] 

Julian Hyde commented on HIVE-8974:
---

I've pushed a new Calcite 1.0.0-SNAPSHOT so this bug should just go away next 
build.

> Upgrade to Calcite 1.0.0-SNAPSHOT (with lots of renames)
> 
>
> Key: HIVE-8974
> URL: https://issues.apache.org/jira/browse/HIVE-8974
> Project: Hive
>  Issue Type: Task
>Affects Versions: 0.15.0
>Reporter: Julian Hyde
>Assignee: Jesus Camacho Rodriguez
> Fix For: 0.15.0
>
> Attachments: HIVE-8974.01.patch, HIVE-8974.02.patch, 
> HIVE-8974.03.patch, HIVE-8974.patch
>
>
> CLEAR LIBRARY CACHE
> Calcite recently (after 0.9.2, before 1.0.0) re-organized its package 
> structure and renamed a lot of classes. CALCITE-296 has the details, 
> including a description of the before:after mapping.
> This task is to upgrade to the version of Calcite that has the renamed 
> packages. There is a 1.0.0-SNAPSHOT in Apache nexus.
> Calcite functionality has not changed significantly, so it should be 
> straightforward to rename. This task should be completed ASAP, before Calcite 
> moves on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-8974) Upgrade to Calcite 1.0.0-SNAPSHOT (with lots of renames)

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-8974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1424#comment-1424
 ] 

Julian Hyde commented on HIVE-8974:
---

Yes, it's a calcite problem. I've logged 
https://issues.apache.org/jira/browse/CALCITE-509 and will fix shortly.

> Upgrade to Calcite 1.0.0-SNAPSHOT (with lots of renames)
> 
>
> Key: HIVE-8974
> URL: https://issues.apache.org/jira/browse/HIVE-8974
> Project: Hive
>  Issue Type: Task
>Affects Versions: 0.15.0
>Reporter: Julian Hyde
>Assignee: Jesus Camacho Rodriguez
> Fix For: 0.15.0
>
> Attachments: HIVE-8974.01.patch, HIVE-8974.02.patch, 
> HIVE-8974.03.patch, HIVE-8974.patch
>
>
> CLEAR LIBRARY CACHE
> Calcite recently (after 0.9.2, before 1.0.0) re-organized its package 
> structure and renamed a lot of classes. CALCITE-296 has the details, 
> including a description of the before:after mapping.
> This task is to upgrade to the version of Calcite that has the renamed 
> packages. There is a 1.0.0-SNAPSHOT in Apache nexus.
> Calcite functionality has not changed significantly, so it should be 
> straightforward to rename. This task should be completed ASAP, before Calcite 
> moves on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 28510: HIVE-8974

[Julian Hyde]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28510/#review63433
---

Ship it!


Ship It!

- Julian Hyde


On Nov. 27, 2014, 2:37 p.m., Jesús Camacho Rodríguez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28510/
> ---
> 
> (Updated Nov. 27, 2014, 2:37 p.m.)
> 
> 
> Review request for hive, John Pullokkaran and Julian Hyde.
> 
> 
> Bugs: HIVE-8974
> https://issues.apache.org/jira/browse/HIVE-8974
> 
> 
> Repository: hive-git
> 
> 
> Description
> ---
> 
> Upgrade to Calcite 1.0.0-SNAPSHOT
> 
> 
> Diffs
> -
> 
>   pom.xml 630b10ce35032e4b2dee50ef3dfe5feb58223b78 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/calcite/reloperators/HiveAggregate.java
>  PRE-CREATION 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/HiveDefaultRelMetadataProvider.java
>  e9e052ffe8759fa9c49377c58d41450feee0b126 
>   ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/HiveOptiqUtil.java 
> 80f657e9b1e7e9e965e6814ae76de78316367135 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/HiveTypeSystemImpl.java 
> 1bc5a2cfca071ea02a446ae517481f927193f23c 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/OptiqSemanticException.java
>  d2b08fa64b868942b7636df171ed89f0081f7253 
>   ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/RelOptHiveTable.java 
> 080d27fa873f071fb2e0f7932ad26819b79d0477 
>   ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/TraitsUtil.java 
> 4b44a28ca77540fd643fc03b89dcb4b2155d081a 
>   ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/cost/HiveCost.java 
> 72fe5d6f26d0fd9a34c8e89be3040cce4593fd4a 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/cost/HiveCostUtil.java 
> 7436f12f662542c41e71a7fee37179e35e4e2553 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/cost/HiveVolcanoPlanner.java
>  5deb801649f47e0629b3583ef57c62d4a4699f78 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/reloperators/HiveAggregateRel.java
>  fc198958735e12cb3503a0b4c486d8328a10a2fa 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/reloperators/HiveFilterRel.java
>  8b850463ac1c3270163725f876404449ef8dc5f9 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/reloperators/HiveJoinRel.java
>  3d6aa848cd4c83ec8eb22f7df449911d67a53b9b 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/reloperators/HiveLimitRel.java
>  f8755d0175c10e5b5461649773bf44abe998b44e 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/reloperators/HiveProjectRel.java
>  7b434ea58451bef6a6566eb241933843ee855606 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/reloperators/HiveRel.java
>  4738c4ac2d33cd15d2db7fe4b8336e1f59dd5212 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/reloperators/HiveSortRel.java
>  f85363d50c1c3eb9cef39072106057669454d4da 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/reloperators/HiveTableScanRel.java
>  bd66459def099df6432f344a9d8439deef09daa6 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/reloperators/HiveUnionRel.java
>  d34fe9540e239c13f6bd23894056305c0c402e0d 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/rules/HiveMergeProjectRule.java
>  d6581e64fc8ea183666ea6c91397378456461088 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/rules/HivePartitionPrunerRule.java
>  ee19a6cbab0597242214e915745631f76214f70f 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/rules/HivePushFilterPastJoinRule.java
>  1c483eabcc1aa43cc80d7b71e21a4ae4d30a7e12 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/rules/PartitionPruner.java
>  bdc8373877c1684855d256c9d45743f383fc7615 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/stats/FilterSelectivityEstimator.java
>  28bf2ad506656b78894467c30364d751b180676e 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/stats/HiveRelMdDistinctRowCount.java
>  4be57b110c1a45819467d55e8a69e5529989c8f6 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/stats/HiveRelMdRowCount.java
>  8c7f643940b74dd7743635c3eaa046d52d41346f 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/stats/HiveRelMdSelectivity.java
>  49d2ee5a67b72fbf6134ce71de1d7260069cd16f 
>   
> ql/src/java/org/apache/hadoop/hive/ql/optimizer/optiq/stats/HiveRelMdUniqueKeys.java
>  c3c8bdd2466b0f46d49437fcf8d49dbb689cf

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--
Status: Open  (was: Patch Available)

> 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.2.patch, HIVE-6361.3.patch, 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.3.4#6332)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--
Affects Version/s: (was: 0.12.0)
   0.14.0
   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.14.0
>    Reporter: Julian Hyde
>Assignee: Julian Hyde
> Attachments: HIVE-6361.2.patch, HIVE-6361.3.patch, HIVE-6361.4.patch, 
> 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.3.4#6332)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--
Attachment: HIVE-6361.4.patch

> 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.2.patch, HIVE-6361.3.patch, HIVE-6361.4.patch, 
> 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.3.4#6332)

[jira] [Created] (HIVE-8974) Upgrade to Calcite 1.0.0-SNAPSHOT (with lots of renames)

[Julian Hyde (JIRA)]

Julian Hyde created HIVE-8974:
-

 Summary: Upgrade to Calcite 1.0.0-SNAPSHOT (with lots of renames)
 Key: HIVE-8974
 URL: https://issues.apache.org/jira/browse/HIVE-8974
 Project: Hive
  Issue Type: Task
Reporter: Julian Hyde
Assignee: Gunther Hagleitner


Calcite recently (after 0.9.2, before 1.0.0) re-organized its package structure 
and renamed a lot of classes. CALCITE-296 has the details, including a 
description of the before:after mapping.

This task is to upgrade to the version of Calcite that has the renamed 
packages. There is a 1.0.0-SNAPSHOT in Apache nexus.

Calcite functionality has not changed significantly, so it should be 
straightforward to rename. This task should be completed ASAP, before Calcite 
moves on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

 [ 
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.2.patch, HIVE-6361.3.patch, 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.3.4#6332)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--
Attachment: HIVE-6361.3.patch

> 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.2.patch, HIVE-6361.3.patch, 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.3.4#6332)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--
Status: Open  (was: Patch Available)

> 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.2.patch, 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.3.4#6332)

sqlline as a sub-project

[Julian Hyde]

DB group,

I am exploring the possibility of making sqlline an Apache DB sub-project.

Sqlline is a JDBC shell along the lines of Oracle's SQL*Plus and
Derby's ij, but it is generic: it works with any JDBC driver. It was
founded about 10 years ago, and was forked (without malice) into Hive
as beeline and into my github project
https://github.com/julianhyde/sqlline. Both forks have seen reasonable
use (Hive's by the Hive community, and mine by Drill, Phoenix,
Cascading among others), ongoing development activity, and regular
releases.

I am currently undertaking the painful task of "un-forking" --
producing a development line that contains the union of all patches,
without unnecessary dependencies such as Hive. The Hive-dependent
pieces of beeline would remain in sub-classes in beeline. See
https://issues.apache.org/jira/browse/HIVE-6361 for details. For
pragmatic reasons, I will be un-forking into a new Hive module,
org.apache.hive.sqlline.

But there is a concern that the project will over time become too
dependent on Hive. Even if we commit to not introduce dependencies,
perception is reality. Also, project development would have to occur
on Hive's (very busy) dev list, and, pragmatically, its releases would
have to be synchronized with Hive's releases.

As a sub-project of DB, sqlline could continue to be developed in the
Apache way but with more room to breathe.

Do you think sqlline would be a good fit as a DB sub-project?

Julian

[jira] [Resolved] (HIVE-8857) hive release has SNAPSHOT dependency, which is not on maven central

[Julian Hyde (JIRA)]

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

Julian Hyde resolved HIVE-8857.
---
Resolution: Duplicate

> hive release has SNAPSHOT dependency, which is not on maven central
> ---
>
> Key: HIVE-8857
> URL: https://issues.apache.org/jira/browse/HIVE-8857
> Project: Hive
>  Issue Type: Bug
>Affects Versions: 0.14.0
>Reporter: André Kelpe
>
> I just tried building a project, which uses hive-exec as a dependency and it 
> bails out, since hive 0.14.0 introduced a SNAPSHOT dependency to apache 
> calcite, which is not on maven central. Do we have to include another 
> repository now? Next to that it also seems problematic to rely on a SNAPSHOT 
> dependency, which can change any time.
> {code}
> :compileJava
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/hive-exec/0.14.0/hive-exec-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/hive/0.14.0/hive-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/hive-ant/0.14.0/hive-ant-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/hive-metastore/0.14.0/hive-metastore-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/hive-shims/0.14.0/hive-shims-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom
> Download 
> http://repo1.maven.org/maven2/org/fusesource/jansi/jansi-project/1.11/jansi-project-1.11.pom
> Download 
> http://repo1.maven.org/maven2/org/fusesource/fusesource-pom/1.8/fusesource-pom-1.8.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/hive-serde/0.14.0/hive-serde-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/shims/hive-shims-common/0.14.0/hive-shims-common-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/shims/hive-shims-common-secure/0.14.0/hive-shims-common-secure-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/shims/hive-shims-0.20/0.14.0/hive-shims-0.20-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/shims/hive-shims-0.20S/0.14.0/hive-shims-0.20S-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/shims/hive-shims-0.23/0.14.0/hive-shims-0.23-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/hive-common/0.14.0/hive-common-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/curator/curator-framework/2.6.0/curator-framework-2.6.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/curator/apache-curator/2.6.0/apache-curator-2.6.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/curator/curator-client/2.6.0/curator-client-2.6.0.pom
> Download 
> http://repo1.maven.org/maven2/org/slf4j/slf4j-api/1.7.6/slf4j-api-1.7.6.pom
> Download 
> http://repo1.maven.org/maven2/org/slf4j/slf4j-parent/1.7.6/slf4j-parent-1.7.6.pom
> FAILURE: Build failed with an exception.
> * What went wrong:
> Could not resolve all dependencies for configuration ':provided'.
> > Could not find org.apache.calcite:calcite-core:0.9.2-incubating-SNAPSHOT.
>   Required by:
>   cascading:cascading-hive:1.1.0-wip-dev > 
> org.apache.hive:hive-exec:0.14.0
> > Could not find org.apache.calcite:calcite-avatica:0.9.2-incubating-SNAPSHOT.
>   Required by:
>   cascading:cascading-hive:1.1.0-wip-dev > 
> org.apache.hive:hive-exec:0.14.0
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
> BUILD FAILED
> Total time: 16.956 secs
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-8857) hive release has SNAPSHOT dependency, which is not on maven central

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-8857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222860#comment-14222860
 ] 

Julian Hyde commented on HIVE-8857:
---

Calcite 0.9.2-incubating was released shortly after Hive 0.14 froze, having 
spent ~6 days in the voting process. It is virtually identical to the 
0.9.2-incubating-SNAPSHOT posted at 
https://repository.apache.org/content/repositories/snapshots/org/apache/calcite/,
 so you could drop it in as a replacement.

> hive release has SNAPSHOT dependency, which is not on maven central
> ---
>
> Key: HIVE-8857
> URL: https://issues.apache.org/jira/browse/HIVE-8857
> Project: Hive
>  Issue Type: Bug
>Affects Versions: 0.14.0
>Reporter: André Kelpe
>
> I just tried building a project, which uses hive-exec as a dependency and it 
> bails out, since hive 0.14.0 introduced a SNAPSHOT dependency to apache 
> calcite, which is not on maven central. Do we have to include another 
> repository now? Next to that it also seems problematic to rely on a SNAPSHOT 
> dependency, which can change any time.
> {code}
> :compileJava
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/hive-exec/0.14.0/hive-exec-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/hive/0.14.0/hive-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/hive-ant/0.14.0/hive-ant-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/hive-metastore/0.14.0/hive-metastore-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/hive-shims/0.14.0/hive-shims-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom
> Download 
> http://repo1.maven.org/maven2/org/fusesource/jansi/jansi-project/1.11/jansi-project-1.11.pom
> Download 
> http://repo1.maven.org/maven2/org/fusesource/fusesource-pom/1.8/fusesource-pom-1.8.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/hive-serde/0.14.0/hive-serde-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/shims/hive-shims-common/0.14.0/hive-shims-common-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/shims/hive-shims-common-secure/0.14.0/hive-shims-common-secure-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/shims/hive-shims-0.20/0.14.0/hive-shims-0.20-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/shims/hive-shims-0.20S/0.14.0/hive-shims-0.20S-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/shims/hive-shims-0.23/0.14.0/hive-shims-0.23-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/hive/hive-common/0.14.0/hive-common-0.14.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/curator/curator-framework/2.6.0/curator-framework-2.6.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/curator/apache-curator/2.6.0/apache-curator-2.6.0.pom
> Download 
> http://repo1.maven.org/maven2/org/apache/curator/curator-client/2.6.0/curator-client-2.6.0.pom
> Download 
> http://repo1.maven.org/maven2/org/slf4j/slf4j-api/1.7.6/slf4j-api-1.7.6.pom
> Download 
> http://repo1.maven.org/maven2/org/slf4j/slf4j-parent/1.7.6/slf4j-parent-1.7.6.pom
> FAILURE: Build failed with an exception.
> * What went wrong:
> Could not resolve all dependencies for configuration ':provided'.
> > Could not find org.apache.calcite:calcite-core:0.9.2-incubating-SNAPSHOT.
>   Required by:
>   cascading:cascading-hive:1.1.0-wip-dev > 
> org.apache.hive:hive-exec:0.14.0
> > Could not find org.apache.calcite:calcite-avatica:0.9.2-incubating-SNAPSHOT.
>   Required by:
>   cascading:cascading-hive:1.1.0-wip-dev > 
> org.apache.hive:hive-exec:0.14.0
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
> BUILD FAILED
> Total time: 16.956 secs
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Propose to put JIRA traffic on separate hive list

[Julian Hyde]

+1 to only have JIRA creations on the dev list.

(I only just heard about Alan's proposal because... ironically... I am
not on the list. I joined once, and unsubscribed 18 hours later.)

I would like to be a "casual contributor" to Hive. I work on other
related projects, some of them in Apache, and would like to contribute
the occasional patch, and assist others working on Hive issues, so I'd
like to know what's going on in Hive that is in my areas of interest.
But I don't have the bandwidth to delete ~100 messages a day. I fear
that the current message volume is such that only professionals --
paid software developers who work full-time on Hive -- can keep up.

This proposal will help make Hive a more diverse and inclusive community.

Julian

[jira] [Commented] (HIVE-8656) CBO: auto_join_filters fails

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14193577#comment-14193577
 ] 

Julian Hyde commented on HIVE-8656:
---

I have updated CALCITE-448's description, and have (finally) found a repro case 
in pure Calcite. I think it is a minor issue, now that TypeConverter has been 
fixed in Hive.

> CBO: auto_join_filters fails
> 
>
> Key: HIVE-8656
> URL: https://issues.apache.org/jira/browse/HIVE-8656
> Project: Hive
>  Issue Type: Sub-task
>  Components: CBO
>Reporter: Sergey Shelukhin
>Assignee: Julian Hyde
>Priority: Critical
> Fix For: 0.14.0
>
> Attachments: HIVE-8656.patch
>
>
> Haven't looked why yet



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-8656) CBO: auto_join_filters fails

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-8656:
--
Attachment: HIVE-8656.patch

> CBO: auto_join_filters fails
> 
>
> Key: HIVE-8656
> URL: https://issues.apache.org/jira/browse/HIVE-8656
> Project: Hive
>  Issue Type: Sub-task
>  Components: CBO
>Reporter: Sergey Shelukhin
>Assignee: Ashutosh Chauhan
>Priority: Critical
> Fix For: 0.14.0
>
> Attachments: HIVE-8656.patch
>
>
> Haven't looked why yet



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-8656) CBO: auto_join_filters fails

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192746#comment-14192746
 ] 

Julian Hyde commented on HIVE-8656:
---

I suspect that CALCITE-448 is (despite its title) a subtle issue in 
PushFiltersThroughJoinRule. If we patch TypeConverter.java to make all columns 
nullable (what we intended anyway) the issue goes away. See attached.

> CBO: auto_join_filters fails
> 
>
> Key: HIVE-8656
> URL: https://issues.apache.org/jira/browse/HIVE-8656
> Project: Hive
>  Issue Type: Sub-task
>  Components: CBO
>Reporter: Sergey Shelukhin
>Assignee: Ashutosh Chauhan
>Priority: Critical
> Fix For: 0.14.0
>
>
> Haven't looked why yet



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-8657) CBO: inputddl5, udf_reverse tests fail

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14189084#comment-14189084
 ] 

Julian Hyde commented on HIVE-8657:
---

I suspect that the Hive-to-Calcite is generating a RexLiteral (possibly a 
SqlLiteral) for a character literal, and that that character literal contains 
Unicode (i.e. non-ASCII) characters. Fix might be to catch the exception and 
create the literal using unicode as the encoding.

Note that in a RexLiteral of type CHAR or VARCHAR, the value object must be of 
type NlsString, and that contains a Java string (in unicode as always), a 
java.nio.charset.Charset, and a SqlCollation.

It should be clearer what to do when we see the call-stack.

> CBO: inputddl5, udf_reverse tests fail
> --
>
> Key: HIVE-8657
> URL: https://issues.apache.org/jira/browse/HIVE-8657
> Project: Hive
>  Issue Type: Sub-task
>  Components: CBO
>Reporter: Sergey Shelukhin
> Fix For: 0.14.0
>
>
> Exception in Hive logs (I spent all of 20 seconds looking at this for now)
> {noformat}
> 2014-10-29 13:27:34,019 ERROR ql.Driver (SessionState.java:printError(825)) - 
> FAILED: EigenbaseException Failed to encode '??' in character set 'ISO-8859-1'
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-8467) Table Copy - Background, incremental data load

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-8467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172767#comment-14172767
 ] 

Julian Hyde commented on HIVE-8467:
---

I see this as a particular kind of materialized view. In general, a 
materialized view is a table whose contents are guaranteed to be the same as 
executing a particular query. In this case, that query is simply 'select * from 
t'.

We don't have materialized view support yet, but I have been working on 
lattices in Calcite (formerly known as Optiq) (see OPTIQ-344) and there is a 
lot of interest in adding them to Hive. Each materialized "tile" in a lattice 
is a materialized view of the form 'select d1, d2, sum(m1), count(m2) from t 
group by d1, d2'.

So, let's talk about whether we could change the syntax to 'create materialized 
view'  and still deliver the functionality you need. Of course if the user 
enters anything other than 'select * from t order by k1, k2' they would get an 
error.

In terms of query planning, I strongly recommend that you build on the CBO work 
powered by Calcite. Let's suppose there is a table T and a copy C. After 
translating the query to a Calcite RelNode tree, there will be a 
TableAccessRel(T). After reading the metadata, we should create a 
TableAccessRel(C) and tell Calcite that it is equivalent.

That's all you need to do. Calcite will take it from there. Assuming the stats 
indicate that C is better (and they should, right, because the ORC 
representation will be smaller?) then the query will end up using C. But if, 
say, T has a partitioning scheme which is more suitable for a particular query, 
then Calcite will choose T.

> Table Copy - Background, incremental data load
> --
>
> Key: HIVE-8467
> URL: https://issues.apache.org/jira/browse/HIVE-8467
> Project: Hive
>  Issue Type: New Feature
>Reporter: Rajat Venkatesh
> Attachments: Table Copies.pdf
>
>
> Traditionally, Hive and other tools in the Hadoop eco-system havent required 
> a load stage. However, with recent developments, Hive is much more performant 
> when data is stored in specific formats like ORC, Parquet, Avro etc. 
> Technologies like Presto, also work much better with certain data formats. At 
> the same time, data is generated or obtained from 3rd parties in non-optimal 
> formats such as CSV, tab-limited or JSON. Many a times, its not an option to 
> change the data format at the source. We've found that users either use 
> sub-optimal formats or spend a large amount of effort creating and 
> maintaining copies. We want to propose a new construct - Table Copy - to help 
> “load” data into an optimal storage format.
> I am going to attach a PDF document with a lot more details especially 
> addressing how is this different from bulk loads in relational DBs or 
> materialized views.
> Looking forward to hear if others see a similar need to formalize conversion 
> of data to different storage formats.  If yes, are the details in the PDF 
> document a good start ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-8336) Update pom, now that Optiq is renamed to Calcite

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-8336:
--
Assignee: Gunther Hagleitner
  Status: Patch Available  (was: Open)

A snapshot of org.apache.calcite 
https://github.com/apache/incubator-optiq/commit/3c4b5982daa318660b989f37905455f3ad74863d
 is deployed to nexus. It is now safe to update hive.

> Update pom, now that Optiq is renamed to Calcite
> 
>
> Key: HIVE-8336
> URL: https://issues.apache.org/jira/browse/HIVE-8336
> Project: Hive
>  Issue Type: Bug
>    Reporter: Julian Hyde
>Assignee: Gunther Hagleitner
> Attachments: HIVE-8336.1.patch
>
>
> Apache Optiq is in the process of renaming to Apache Calcite. See INFRA-8413 
> and OPTIQ-430.
> There is not yet a snapshot of {groupId: 'org.apache.calcite', artifactId: 
> 'calcite-*'} deployed to nexus. When there is, I'll post a patch to pom.xml.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-8336) Update pom, now that Optiq is renamed to Calcite

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-8336:
--
Attachment: HIVE-8336.1.patch

> Update pom, now that Optiq is renamed to Calcite
> 
>
> Key: HIVE-8336
> URL: https://issues.apache.org/jira/browse/HIVE-8336
> Project: Hive
>  Issue Type: Bug
>    Reporter: Julian Hyde
> Attachments: HIVE-8336.1.patch
>
>
> Apache Optiq is in the process of renaming to Apache Calcite. See INFRA-8413 
> and OPTIQ-430.
> There is not yet a snapshot of {groupId: 'org.apache.calcite', artifactId: 
> 'calcite-*'} deployed to nexus. When there is, I'll post a patch to pom.xml.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-8336) Update pom, now that Optiq is renamed to Calcite

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-8336:
--
Description: 
Apache Optiq is in the process of renaming to Apache Calcite. See INFRA-8413 
and OPTIQ-430.

There is not yet a snapshot of {groupId: 'org.apache.calcite', artifactId: 
'calcite-*'} deployed to nexus. When there is, I'll post a patch to pom.xml.

  was:
Apache Optiq is in the process of renaming to Apache Calcite. See INFRA-8413 
and OPTIQ-430.

There is not yet a snapshot of {groupId: 'org.apache.calcite', 'calcite-*'} 
deployed to nexus. When there is, I'll post a patch to pom.xml.


> Update pom, now that Optiq is renamed to Calcite
> 
>
> Key: HIVE-8336
> URL: https://issues.apache.org/jira/browse/HIVE-8336
> Project: Hive
>  Issue Type: Bug
>Reporter: Julian Hyde
>
> Apache Optiq is in the process of renaming to Apache Calcite. See INFRA-8413 
> and OPTIQ-430.
> There is not yet a snapshot of {groupId: 'org.apache.calcite', artifactId: 
> 'calcite-*'} deployed to nexus. When there is, I'll post a patch to pom.xml.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HIVE-8336) Update pom, now that Optiq is renamed to Calcite

[Julian Hyde (JIRA)]

Julian Hyde created HIVE-8336:
-

 Summary: Update pom, now that Optiq is renamed to Calcite
 Key: HIVE-8336
 URL: https://issues.apache.org/jira/browse/HIVE-8336
 Project: Hive
  Issue Type: Bug
Reporter: Julian Hyde


Apache Optiq is in the process of renaming to Apache Calcite. See INFRA-8413 
and OPTIQ-430.

There is not yet a snapshot of {groupId: 'org.apache.calcite', 'calcite-*'} 
deployed to nexus. When there is, I'll post a patch to pom.xml.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: HIVE-6361.2.patch

> 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.2.patch, 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

 [ 
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)

Attached, patch HIVE-6361.2.patch, commit c96a790, parent 253a869.

> 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.2.patch, 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Status: Open  (was: Patch Available)

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Status: Open  (was: Patch Available)

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: HIVE-6361.patch

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: (was: HIVE-6361.patch)

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

 [ 
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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

 [ 
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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Status: Open  (was: Patch Available)

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

 [ 
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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: HIVE-6361.patch

Attaching patch, commit 2e84999, parent 253a869.

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Status: Open  (was: Patch Available)

> 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
>
> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: (was: HIVE-6361.patch)

> 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
>
> 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)

[jira] [Commented] (HIVE-7680) Do not throw SQLException for HiveStatement getMoreResults and setEscapeProcessing(false)

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14104490#comment-14104490
 ] 

Julian Hyde commented on HIVE-7680:
---

A stackoverflow thread [What does it mean when Statement.executeUpdate returns 
-1?|http://stackoverflow.com/questions/12400985/what-does-it-mean-when-statement-executeupdate-returns-1]
 is basically supportive of the idea of returning -1. In particular this 
comment:

{quote}
UPDATE: While reading [Mark Rotteveel's 
answer|http://stackoverflow.com/a/12412073/521799], I tend to agree with him, 
assuming that -1 is the JDBC-compliant value for "unknown update counts". Even 
if this isn't documented on the relevant method's Javadoc, it's documented in 
the [JDBC specs, chapter 13.1.2.3 Returning Unknown or Multiple 
Results|http://download.oracle.com/otn-pub/jcp/jdbc-4_1-mrel-spec/jdbc4.1-fr-spec.pdf].
 In this very case, it could be said that an IF .. INSERT .. statement will 
have an "unknown update count", as this statement isn't SQL-standard compliant 
anyway.
{quote}

> Do not throw SQLException for HiveStatement getMoreResults and 
> setEscapeProcessing(false)
> -
>
> Key: HIVE-7680
> URL: https://issues.apache.org/jira/browse/HIVE-7680
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Affects Versions: 0.13.1
>Reporter: Alexander Pivovarov
>Assignee: Alexander Pivovarov
>Priority: Minor
> Attachments: HIVE-7680.patch
>
>
> 1. Some JDBC clients call method setEscapeProcessing(false)  (e.g. SQL 
> Workbench)
> Looks like setEscapeProcessing(false) should do nothing.So, lets do  nothing 
> instead of throwing SQLException
> 2. getMoreResults is needed in case Statements returns several ReseltSet.
> Hive does not support Multiple ResultSets. So this method can safely always 
> return false.
> 3. getUpdateCount. Currently this method always returns 0. Hive cannot tell 
> us how many rows were inserted. According to JDBC spec it should return " -1 
> if the current result is a ResultSet object or there are no more results" 
> if this method returns 0 then in case of execution insert statement JDBC 
> client shows "0 rows were inserted" which is not true.
> if this method returns -1 then JDBC client runs insert statements and  shows 
> that it was executed successfully, no result were returned. 
> I think the latter behaviour is more correct.
> 4. Some methods in Statement class should throw 
> SQLFeatureNotSupportedException if they are not supported.  Current 
> implementation throws SQLException instead which means database access error.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

 [ 
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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Status: Open  (was: Patch Available)

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

 [ 
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)

Attaching re-based patch. Commit db5e7181d329331d76d6d53741beb87b44f5263f, 
parent commit 253a869dc62c7d36b1020a70932ddd35cb44cb81.

> 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
>
> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: (was: HIVE-6361.patch)

> 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
>
> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Status: Open  (was: Patch Available)

> 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
>
> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: HIVE-6361.patch

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: HIVE-6361.patch

New patch attached.

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

 [ 
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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Status: Open  (was: Patch Available)

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: (was: HIVE-6361.patch)

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: HIVE-6361.patch

Add patch based on 21390db. Corresponds to 
https://github.com/julianhyde/hive/commit/ebe89fe8f93bfeb7976451eea8549acf3422b58f.

Fixes compile error in TestBeeLineWithArgs.java, and adds missing 
BeeLine.properties.

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

 [ 
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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Status: Open  (was: Patch Available)

> 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
>
> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: (was: HIVE-6361.patch)

> 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
>
> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: HIVE-6361.patch

Patch based on 21390db.

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Status: Open  (was: Patch Available)

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: (was: 0001-HIVE-6361-Un-fork-Sqlline.patch)

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

 [ 
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)

See attached, patch based on 21390db.

> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

 [ 
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: 0001-HIVE-6361-Un-fork-Sqlline.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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: 0001-HIVE-6361-Un-fork-Sqlline.patch

This is a combined patch based on trunk 21390db.

> 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: 0001-HIVE-6361-Un-fork-Sqlline.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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Status: Open  (was: Patch Available)

> 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
>
> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: (was: 
0004-Apply-to-SqlLine-commits-made-to-BeeLine-in-trunk-ov.patch)

> 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
>
> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: (was: 
0002-Refactor-SqlLine-into-org.apache.hive.sqlline-packag.patch)

> 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
>
> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: (was: 
0001-Copy-https-github.com-julianhyde-sqlline-as-new-modu.patch)

> 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
>
> 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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: (was: 0003-Merge-beeline-package-into-sqlline.patch)

> 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
>
> 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)

[jira] [Commented] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095682#comment-14095682
 ] 

Julian Hyde commented on HIVE-6361:
---

I've attached patches.

The patches are based on the 4 commits in the git branch 
https://github.com/julianhyde/hive/commits/sqlline-4. However if you want to 
see how each individual Hive commit was applied, see the un-squashed branch 
https://github.com/julianhyde/hive/commits/sqlline-0.

> 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
> Attachments: 
> 0001-Copy-https-github.com-julianhyde-sqlline-as-new-modu.patch, 
> 0002-Refactor-SqlLine-into-org.apache.hive.sqlline-packag.patch, 
> 0003-Merge-beeline-package-into-sqlline.patch, 
> 0004-Apply-to-SqlLine-commits-made-to-BeeLine-in-trunk-ov.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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

 [ 
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
> Attachments: 
> 0001-Copy-https-github.com-julianhyde-sqlline-as-new-modu.patch, 
> 0002-Refactor-SqlLine-into-org.apache.hive.sqlline-packag.patch, 
> 0003-Merge-beeline-package-into-sqlline.patch, 
> 0004-Apply-to-SqlLine-commits-made-to-BeeLine-in-trunk-ov.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)

[jira] [Updated] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

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

Julian Hyde updated HIVE-6361:
--

Attachment: 0004-Apply-to-SqlLine-commits-made-to-BeeLine-in-trunk-ov.patch
0003-Merge-beeline-package-into-sqlline.patch
0002-Refactor-SqlLine-into-org.apache.hive.sqlline-packag.patch
0001-Copy-https-github.com-julianhyde-sqlline-as-new-modu.patch

> 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
> Attachments: 
> 0001-Copy-https-github.com-julianhyde-sqlline-as-new-modu.patch, 
> 0002-Refactor-SqlLine-into-org.apache.hive.sqlline-packag.patch, 
> 0003-Merge-beeline-package-into-sqlline.patch, 
> 0004-Apply-to-SqlLine-commits-made-to-BeeLine-in-trunk-ov.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)

[jira] [Commented] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086594#comment-14086594
 ] 

Julian Hyde commented on HIVE-6361:
---

A lot more than a week so far... but making progress: 
https://github.com/julianhyde/hive/commit/69460019e628c0077aec4865bba65b6aad11d5f4

> 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
>
> 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)

[jira] [Commented] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973500#comment-13973500
 ] 

Julian Hyde commented on HIVE-6361:
---

Agreed. Expect a patch in about a week.

> 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
>
> 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)

Re: Proposal to un-fork Sqlline

[Julian Hyde]

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 independent module.

Yeah, I agree in principle. But to create a small independent module in Apache 
you have to go through the whole incubator process. I think a library within 
the Hive namespace is an acceptable compromise. When that is complete I will 
look at moving it elsewhere, say commons or as a sub-project within 
http://db.apache.org/.

(Am I the first person to note that Apache effectively discourages code re-use 
because they set a very high bar for creating a project?)

Julian

[jira] [Commented] (HIVE-6361) Un-fork Sqlline

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890847#comment-13890847
 ] 

Julian Hyde commented on HIVE-6361:
---

Additional step:

1.5. Re-organize Julian Hyde's sqlline to match structure of hive-beeline (in 
package org.apache.hive.sqlline, standard Hive formatting, and break out inner 
classes). Then it can more easily be compared with beeline.

I am working on a patch.

> 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
>
> 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.1.5#6160)

Re: Proposal to un-fork Sqlline

[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 are immediate across multiple
> projects.

You’re basically suggesting that I do step 3 before 1 and 2. It makes sense, 
because it reduces risk.

I have logged https://issues.apache.org/jira/browse/HIVE-6361 with an updated 
proposal.

Julian