Polaris Setup Export/Apply for Tables

[fzhao06]

Hello

Are there any plans to add support for tables/views and privileges scoped to them to the polaris setup export/apply tool? We would like a way to bootstrap a realm with those included. I've seen other tools like the synchronizer, but I'd like a way to modify the file paths and having an export artifact we could save.

Thanks!

[flyrain]

I think it's a good idea, and should be doable. cc @MonkeyCanCode

[MonkeyCanCode]

Yes, I had been thinking about this for some time. However, my main concern is the syntax that we need to support for those. Let me draft something and start a Dev ML on this later this week.

The main concerns I had was following:

1. We can do table creation without SQL, but we need to agree on the syntax
2. We can do view but this is dialect specific. We will need some validation here against dialect.
3. How useful is export as it will contains FS path with we cannot re-use directly across environments.

[flyrain]

For 1, 2, can we use the REST API for registering a table/view?

How useful is export as it will contains FS path with we cannot re-use directly across environments.

Path replacement is the next step after export, I assume. Basically the process would be export -> path change -> apply. @fzhao06 can confirm.

[MonkeyCanCode]

For 1, 2, can we use the REST API for registering a table/view?

How useful is export as it will contains FS path with we cannot re-use directly across environments.

Path replacement is the next step after export, I assume. Basically the process would be export -> path change -> apply. @fzhao06 can correct me if my understand is wrong.

For 1 and 2, yea which we are currently doing for view already (in summarize). Basically, instead of using SQL, we would be using a REST with a big length payload for creating table. It is do-able but let me check if there is more nature way of doing this.

[MonkeyCanCode]

Another things is we have tables and views commands which we should plan to add those support as well along with setup command.

[fzhao06]

How useful is export as it will contains FS path with we cannot re-use directly across environments.

Path replacement is the next step after export, I assume. Basically the process would be export -> path change -> apply. @fzhao06 can confirm.

Thanks for the quick response! That's right, our plan is to do some post processing on the export yaml ourselves. If replacement was built into the tool, that would be nice. Maybe not export itself, but on apply or a separate processing command.