dimas-b commented on PR #924: URL: https://github.com/apache/polaris/pull/924#issuecomment-2631916379
> Moving forward, I think we could separate build-time properties and run-time properties to different files [...] TBH, I'm not sure what the benefit would be. I can see two use case: 1) End users take Apache Polaris binaries and deploy. In this case the use configures what is possible in runtime, using environment-specific configuration (e.g. helm values). The user does not deal with config in Polaris sources. 2) A user take Apache Polaris artifacts (jars) and builds a custom server for deployment. In this case I'd argue that the user should have local build and runtime properties and should not reuse any default quarkus configuration from Polaris artifacts. This is what #811 enables. Reusing Quarkus properties from upstream is technically possible, but in my experience is very risky and inconvenient as actual behaviour is hard to predict. We can go into more details on this, but maybe it's preferable to have that discussion on the `dev` ML rather than GH comments. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
