Skip to content

Commit 20e494b

Browse files
committed
Merge branch 'main' into prepare-version-3.16
2 parents be961ce + 0acc5b4 commit 20e494b

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

versioned_docs/version-3.15/scalardb-analytics/run-analytical-queries.mdx

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -146,6 +146,23 @@ You can use an arbitrary name for `<DATA_SOURCE_NAME>`.
146146
| `spark.sql.catalog.<CATALOG_NAME>.data_source.<DATA_SOURCE_NAME>.database` | No | The name of the database to connect to |
147147
| `spark.sql.catalog.<CATALOG_NAME>.data_source.<DATA_SOURCE_NAME>.secure` | No | Whether to use a secure connection to the SQL Server server. Set to `true` to use a secure connection. |
148148

149+
:::tip
150+
151+
You can use an arbitrary name for `<DATA_SOURCE_NAME>`.
152+
153+
:::
154+
155+
</TabItem>
156+
<TabItem value="dynamodb" label="DynamoDB">
157+
158+
| Configuration Key | Required | Description |
159+
|:---------------------------------------------------------------------------|:------------------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------|
160+
| `spark.sql.catalog.<CATALOG_NAME>.data_source.<DATA_SOURCE_NAME>.type` | Yes | Always set to `dynamodb` |
161+
| `spark.sql.catalog.<CATALOG_NAME>.data_source.<DATA_SOURCE_NAME>.region` | Either `region` or `endpoint` must be set | The AWS region of the DynamoDB instance |
162+
| `spark.sql.catalog.<CATALOG_NAME>.data_source.<DATA_SOURCE_NAME>.endpoint` | Either `region` or `endpoint` must be set | The AWS endpoint of the DynamoDB instance |
163+
| `spark.sql.catalog.<CATALOG_NAME>.data_source.<DATA_SOURCE_NAME>.schema` | Yes | A JSON object representing the schema of the catalog. For details on the format, see [Catalog-level mappings](./design.mdx#catalog-level-mappings). |
164+
165+
149166
:::tip
150167

151168
You can use an arbitrary name for `<DATA_SOURCE_NAME>`.

0 commit comments

Comments
 (0)