-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starburst materialization documentation #1363
Conversation
site/docs/reference/Connectors/materialization-connectors/starburst.md
Outdated
Show resolved
Hide resolved
site/docs/reference/Connectors/materialization-connectors/starburst.md
Outdated
Show resolved
Hide resolved
site/docs/reference/Connectors/materialization-connectors/starburst.md
Outdated
Show resolved
Hide resolved
site/docs/reference/Connectors/materialization-connectors/starburst.md
Outdated
Show resolved
Hide resolved
site/docs/reference/Connectors/materialization-connectors/starburst.md
Outdated
Show resolved
Hide resolved
|
||
To get HOST and PORT go to your Cluster -> Connection info | ||
|
||
There is also need to grant access to temporary storage (Roles and privileges -> Select specific role -> Privileges -> Add privilege -> Location). "Create schema and table in location" should be selected. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add also the fact that the location privileges should correspond to the location of the schema configured for this connector.
site/docs/reference/Connectors/materialization-connectors/starburst.md
Outdated
Show resolved
Hide resolved
site/docs/reference/Connectors/materialization-connectors/starburst.md
Outdated
Show resolved
Hide resolved
Galaxy has a list of reserved words that must be quoted in order to be used as an identifier. Flow automatically quotes fields that are in the reserved words list. You can find this list in Trino's documentation [here](https://trino.io/docs/current/language/reserved.html) and in the table below. | ||
|
||
:::caution | ||
In Galaxy, objects created with quoted identifiers must always be referenced exactly as created, including the quotes. Otherwise, SQL statements and queries can result in errors. See the [Trino docs](https://trino.io/docs/current/language/reserved.html#language-identifiers). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
quoted identifiers -> is rather abstract for a newbie in the Trino ecosystem.
Maybe provide an example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Example is in Trino docs.
ad52abc
to
ff0874b
Compare
site/docs/reference/Connectors/materialization-connectors/starburst.md
Outdated
Show resolved
Hide resolved
site/docs/reference/Connectors/materialization-connectors/starburst.md
Outdated
Show resolved
Hide resolved
* A Starburst Galaxy account (To create one: [Staburst Galaxy start](https://www.starburst.io/platform/starburst-galaxy/start/) that includes: | ||
* A running cluster containing an [Amazon S3](https://docs.starburst.io/starburst-galaxy/working-with-data/create-catalogs/object-storage/s3.html) catalog | ||
* A [schema](https://docs.starburst.io/starburst-galaxy/data-engineering/working-with-data-lakes/table-formats/index.html#create-schema) which is a logical grouping of tables | ||
* Storage on S3 for temporary data with `awsAccessKeyId` and `awsSecretAccessKey` which should correspond to used catalog |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason why we didn't use cross account IAM role?
|
||
To get host go to your Cluster -> Connection info -> Other clients ([Connect clients](https://docs.starburst.io/starburst-galaxy/working-with-data/query-data/connect-clients.html)) | ||
|
||
There is also need to grant access to temporary storage (Roles and privileges -> Select specific role -> Privileges -> Add privilege -> Location). "Create schema and table in location" should be selected. [Doc](https://docs.starburst.io/starburst-galaxy/cluster-administration/manage-cluster-access/manage-users-roles-and-tags/account-and-cluster-privileges-and-entities.html#location-privileges-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What location would one specific?
* A user with a role assigned that grants access to create, modify, drop tables in specified Amazon S3 catalog | ||
* At least one Flow collection | ||
|
||
### Setup |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should specify this is setup for Starburst Galaxy
|
||
There is also need to grant access to temporary storage (Roles and privileges -> Select specific role -> Privileges -> Add privilege -> Location). "Create schema and table in location" should be selected. [Doc](https://docs.starburst.io/starburst-galaxy/cluster-administration/manage-cluster-access/manage-users-roles-and-tags/account-and-cluster-privileges-and-entities.html#location-privileges-) | ||
|
||
## Configuration |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should call this setup for Estuary. Or call the other one configuration. Trying to be consistent in terminology for setups steps for both products.
To use this connector, begin with data in one or more Flow collections. | ||
Use the below properties to configure a Starburst materialization, which will direct one or more of your Flow collections to new Starburst tables. | ||
|
||
### Properties |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we put an example?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nm. I see it below
| **`/awsAccessKeyId`** | AWS Access Key ID | | string | Required | | ||
| **`/awsSecretAccessKey`** | AWS Secret Access Key | | string | Required | | ||
| **`/region`** | AWS Region | Region of AWS storage | string | Required | | ||
| **`/bucket`** | Bucket name | | string | Required | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these for the temporary storage?
LGTM |
Description:
Add starburst documentation
This change is