stoty commented on issue #687: Hbase compat buildtime
URL: https://github.com/apache/phoenix/pull/687#issuecomment-580414949
 
 
   Yes, that is correct.
   
   However, we'd better think of the compatibility modules not as supporting 
minor releases, but as supporting HBase version ranges, which may not even be 
continuous (e.g. the 2.0.1 module supports both 2.0 and 2.1 releases made in 
the same timeframe, but breaks on a change introduced in both branches).
    
   What @joshelser  is describing may well end being the way we handle breaking 
HBase API changes (i.e. we support the latest patch releases of each minor 
version), but that would not be a consequence of how the module system works, 
but rather decision made by us to limit the number of HBase compatibility 
modules we support/test/maintain, and as suggested, to nudge users to update to 
the latest HBase point release.
   
   We will also definitely need to flesh out the build instructions, and 
document how to download the HBase specific artifacts/assemblies, though I am 
not sure wether to put this in the repo, or add it to web site (or both). Maybe 
keeping it on the website, and adding a direct link to the build instructions 
in README.md would be the best.

----------------------------------------------------------------
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

Reply via email to