Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented May 20, 2025

curl -u root:'xxxx' \
--location 'http://localhost:8030/api/load_test/Employees/_query_plan' \
--header 'Content-Type: application/json' \
--header 'warehouse:sub_wh' \
--data '{"sql": "select * from load_test.Employees;"}'

log sample

2025-04-25 13:56:48.589+08:00 INFO (nioEventLoopGroup-6-1|152) [TableQueryPlanAction.executeWithoutPassword():157] receive SQL statement [select * from load_test.Employees;] from external service [ user ['root'@'%']] for database [load_test] table [Employees] warehouse [sub_wh]
2025-04-25 13:57:54.420+08:00 INFO (nioEventLoopGroup-6-2|153) [TableQueryPlanAction.executeWithoutPassword():157] receive SQL statement [select * from load_test.Employees;] from external service [ user ['root'@'%']] for database [load_test] table [Employees] warehouse [default_warehouse]

Why I'm doing:

What I'm doing:

Fixes #issue

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 3.5
    • 3.4
    • 3.3
    • 3.2
    • 3.1

This is an automatic backport of pull request #58387 done by [Mergify](https://mergify.com).

@kevincai
Copy link
Contributor

@Mergifyio rebase

@kevincai kevincai self-assigned this Jun 12, 2025
…ttp action (#58387)

Signed-off-by: drake_wang <wxl250059@alibaba-inc.com>
(cherry picked from commit 506f15e)
@mergify
Copy link
Contributor Author

mergify bot commented Jun 12, 2025

rebase

✅ Branch has been successfully rebased

@kevincai kevincai force-pushed the mergify/bp/branch-3.4/pr-58387 branch from 2828fdb to f480cdb Compare June 12, 2025 09:02
@sonarqubecloud
Copy link

@wanpengfei-git wanpengfei-git merged commit c499c09 into branch-3.4 Jun 12, 2025
31 of 32 checks passed
@wanpengfei-git wanpengfei-git deleted the mergify/bp/branch-3.4/pr-58387 branch June 12, 2025 10:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants