Shulou(Shulou.com)06/01 Report--

This article mainly introduces the relevant knowledge of "what is the data integrity in the operational database". The editor shows you the operation process through an actual case, and the operation method is simple, fast and practical. I hope this article "what is the data integrity in the operational database" can help you solve the problem.

Referential integrity supports referential integrity by implementing constraints and enforcing business rules on attributes in the table.

The constraint is configurable and you can use it in different tables. Keep in mind that you must choose a behavior based on the specific configuration assigned to the constraint. You can use constraints to enforce certain business rules. Data policies can be implemented by checking all "put" in the table. For example, you can set a policy where the value of a column family-column qualifier pair is always between 1 and 20. In this way, when the value is not in the range, "put" will be rejected and data integrity will be maintained. For more information about constraints, see constraints in the API documentation for Apache HBase developers. Non-relational integrity is similar to referential integrity, which is achieved by implementing constraints and is used to enforce business rules on any content type attribute of the user in the table (for example, ensure that the value is in the range of 1 to 10). The user chooses to enforce these rules in his Schema. The integrity of entities and domains you can use several tools that come with OpDB, including HBCK2 and IndexScrutinyTool. The HBCK2 tool can help you find and resolve any integrity issues. Also, you can use IndexScrutinyTool to identify invalid rows in the source table (usually a date table or an index table). IndexScrutinyTool writes invalid rows found to a file or output table. For more information about using the HBCK2 tool, see using the HBCK2 tool to repair an HBase cluster. The ACID transaction system complies with ACID features for single-line transactions and the flexibility of Schema-on-Read bound in the middle and later stages of the NoSQL world. OpDB guarantees the following attributes:

Atomicity: all changes in the transaction will be applied successfully, or no changes will be applied in the event of failure. Persistence: data written during a successful transaction is persisted to storage and is not lost in the event of a system failure. Consistency: the operation causes the table to transition from one valid state to another. For example, this means that the table will not be lost during the transaction. Visibility: any subsequent reads after the update is committed will see the update. Adjustable consistency supports strong consistency and timeline consistency. The client can indicate the level of consistency required for a given read operation. The default consistency level is STRONG, which means that read requests are sent only to the RegionServer serving the region. This is the same behavior as when not using a read-only copy. Another possibility is that TIMELINE sends the request to all RegionServer with copies, including the master copy. The client accepts the first response, including whether it is from the primary or secondary RegionServer. If it is from a secondary server, the client can choose whether to validate the read later or not to treat it as a determined read. This is the end of the content about "what is the data integrity in the operational database". Thank you for your reading. If you want to know more about the industry, you can follow the industry information channel. The editor will update different knowledge points for you every day.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.