Skip to content
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

Merged
merged 1 commit into from
Dec 18, 2020
Merged

Release 2.0.0 #2753

merged 1 commit into from
Dec 18, 2020

Conversation

k-rus
Copy link
Contributor

@k-rus k-rus commented Dec 17, 2020

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:

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:

  • @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

@codecov
Copy link

codecov bot commented Dec 17, 2020

Codecov Report

Merging #2753 (e3a0cf3) into master (d13afc7) will increase coverage by 0.11%.
The diff coverage is 90.00%.

Impacted file tree graph

@@            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     
Impacted Files Coverage Δ
tsl/src/dist_util.c 93.28% <ø> (ø)
tsl/src/remote/connection.c 91.57% <88.57%> (-0.56%) ⬇️
tsl/src/data_node.c 96.25% <100.00%> (+0.02%) ⬆️
tsl/src/data_node_dispatch.c 97.02% <0.00%> (-0.25%) ⬇️
src/loader/bgw_message_queue.c 87.09% <0.00%> (ø)
src/import/planner.c 70.30% <0.00%> (+11.12%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a2275c7...e3a0cf3. Read the comment docs.

CHANGELOG.md Outdated Show resolved Hide resolved
@mfreed
Copy link
Member

mfreed commented Dec 17, 2020

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

CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Show resolved Hide resolved
@erimatnor
Copy link
Contributor

I think the PR is also missing an update to version.config

@mfreed
Copy link
Member

mfreed commented Dec 17, 2020

How about something like:


With this release, we’re 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 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.

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 view
    creation from 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 policies and user-defined actions, as well as support for
    multi-node TimescaleDB.
  • Moving all formerly enterprise features into our Community Edition, and
    our updated Timescale License which 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 should 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:

  • Properly block more unsupported functionalities on multinode
  • Improve and fix bugs in communication to data nodes
  • Optimize locking for create chunk API
  • Fix compression status in chunks view for distributed chunks

Bugfixes

Since the last release candidate 4, it includes several bugfixes:
*
*

Thanks

Thanks to all contributors for the TimescaleDB 2.0 release:

  • @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

CHANGELOG.md Outdated
Comment on lines 53 to 58
* Improve Continuous Aggregate API
* Redesign informational views
Copy link
Member

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?

CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
Copy link
Contributor

@erimatnor erimatnor left a 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.

@feikesteenbergen
Copy link
Member

If I build from this commit, I end up with a version 2.1.0-dev, is that supposed to happen (My expectation is that this commit would point to 2.0.0)

@k-rus
Copy link
Contributor Author

k-rus commented Dec 18, 2020

If I build from this commit, I end up with a version 2.1.0-dev, is that supposed to happen (My expectation is that this commit would point to 2.0.0)

@feikesteenbergen That's correct, since we are continuing to develop in master branch. The release branch will have version 2.0.0.

@k-rus k-rus marked this pull request as ready for review December 18, 2020 16:24
@k-rus k-rus requested a review from a team as a code owner December 18, 2020 16:24
@k-rus k-rus requested review from svenklemm and removed request for a team December 18, 2020 16:24
Copy link
Contributor

@pmwkaa pmwkaa left a 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
@k-rus k-rus merged commit 07175eb into timescale:master Dec 18, 2020
@k-rus k-rus deleted the 2.0.0-release branch December 18, 2020 20:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants