This is an automated email from the ASF dual-hosted git repository.

victoria 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 d65e015c940 docs: nit for link format (#16687)
d65e015c940 is described below

commit d65e015c94008bc1b6b08ae2a7a43948a03f71a0
Author: 317brian <[email protected]>
AuthorDate: Tue Jul 2 16:45:09 2024 -0700

    docs: nit for link format (#16687)
---
 docs/release-info/migr-mvd-array.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/release-info/migr-mvd-array.md 
b/docs/release-info/migr-mvd-array.md
index 6ec9e9ff241..e089a6a733e 100644
--- a/docs/release-info/migr-mvd-array.md
+++ b/docs/release-info/migr-mvd-array.md
@@ -242,5 +242,5 @@ For an example, see [Ingesting arrays: Native batch and 
streaming ingestion](../
 * For SQL-based batch ingestion, include the [query context 
parameter](../multi-stage-query/reference.md#context-parameters) 
`"arrayIngestMode": "array"` and reference the relevant array type (`VARCHAR 
ARRAY`, `BIGINT ARRAY`, or `DOUBLE ARRAY`) in the [EXTEND 
clause](../multi-stage-query/reference.md#extern-function) that lists the 
column names and data types.
 For examples, see [Ingesting arrays: SQL-based 
ingestion](../querying/arrays.md#sql-based-ingestion).
 
-   As a best practice, always use the ARRAY data type in your input schema. If 
you want to ingest MVDs, explicitly wrap the string array in 
[ARRAY_TO_MV](../querying/sql-functions.md#array_to_mv). For an example, see 
[Multi-value dimensions: SQL-based 
ingestion](/querying/multi-value-dimensions.md#sql-based-ingestion).
+   As a best practice, always use the ARRAY data type in your input schema. If 
you want to ingest MVDs, explicitly wrap the string array in 
[ARRAY_TO_MV](../querying/sql-functions.md#array_to_mv). For an example, see 
[Multi-value dimensions: SQL-based 
ingestion](../querying/multi-value-dimensions.md#sql-based-ingestion).
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to