You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Sean Busbey <bu...@apache.org> on 2018/06/20 20:03:15 UTC

[DISCUSS] are Constraints for downstream?

Our ref guide explains constraints

http://hbase.apache.org/book.html#_constraints

> HBase currently supports 'constraints' in traditional (SQL) database parlance. The advised usage
> for Constraints is in enforcing business rules for attributes in the table (e.g. make sure values are
> in the range 1-10). Constraints could also be used to enforce referential integrity, but this is
> strongly discouraged as it will dramatically decrease the write throughput of the tables where
> integrity checking is enabled. Extensive documentation on using Constraints can be found at
> Constraint since version 0.94.

But the link to the "extensive documentation" is to dev api docs and
the class in question is labeled  @InterfaceAudience.Private.

Which is it? If the feature is downstream facing, what's the IA.Public
bit? If there isn't one (even e.g. shell commands) then is there an
objection to me removing references from the ref guide?