clickhouse version is out of support period
Nobody has claimed this yet.
- Dominant language
- HCL
- Stars
- 4
- Forks
- 15
- Avg merge
- 1h 50m
- Merged PRs (30d)
- 4
Description
https://clickhouse.com/docs/faq/operations/production#how-to-choose-between-clickhouse-releases
stable is the kind of package we recommend by default. They're released roughly monthly (and thus provide new features with reasonable delay) and three latest stable releases are supported in terms of diagnostics and backporting of bug fixes.
lts are released twice a year and are supported for a year after their initial release. You might prefer them over stable in the following cases:Your company has some internal policies that don't allow for frequent upgrades or using non-LTS software. You're using ClickHouse in some secondary products that either don't require any complex ClickHouse features or don't have enough resources to keep it updated.
we're on version 24.8.6.70 which is EOL. I looked at the changelog and there don't appear to be any issues that require urgent upgrade but we should consider doing this sooner or later as some changes are not backwards compatible and therefore we may not want to get too far behind a stable or LTS release.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ClickHouse support guidance linked in the issue and locate where version 24.8.6.70 is configured in this repository. Choose a supported stable or LTS release, update the pinned version, and verify the deployment; the issue mentions no specific file or test, so compatibility checks are needed to define done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse
- Domain
- databases, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100