docs: Publish Cortex v1.20.0 release blog post #7218
Conversation
This file contains hidden or 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
Highlights new features and benefits in v1.20.0 release including: - Prometheus Remote Write 2.0 support (experimental) - Parquet format support for storage (experimental) - Advanced query federation with regex tenant resolver - gRPC stream push for distributor-ingester communication - Enhanced native histogram support - Resource-based monitoring and limiting - UTF-8 name validation support Signed-off-by: shri3016] <[email protected]>
Author
Author
|
Thanks @yeya24 for allowing the workflow run,I can see that 3 tests are failing,can you guide on what is to be done from my side? Thank you! |
friedrichg
reviewed
Jan 16, 2026
| - A new **Parquet converter service** to transform TSDB blocks into Parquet format. | ||
| - A **Parquet querier** for querying Parquet files directly. | ||
|
|
||
| Parquet's columnar storage offers superior compression and query performance, especially for analytical workloads. This feature allows users to optimize storage costs and query speeds for historical data, potentially reducing infrastructure expenses by up to 50% in certain scenarios. |
Member
There was a problem hiding this comment.
Suggested change
| Parquet's columnar storage offers superior compression and query performance, especially for analytical workloads. This feature allows users to optimize storage costs and query speeds for historical data, potentially reducing infrastructure expenses by up to 50% in certain scenarios. | |
| Parquet's columnar storage offers superior compression and query performance, especially for analytical workloads. This feature allows users to optimize query speeds for historical data and storage footprint |
I think parquet is great, but I am not sure it will save us that much in infrastructure. I think it improves query speed and storage footprint, but 50% savings sounds wild.
Or maybe there is something I don't know. Can you chime in @yeya24 here?
Contributor
There was a problem hiding this comment.
I am not sure where those numbers are coming from. I don't have specific number for this
Contributor
|
Probably just my personal opinion but I think we should probably dive deeper here. This blog post seems similar to the release post we did |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What this PR does
Publishes a blog post announcing Cortex v1.20.0 release, highlighting major new features and their benefits for Cortex users.
The blog post covers:
This helps inform the Cortex community about the significant improvements and capabilities introduced in v1.20.0.
Which issue(s) this PR fixes
Fixes #7104
Checklist
CHANGELOG.mdupdated (N/A - documentation only)