-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[Fix](tvf) Pass through user-defined properties #35515
Conversation
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
TPC-H: Total hot run time: 40045 ms
|
TPC-DS: Total hot run time: 173721 ms
|
ClickBench: Total hot run time: 31.14 s
|
run buildall |
TPC-H: Total hot run time: 41699 ms
|
TPC-DS: Total hot run time: 167914 ms
|
ClickBench: Total hot run time: 30.65 s
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
1a173ec
to
ecc779f
Compare
run buildall |
TPC-H: Total hot run time: 39706 ms
|
TPC-H: Total hot run time: 40133 ms
|
TPC-DS: Total hot run time: 172701 ms
|
ClickBench: Total hot run time: 29.85 s
|
## Proposed changes Issue Number: close #xxx Previously, irrelevant properties passed by users when using TVF were directly ignored by Doris. Now, we retain and pass these additional user-defined properties to the S3 SDK. <!--Describe your changes.--> ## Further comments If this is a relatively large or complex change, kick off the discussion at [dev@doris.apache.org](mailto:dev@doris.apache.org) by explaining why you chose the solution you did and what alternatives you considered, etc...
## Proposed changes Introduced from #35515 1. Fix invalid `to_int()` method logic 2. Remove unnecessary properties when creating s3 resource Before, after recreating s3 resource, there will be some extra properties being added to the resource properties, such as AWS_ACCESS_KEY, but this keys are only for s3 client on BE side, don' t needed when ping s3. But it will add some invalid properties such as `AWS_TOKEN=null`
## Proposed changes Issue Number: close #xxx Previously, irrelevant properties passed by users when using TVF were directly ignored by Doris. Now, we retain and pass these additional user-defined properties to the S3 SDK. <!--Describe your changes.--> ## Further comments If this is a relatively large or complex change, kick off the discussion at [dev@doris.apache.org](mailto:dev@doris.apache.org) by explaining why you chose the solution you did and what alternatives you considered, etc...
## Proposed changes Introduced from #35515 1. Fix invalid `to_int()` method logic 2. Remove unnecessary properties when creating s3 resource Before, after recreating s3 resource, there will be some extra properties being added to the resource properties, such as AWS_ACCESS_KEY, but this keys are only for s3 client on BE side, don' t needed when ping s3. But it will add some invalid properties such as `AWS_TOKEN=null`
## Proposed changes Issue Number: close #xxx Previously, irrelevant properties passed by users when using TVF were directly ignored by Doris. Now, we retain and pass these additional user-defined properties to the S3 SDK. <!--Describe your changes.--> ## Further comments If this is a relatively large or complex change, kick off the discussion at [dev@doris.apache.org](mailto:dev@doris.apache.org) by explaining why you chose the solution you did and what alternatives you considered, etc...
## Proposed changes Introduced from apache#35515 1. Fix invalid `to_int()` method logic 2. Remove unnecessary properties when creating s3 resource Before, after recreating s3 resource, there will be some extra properties being added to the resource properties, such as AWS_ACCESS_KEY, but this keys are only for s3 client on BE side, don' t needed when ping s3. But it will add some invalid properties such as `AWS_TOKEN=null`
Issue Number: close #xxx Previously, irrelevant properties passed by users when using TVF were directly ignored by Doris. Now, we retain and pass these additional user-defined properties to the S3 SDK. <!--Describe your changes.--> If this is a relatively large or complex change, kick off the discussion at [dev@doris.apache.org](mailto:dev@doris.apache.org) by explaining why you chose the solution you did and what alternatives you considered, etc...
Issue Number: close #xxx Previously, irrelevant properties passed by users when using TVF were directly ignored by Doris. Now, we retain and pass these additional user-defined properties to the S3 SDK. <!--Describe your changes.--> If this is a relatively large or complex change, kick off the discussion at [dev@doris.apache.org](mailto:dev@doris.apache.org) by explaining why you chose the solution you did and what alternatives you considered, etc...
bp: #35515 Previously, irrelevant properties passed by users when using TVF were directly ignored by Doris. Now, we retain and pass these additional user-defined properties to the S3 SDK.
bp: apache#35515 Previously, irrelevant properties passed by users when using TVF were directly ignored by Doris. Now, we retain and pass these additional user-defined properties to the S3 SDK.
Proposed changes
Issue Number: close #xxx
Previously, irrelevant properties passed by users when using TVF were directly ignored by Doris.
Now, we retain and pass these additional user-defined properties to the S3 SDK.
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...