[PHOENIX-5630] MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE_BYTES_EXCEEDED SQLExceptions should print existing size

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.15.0
• Fix Version/s: 5.1.0, 4.15.1, 4.16.0
• Labels: beginner newbie
• Assignee: Neha Gupta
• Reporter: Chinmay Kulkarni
• Created: 17/Dec/19 05:51
• Updated: 15/Jan/21 12:02
• Resolved: 09/Jan/20 01:35

Description

These exceptions do not print the existing size of the MutationState. We should add the existing size to the exception message for help in debugging. For ex:

Caused by: java.sql.SQLException: ERROR 730 (LIM02): MutationState size is bigger than maximum allowed number of bytes
    at org.apache.phoenix.exception.SQLExceptionCode$Factory$1.newException(SQLExceptionCode.java:494)
    at org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:150)
    at org.apache.phoenix.execute.MutationState.throwIfTooBig(MutationState.java:371)
    at org.apache.phoenix.execute.MutationState.join(MutationState.java:471)
    at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:409)
    at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:391)
    at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
    at org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:390)
    at org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:378)
    at org.apache.phoenix.jdbc.PhoenixPreparedStatement.execute(PhoenixPreparedStatement.java:173)
    at org.apache.phoenix.jdbc.PhoenixPreparedStatement.execute(PhoenixPreparedStatement.java:183)
    at org.apache.phoenix.jdbc.DelegatePreparedStatement.execute(DelegatePreparedStatement.java:284)

Issue Links

• links to: GitHub Pull Request #670