-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](jdbc) Set the correct jdbctable id for query tvf #57745
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
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
TPC-DS: Total hot run time: 189570 ms |
ClickBench: Total hot run time: 27.79 s |
|
run buildall |
FE Regression Coverage ReportIncrement line coverage |
TPC-DS: Total hot run time: 189720 ms |
ClickBench: Total hot run time: 27.27 s |
FE UT Coverage ReportIncrement line coverage |
FE Regression Coverage ReportIncrement line coverage |
|
PR approved by anyone and no changes requested. |
|
PR approved by at least one committer and no changes requested. |
When using `query()` to query two different catalogs in a single SQL statement, due to the hard-coded tableid, the BE will assume that all scanNodes are querying the same table. This will cause scanner reuse, resulting in different catalogs using the same JDBC connection.
When using `query()` to query two different catalogs in a single SQL statement, due to the hard-coded tableid, the BE will assume that all scanNodes are querying the same table. This will cause scanner reuse, resulting in different catalogs using the same JDBC connection.
When using `query()` to query two different catalogs in a single SQL statement, due to the hard-coded tableid, the BE will assume that all scanNodes are querying the same table. This will cause scanner reuse, resulting in different catalogs using the same JDBC connection.
…or query tvf apache#57745 (apache#5618) cherry-picks from apache#57745 Related to apache#5568 Co-authored-by: zy-kkk <zhongyk10@gmail.com>
When using `query()` to query two different catalogs in a single SQL statement, due to the hard-coded tableid, the BE will assume that all scanNodes are querying the same table. This will cause scanner reuse, resulting in different catalogs using the same JDBC connection.
When using
query()to query two different catalogs in a single SQL statement, due to the hard-coded tableid, the BE will assume that all scanNodes are querying the same table. This will cause scanner reuse, resulting in different catalogs using the same JDBC connection.