[PHOENIX-6665] PreparedStatement#getMetaData() fails on parametrized "select next ? values for SEQ"

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.2.0
• Fix Version/s: 4.17.0, 5.2.0, 4.16.2, 5.1.3
• Component/s: core

Release Note

PreparedStatement#getMetaData() no longer fails on parametrized "select next ? values" sequence operations.
This also fixes a problem where parametrized sequence operations didn't work via Phoenix Query Server.

• Assignee: Istvan Toth
• Reporter: Istvan Toth
• Created: 11/Mar/22 07:47
• Updated: 09/Nov/22 01:42
• Resolved: 21/Mar/22 16:40

Description

 

PreparedStatement nextStmt = conn.prepareStatement("SELECT NEXT ? VALUES FOR SEQ_TABLE");
nextStmt.getMetaData();

Fails.

According to the PreparedStatement javadoc, this should work:

Because a PreparedStatement object is precompiled, it is possible to know about the ResultSet object that it will return without having to execute it. Consequently, it is possible to invoke the method getMetaData on a PreparedStatement object rather than waiting to execute it and then invoking the ResultSet.getMetaData method on the ResultSet object that is returned.

 

Issue Links

• causes: PHOENIX-6679 PHOENIX-6665 changed column name for CURRENT seqence values
• links to: GitHub Pull Request #1406