dimas-b commented on PR #2196: URL: https://github.com/apache/polaris/pull/2196#issuecomment-3141609951
I think it's a good idea for the `bootstrap` command to also setup the schema by default (nicer user experience as @snazy commented). Still, I believe the `bootstrap` command show have the option to _not_ try to create the schema (it may or may not be idempotent), in which case the admin user can explicitly run the `setup` command. Subsequently, there is already an existing [mechanism](https://github.com/apache/polaris/blob/ca85339deee9645f0682194141ae8445ab3af768/runtime/service/src/main/java/org/apache/polaris/service/quarkus/config/QuarkusProducers.java#L238) for Polaris Servers to perform "bootstrap" automatically on startup. With all three options combined, I think, the "getting started" experience can remain simple, while more advanced scenarios are still possible for users that need them. That said, I do _not_ think that JDBC Persistence code should run any DDL on the main call path (i.e. outside of "bootstrap" or "setup" use cases). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@polaris.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
