Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PHOENIX-7527 NPE thrown when extract table schema using sqlline. #2079

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

chaijunjie0101
Copy link
Contributor

No description provided.

@chaijunjie0101 chaijunjie0101 changed the title PHOENIX-7527 NPE thrown when exatact table schema use sqlline. PHOENIX-7527 NPE thrown when extract table schema use sqlline. Feb 17, 2025
@chaijunjie0101 chaijunjie0101 changed the title PHOENIX-7527 NPE thrown when extract table schema use sqlline. PHOENIX-7527 NPE thrown when extract table schema using sqlline. Feb 17, 2025
@chaijunjie0101 chaijunjie0101 force-pushed the PHOENIX-7527 branch 2 times, most recently from 2e2543e to 1c067d6 Compare February 17, 2025 14:57
@@ -2614,6 +2614,15 @@ public QueryPlan getQueryPlan() {
@Override
public ResultSet getResultSet() throws SQLException {
ResultSet rs = getLastResultSet();
if (!isClosed && rs == null && lastQueryPlan != null) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feels like this a band-aid to cover for an error in the resultset logic.

Can we fix the logic instad so that this is hacky solution is not needed ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feels like this a band-aid to cover for an error in the resultset logic.

Can we fix the logic instad so that this is hacky solution is not needed ?

yeah...But if we set the resultSet on this statement...may break the old logic...not sure why set ResultSet in the QueryPlan's context? it is differnt with JDBC statement logic...we need be careful to change some old logic even it is wrong...need keep maintain compatibility.
I will check again if we could fix the wrong resultset logic, or if you want to fix it, you also could do it~
Thanks for reviewing~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants