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 not work 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.
This chapter expands upon the Getting Started chapter to further explain configuration of Apache HBase.
In reality, you need a fully-distributed configuration to fully test HBase and to use it in real-world scenarios.
In a distributed configuration, the cluster contains multiple nodes, each of which runs one or more HBase daemon.
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.