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.

Sign up for GitHub

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

Jump to bottom

chore: release branch for TimescaleDB v2.18.0. #3764

Draft
wants to merge 16 commits into
base: latest
Choose a base branch
from
Draft

chore: release branch for TimescaleDB v2.18.0. #3764

wants to merge 16 commits into from

Conversation

billy-the-fish
Copy link
Contributor

No description provided.

@billy-the-fish billy-the-fish self-assigned this Jan 27, 2025
@billy-the-fish billy-the-fish linked an issue Jan 27, 2025 that may be closed by this pull request
Milestone branch for TimescaleDB v2.18.0 #3763
Open
@billy-the-fish billy-the-fish marked this pull request as draft January 27, 2025 09:40
@github-actions GitHub Actions
Copy link

Allow 10 minutes from last push for the staging site to build. If the link doesn't work, try using incognito mode instead. For internal reviewers, check web-documentation repo actions for staging build status. Link to build for this PR: http://docs-dev.timescale.com/docs-release-2-18-0-main

fabriziomello and others added 5 commits January 28, 2025 15:46
@fabriziomello @gayyappan
@mkindahl @billy-the-fish
Update some API changes: (#3759)
47f0aa2 
- `add_continuous_aggregate_policy`: added new optional argument
  `include_tiered_data` introduced by 2.18.0.
- `refresh_continuous_aggregate`: added new optional argument `force`
  introduced by 2.18.0.

Signed-off-by: Fabrízio de Royes Mello <[email protected]>
Co-authored-by: Gayathri Ayyappan <[email protected]>
Co-authored-by: Mats Kindahl <[email protected]>
Co-authored-by: Iain Cox <[email protected]>
@billy-the-fish @erimatnor
Hypercore API ref (#3699)
e5140f9 
* chore: add api ref files and alter_table to the build.

Signed-off-by: Iain Cox <[email protected]>
Co-authored-by: Erik Nordström <[email protected]>
@billy-the-fish
Merge branch 'latest' into release-2.18.0-main
c1b22ef
@billy-the-fish @erimatnor
@atovpeko @MetalBlueberry @mkindahl
262 docs rfccreate a page automate hypercore using jobs (#3728)
9abfedd 
* chore: lots of messing about

---------

Signed-off-by: Iain Cox <[email protected]>
Co-authored-by: Erik Nordström <[email protected]>
Co-authored-by: Anastasiia Tovpeko <[email protected]>
Co-authored-by: Victor Perez <[email protected]>
Co-authored-by: Mats Kindahl <[email protected]>
@billy-the-fish
chore: empty commit to kickstart the build.
28e8b39
ramonguiu
ramonguiu reviewed Feb 6, 2025
View reviewed changes
use-timescale/hypercore/index.md Outdated
Comment on lines 41 to 42
- **Indexing row and columnar data**: the `hypercore` table access method enables chunks in a
hypertable to maintain indexes over data in the rowstore and the columnstore. <Tag variant="hollow">Early access: TimescaleDB v2.18.0</Tag>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would remove this. We offer multiple options to index data but this feels out of place here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

use-timescale/hypercore/index.md Outdated

![Hypercore workflow](https://assets.timescale.com/docs/images/hypercore-overview.png)

<UsageBasedStorage />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The text for this also feels a bit out of place. I don't think that it belongs in here.
It "may" be worth pointing out that you only pay for what you use and os moving data to the columnstore which compresses it immediately translates into cost savings.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

use-timescale/hypercore/real-time-analytics-in-hypercore.md Outdated Show resolved Hide resolved
use-timescale/hypercore/real-time-analytics-in-hypercore.md Outdated
Comment on lines 26 to 28
<EarlyAccess /> Indexes are a central component to designing efficient and performant databases: they allow
unstructured data to be searched in efficiently executed queries. TimescaleDB supplies the `hypercore` table access
method that enables chunks in a hypertable to maintain indexes over data in the rowstore and the columnstore.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this belongs in here. We have other multiple indexes that help with performance that we are not calling out here. I would keep all information about indexes in its own section.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

use-timescale/hypercore/real-time-analytics-in-hypercore.md Outdated

<HCConversionOverview />

<UsageBasedStorage />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This again feels a bit out of place.

In most modern databases you pay for the storage you consume. This is just a differentiator against RDS. I don't think we need to call that out all the time. And if we do, we should not talk about growing the disk automatically but the important piece would be that when you reduce the storage size you immediately realize the savings.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

_partials/_hypercore_policy_workflow.md Outdated
Comment on lines 44 to 52
* <EarlyAccess /> To enable indexing over data in the rowstore and the columnstore, tell the policy
to use the Hypercore table access method.

``` sql
CALL add_columnstore_policy(
'older_stock_prices',
after => INTERVAL '60d',
hypercore_use_access_method => true);
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, I don't think this belongs in here. This should be listed with other indexing options and explaining tradeoffs / when to use not to use. We should NOT guide everyone to enable this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

_partials/_hypercore_policy_workflow.md Outdated
```
Before you say `huh`, a continuous aggregate is a specialized hypertable.

* <EarlyAccess /> Enable indexing over all data in the rowstore and columnstore:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove from here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

_partials/_hypercore_policy_workflow.md Outdated
```
This is also early access for continuous aggregates.

1. **Add a policy to move chunks to the columnstore at a specific time interval**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We say convert not move

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

billy-the-fish and others added 10 commits February 7, 2025 09:43
@billy-the-fish
chore: remove secondary indexing stuff and other review updates.
8109403
@billy-the-fish
chore: remove secondary indexing stuff and other review updates.
525565f
@atovpeko @billy-the-fish
Data mode clarification (#3800)
7313063
@atovpeko @billy-the-fish
Added the data mode part to IP allow list (#3797)
4c25758
@mrksngl @billy-the-fish
Update hypertable_compression_stats.md (#3765)
ff4e215 
minor typo and return type fix

Signed-off-by: Markus Engel <[email protected]>
Co-authored-by: Iain Cox <[email protected]>
@rahilsondhi @billy-the-fish
TimescaleDB v2.18 and SQL Assistant Improvements in Data Mode and Pop…
a516aaa 
…SQL (#3810)
@atovpeko @billy-the-fish
Clarified refresh policy for CAGGs
91c0cac
@atovpeko @billy-the-fish
Update images in the changelog
a37d76e
@atovpeko @billy-the-fish
Fix links
b247ea0
@billy-the-fish @erimatnor
Hypercore API ref (#3699)
2e47554 
* chore: add api ref files and alter_table to the build.

Signed-off-by: Iain Cox <[email protected]>
Co-authored-by: Erik Nordström <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ramonguiu ramonguiu ramonguiu left review comments

At least 1 approving review is required to merge this pull request.

Assignees

@billy-the-fish billy-the-fish

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Milestone branch for TimescaleDB v2.18.0
6 participants
@billy-the-fish @ramonguiu @fabriziomello @atovpeko @mrksngl @rahilsondhi