flyrain commented on code in PR #3692: URL: https://github.com/apache/polaris/pull/3692#discussion_r2790592322
########## site/content/in-dev/unreleased/downstream-build.md: ########## @@ -37,6 +37,16 @@ according to the terms of the license included in Polaris distributions. * Provide your own `application.properties` file for your Quarkus build. * Define your own Quarkus Application Name and Version (do not use "Apache Polaris" as the application name). +## Handling Java Code Changes + +As noted in the [Evolution](../evolution) page, Polaris classes are subject to change even in their +`public` methods at any moment. + +The Polaris Community strives to evolve the project in a way that preserve existing features and +capabilities (unless noted otherwise), but technical compilation errors are to be expected in +downstream projects. In most cases, it should be possible to adjust the code with minimal efforts Review Comment: This is exactly the problem the community is trying to solve. The goal is to clarify and stabilize the SPI, rather than continuing to treat it as explicitly breakable. For example, incompatible changes to `PolarisAuthorizableOperation` can directly break OPA integrations, cc @sungwy. Instead of reiterating that these interfaces are breakable, we should take concrete steps to reduce or avoid this kind of breakage. -- 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]
