Skip to content
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

feat: update indexing to risingwave index instead of postgres #50

Open
MattiasMTS opened this issue Oct 8, 2024 · 0 comments
Open

feat: update indexing to risingwave index instead of postgres #50

MattiasMTS opened this issue Oct 8, 2024 · 0 comments

Comments

@MattiasMTS
Copy link
Collaborator

Currently, the indexing is done by the dbt-postgres adapter due to inheritance. Risingwave's indexing supports this but it has additional configuration that is not configurable if you build e.g. MWs with indexes.

Docs
https://docs.risingwave.com/docs/current/indexes/

Mainly, the two INCLUDE and DISTRIBUTED BY should be configurable in the config of a dbt model.

Also, right now you can also configure the type (i.e. index method) and unique as indicated by https://docs.getdbt.com/reference/resource-configs/postgres-configs#indexes. However, RisingWave doesn't support these changes and if you try to change them it doesn't make any impact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant