yunus opened a new pull request #2700:
URL: https://github.com/apache/hive/pull/2700
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/Hive/HowToContribute
2. Ensure that you have created an issue on the Hive project JIRA:
https://issues.apache.org/jira/projects/HIVE/summary
3. Ensure you have added or run the appropriate tests for your PR:
4. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP]HIVE-XXXXX: Your PR title ...'.
5. Be sure to keep the PR description updated to reflect all changes.
6. Please write your PR title to summarize what this PR proposes.
7. If possible, provide a concise example to reproduce the issue for a
faster review.
-->
### What changes were proposed in this pull request?
This PR adds Cloud Spanner as a backend database option. Currently, I
provide only for 2.3 branch. For master and 3.x branches soon I will provide
another pull request.
Changes make Hive Metastore compatible with Spanner database. Notable
changes are:
- Spanner does not accept username, password so we have avoided them for
spanner
- Spanner requires primary keys. We have changed schema and calls to
NEXT_TXN_ID table
- For direct sql statements, we got rid of quotation
- During the partition deletions, instead of deleting all the partitions
connected with "OR" statements, we have moved to bulk delete which uses "IN"
- Spanner only supports SERIALIZABLE transaction isolation. For the Hive
ACID TXNs, we replace READ_COMMITTED level to SERIALIZABLE only for Spanner.
Transaction isolation is a configuration option with READ_COMMITTED as the
default.
### Why are the changes needed?
We want to run Hive Metastore on a cloud native database that can scale
horizontally and no need for maintenance.
### Does this PR introduce _any_ user-facing change?
No
### How was this patch tested?
We have run the integration tests on Spanner instead of Derby.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
