HIVE-29062: Add standalone module for packaging the Metastore (#5923) #5936
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
Could you please fill out the description? This ticket means the Metastore will be separate entity and it could deploy separate? |
Member
Author
Done, we have a standard way to provide the official standalone Metastore binary/source tarball and the Docker image. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Add a new module to package the standalone Metastore
Why are the changes needed?
On the thread https://lists.apache.org/thread/tvozv88sjjmnx8n5rktjg1c6x1y0mlpv, we agree to release the standalone Metastore and the Docker image in 4.1.0. In order to fix the circular dependency issue we build the Metastore binary tarball and the image from the module metastore-server, we introduced a profile
allModuleto include all the necessities, and the source tarball is built from the standalone metastore root. this is quite not straightforward and don't follow the way we build the Hive tarball. This new module also normalizes the Metastore binary/source tarball we are going to release, which keeps the old behavior of Hive Metastore 3.0.0.Does this PR introduce any user-facing change?
No
How was this patch tested?
Tested locally using the command
mvn clean package -Pdist,docker