This is an automated email from the ASF dual-hosted git repository.
cwylie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/druid.git
The following commit(s) were added to refs/heads/master by this push:
new a860baf496 Updated docs on front coding (#13387)
a860baf496 is described below
commit a860baf4965cb46f35ba3b38e1651fa5838da1b3
Author: Jill Osborne <[email protected]>
AuthorDate: Sat Nov 19 08:01:04 2022 +0000
Updated docs on front coding (#13387)
---
docs/ingestion/ingestion-spec.md | 2 +-
docs/multi-stage-query/reference.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/ingestion/ingestion-spec.md b/docs/ingestion/ingestion-spec.md
index 86a6f57b33..c25e67fbf4 100644
--- a/docs/ingestion/ingestion-spec.md
+++ b/docs/ingestion/ingestion-spec.md
@@ -486,7 +486,7 @@ The `indexSpec` object can include the following properties:
Front coding is an experimental feature starting in version 25.0. Front coding
is an incremental encoding strategy that Druid can use to store STRING and
[COMPLEX<json>](../querying/nested-columns.md) columns. It allows Druid
to create smaller UTF-8 encoded segments with very little performance cost.
-To enable front coding with SQL-based ingestion, define an `indexSpec` in a
query context. See [SQL-based ingestion
reference](../multi-stage-query/reference.md#context-parameters) for more
information.
+You can enable front coding with all types of ingestion. For information on
defining an `indexSpec` in a query context, see [SQL-based ingestion
reference](../multi-stage-query/reference.md#context-parameters).
> Front coding is new to Druid 25.0 so the current recommendation is to enable
> it in a staging environment and fully test your use case before using in
> production. Segments created with front coding enabled are not compatible
> with Druid versions older than 25.0.
diff --git a/docs/multi-stage-query/reference.md
b/docs/multi-stage-query/reference.md
index 589d27db7a..3550566874 100644
--- a/docs/multi-stage-query/reference.md
+++ b/docs/multi-stage-query/reference.md
@@ -202,7 +202,7 @@ The following table lists the context parameters for the
MSQ task engine:
| `segmentSortOrder` | INSERT or REPLACE<br /><br />Normally, Druid sorts rows
in individual segments using `__time` first, followed by the [CLUSTERED
BY](#clustered-by) clause. When you set `segmentSortOrder`, Druid sorts rows in
segments using this column list first, followed by the CLUSTERED BY order.<br
/><br />You provide the column list as comma-separated values or as a JSON
array in string form. If your query includes `__time`, then this list must
begin with `__time`. For example, [...]
| `maxParseExceptions`| SELECT, INSERT, REPLACE<br /><br />Maximum number of
parse exceptions that are ignored while executing the query before it stops
with `TooManyWarningsFault`. To ignore all the parse exceptions, set the value
to -1.| 0 |
| `rowsPerSegment` | INSERT or REPLACE<br /><br />The number of rows per
segment to target. The actual number of rows per segment may be somewhat higher
or lower than this number. In most cases, use the default. For general
information about sizing rows per segment, see [Segment Size
Optimization](../operations/segment-optimization.md). | 3,000,000 |
-| `indexSpec` | INSERT or REPLACE<br /><br />An
[`indexSpec`](../ingestion/ingestion-spec.md#indexspec) to use when generating
segments. May be a JSON string or object. | See
[`indexSpec`](../ingestion/ingestion-spec.md#indexspec). |
+| `indexSpec` | INSERT or REPLACE<br /><br />An
[`indexSpec`](../ingestion/ingestion-spec.md#indexspec) to use when generating
segments. May be a JSON string or object. See [Front
coding](../ingestion/ingestion-spec.md#front-coding) for details on configuring
an `indexSpec` with front coding. | See
[`indexSpec`](../ingestion/ingestion-spec.md#indexspec). |
## Durable Storage
This section enumerates the advantages and performance implications of
enabling durable storage while executing MSQ tasks.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
