Upgrade minimum supported Altinity to version 20.8 #10975
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ebyhr
force-pushed
the
ebi/clickhouse-remove-20.3
branch
from
08d0003 to
251ed52
Compare
hashhar
approved these changes
Feb 8, 2022
Altinity server 20.3 hasn't yet reached EOL, but ClickHouse JDBC driver doesn't support it.
ebyhr
force-pushed
the
ebi/clickhouse-remove-20.3
branch
from
251ed52 to
df2d03e
Compare
hashhar
approved these changes
Feb 8, 2022
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Upgrade minimum supported Altinity to version 20.8
General information
Is this change a fix, improvement, new feature, refactoring, or other?
maintenance
Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)
connector
How would you describe this change to a non-technical end user or system administrator?
n/a
Related issues, pull requests, and links
Documentation
( ) No documentation is needed.
(x) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.
Release notes
( ) No release notes entries required.
( ) Release notes entries required with the following suggested text: