Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[#2080] feat(core): Add JDBC backend operations for metalake #1980

Merged
merged 20 commits into from
Feb 26, 2024

Conversation

xloya
Copy link
Contributor

@xloya xloya commented Feb 2, 2024

What changes were proposed in this pull request?

The purpose of this PR is to implement JDBC backend operation Metalake metadata which use MySQL as the database. Depend on #1930. Metadata operations of Catalog, Schema, Table and Fileset will be supported in the remaining PRs.

Why are the changes needed?

Fix: #2080

How was this patch tested?

Add unit tests to test the metalake metadata ops.

@xloya xloya changed the title [#1811] feat(relation-entity-store): Add MySQL backend operation for metalake [#1811] feat(relation-entity-store): Add MySQL backend operations for metalake Feb 2, 2024
@xloya xloya marked this pull request as draft February 2, 2024 07:17
@xloya
Copy link
Contributor Author

xloya commented Feb 2, 2024

In this PR, Mybatis is used as the ORM framework to implement complex joint queries through SQL in the future, and transaction management can be performed well.

@xloya xloya force-pushed the add-mysql-backend-ops-for-metalake branch 2 times, most recently from 9a8389b to 92ca94b Compare February 4, 2024 03:03
@xloya xloya marked this pull request as ready for review February 5, 2024 04:00
@xloya
Copy link
Contributor Author

xloya commented Feb 5, 2024

@jerryshao @yuqi1129 @coolderli This PR is ready for review, please take a look when you have time, thanks!

@xloya xloya force-pushed the add-mysql-backend-ops-for-metalake branch 4 times, most recently from 4594fe2 to 1fc8cd0 Compare February 5, 2024 08:11
@xloya xloya force-pushed the add-mysql-backend-ops-for-metalake branch from 1fc8cd0 to 3442dbe Compare February 5, 2024 11:00
@xloya xloya changed the title [#1811] feat(relation-entity-store): Add MySQL backend operations for metalake [#2080] feat(relation-entity-store): Add MySQL backend operations for metalake Feb 5, 2024
@xloya xloya force-pushed the add-mysql-backend-ops-for-metalake branch 2 times, most recently from eb4164e to fde3c14 Compare February 6, 2024 06:16
LICENSE.bin Outdated Show resolved Hide resolved
@xloya xloya force-pushed the add-mysql-backend-ops-for-metalake branch 3 times, most recently from 0010748 to 2512912 Compare February 6, 2024 07:46
@qqqttt123 qqqttt123 changed the title [#2080] feat(relation-entity-store): Add MySQL backend operations for metalake [#2080] feat(relational-entity-store): Add MySQL backend operations for metalake Feb 6, 2024
@yuqi1129
Copy link
Contributor

yuqi1129 commented Feb 6, 2024

@xloya Thanks for your PR.
I have something in mind.
We need to distinguish the function and boundary Backend and EntityStore. In my opinion, Backend should not sense the existence of Entity and only focus on storage. For example, MySQLBackend only needs to handle SQL and KvBackend only focuses on KV. Can we move the SQL session and related entity logic to EntityStore?

@xloya xloya force-pushed the add-mysql-backend-ops-for-metalake branch 3 times, most recently from 2b2aef4 to 0faa6ec Compare February 26, 2024 08:27
@xloya xloya force-pushed the add-mysql-backend-ops-for-metalake branch from 0faa6ec to 7760554 Compare February 26, 2024 08:31
@jerryshao
Copy link
Contributor

@xloya , overall LGTM, I have no further comment, we can update anything missing in the follow-up PRs.

@jerryshao jerryshao merged commit 2a03fd7 into apache:main Feb 26, 2024
5 checks passed
@xloya
Copy link
Contributor Author

xloya commented Feb 26, 2024

Thanks @qqqttt123 @yuqi1129 @jerryshao @diqiu50 @YxAc @coolderli @justinmclean for your reviews!

yuqi1129 pushed a commit that referenced this pull request Feb 28, 2024
### What changes were proposed in this pull request?

The purpose of this PR is to implement JDBC backend operation `Catalog`
metadata. Depend on #1980 . Metadata operations of Schema, Table and
Fileset will be supported in the remaining PRs.

### Why are the changes needed?

Fix: #2081 

### How was this patch tested?

Add unit tests to test the catalog metadata ops.

---------

Co-authored-by: xiaojiebao <[email protected]>
@xloya xloya deleted the add-mysql-backend-ops-for-metalake branch February 29, 2024 11:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Subtask] Add JDBC Backend ops for Metalake
8 participants