6 list the configuration options available for updating the os aspxgridview rowupdating example
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.
The Apache HBase team assumes no responsibility for your HBase clusters, your configuration, or your data.
First off, distributed systems are hard; making a distributed system hum requires a disparate skillset that spans systems (hardware and software) and networking.
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.
Your cluster’s operation can hiccup because of any of a myriad set of reasons from bugs in HBase itself through misconfigurations — misconfiguration of HBase but also operating system misconfigurations — through to hardware problems whether it be a bug in your network card drivers or an underprovisioned RAM bus (to mention two recent examples of hardware issues that manifested as "HBase is slow").
You will also need to do a recalibration if up to this your computing has been bound to a single box.