guluo2016 commented on code in PR #7878: URL: https://github.com/apache/hbase/pull/7878#discussion_r2898932769
########## hbase-website/app/pages/_docs/docs/_mdx/(multi-page)/upgrading/version-number.mdx: ########## @@ -145,6 +145,10 @@ All classes annotated with InterfaceAudience.Private or all classes that do not When we say two HBase versions are compatible, we mean that the versions are wire and binary compatible. Compatible HBase versions means that clients can talk to compatible but differently versioned servers. It means too that you can just swap out the jars of one version and replace them with the jars of another, compatible version and all will just work. Unless otherwise specified, HBase point versions are (mostly) binary compatible. You can safely do rolling upgrades between binary compatible versions; i.e. across maintenance releases: e.g. from 1.4.4 to 1.4.6. See "Does compatibility between versions also mean binary compatibility?" discussion on the HBase dev mailing list. -[^1]: Running an offline upgrade tool without downgrade might be needed. We will typically only support migrating data from major version X to major version X+1. +[^1]: See 'Source Compatibility' https://wiki.openjdk.org/spaces/csr/pages/32342052/Kinds+of+Compatibility [^2]: See http://docs.oracle.com/javase/specs/jls/se7/html/jls-13.html. Review Comment: As I mentioned here https://issues.apache.org/jira/browse/HBASE-29957?filter=12352185#:~:text=Additionally%2C%20I%20noticed,8%20or%2017)%EF%BC%9F, The link we are using is for Java SE 7. Isn't this version a bit outdated? I suggest updating it to SE 8. What do you think? @PDavid @yuriipalam -- 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]
