Mispartitioned tuple in single-partition insert statement.
Mar 23, 2016
If you're seeing an error that reads similar to the following during execution of a partitioned stored procedure (from class) and you're pretty sure you're not insane...
ERROR: Invalid input on line xxx. VOLTDB ERROR: CONSTRAINT VIOLATION
Mispartitioned tuple in single-partition insert statement.
Constraint Type PARTITIONING, Table CatalogId TBL
Check if the procedure partition key happens to be at the first position in the run() function's parameter list. If it is not, than make sure you've created the procedure with
optional POSITION clause set to 0-indexed position of the partition key in the parameter list. You may save yourself a few days of debugging and hair pulling.
ERROR: Invalid input on line xxx. VOLTDB ERROR: CONSTRAINT VIOLATION
Mispartitioned tuple in single-partition insert statement.
Constraint Type PARTITIONING, Table CatalogId TBL
Check if the procedure partition key happens to be at the first position in the run() function's parameter list. If it is not, than make sure you've created the procedure with
optional POSITION clause set to 0-indexed position of the partition key in the parameter list. You may save yourself a few days of debugging and hair pulling.