stoty commented on issue #687: Hbase compat buildtime URL: https://github.com/apache/phoenix/pull/687#issuecomment-581491772 This version includes most of your suggestions @joshelser. You can set hbase.profile to 2.0 2.1 or 2.2 , and get a build with the latest supported HBase patch release (except for 2.0, which is EOM, and I kept it at the 2.0.1 API level to be directly comparable with the current master version) I kept the full version number in the compatibility modules names, as I am uncomfortable with changing their semantics when following the Hbase API changes, and I'd prefer to keep the door open for supporting multiple HBase patch versions for some time in case the API changes. I've left the maven qualifier equal to the hbase.profile, to ease CI/CD, and to keep the number of download assemblys / official maven artifact versions manageable. We could use compat.hbase.version or hbase.version as well here, none of the choices is perfect. Yo can still override the defaults that come from the -Dhbase.profile setting, i.e. mvn clean package -Dhbase.profile=2.0 -Dhbase.version=2.1.1 will build a version with the 2.0.1 compatibility module, but include the 2.1.1 runtime.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
