484 create table with start columnstore policy immediately and selecting partition column optional (#4529)

* chore: first steps for new create table.

* chore: change to using CREATE TABLE with the default columnstore policy rather than add_columnstore_policy in another step.

* chore: review updates.

* Apply suggestions from code review

Co-authored-by: Anastasiia Tovpeko <[email protected]>
Signed-off-by: Iain Cox <[email protected]>

* chore: update on review

* chore: change includes to show new way of working

* chore: update after review.

* Apply suggestions from code review

Co-authored-by: Philip Krauss <[email protected]>
Signed-off-by: Iain Cox <[email protected]>

* chore: update links

---------

Signed-off-by: Iain Cox <[email protected]>
Co-authored-by: billy-the-fish <[email protected]>
Co-authored-by: Anastasiia Tovpeko <[email protected]>
Co-authored-by: Philip Krauss <[email protected]>

Author: 4 people

.helper-scripts/llms/generate_llms_full.py

@@ -712,7 +712,7 @@ def process_imports(self, content: str, current_file_path: Path) -> str:
                     print(f"Replaced {component_name} using default path: {default_path}")
 
         # Remove or replace components that don't have clear partials
-        orphaned_components = ['Installation', 'Skip', 'OldCreateHypertable', 'PolicyVisualizerDownsampling', 'APIReference', 'Since2180']
+        orphaned_components = ['Installation', 'Skip', 'OldCreateHypertable', 'CreateHypertablePolicyNote', 'PolicyVisualizerDownsampling', 'APIReference', 'Since2180']
         for component_name in orphaned_components:
             # Handle both normal and spaced component tags
             component_tags = [

_partials/_create-hypertable-blockchain.md

@@ -1,4 +1,4 @@
-import OldCreateHypertable from "versionContent/_partials/_old-api-create-hypertable.mdx";
+import CreateHypertablePolicyNote from "versionContent/_partials/_create-hypertable-columnstore-policy-note.mdx";
 import HypertableIntro from "versionContent/_partials/_tutorials_hypertable_intro.mdx";
 
 ## Optimize time-series data using hypertables
@@ -31,13 +31,12 @@ import HypertableIntro from "versionContent/_partials/_tutorials_hypertable_intr
        details JSONB
     ) WITH (
        tsdb.hypertable,
-       tsdb.partition_column='time',
        tsdb.segmentby='block_id', 
        tsdb.orderby='time DESC'
     );
     ```
 
-    <OldCreateHypertable />
+    <CreateHypertablePolicyNote />
 
 1.  Create an index on the `hash` column to make queries for individual
     transactions faster:

_partials/_create-hypertable-columnstore-policy-note.md

@@ -0,0 +1,18 @@
+When you create a $HYPERTABLE using [CREATE TABLE ... WITH ...][hypertable-create-table], the default partitioning 
+column is automatically the first column with a timestamp data type. Also, $TIMESCALE_DB creates a 
+[columnstore policy][add_columnstore_policy] that automatically converts your data to the $COLUMNSTORE, after an interval equal to the value of the [chunk_interval][create_table_arguments], defined through `compress_after` in the policy. This columnar format enables fast scanning and 
+aggregation, optimizing performance for analytical workloads while also saving significant storage space. In the 
+$COLUMNSTORE conversion, $HYPERTABLE chunks are compressed by up to 98%, and organized for efficient, large-scale queries.
+
+You can customize this policy later using [alter_job][alter_job_samples]. However, to change `after` or 
+`created_before`, the compression settings, or the $HYPERTABLE the policy is acting on, you must 
+[remove the columnstore policy][remove_columnstore_policy] and [add a new one][add_columnstore_policy].
+
+You can also manually [convert chunks][convert_to_columnstore] in a $HYPERTABLE to the $COLUMNSTORE.
+
+[add_columnstore_policy]: /api/:currentVersion:/hypercore/add_columnstore_policy/
+[remove_columnstore_policy]: /api/:currentVersion:/hypercore/remove_columnstore_policy/
+[create_table_arguments]: /api/:currentVersion:/hypertable/create_table/#arguments
+[alter_job_samples]: /api/:currentVersion:/jobs-automation/alter_job/#samples
+[convert_to_columnstore]: /api/:currentVersion:/hypercore/convert_to_columnstore/
+[hypertable-create-table]: /api/:currentVersion:/hypertable/create_table/

_partials/_create-hypertable-energy.md

@@ -1,4 +1,4 @@
-import OldCreateHypertable from "versionContent/_partials/_old-api-create-hypertable.mdx";
+import CreateHypertablePolicyNote from "versionContent/_partials/_create-hypertable-columnstore-policy-note.mdx";
 import HypertableIntro from "versionContent/_partials/_tutorials_hypertable_intro.mdx";
 
 ## Optimize time-series data in hypertables
@@ -15,12 +15,11 @@ import HypertableIntro from "versionContent/_partials/_tutorials_hypertable_intr
         type_id integer                                not null,
         value   double precision                       not null
     ) WITH (
-       tsdb.hypertable,
-       tsdb.partition_column='time'
+       tsdb.hypertable
     );
     ```
 
-    <OldCreateHypertable />
+    <CreateHypertablePolicyNote />
 
 </Procedure>
 

_partials/_create-hypertable-nyctaxis.md

@@ -1,4 +1,4 @@
-import OldCreateHypertable from "versionContent/_partials/_old-api-create-hypertable.mdx";
+import CreateHypertablePolicyNote from "versionContent/_partials/_create-hypertable-columnstore-policy-note.mdx";
 
 
 ## Optimize time-series data in hypertables
@@ -15,7 +15,6 @@ same way. You use regular $PG tables for relational data.
 
 1. **Create a $HYPERTABLE to store the taxi trip data**
 
-
     ```sql
     CREATE TABLE "rides"(
         vendor_id TEXT,
@@ -38,11 +37,10 @@ same way. You use regular $PG tables for relational data.
         total_amount NUMERIC
     ) WITH (
        tsdb.hypertable,
-       tsdb.partition_column='pickup_datetime',
        tsdb.create_default_indexes=false
     );
     ```
-    <OldCreateHypertable />
+    <CreateHypertablePolicyNote />
 
 1.  **Add another dimension to partition your $HYPERTABLE more efficiently**
 

_partials/_create-hypertable-twelvedata-crypto.md

@@ -1,5 +1,5 @@
 import HypertableIntro from "versionContent/_partials/_tutorials_hypertable_intro.mdx";
-import OldCreateHypertable from "versionContent/_partials/_old-api-create-hypertable.mdx";
+import CreateHypertablePolicyNote from "versionContent/_partials/_create-hypertable-columnstore-policy-note.mdx";
 
 ## Optimize time-series data in a hypertable
 
@@ -25,12 +25,11 @@ import OldCreateHypertable from "versionContent/_partials/_old-api-create-hypert
         day_volume NUMERIC
     ) WITH (
        tsdb.hypertable,
-       tsdb.partition_column='time',
        tsdb.segmentby='symbol', 
        tsdb.orderby='time DESC'
     );
     ```
-   <OldCreateHypertable />
+   <CreateHypertablePolicyNote />
 
 </Procedure>
 

_partials/_create-hypertable-twelvedata-stocks.md

@@ -1,5 +1,5 @@
 import HypertableIntro from "versionContent/_partials/_tutorials_hypertable_intro.mdx";
-import OldCreateHypertable from "versionContent/_partials/_old-api-create-hypertable.mdx";
+import CreateHypertablePolicyNote from "versionContent/_partials/_create-hypertable-columnstore-policy-note.mdx";
 
 ## Optimize time-series data in hypertables
 
@@ -20,11 +20,10 @@ import OldCreateHypertable from "versionContent/_partials/_old-api-create-hypert
       price DOUBLE PRECISION NULL,
       day_volume INT NULL
     ) WITH (
-       tsdb.hypertable,
-       tsdb.partition_column='time'
+       tsdb.hypertable
     );
     ```
-   <OldCreateHypertable />
+   <CreateHypertablePolicyNote />
 
 1.  **Create an index to support efficient queries** 
 

_partials/_create-hypertable.md

@@ -1,5 +1,5 @@
 import HypertableIntro from "versionContent/_partials/_tutorials_hypertable_intro.mdx";
-import OldCreateHypertable from "versionContent/_partials/_old-api-create-hypertable.mdx";
+import CreateHypertablePolicyNote from "versionContent/_partials/_create-hypertable-columnstore-policy-note.mdx";
 
 <Procedure>
 
@@ -22,11 +22,10 @@ To create a hypertable:
       price DOUBLE PRECISION NULL,
       day_volume INT NULL
     ) WITH (
-       tsdb.hypertable,
-       tsdb.partition_column='time'
+       tsdb.hypertable
     );
     ```
-   <OldCreateHypertable />
+   <CreateHypertablePolicyNote />
 
    You see the result immediately:
 

_partials/_dimensions_info.md

@@ -1,4 +1,4 @@
-import OldCreateHypertable from "versionContent/_partials/_old-api-create-hypertable.mdx";
+import CreateHypertablePolicyNote from "versionContent/_partials/_create-hypertable-columnstore-policy-note.mdx";
 
 ### Dimension info
 
@@ -46,12 +46,11 @@ Create a by-range dimension builder. You can partition `by_range` on it's own.
       temperature DOUBLE PRECISION  NULL,
       humidity    DOUBLE PRECISION  NULL
    ) WITH (
-      tsdb.hypertable,
-      tsdb.partition_column='time'
+      tsdb.hypertable
    );
    ```
 
-   <OldCreateHypertable />
+   <CreateHypertablePolicyNote />
 
    This is the default partition, you do not need to add it explicitly.
 
@@ -152,8 +151,7 @@ CREATE TABLE conditions (
    temperature DOUBLE PRECISION  NULL,
    humidity    DOUBLE PRECISION  NULL
 ) WITH (
-   tsdb.hypertable,
-   tsdb.partition_column='time',
+   tsdb.hypertable
    tsdb.chunk_interval='1 day'
 );
 

_partials/_hypercore-intro-short.md

@@ -6,6 +6,8 @@ transactional capabilities.
 
 $HYPERCORE_CAP dynamically stores data in the most efficient format for its lifecycle:
 
+![Move from rowstore to columstore in hypercore](https://assets.timescale.com/docs/images/hypercore_intro.svg )
+
 * **Row-based storage for recent data**: the most recent chunk (and possibly more) is always stored in the $ROWSTORE, 
    ensuring fast inserts, updates, and low-latency single record queries. Additionally, row-based storage is used as a 
    writethrough for inserts and updates to columnar storage.