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

MySQL binary protocol implementation for initial support of Tableau Online #54115

Merged

Conversation

slvrtrn
Copy link
Contributor

@slvrtrn slvrtrn commented Aug 31, 2023

Resolves #51103.

This PR allows connecting to Tableau Online, discovering the tables, and fetching the data.

Tableau Online wraps everything into prepared statements, even the simplest SELECTs. However, it does not add the parameters to bind - everything is hardcoded into the query. The current MySQL interface implementation was missing binary protocol implementation, as well as COM_STMT_PREPARE, COM_STMT_EXECUTE, and COM_STMT_CLOSE handlers. This PR addresses this.

Please note: the prepared statements implementation is pretty minimal, we do not support arguments binding yet, it is not required in this particular Tableau online use case. It will be implemented as a follow-up if necessary after extensive testing of Tableau Online in case we discover issues.

I also tweaked SHOW COLUMNS a bit as it did not 100% match the MySQL spec.

Corner cases of Decimal128 with precision > 65 or scale > 30 were also addressed, as this is the maximum according to the spec.

Changelog category (leave one):

  • Improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

The MySQL interface gained a minimal implementation of prepared statements, just enough to allow a connection from Tableau Online to ClickHouse via the MySQL connector.

@rschu1ze rschu1ze self-assigned this Aug 31, 2023
@robot-ch-test-poll3 robot-ch-test-poll3 added the pr-improvement Pull request with some product improvements label Aug 31, 2023
@robot-ch-test-poll3
Copy link
Contributor

robot-ch-test-poll3 commented Aug 31, 2023

This is an automated comment for commit 44e1f6b with description of existing statuses. It's updated for the latest CI running

❌ Click here to open a full report in a separate page

Successful checks
Check nameDescriptionStatus
AST fuzzerRuns randomly generated queries to catch program errors. The build type is optionally given in parenthesis. If it fails, ask a maintainer for help✅ success
CI runningA meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR✅ success
ClickHouse build checkBuilds ClickHouse in various configurations for use in further steps. You have to fix the builds that fail. Build logs often has enough information to fix the error, but you might have to reproduce the failure locally. The cmake options can be found in the build log, grepping for cmake. Use these options and follow the general build process✅ success
Compatibility checkChecks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help✅ success
Docker image for serversThe check to build and optionally push the mentioned image to docker hub✅ success
Docs CheckBuilds and tests the documentation✅ success
Fast testNormally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here✅ success
Flaky testsChecks if new added or modified tests are flaky by running them repeatedly, in parallel, with more randomization. Functional tests are run 100 times with address sanitizer, and additional randomization of thread scheduling. Integrational tests are run up to 10 times. If at least once a new test has failed, or was too long, this check will be red. We don't allow flaky tests, read the doc✅ success
Install packagesChecks that the built packages are installable in a clear environment✅ success
Mergeable CheckChecks if all other necessary checks are successful✅ success
Performance ComparisonMeasure changes in query performance. The performance test report is described in detail here. In square brackets are the optional part/total tests✅ success
Push to DockerhubThe check for building and pushing the CI related docker images to docker hub✅ success
SQLTestThere's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS✅ success
SQLancerFuzzing tests that detect logical bugs with SQLancer tool✅ success
SqllogicRun clickhouse on the sqllogic test set against sqlite and checks that all statements are passed✅ success
Stateful testsRuns stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc✅ success
Stress testRuns stateless functional tests concurrently from several clients to detect concurrency-related errors✅ success
Style CheckRuns a set of checks to keep the code style clean. If some of tests failed, see the related log from the report✅ success
Unit testsRuns the unit tests for different release types✅ success
Upgrade checkRuns stress tests on server version from last release and then tries to upgrade it to the version from the PR. It checks if the new server can successfully startup without any errors, crashes or sanitizer asserts✅ success
Check nameDescriptionStatus
Integration testsThe integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests❌ failure
Stateless testsRuns stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc❌ failure

@mshustov mshustov added the can be tested Allows running workflows for external contributors label Aug 31, 2023
@clickhouse-ci
Copy link

clickhouse-ci bot commented Sep 1, 2023

This is an automatic comment. The PR descriptions does not match the template.

Please, edit it accordingly.

The error is: Changelog entry required for category 'Improvement'

4 similar comments
@clickhouse-ci
Copy link

clickhouse-ci bot commented Sep 1, 2023

This is an automatic comment. The PR descriptions does not match the template.

Please, edit it accordingly.

The error is: Changelog entry required for category 'Improvement'

@clickhouse-ci
Copy link

clickhouse-ci bot commented Sep 1, 2023

This is an automatic comment. The PR descriptions does not match the template.

Please, edit it accordingly.

The error is: Changelog entry required for category 'Improvement'

@clickhouse-ci
Copy link

clickhouse-ci bot commented Sep 1, 2023

This is an automatic comment. The PR descriptions does not match the template.

Please, edit it accordingly.

The error is: Changelog entry required for category 'Improvement'

@clickhouse-ci
Copy link

clickhouse-ci bot commented Sep 1, 2023

This is an automatic comment. The PR descriptions does not match the template.

Please, edit it accordingly.

The error is: Changelog entry required for category 'Improvement'

@clickhouse-ci clickhouse-ci bot added manual approve Manual approve required to run CI labels Sep 4, 2023
@slvrtrn slvrtrn marked this pull request as ready for review September 4, 2023 19:51
@rschu1ze rschu1ze changed the title MySQL binary protocol implementation and initial Tableau online support Implement the MySQL binary protocol implementation for initial support of Tableau Online Sep 5, 2023
Copy link
Member

@rschu1ze rschu1ze left a comment

Choose a reason for hiding this comment

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

Second batch of comments.

src/Core/MySQL/PacketsProtocolBinary.cpp Outdated Show resolved Hide resolved
src/Core/MySQL/PacketsProtocolBinary.h Outdated Show resolved Hide resolved
src/Core/MySQL/PacketsProtocolBinary.cpp Outdated Show resolved Hide resolved
src/Core/MySQL/PacketsProtocolBinary.cpp Outdated Show resolved Hide resolved
src/Core/MySQL/PacketsProtocolBinary.cpp Outdated Show resolved Hide resolved
break;
}
case TypeIndex::UInt16: {
UInt16 value = assert_cast<const ColumnVector<UInt16> &>(*col).getData()[row_num];
Copy link
Member

Choose a reason for hiding this comment

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

We are casting *col to the specific column implementation of the corresponding type (e.g. ColumnVector<UInt16>). That is okay.

But: This only works if col is not of low-cardinality (ColumnLowCardinality), or nullable (ColumnNullable), sparse (ColumnSparse) or const (ColumnConst) type. These classes are (possibly chained) wrappers around the actual column structure. In l. 164, we are stripping the low-cardinality and nullness of the datatype away, but we would need to do something equivalent for col. Check e.g. recursiveRemoveSparse() (Columns/ColumnSparse.h), etc.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

LowCardinality and Nullable are removed prior to that, so I assumed it should always work as intended.

Copy link
Member

Choose a reason for hiding this comment

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

They are only removed from the data type, not from the actual data. I am pretty sure this will go boom, please try it out.

src/Core/MySQL/PacketsProtocolBinary.cpp Outdated Show resolved Hide resolved
src/Core/MySQL/PacketsProtocolBinary.cpp Outdated Show resolved Hide resolved
src/Core/MySQL/PacketsProtocolBinary.cpp Outdated Show resolved Hide resolved
src/Core/MySQL/PacketsProtocolBinary.cpp Outdated Show resolved Hide resolved
Copy link
Member

@rschu1ze rschu1ze left a comment

Choose a reason for hiding this comment

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

Dumping the 3rd batch of comments. More tomorrow.

src/Core/MySQL/PacketsProtocolBinary.cpp Outdated Show resolved Hide resolved
src/Core/MySQL/PacketsProtocolBinary.cpp Outdated Show resolved Hide resolved
src/Core/MySQL/PacketsProtocolBinary.cpp Outdated Show resolved Hide resolved
src/Core/MySQL/PacketsProtocolBinary.cpp Outdated Show resolved Hide resolved
src/DataTypes/DataTypesDecimal.cpp Show resolved Hide resolved
src/Server/MySQLHandler.h Outdated Show resolved Hide resolved
src/Server/MySQLHandler.h Outdated Show resolved Hide resolved
src/Server/MySQLHandler.cpp Outdated Show resolved Hide resolved
src/Server/MySQLHandler.cpp Outdated Show resolved Hide resolved
src/Server/MySQLHandler.cpp Outdated Show resolved Hide resolved
Copy link
Member

@rschu1ze rschu1ze left a comment

Choose a reason for hiding this comment

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

Lgtm, thanks.

Kindly look at the remaining (mostly small) comments, we can submit afterwards.

src/Core/MySQL/PacketsProtocolBinary.h Outdated Show resolved Hide resolved
src/Core/MySQL/PacketsProtocolBinary.cpp Outdated Show resolved Hide resolved
src/Server/MySQLHandler.h Outdated Show resolved Hide resolved
src/Server/MySQLHandler.cpp Outdated Show resolved Hide resolved
src/Server/MySQLHandler.cpp Outdated Show resolved Hide resolved
src/Server/MySQLHandler.cpp Outdated Show resolved Hide resolved
src/Server/MySQLHandler.cpp Outdated Show resolved Hide resolved
break;
}
case TypeIndex::UInt16: {
UInt16 value = assert_cast<const ColumnVector<UInt16> &>(*col).getData()[row_num];
Copy link
Member

Choose a reason for hiding this comment

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

They are only removed from the data type, not from the actual data. I am pretty sure this will go boom, please try it out.

rschu1ze added a commit to rschu1ze/ClickHouse that referenced this pull request Sep 12, 2023
1. Disables namespace indentation in accordance with 16. of (*) and the
   majority of the codebase.
2. Disables {} for single-statement if/for/while in accordance with 17.
   of (*) and the majority of the codebase.

Note: clang-format is used manually and voluntarily, usually only on new
files. Nothing is automatically reformatted, this is only about how new
files look.

Motivated by ClickHouse#54115 (comment).

(*) https://clickhouse.com/docs/en/development/style#formatting
@robot-clickhouse-ci-1 robot-clickhouse-ci-1 added the pr-status-⏳ PR with some pending statuses label Sep 13, 2023
@robot-ch-test-poll robot-ch-test-poll added pr-status-✅ PR with only success statuses and removed pr-status-⏳ PR with some pending statuses labels Sep 13, 2023
@robot-ch-test-poll2 robot-ch-test-poll2 added pr-status-⏳ PR with some pending statuses and removed pr-status-✅ PR with only success statuses labels Sep 13, 2023
@robot-ch-test-poll1 robot-ch-test-poll1 added pr-status-❌ PR with some error/faliure statuses and removed pr-status-⏳ PR with some pending statuses labels Sep 13, 2023
@rschu1ze rschu1ze merged commit a9ae813 into ClickHouse:master Sep 14, 2023
280 of 283 checks passed
@slvrtrn slvrtrn changed the title Implement the MySQL binary protocol implementation for initial support of Tableau Online MySQL binary protocol implementation for initial support of Tableau Online Sep 15, 2023
@MaceWindu
Copy link
Contributor

Is it possible to disable this feature using CH option? It introduce several protocol violations making it unusable (I will try to fill found issues if they are not reported yet) as client library now switch to binary protocol

@rschu1ze
Copy link
Member

rschu1ze commented Oct 7, 2023

@MaceWindu No, it is not possible to disable the binary protocol as it an integral part of the MySQL wire protocol. If you run into problems due to this PR, kindly open an issue, ideally with a small example that doesn't work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
can be tested Allows running workflows for external contributors manual approve Manual approve required to run CI pr-improvement Pull request with some product improvements pr-status-❌ PR with some error/faliure statuses
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MySQL compatibility: command \x16 is not implemented
9 participants