If you think this designation should be reconsidered for a given feature or use pattern, file a JIRA or start a discussion on one of the mailing lists.
In the context of Apache HBase, /not tested/ means that a feature or use pattern may or may notwork in a given way, and may or may not corrupt your data or cause operational issues. If you can provide proof that a feature designated as /not tested/ does work in a given way, please submit the tests and/or the metrics so that other users can gain certainty about such features or use patterns.
Instead, send your report to the mailing list [email protected], which allows anyone to send messages, but restricts who can read them.
Someone on that list will contact you to follow up on your report.
The phrases /supported/, /not supported/, /tested/, and /not tested/ occur several places throughout this guide.
In the interest of clarity, here is a brief explanation of what is generally meant by these phrases, in the context of HBase.
Commercial technical support for Apache HBase is provided by many Hadoop vendors.
This is not the sense in which the term /support/ is used in the context of the Apache HBase project.
The Apache HBase team assumes no responsibility for your HBase clusters, your configuration, or your data.
In the context of Apache HBase, /not supported/ means that a use case or use pattern is not expected to work and should be considered an antipattern.
Herein you will find either the definitive documentation on an HBase topic as of its standing when the referenced HBase version shipped, or it will point to the location in Javadoc or JIRA where the pertinent information can be found. The source for this guide can be found in the _src/main/asciidoc directory of the HBase source.