[DISCUSS] Propose reverting HIVE-10304 CLI deprecation message

I apologize for not catching this sooner, but I'd like to revert this patch. Something as major as deprecating a component should be discussed on the dev list, not just put in as a patch. Alan.

Re: [DISCUSS] Propose reverting HIVE-10304 CLI deprecation message

for our users to access Hive and we do not see that changing any time soon.") - Deprecating CLI <http://mail-archives.apache.org/mod_mbox/hive-dev/201412.mbox/%3c5485e1be.3060...@hortonworks.com%3e> (Alan Gates, Thejas Nair) -- Lefty Alan Gates <mailto:alanfga...@gmail.com> Apri

Re: [DISCUSS] Deprecating Hive CLI

Xuefu, thanks for getting this discussion started. Limiting our code paths is definitely a plus. My inclination would be to go towards option 2. A few questions: 1) Is there any functionality in CLI that's not in beeline? 2) If I understand correctly option 2 would have an implicit HS2 in p

Re: [DISCUSS] Deprecating Hive CLI

e "hive" command to get an embedded HS2 in Beeline 4) Add some documentation to beeline reminding people on startup of beeline on how to connect and how to use embedded mode The fact is that the old shell just works for lots of people and there's just no need for beeline for th

Re: Why SQL Standards Based Authorization is implemented on HiveServer2 side only?

The issue is that security checks are done in the client. In order to fully do them in the metastore we would have been forced to move significant amounts of functionality out of the client and into the metastore. Query parsing and planning would have had to be moved to the metastore, basical

Re: [VOTE] Apache Hive 1.2.0 release candidate 2

-1 A couple of jar files found there way into the src release: gates> find . -name \*.jar ./beeline/src/test/resources/DummyDriver-1.0-SNAPSHOT.jar ./beeline/src/test/resources/postgresql-9.3.jdbc3.jar We can't have any binaries in the source release. In the README: * At what point is the @VERS

Re: [VOTE] Apache Hive 1.2.0 release candidate 2

rk in that list. -- I'll update this. Re: JDK1.6 : Also true, we no longer compile under jdk 1.6 (I just verified that was the case) -- I'll update this Alan Gates <mailto:alanfga...@gmail.com> May 11, 2015 at 10:51 -1 A couple of jar files found there way into the src release

[DISCUSS] Supporting Hadoop-1 and experimental features

There is a lot of forward-looking work going on in various branches of Hive: LLAP, the HBase metastore, and the work to drop the CLI. It would be good to have a way to release this code to users so that they can experiment with it. Releasing it will also provide feedback to developers. At

Re: [VOTE] Apache Hive 1.2.0 release candidate 3

+1. Checked LICENSE, NOTICE, README, and RELEASE_NOTES, signatures, looked for .class or .jar files, did a quick build. Alan. Sushanth Sowmyan May 11, 2015 at 19:11 Hi Folks, We've cleared all the blockers listed for 1.2.0 release, either committing them, or defer

Re: [VOTE] Apache Hive 1.2.0 release candidate 4

+1, same checks as last vote. Alan. Sushanth Sowmyan May 13, 2015 at 11:50 Hi Folks, We've cleared all the blockers listed for 1.2.0 release, either committing them, or deferring out to an eventual 1.2.1 stabilization release. (Any deferrals were a result of discuss

Re: [DISCUSS] Supporting Hadoop-1 and experimental features

eatures could be back ported to branch-1 if viable, but at least new stuff would not be burdened by Hadoop 1/MR code paths. Probably also a good place to enable vectorization and other perf features by default while we make alpha releases. +1 Alan Gates <mailto:alanfga...@gmail.com> May 11, 2

Re: [DISCUSS] Supporting Hadoop-1 and experimental features

said above, I don't see this as tied to Hadoop versions. Alan. Thanks, Xuefu On Fri, May 15, 2015 at 4:43 PM, Vaibhav Gumashta wrote: +1 on the new branch. I think it’ll help in faster dev time for these important changes. —Vaibhav From: Alan Gates Reply-To: "dev@hive.ap

Re: [DISCUSS] Supporting Hadoop-1 and experimental features

by Hadoop 1/MR code paths. Probably also a good place to enable vectorization and other perf features by default while we make alpha releases. +1 Alan Gates May 11, 2015 at 15:38 There is a lot of forward-looking work going on in various branches of Hive: LLAP, the HBase metastore, and th

Re: [DISCUSS] Supporting Hadoop-1 and experimental features

g and also burdensome if we release say 1.3, 2.0, 2.1, 1.4... Please note that we will have hadoop 3 soon. What's the story there? Thanks, Xuefu On Fri, May 15, 2015 at 4:43 PM, Vaibhav Gumashta wrote: +1 on the new branch. I think it’ll help in faster dev time for these important

Re: Request for addition as contributor

On JIRA or the wiki? I tried to add you to the JIRA but it didn't find a szita or Adam Szita user. I'm not sure I have permission to add you to the wiki. Alan. > On Dec 8, 2016, at 07:21, Adam Szita wrote: > > Hi, > > Can you add my userid (szita) as contributor to Hive please. > > Thanks,

Re: Request for addition as contributor

e. Alan. > > -- Lefty > > > On Thu, Dec 8, 2016 at 7:27 AM, Alan Gates wrote: > >> On JIRA or the wiki? I tried to add you to the JIRA but it didn't find a >> szita or Adam Szita user. I'm not sure I have permission to add you to the >> wiki. &

Re: [DISCUSS] Separate release of storage-api

90% of the discussion on the previous thread was on version numbering, which never came to a conclusion. Based on your RC candidate I assume you chose the separate version numbering, but starting from the same 2.2.0 base number. I agree this is the only viable option[1], but I wanted to point i

Re: [VOTE] Should we release hive-storage 2.2.0RC0

+1. Did a build, checked the signatures, looked over the new LICENSE and NOTICE files, ran rat. Alan. > On Jan 5, 2017, at 9:39 AM, Owen O'Malley wrote: > > All, > I'd like to make a release of Hive's storage-api module. This will allow > ORC to remove its fork of storage-api and make a rel

Re: [VOTE] Should we release hive-storage-2.2.1rc0?

+1. Did a build with a clean maven repo, ran rat, checked the signatures, checked for any binary files in the tarball. Alan. > On Feb 16, 2017, at 10:56 AM, Owen O'Malley wrote: > > All, > We've made some fixes to the storage-api since 2.2.0 and I'd like to > make a new release. > > Issues

[ANNOUNCE] New committer: Zoltan Haindrich

On behalf of the Hive PMC I am happy to announce Zoltan Haindrich is our newest committer. He has been contributing to Hive for several months across a number of areas, including the parser, HiveServer2, and cleaning up unit tests and documentation. Please join me in welcoming Zoltan to Hive.

Re: [DISCUSS] Spark's fork of hive

I think the issues you point out fall into a couple of different buckets: 1) Spark forking Hive code. As you point out, based on the license, there's nothing wrong with this (see naming concerns below). I agree it's crappy technical practice because in the long term Hive and Spark will diverge

Re: Need help to contribute in Hive

Prince, welcome to Hive. Probably the best way is to find a JIRA no one else is working on, assign it to yourself, and then start working on it. I did a quick search on open JIRAs relating to the thrift interface and found https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%2

Re: [VOTE] Should we release hive-storage-2.3.0rc0?

+1.  Did a build with a fresh maven repo, checked the signatures, ran rat. Alan. On Apr 27, 2017, 16:08 -0700, Owen O'Malley , wrote: > All, > I'd like to make a new release of the storage-api for the upcoming 2.2 > release. Since storage-api rolls releases faster than Hive, this will be > the st

CFP for Dataworks Summit Sydney

Resend, sorry if this shows up twice. The Australia/Pacific version of Dataworks Summit is in Sydney this year, September 20-21.   This is a great place to talk about work you are doing in Apache Hive or how you are using Hive.  Information on submitting an abstract is at https://dataworkssummi

CFP for Dataworks Summit Sydney

The Australia/Pacific version of Dataworks Summit is in Sydney this year, September 20-21. This is a great place to talk about work you are doing in Apache Hive or how you are using Hive. Information on submitting an abstract is at https://dataworkssummit.com/sydney-2017/abstracts/submit-abst

Fwd: JSON reminder

This applies to Hive and blocks the 2.2 and 2.3 releases. The issue has not been resolved on master as well. Alan. -- Forwarded message -- From: Jim Jagielski Date: Tue, May 23, 2017 at 6:57 AM Subject: JSON reminder To: legal discuss The grandfather exception closed last mon

[DISCUSS] Separating out the metastore as its own TLP

Hagleitner Thejas Nair Alan Gates

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

Comments inlined. On Sun, Jul 2, 2017 at 3:22 PM, Edward Capriolo wrote: > I am not sure I am on the fence with this. > > I am -1, and I offer this -1 with the hope of being convinced otherwise > Thank you for being open to reconsider. > > > "By making it a separate project we will enable other

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

On Mon, Jul 3, 2017 at 6:20 AM, Edward Capriolo wrote: > > We already have things in the meta-store not directly tied to language > features. For example hive metastore has a "retention" property which is > not actively in use by anything. In reality, we rarely say 'no' or -1 to > much. Which in

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

On Mon, Jul 3, 2017 at 10:17 AM, Dain Sundstrom wrote: > +1 > > I work on Presto and I think this the right direction for our users. We > have several users running Presto without Hive and anything we can do to > help simplify the Metastore experience would be a good help. > > When I read propos

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

cts to use HMS as it is. The issue of Spark > including > > a Hive fork, which was brought up some time back, is certainly not one of > > them. > > > > Thanks, > > Xuefu > > > > On Wed, Jul 5, 2017 at 12:33 PM, Edward Capriolo > > wrote: > >

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

nly not one of > them. > > Thanks, > Xuefu > > On Wed, Jul 5, 2017 at 12:33 PM, Edward Capriolo > wrote: > > > On Wed, Jul 5, 2017 at 1:51 PM, Alan Gates wrote: > > > > > On Mon, Jul 3, 2017 at 6:20 AM, Edward Capriolo > > > > wrote: >

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

On Wed, Jul 5, 2017 at 12:33 PM, Edward Capriolo wrote: > > I hate to draw in something else but I feel it is related: > > 8 December 2016 : release 2.1.1 available > 07 April 2017 : release 1.2.2 available > hive-dev [DISCUSS] Supporting Hadoop-1 and experimental features > hive-dev Re: release

Re: [VOTE] storage-release-2.4.0rc1

+1. Checked the signatures, did a build with a fresh maven repo, ran rat. On Mon, Jul 10, 2017 at 11:58 PM, Pengcheng Xiong wrote: > Hi all, > >Here is a new release candidate for hive-storage-2.4.0 which Hive 2.3 > will depend on. Please take a look and vote. Thanks. > > Here is my +1 afte

Re: [VOTE] storage-release-2.4.0rc1

ul 12, 2017 at 11:08 AM, Ashutosh Chauhan > wrote: > > > +1 > > Did a build and some basic testing. > > > > On Tue, Jul 11, 2017 at 1:36 PM, Alan Gates > wrote: > > > > > +1. Checked the signatures, did a build with a fresh maven repo, ran > > ra

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

It seems we have settled into a consensus that this will be good for the ecosystem, but there are concerns that this will be a burden on Hive. The original proposal included a time to work on the separation inside the Hive project to help address any such issues. This would culminate in a source

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

In the same vein Carter and Gunther suggested Omegastore. Pick your alphabet and whether it’s a catalog or a store I guess. Alan. On Mon, Jul 24, 2017 at 1:35 PM, Sergey Shelukhin wrote: > I’d like to suggest ZCatalog. > > On 17/7/11, 15:41, "Lefty Leverenz" wrote: > > >>> I'd like to suggest

Re: [VOTE] Shall we release Hive 2.2.0 rc1?

+1, checked the signatures, did a build with a clean repo, ran RAT. Alan. On Fri, Jul 21, 2017 at 5:20 PM, Owen O'Malley wrote: > Ok, I rolled a new RC with the Apache header problem fixed. > > Artifacts: https://home.apache.org/~omalley/hive-2.2.0/ > Tag: https://github.com/apache/hive/release

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

> > On Mon, Jul 24, 2017 at 5:20 PM, Vihang Karajgaonkar < > vih...@cloudera.com> > > wrote: > > > > > Before we see a flood of name suggestions :) Why not just keep it > > > Metastore? Its already well-known in the community and easy to

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

> > On Mon, Jul 24, 2017 at 5:20 PM, Vihang Karajgaonkar < > > vih...@cloudera.com> > > > wrote: > > > > > > > Before we see a flood of name suggestions :) Why not just keep it > > > > Metastore

Re: Hive Custom Inputformat mapred.* vs. mapreduce.*

I’m not aware of any plans in Hive to do any more work that uses Map Reduce as the execution engine, so I expect Hive will continue to use mapred. Alan. On Wed, Sep 13, 2017 at 4:25 AM, Jörn Franke wrote: > Dear all, > > I have developed several custom input formats (e.g. for the Bitcoin > bloc

Re: Review Request 34473: HIVE-10749 Implement Insert statement for parquet

/ParquetRecordUpdater.java <https://reviews.apache.org/r/34473/#comment136066> Do you intend to use this in conjunction with hive.hcatalog.streaming? If so, closing the file on a flush is not what you'll want. - Alan Gates On May 21, 2015, 7:45 a.m., che

Re: [DISCUSS] Supporting Hadoop-1 and experimental features

I don't think anyone is advocating for option 2, as that would be disastrous. Option 3 is closest to what I'm proposing, though again dropping support for Hadoop 1 is only a part of it. Alan. Alexander Pivovarov May 22, 2015 at 10:03 Looks like we discussing 3 o

Re: [DISCUSS] Supporting Hadoop-1 and experimental features

Thanks for your feedback Chris. It sounds like there are a couple of reasonable concerns being voiced repeatedly: 1) Fragmentation, the two branches will drift too far apart. 2) Stagnation, branch-1 will effectively become a dead-end. So I modify the proposal as follows to deal with those: 1)

Re: [DISCUSS] Supporting Hadoop-1 and experimental features

I agree with *All* features with the exception that some features might be branch-1 specific (if it's a feature on something no longer supported in master, like hadoop-1). Without this we prevent new features for older technology, which doesn't strike me as reasonable. I see your point on say

Re: Caching metastore objects

Sivaramakrishnan Narayanan May 25, 2015 at 20:19 Apologies if this has been discussed in the past - my searches did not pull up any relevant threads. If there are better solutions available out of the box, please let me know! Problem statement

[VOTE] Stable releases from branch-1 and experimental releases from master

We have discussed this for several weeks now. Some concerns have been raised which I have tried to address. I think it is time to vote on it as our release plan. To be specific, I propose: Hive makes a branch-1 from the current master. This would be used for 1.3 and future 1.x releases. T

[VOTE][RESULT] Stable releases from branch-1 and experimental releases from master

ht for them. - This also lets developers focus on major new features without the burden of maintaining hadoop-1 compatibility. Alan Gates <mailto:alanfga...@gmail.com> May 26, 2015 at 11:41 We have discussed this for several weeks now. Some concerns have been raised which I have tried to address. I

Creating branch-1

Based on our discussion and vote last week I'm working on creating branch-1. I plan to make the branch tomorrow. If anyone has a large commit they don't want to have to commit twice and they are close to committing it let me know so I can make sure it gets in before I branch. I'll also be u

Re: Creating branch-1

Ok, I've created branch-1. I've also updated HowToContribute with information on what patches go where now. Proofreaders and feedback on clarity are welcomed. (At the same time I updated the page to contain git instructions instead of SVN, so feedback on that is good too.) Al

Re: Creating branch-1

I pushed it to apache, so it should auto-clone to github, correct? Alan. Alexander Pivovarov June 2, 2015 at 11:34 Hi Alan Is branch-1 on github already? https://github.com/apache/hive/tree/branch-1

Re: Creating branch-1

+1. Alan. Thejas Nair <mailto:thejas.n...@gmail.com> June 2, 2015 at 14:31 I believe we should start using 2.0.0 as the fix version for patches that go into master, and 1.3.0 for the ones going into branch-1. Is that the belief of others as well ? Alan Gates <mailto:alanfga...@

Re: Creating branch-1

;. We can parse different branches there, and let jenkins-submit-build.sh call the correct job with specific branch details. Any other ideas? - Sergio Alan Gates <mailto:alanfga...@gmail.com> June 1, 2015 at 16:19 Based on our discussion and vote last week I'm working on creating

Re: Creating branch-1

Wed, Jun 3, 2015 at 12:17 PM, Vinod Kumar Vavilapalli < Vinod Kumar Vavilapalli <mailto:vino...@hortonworks.com> June 3, 2015 at 12:17 Hadoop uses a "Target Version" field. Not sure if this was done for all projects. +Vinod On Jun 3, 2015, at 9:16 AM, Alan Gates <mai

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

ursday, 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.apac

Re: PL/HQL and Hive

Here's what we need to do: 1) You need to file a JIRA proposing to contribute the code. 2) You can then contribute the code as a patch to that JIRA. As long as you've written all the code yourself this is sufficient to hand legal rights to Apache to contribute the code. If others beyond you h

Re: PL/HQL and Hive

SQL is a good name, I am ok with this change. Right now I am the only one developer of PL/HQL. Which status will I be given in the Hive project, so I can continue developing the tool? I will read docs and try to create a patch. Thanks, Dmitry Alan Gates <mailto:alanfga...@gmail.com> J

Re: [VOTE] Apache Hive 1.2.1 Release Candidate 0

+1. Checked signatures, looked for binary files, compiled the code, and ran a rat check. Alan. Sushanth Sowmyan June 19, 2015 at 2:44 Hi Folks, It's been a month since 1.2.0, and I promised to do a stabilization 1.2.1 release, and this is it. A large number of pat

Re: new to hive and could't build success

Hive no longer uses svn. The official code is now in git. So the below should be: git clone https://git-wip-us.apache.org/repos/asf/hive.git cd hive mvn clean install -Phadoop-2 # you don't need dist unless your building the package Alan. baishaoqi July 2

Review Request 36355: Remove OFFLINE and NO_DROP from tables and partitions

.q.out fe67448 ql/src/test/results/clientpositive/union_remove_9.q.out 684091b Diff: https://reviews.apache.org/r/36355/diff/ Testing --- Thanks, Alan Gates

Re: [Discuss] Patch submission and commit format

When we are committing another's patch is there an easy way to tell whether they properly generated via git format-patch or another method? Alan. Thejas Nair July 14, 2015 at 10:56 In case the patch is generated using a simple git-diff or another method that is n

Re: [GitHub] hive pull request: Hbase metastore

at: https://github.com/apache/hive/pull/46.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #46 commit 58ca965ca58925e4846e14cf37d64638edb3e353 Author: Alan Gates Date: 2015-01-23T19:05:19Z Creating

Re: HIVE-11254 Review Request (HPL/SQL tool)

I'll look at it later today. Alan. Dmitry Tolpeko July 21, 2015 at 0:41 Can please anyone review https://issues.apache.org/jira/browse/HIVE-11254? The changes are related to new HPL/SQL component only. When renaming the tool from plhql to hplsql I introduced a b

Re: [DISCUSS] Hive and HBase dependency

On the hbase-metastore branch I've actually already moved to HBase 1.1. I'm +1 for moving to 1.1 or 1.0 on master and staying at 0.98 on branch-1. Alan. kulkarni.swar...@gmail.com August 12, 2015 at 8:43 Hi all, It seems like our current dependency on HBas

Re: [DISCUSS] Hive and HBase dependency

on might be needed as some of the stuff in the hive hbase integration might need some massaging before that is done. [1] https://issues.apache.org/jira/browse/HIVE-11559 -- Swarnim Alan Gates <mailto:alanfga...@gmail.com> August 13, 2015 at 10:52 On the hbase-metastore branch I've act

Testing in the HBase metastore branch

I have a set of tests I run before a commit in the HBase metastore branch since we don't have automated testing on that branch right now. I realized I haven't shared those with others. They are: in metastore: TestHBaseStore, TestHBaseStoreCached, TestHBaseUtils, TestSharedStorageDescriptor,

Re: Please double-check JIRA number on commit

+1 to putting it in source. We could start an "errata" file or something that lists these. Alan. Lefty Leverenz August 29, 2015 at 22:45 One more for the list of commits that don't have the right JIRA issue number -- but in this case, it doesn't have any issue

windows line endings and git

After Dmitry checked in HIVE-11536 and I fetched and merged, I had issues in my git repository with line endings. It insisted on modifying the files without me so much as opening the files, and would not let me switch branches until I dealt with it. I think it automatically changed the window

Re: windows line endings and git

I'm not saying it's your fault. We need to be able to support people developing on Windows, Linux, and Mac. I just wanted to know who needs to set what to make this happen. Alan. Dmitry Tolpeko September 1, 2015 at 10:41 I develop in Eclipse on Windows, but fina

Re: windows line endings and git

Me, or Dmitry, or both? Alan. Sergey Shelukhin <mailto:ser...@hortonworks.com> September 1, 2015 at 10:38 Set core.autocrlf to false in git config. On 15/9/1, 10:17, "Alan Gates" wrote: After Dmitry checked in HIVE-11536 and I fetched and merged, I had issues in my git repo

Re: How to enable compaction for table with external data?

If you want it to compact automatically you should not put NO_AUTO_COMPACTION in the table properties. First question, did you turn on the compactor on your metastore thrift server? To do this you need to set a couple of values in the metastore's hive-site.xml: hive.compactor.initiator.on=t

Re: How to enable compaction for table with external data?

achin From: Alan Gates mailto:alanfga...@gmail.com>> Reply-To: "dev@hive.apache.org <mailto:dev@hive.apache.org>" mailto:dev@hive.apache.org>> Date: Tuesday, 15 September 2015 10:30 pm To: "dev@hive.apache.org <mailto:dev@hive.apache.org>" mailto:dev@hive.

Re: Review Request 39026: HIVE-11676 implement metastore API to do file footer PPD

ve partition expressions into HBase filters. I'm not sure if you could re-use that here or not. - Alan Gates On Oct. 15, 2015, 1:47 a.m., Sergey Shelukhin wrote: > > --- > This is an automatically generated e-mail

Review Request 39578: Remove hadoop-1 support from master branch

pache/hadoop/hive/thrift/HadoopThriftAuthBridge.java 7ed7265 shims/pom.xml 12113d5 shims/scheduler/pom.xml 407d57d storage-api/pom.xml 71b79f1 Diff: https://reviews.apache.org/r/39578/diff/ Testing --- Tested that I can build and run tests. Thanks, Alan Gates

Hadoop-1 is dead, long live Hadoop

I've committed HIVE-11378 to master, which means Hadoop-1 is no longer supported in Hive's master branch. When building it is no longer necessary to say -Phadoop-2. No profile is needed for regular builds. Alan.

Re: Hadoop-1 is dead, long live Hadoop

I guess they need to move to hadoop-2 org.apache.hadoop.util.VersionInfo.getVersion res8: String = 1.2.2-SNAPSHOT On Mon, Oct 26, 2015 at 3:02 PM, Alan Gates wrote: I've committed HIVE-11378 to master, which means Hadoop-1 is no longer supported in Hive's master branch. When bu

Re: [CONF] Apache Hive > GettingStarted

This isn't correct. If we just want to build jars, the command is "mvn clean install -Phadoop-1". If we want to build packages the command is "mvn clean package -Phadoop-1,dist". I wasn't sure which was intended and opted for building packages. We should clarify which is intended and then g

Build breakage

HIVE-12295 broke the qfile and itest/hive-unit tests. Jimmy put up a patch in HIVE-12318 that appeared to fix it. I went ahead and committed that patch without waiting for the precommit testing because there were several patches ahead of it in line that would have failed. This means the test

Re: [DISCUSS] the first Hive 2 release

The stated plan for 2.0 when we created branch-1 was to be able to release more aggressively from master. As Xuefu points out we've added a lot of code and features. I'm +1 for having a 2.0 release soon, but we should be very clear with users that many of the new features are in alpha or beta

Re: [DISCUSS] the first Hive 2 release

We shouldn't block either branch releasing for the other. 1.3.0 should be released when someone volunteers to pick it up and drive the release. Alan. Lefty Leverenz November 11, 2015 at 23:03 Should 1.3.0 be released at the same time, or even before 2.0.0? --

Re: [VOTE] Hive 2.0 release plan

+1. Alan. Sergey Shelukhin November 13, 2015 at 12:38 Hi. With no strong objections on DISCUSS thread, some issues raised and addressed, and a reminder from Carl about the bylaws for the release process, I propose we release the first version of Hive 2 (2.0), and

Re: Review Request 40467: HIVE-12075 analyze for file metadata

weird. I know we never talk about metadatum, but still... metastore/src/java/org/apache/hadoop/hive/metastore/hbase/HBaseReadWrite.java (line 2150) <https://reviews.apache.org/r/40467/#comment166303> I don't understand what's in the addedCol

Re: [DISCUSSION] Data correctness issue reporting procedural

Xuefu, thanks, I think this is a good start. I've inlined a few responses. Xuefu Zhang November 24, 2015 at 7:26 Hi all, In the last contributor meetup, the topic around data correctness or data corruption is rather concerning. Not only is the number of such issues

Re: Wish to work on an Open Source Project

Hi Mihir, welcome to open source. See https://cwiki.apache.org/confluence/display/Hive/HowToContribute for a good overview of how to contribute to Hive. One of the best ways to get started is to find a bug you'd like to fix and work on fixing it. You can find a list of open Hive bugs at htt

Re: Allow other implementations of IMetaStoreClient in Hive

o, wouldn't backward compatibility guarantees for Thrift translate to backward compatibility guarantees for this interface as well? From the way it is used by Query Planning, I think it could be made an "external" interface that belongs in hive-metastore. Alan Gates <mailto

Re: Allow other implementations of IMetaStoreClient in Hive

I don't see an issue with this, it seems fine. One caveat though is we see this as an internal interface and we change it all the time. I wouldn't want to be pushed into making backwards compatibility guarantees for IMetaStoreClient. Which means that if you develop a different implementation

Re: Allow other implementations of IMetaStoreClient in Hive

sound good? Thanks, Austin Alan Gates <mailto:alanfga...@gmail.com> December 15, 2015 at 11:04 For work along the same lines you should check out the HBase metastore work in Hive 2.0. It still uses the thrift server and RawStore but puts HBase behind it instead of an RDBMS. We did this

Re: Hive has standalone mode?

Hive cannot run without the Hadoop binaries, but it can run locally without a cluster running. If you install Hadoop in standalone mode (see http://hadoop.apache.org/docs/r2.7.1/hadoop-project-dist/hadoop-common/SingleCluster.html#Standalone_Operation ) then set HADOOP_HOME to the location whe

Re: Need your opinion on HIVE-12916 to clean up metastore API

Are you proposing to do this in 2.0 or branch-1 or both? In master we can put up with some backwards incompatibility for now. But given that it's straightforward to maintain it (as Sergey outlines) even there it doesn't seem worth it. So unless there's a very compelling reason (i.e. more tha

Re: [VOTE] Apache Hive 2.0.0 Release Candidate 0

-1. There's a jar file in the src distribution, ./data/files/identity_udf.jar We can't have any binary files in the src distribution. When I do: mvn install -DskipTests -Dmaven.repo.local=/Users/gates/tmp/hive/m2 I get: [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR]

Re: [VOTE] Apache Hive 2.0.0 Release Candidate 1

When I installed it locally and tried to run it I get the following failure: Caused by: org.datanucleus.store.rdbms.exceptions.MissingTableException: Required table missing : "VERSION" in Catalog "" Schema "". DataNucleus requires this table to perform its persistence operations. Either your M

Re: [VOTE] Apache Hive 2.0.0 Release Candidate 1

is could be caused by the change to not allow DN to mutate the schema. I cannot find the JIRA right now, Ashutosh might know. The metastore database has to be created via the install script and schema tool. Perhaps we can document that. From: Alan Gates mailto:alanfga...@gmail.com>&g

Re: [VOTE] Apache Hive 2.0.0 Release Candidate 1

+1. Signatures and licenses look good, build is good. We should file a JIRA to resolve the docs for local install ASAP so people can use this out of the box. Alan. Sergey Shelukhin February 2, 2016 at 18:26 Apache Hive 2.0.0 Release Candidate 1 is available h

Re: [VOTE] Apache Hive 2.0.0 Release Candidate 2

FYI the URL for the candidate returns 404, the correct URL is http://people.apache.org/~sershe/hive-2.0.0-rc2/ +1, checks signatures, did a build with a brand new maven repo, and ran a quick smoke test. Alan. Sergey Shelukhin February 8, 2016 at 18:29 Apache Hive

Re: [VOTE] Apache Hive 2.0.0 Release Candidate 2

It is expected, you now have to run SchemaTool manually, as the error message indicates. See https://issues.apache.org/jira/browse/HIVE-1841 Alan. Xuefu Zhang February 9, 2016 at 10:37 Some trouble I met: 1. downloaded source and build Hive with -Pdist. 2. try to

Re: [VOTE] Apache Hive 2.0.0 Release Candidate 3

+1, checks sigs, build with fresh maven repo, and did a quick smoke test. Does the PMC member who votes on the most RC's get a prize? Alan. Sergey Shelukhin February 9, 2016 at 18:52 Another day, another release candidate... this time fixing the logging issue. Apach

Re: Spark and HBase metastore jiras in 2.0 release

It makes sense to update the branch fix versions when we merge so that people can figure out what release version a fix or feature is in. So +1. Alan. Thejas Nair February 16, 2016 at 21:48 The hbase-metastore branch jiras are all part of Hive 2.0.0 release, as

Re: hive/odbc codebase

AFAIK it’s dead. Alan. > On Mar 7, 2016, at 20:33, Gopal Vijayaraghavan wrote: > > Hi, > > Does anyone know if the hive/odbc codebase works? > > https://github.com/apache/hive/tree/master/odbc/src/cpp > > Is it dead-code we can remove as part of the hive-2.0 branch? > > Cheers, > Gopal > >

Re: SELECT without FROM

I’m not aware of any JIRA on it. The easiest way to find out will be to look at the git history of Hive’s grammar file and see when it changed. As for taking out, we shouldn’t since it’s valid SQL and we’re pushing towards more ANSI compliance. Alan. > On Mar 9, 2016, at 01:50, Dmitry Tolpeko

Re: Reviews & commits (RTC/CTR), contributions, bylaws

I’m +1 on this change of allowing simple cleanup changes without requiring a full review. But jumping to this fix obscures a bigger problem we have as a community. This fix only works for committers, not for non-committers who may also contribute such patches. And it doesn’t solve the situa

<    1   2   3   4   5   6   7   8   9   10   >