[ACCUMULO-461] Provide convenient mechanism for checking constraints client side

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: client
• Assignee: Unassigned
• Reporter: John Vines
• Created: 13/Mar/12 10:43
• Updated: 20/Feb/14 23:29

Description

Currently constraints are run on the server side. If the user is running a map reduce which is writing, they may want to make attempts to validate data before writing to make error handling easier. We should provide a generic client mechanism to load a table's constraints and check them before sending them to the batchwriter.

Issue Links

• relates to: ACCUMULO-360 Bulk importing Keys with invalid ColumnVisibility doesn't fail until scan

Sub-Tasks

• Add constraint configuration methods to table operations: Resolved