I have pushed the standalone metastore src and bin tarballs and their
signatures and hashes into Hive's dist area, so they should soon be
available for download. Congrats to all who worked on this!
As part of creating a release tag for the standalone metastore I noticed we
didn't have one for
I have put the binary and source objects up at
https://home.apache.org/~gates/hive-standalone-metastore-3.0.0/ so everyone
can take a look before I officially push them to dist.
I don't think we need to vote on this as we have already officially
released these objects, I'm just adding sha and gpg
The proposal to post the source and bin to the distribution sounds good to
me. We can do the testing and release standalone-metastore 3.1 like to you
suggested above.
On Tue, May 29, 2018 at 10:49 PM, Peter Vary wrote:
> What do you think about adding a ne profile, which adds a possibility to
>
What do you think about adding a ne profile, which adds a possibility to
compile the code with one command, until we separate standalone metastore
to a new project? Like -Pitests, but -Pmetastore. So "mvn clean install
-Pmetastore,itests" will compile everything.
Alan Gates ezt írta (időpont:
On Tue, May 29, 2018 at 3:29 PM Vihang Karajgaonkar
wrote:
> How about cutting out a branch-3.0.1 and releasing 3.0.1 with the pom.xml
> fixed? My concern with above approach is we haven't tested
> standalone-metastore when deployed independent of Hive.
Actually, there is. The tarballs for
How about cutting out a branch-3.0.1 and releasing 3.0.1 with the pom.xml
fixed? My concern with above approach is we haven't tested
standalone-metastore when deployed independent of Hive. So we don't know if
there is something is fundamentally broken in that mode and given that we
don't know when
In the thread on releasing Hive 3.0 I wrote
We should work on producing a standalone-metastore
release in the same time frame so that the schema's, etc. match. I can RM
that unless someone else wants to.
