-
Notifications
You must be signed in to change notification settings - Fork 879
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
Release 2.0.0 #2753
Release 2.0.0 #2753
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2753 +/- ##
==========================================
+ Coverage 90.12% 90.24% +0.11%
==========================================
Files 212 212
Lines 34640 34614 -26
==========================================
+ Hits 31218 31236 +18
+ Misses 3422 3378 -44
Continue to review full report at Codecov.
|
Let me leave comments later today. I think we want to really flesh out the release notes here a bit more, and possibly link back to the 4 RCs: etc |
I think the PR is also missing an update to |
How about something like: With this release, we’re officially moving TimescaleDB 2.0 to GA, concluding TimescaleDB 2.0 adds the much-anticipated support for distributed hypertables Multi-node architecture: In particular, with TimescaleDB 2.0, users can now This release also adds:
Some of the changes above (e.g., continuous aggregates, updated informational Major Features TimescaleDB 2.0 moves the following major features to GA:
Previous Release Candidates
Minor Features Since the last release candidate 4, it includes several minor improvements:
Bugfixes Since the last release candidate 4, it includes several bugfixes: Thanks Thanks to all contributors for the TimescaleDB 2.0 release:
|
CHANGELOG.md
Outdated
* Improve Continuous Aggregate API | ||
* Redesign informational views |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possible to link more than one github issues to these features?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving, but assuming merge wont happen until prerelease tests pass and tagging will happen.
If I build from this commit, I end up with a version |
@feikesteenbergen That's correct, since we are continuing to develop in master branch. The release branch will have version 2.0.0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
With this release, we are officially moving TimescaleDB 2.0 to GA, concluding several release candidates. TimescaleDB 2.0 adds the much-anticipated support for distributed hypertables (multi-node TimescaleDB), as well as new features and enhancements to core functionality to give users better clarity and more control and flexibility over their data. Multi-node architecture: In particular, with TimescaleDB 2.0, users can now create distributed hypertables across multiple instances of TimescaleDB, configured so that one instance serves as an access node and multiple others as data nodes. All queries for a distributed hypertable are issued to the access node, but inserted data and queries are pushed down across data nodes for greater scale and performance. Multi-node TimescaleDB can be self managed or, for easier operation, launched within Timescale's fully-managed cloud services. This release also adds: * Support for user-defined actions, allowing users to define, customize, and schedule automated tasks, which can be run by the built-in jobs scheduling framework now exposed to users. * Significant changes to continuous aggregates, which now separate the view creation from the policy. Users can now refresh individual regions of the continuous aggregate materialized view, or schedule automated refreshing via policy. * Redesigned informational views, including new (and more general) views for information about hypertable's dimensions and chunks, policies and user-defined actions, as well as support for multi-node TimescaleDB. * Moving all formerly enterprise features into our Community Edition, and updating Timescale License, which now provides additional (more permissive) rights to users and developers. Some of the changes above (e.g., continuous aggregates, updated informational views) do introduce breaking changes to APIs and are not backwards compatible. While the update scripts in TimescaleDB 2.0 will upgrade databases running TimescaleDB 1.x automatically, some of these API and feature changes may require changes to clients and/or upstream scripts that rely on the previous APIs. Before upgrading, we recommend reviewing upgrade documentation at docs.timescale.com for more details. **Major Features** TimescaleDB 2.0 moves the following major features to GA: * timescale#1923 Add support for distributed hypertables * timescale#2006 Add support for user-defined actions * timescale#2125 timescale#2221 Improve Continuous Aggregate API * timescale#2084 timescale#2089 timescale#2098 timescale#2417 Redesign informational views * timescale#2435 Move enterprise features to community * timescale#2437 Update Timescale License **Previous Release Candidates** * timescale#2702 Release Candidate 4 (December 2, 2020) * timescale#2637 Release Candidate 3 (November 12, 2020) * timescale#2554 Release Candidate 2 (October 20, 2020) * timescale#2478 Release Candidate 1 (October 1, 2020) **Minor Features** Since the last release candidate 4, it includes several minor improvements: * timescale#2746 Optimize locking for create chunk API * timescale#2705 Block tableoid access on distributed hypertable * timescale#2730 Do not allow unique index on compressed hypertables **Bugfixes** Since the last release candidate 4, it includes several bugfixes: * timescale#2719 Support disabling compression on distributed hypertables * timescale#2742 Fix compression status in chunks view for distributed chunks * timescale#2751 Fix crash and cancel when adding data node **Thanks** Thanks to all contributors for the TimescaleDB 2.0 release: * @airton-neto for reporting a bug in executing some queries with UNION * @nshah14285 for reporting an issue with propagating privileges * @kalman5 for reporting an issue with renaming constraints * @LbaNeXte for reporting a bug in decompression for queries with subqueries * @semtexzv for reporting an issue with continuous aggregates on int-based hypertables * @mr-ns for reporting an issue with privileges for creating chunks * @cloud-rocket for reporting an issue with setting an owner on continuous aggregate * @jocrau for reporting a bug during creating an index with transaction per chunk * @fvannee for reporting an issue with custom time types * @ArtificialPB for reporting a bug in executing queries with conditional ordering on compressed hypertable * @dutchgecko for reporting an issue with continuous aggregate datatype handling * @lambdaq for suggesting to improve error message in continuous aggregate creation * @francesco11112 for reporting memory issue on COPY * @Netskeh for reporting bug on time_bucket problem in continuous aggregates * @mr-ns for reporting the issue with CTEs on distributed hypertables * @akamensky for reporting an issue with recursive cache invalidation * @ryanbooz for reporting slow queries with real-time aggregation on continuous aggregates * @cevian for reporting an issue with disabling compression on distributed hypertables
With this release, we are officially moving TimescaleDB 2.0 to GA,
concluding several release candidates.
TimescaleDB 2.0 adds the much-anticipated support for distributed
hypertables (multi-node TimescaleDB), as well as new features and
enhancements to core functionality to give users better clarity and
more control and flexibility over their data.
Multi-node architecture: In particular, with TimescaleDB 2.0, users
can now create distributed hypertables across multiple instances of
TimescaleDB, configured so that one instance serves as an access node
and multiple others as data nodes. All queries for a distributed
hypertable are issued to the access node, but inserted data and queries
are pushed down across data nodes for greater scale and performance.
Multi-node TimescaleDB can be self managed or, for easier operation,
launched within Timescale's fully-managed cloud services.
This release also adds:
customize, and schedule automated tasks, which can be run by the
built-in jobs scheduling framework now exposed to users.
view creation from the policy. Users can now refresh individual
regions of the continuous aggregate materialized view, or schedule
automated refreshing via policy.
views for information about hypertable's dimensions and chunks,
policies and user-defined actions, as well as support for multi-node
TimescaleDB.
and updating Timescale License, which now provides additional (more
permissive) rights to users and developers.
Some of the changes above (e.g., continuous aggregates, updated
informational views) do introduce breaking changes to APIs and are not
backwards compatible. While the update scripts in TimescaleDB 2.0 will
upgrade databases running TimescaleDB 1.x automatically, some of these
API and feature changes may require changes to clients and/or upstream
scripts that rely on the previous APIs. Before upgrading, we recommend
reviewing upgrade documentation at docs.timescale.com for more details.
Major Features
TimescaleDB 2.0 moves the following major features to GA:
Previous Release Candidates
Minor Features
Since the last release candidate 4, it includes several minor
improvements:
Bugfixes
Since the last release candidate 4, it includes several bugfixes:
Thanks
Thanks to all contributors for the TimescaleDB 2.0 release:
subqueries
int-based hypertables
continuous aggregate
per chunk
conditional ordering on compressed hypertable
handling
aggregate creation
aggregates
continuous aggregates
distributed hypertables