Re: Preparation for Hive-1.2 release

Hi, I notice that the process of creating a new version does not involve a JIRA ticket where we track a patch for changes committed to master. One of the tests that was recently created on Jenkins is a job that run all HMS upgrade tests for mysql/postgres/derby (oracle is still in progress) when

Re: VOTE: move to git

I opened HIVE-10486 "Update wiki for switch from svn to git" and listed all the wikidocs that need revision. -- Lefty On Mon, Apr 20, 2015 at 7:22 PM, Sergey Shelukhin wrote: > INFRA jira has been filed: > https://issues.apache.org/jira/browse/

Re: svn commits

> > I think it would be good if we can update the wiki on how to commit as we > switch the tool. > +1 (see HIVE-10486 Update wiki for switch from svn to git -- any volunteers?) -- Lefty On Wed, Apr 22, 2015 at 6:59 PM, Xuefu Zhang wrote: > I

[jira] [Created] (HIVE-10487) remove non-ISO restriction that projections in a union have identical column names

N Campbell created HIVE-10487: - Summary: remove non-ISO restriction that projections in a union have identical column names Key: HIVE-10487 URL: https://issues.apache.org/jira/browse/HIVE-10487 Project: H

[jira] [Created] (HIVE-10486) Update wiki for switch from svn to git

Lefty Leverenz created HIVE-10486: - Summary: Update wiki for switch from svn to git Key: HIVE-10486 URL: https://issues.apache.org/jira/browse/HIVE-10486 Project: Hive Issue Type: Bug

Re: PreCommit-HIVE-TRUNK-Build still on svn repo

Thanks so much Sergio! Looks like the tests are running fine now! On Fri, Apr 24, 2015 at 12:53 PM, Sergio Pena wrote: > Thanks Thejas, > > I just added the 'branch' variable to the properties file. > Let's see if that fixes the issue after the tests run. > > - Sergio > > > > On Thu, Apr 23, 201

Build failed in Jenkins: HIVE-TRUNK-JAVA8 #63

See -- [...truncated 11553 lines...] 36/59 KB 27/27 KB 227/227 KB 40/59 KB 27/27 KB 227/227 KB 44/59 KB 27/27 KB 227/227 KB 48/59 KB 27/27 KB 227/2

Re: Preparation for Hive-1.2 release

Hi Folks, branch-1.2 is now created, and master has been bumped to 1.3.0-SNAPSHOT. Carl/Thejas, I do not have permissions to create a new unreleased version number for 1.3.0 on jira - could one of you please create this so any new resolved jiras can be marked with this instead? Everyone else : O

Re: [DISCUSS] Deprecating Hive CLI

Yes, well put. It is about usability and "least surprise". So if people wouldn't have to deal with JDBC syntax by default and could use "hive" instead of "beeline" to start that'd be good. On Sat, Apr 25, 2015 at 12:38 AM, Alan Gates wrote: > If I understand correctly this is an argument about