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

Initial version of MySQL frontend connector (based on Vitess) #1212

Merged
merged 2 commits into from
Jan 29, 2025

Conversation

avelanarius
Copy link
Member

@avelanarius avelanarius commented Jan 22, 2025

In #1211, an initial (experimental) version of (TCP) passthrough MySQL processor was introduced. That processor/frontend was merely a minimally invasive TCP proxy, which snooped on the traffic, was able to recognize Query packets and potentially modify some packets. That processor/frontend required us to always have a real MySQL instance running and it was not easy for the processor to use a different SQL DB as a backend (such as Postgres).

The components in this PR are MySQL frontend connector (based on Vitess) and MySQL processor (paired with MySQL Vitess frontend connector). They try to emulate a MySQL instance and don't require having a real MySQL instance running. A disadvantage of this approach is that we have to manually construct MySQL responses (abstracted by Vitess structures).

This is still an experimental frontend/processor (alpha) and it's only a base code, on which we will further experiment.

@avelanarius avelanarius force-pushed the mysql_vitess branch 2 times, most recently from 20dc912 to fbe1269 Compare January 29, 2025 10:21
@@ -1,6 +1,6 @@
module github.com/QuesmaOrg/quesma/quesma

go 1.23.2
go 1.23.5
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vitess library requires go 1.23.5

@avelanarius avelanarius changed the title [early experimental WIP] MySQL frontend connector based on Vitess [WIP] MySQL frontend connector based on Vitess Jan 29, 2025
@avelanarius avelanarius changed the title [WIP] MySQL frontend connector based on Vitess Initial version of MySQL frontend connector (based on Vitess) Jan 29, 2025
@avelanarius avelanarius marked this pull request as ready for review January 29, 2025 10:58
@avelanarius avelanarius requested a review from a team as a code owner January 29, 2025 10:58
@avelanarius avelanarius added this pull request to the merge queue Jan 29, 2025
Merged via the queue into QuesmaOrg:main with commit a7c2a17 Jan 29, 2025
5 checks passed
@avelanarius avelanarius deleted the mysql_vitess branch January 29, 2025 14:12
avelanarius added a commit to avelanarius/quesma that referenced this pull request Jan 29, 2025
After QuesmaOrg#1212, go-licence-detector GitHub Actions job started failing.
One of the added dependencies uses Unlicence licence, which is not
on the allowlist of the default go-licence-detector rules list.

Unlicence is a public-domain-equivalent licence. The default rules list
already allowed similar licences, such as "CC0-1.0" and "Public Domain",
so it should be OK to add Unlicence to the allowed list.

The added rules.json is a default rules file with only Unlicence added.

This fixes the NOTICE.MD generation with go-licence-detector.
avelanarius added a commit to avelanarius/quesma that referenced this pull request Jan 29, 2025
After QuesmaOrg#1212, go-licence-detector GitHub Actions job started failing.
One of the added dependencies uses Unlicence licence, which is not
on the allowlist of the default go-licence-detector rules list.

Unlicence is a public-domain-equivalent licence. The default rules list
already allowed similar licences, such as "CC0-1.0" and "Public Domain",
so it should be OK to add Unlicence to the allowed list.

The added rules.json is a default rules file with only Unlicence added.

This fixes the NOTICE.MD generation with go-licence-detector.
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.

2 participants