feat(clickhouse-driver): add intelligent DDL handling for unsupported operations #9845
+367
−8
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.
Check List
Issue Reference this PR resolves
No specific issue reference - this is a proactive enhancement to improve ClickHouse driver compatibility
Description of Changes Made
This PR adds intelligent DDL (Data Definition Language) handling to the ClickHouse driver to handle operations that are not natively supported by certain ClickHouse storage engines, particularly the
Log
engine.Key Changes:
CREATE
,ALTER
,DROP
,TRUNCATE
,RENAME
,ATTACH
,DETACH
,GRANT
,REVOKE
)ALTER TABLE ADD COLUMN
onLog
engineTechnical Implementation:
connection.command()
instead ofconnection.query()
to avoid JSON parsing errorsALTER TABLE ADD COLUMN
onLog
engine: automatically recreates table with new schema, copies data, drops old table, renames new tableTesting:
ALTER TABLE ADD COLUMN
compatibility layer works as expectedProblem Solved:
The ClickHouse
Log
engine doesn't supportALTER TABLE ADD COLUMN
operations, returning error code 48 (NOT_IMPLEMENTED). This PR implements a compatibility layer that automatically handles this limitation by recreating the table with the new schema, ensuring data integrity while maintaining the expected behavior.