fix(monolith): Core and Enterprise release note cleanup.
Jason Stirnaman
parent
2f3c1c4bd1
commit
be22f14f92
|
|
@ -1,16 +1,17 @@
|
|||
---
|
||||
title: InfluxDB 3 Core Release Notes
|
||||
title: InfluxDB 3 Core release notes
|
||||
description: >
|
||||
Changes and updates to InfluxDB 3 Core
|
||||
menu:
|
||||
influxdb3_core:
|
||||
parent: Reference
|
||||
name: Release Notes
|
||||
weight: 21
|
||||
weight: 210
|
||||
related:
|
||||
- /influxdb3/core/get-started/
|
||||
source: /shared/v3-core-enterprise-release-notes/_index.md
|
||||
---
|
||||
|
||||
<!--
|
||||
The content of this file is located at /shared/v3-core-enterprise-release-notes/_index.md
|
||||
//SOURCE content/shared/v3-core-enterprise-release-notes/_index.md
|
||||
-->
|
||||
|
|
@ -1,16 +1,17 @@
|
|||
---
|
||||
title: InfluxDB 3 Enterprise Release Notes
|
||||
title: InfluxDB 3 Enterprise release notes
|
||||
description: >
|
||||
Changes and updates to InfluxDB 3 Enterprise
|
||||
menu:
|
||||
influxdb3_enterprise:
|
||||
parent: Reference
|
||||
name: Release Notes
|
||||
weight: 21
|
||||
weight: 210
|
||||
related:
|
||||
- /influxdb/enterprise/get-started/
|
||||
- /influxdb3/enterprise/get-started/
|
||||
source: /shared/v3-core-enterprise-release-notes/_index.md
|
||||
---
|
||||
|
||||
<!--
|
||||
The content of this file is located at /shared/v3-core-enterprise-release-notes/_index.md
|
||||
//SOURCE content/shared/v3-core-enterprise-release-notes/_index.md
|
||||
-->
|
||||
|
|
@ -1,44 +1,44 @@
|
|||
> [!Note]
|
||||
> InfluxDB 3 Enterprise is a super set of InfluxDB 3 Core. Any updates to Core are also reflected in Enterprise. Only non-Core updates are listed in the Enterprise sections below.
|
||||
> [!Note]
|
||||
> #### InfluxDB Core and Enterprise relationship
|
||||
>
|
||||
> InfluxDB 3 Enterprise is a superset of InfluxDB 3 Core.
|
||||
> All updates to Core are automatically included in Enterprise.
|
||||
> The Enterprise sections below only list features exclusive to Enterprise.
|
||||
|
||||
## v0.1.0 Beta {date="2025-03-17"}
|
||||
|
||||
### Core
|
||||
#### Features
|
||||
- **Query & Storage Enhancements**
|
||||
- New ability to stream data back for CSV and JSON queries, similar to how JSONL streaming works.
|
||||
- **Query and storage enhancements**
|
||||
- New ability to stream response data for CSV and JSON queries, similar to how JSONL streaming works.
|
||||
- Parquet files are now cached on the query path, improving performance.
|
||||
- Query buffer is incrementally cleared when snapshotting, lowering memory spikes.
|
||||
|
||||
- **Processing Engine Improvements**
|
||||
- New _scheduled_ trigger, enabling Python plugins to run on a custom, time-defined basis.
|
||||
- New _request_ trigger, enabling Python plugins to be called via HTTP requests.
|
||||
- New in-memory cache for storing data temporarily; this data can be stored for a single trigger or across all triggers.
|
||||
- Integration with virtual environments and install packages. You can now specify a Python virtual environment via the CLI or `VIRTUAL_ENV` variable and install packages or a requirements.txt.
|
||||
- Plugins no longer need to be created as their own entity. Simply creating a trigger and tying it to a Python file is enough.
|
||||
- **Processing engine improvements**
|
||||
- New _scheduled_ trigger enables Python plugins to run on a custom, time-defined basis.
|
||||
- New _request_ trigger enables calling Python plugins via HTTP requests.
|
||||
- New in-memory cache for storing data temporarily; cached data can be stored for a single trigger or across all triggers.
|
||||
- Integration with virtual environments and install packages. You can now specify a Python virtual environment via the CLI or `VIRTUAL_ENV` variable and install packages or a `requirements.txt`.
|
||||
- Python plugins are now implemented through triggers only. Simply create a trigger that references your Python plugin code file directly.
|
||||
- Snapshots are now persisted in parallel, improving performance by running jobs simultaneously, rather than sequentially.
|
||||
- You can now leverage logging from within the Processing Engine.
|
||||
- Write to logs from within the Processing Engine.
|
||||
|
||||
- **DB and CLI Improvements**
|
||||
- **DB and CLI improvements**
|
||||
- You can now specify the precision on your timestamps for writes using the `--precision` flag. Includes nano/micro/milli/seconds (ns/us/ms/s).
|
||||
- Added a new `show` system subcommand to display system tables with different options via SQL (default limit: 100)
|
||||
- Clearer table creation error messages
|
||||
|
||||
#### Bug Fixes
|
||||
#### Bug fixes
|
||||
- If a database was created and the service was killed before any data was written, the database would not be retained.
|
||||
- A last cache with specific “value” columns could not be queried.
|
||||
- Running CTRL-C no longer stopped an InfluxDB process, due to a Python trigger.
|
||||
- A previous build had broken JSON queries for RecordBatches.
|
||||
- There was an issue with the distinct cache that caused panics.
|
||||
|
||||
|
||||
### Enterprise
|
||||
#### Features
|
||||
- **Cluster Management**
|
||||
- Nodes are now tied to clusters simplifying compaction, read replication, processing, and more.
|
||||
- **Cluster management**
|
||||
- Nodes are now associated with _clusters_, simplifying compaction, read replication, and rocessing.
|
||||
- Node specs are now available for simpler management of cache creations.
|
||||
- **Mode Types**
|
||||
- Ingest, query, compaction, and processing engine can now all be set individually per node.
|
||||
|
||||
|
||||
|
||||
- **Mode types**
|
||||
- Ingest, query, compaction, and processing engine can now all be set individually per node.
|
||||
|
|
|
|||
Loading…
Reference in New Issue