Skip to content

IGNITE-27836 Fix documentation for QuerySqlTableFunction#12743

Open
zstan wants to merge 8 commits intoapache:masterfrom
zstan:ignite-27836
Open

IGNITE-27836 Fix documentation for QuerySqlTableFunction#12743
zstan wants to merge 8 commits intoapache:masterfrom
zstan:ignite-27836

Conversation

@zstan
Copy link
Contributor

@zstan zstan commented Feb 16, 2026

https://issues.apache.org/jira/browse/IGNITE-27836

Thank you for submitting the pull request to the Apache Ignite.

In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:

The Contribution Checklist

  • There is a single JIRA ticket related to the pull request.
  • The web-link to the pull request is attached to the JIRA ticket.
  • The JIRA ticket has the Patch Available state.
  • The pull request body describes changes that have been made.
    The description explains WHAT and WHY was made instead of HOW.
  • The pull request title is treated as the final commit message.
    The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
  • A reviewer has been mentioned through the JIRA comments
    (see the Maintainers list)
  • The pull request has been checked by the Teamcity Bot and
    the green visa attached to the JIRA ticket (see TC.Bot: Check PR)

Notes

If you need any help, please email dev@ignite.apache.org or ask anу advice on http://asf.slack.com #ignite channel.

assertQuery("select TYPEOF(?)").withParams(1L).returns("BIGINT").check();
assertQuery("select ? + ?").withParams(1, 2).returns(3).check();
assertThrows("select PLUS(?, ?)", SqlValidatorException.class, "No match found for function signature", 1, 2);
assertQuery("SELECT UNIX_SECONDS(TIMESTAMP '2021-01-01 00:00:00')").returns(1609459200L).check();
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think these changes are necessary to this ticket, it's at your discretion, of course.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

why not to align all these stuff here ?

Copy link
Contributor

Choose a reason for hiding this comment

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

In my opinion, these changes are redundant within the scope of the documentation ticket and are not related to this issue.
From my experience, when looking at the diff, it's better to see the ticket where the change occurred and made sense, rather than having to delve into an unrelated PR and look through everything there to figure it out.
In my opinion, it's better not to do this in this ticket.
Refactoring and other issues should be a separate ticket.
I'm not insisting it's up to you.

@sonarqubecloud
Copy link


assertTrue(rs.next());
assertEquals("row2", rs.getString(1));
}
Copy link
Contributor

Choose a reason for hiding this comment

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

assertFalse(rs.next());? Up to you.

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.

3 participants

Comments