Ignite 23722 jdbc client info#1
Open
timoninmaxim wants to merge 46 commits intoIGNITE-23392__application_context_srvfrom
Open
Ignite 23722 jdbc client info#1timoninmaxim wants to merge 46 commits intoIGNITE-23392__application_context_srvfrom
timoninmaxim wants to merge 46 commits intoIGNITE-23392__application_context_srvfrom
Conversation
timoninmaxim
force-pushed
the
IGNITE-23722__jdbc_client_info
branch
from
623f725 to
159efe5
Compare
…custom format - Fixes apache#11674. Signed-off-by: Aleksey Plekhanov <plehanov.alex@gmail.com>
…or JOINs and other SQL nodes - Fixes apache#11663. Signed-off-by: Aleksey Plekhanov <plehanov.alex@gmail.com>
…he#11691) `sonar-pr-from-fork-build.yml` and `sonar-pr-from-fork-scan.yml` analyze PRs. `sonar-pr-from-fork-scan.yml` needs privileges to access the `SONARCLOUD_TOKEN` and to update the status of the PR check. To avoid a malicious PR from accessing those privileges, Ignite requires approval for GitHub Actions, and reviews the PR to catch any malicious code before approving the workflow. These changes makes sure the privileged workflow is ran against the commit that was approved, and does not pull in any changes that may have been added to the PR after approval.
…ystem functions/operators - Fixes apache#11684. Signed-off-by: Aleksey Plekhanov <plehanov.alex@gmail.com>
…#11707. Signed-off-by: Aleksey Plekhanov <plehanov.alex@gmail.com>
…can - Fixes apache#11651. Signed-off-by: Aleksey Plekhanov <plehanov.alex@gmail.com>
…ractSelfTest and other tests (apache#11712)
…IDING and related code (apache#11700)
timoninmaxim
force-pushed
the
IGNITE-23722__jdbc_client_info
branch
from
ad8e43c to
12ddf01
Compare
timoninmaxim
force-pushed
the
IGNITE-23722__jdbc_client_info
branch
from
2053616 to
cbe0870
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
11 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
The description explains WHAT and WHY was made instead of HOW.
The following pattern must be used:
IGNITE-XXXX Change summarywhereXXXX- number of JIRA issue.(see the Maintainers list)
the
green visaattached 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.