-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](be) resolves some unused-raii and used-after-moved issues #29285
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
Signed-off-by: pengyu <pengyu@selectdb.com>
Signed-off-by: pengyu <pengyu@selectdb.com>
Signed-off-by: pengyu <pengyu@selectdb.com>
Signed-off-by: pengyu <pengyu@selectdb.com>
|
clang-tidy review says "All clean, LGTM! 👍" |
yiguolei
left a comment
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. |
| std::string status(s.ok() ? "OK" : "BAD"); | ||
| rapidjson::Value result; | ||
| result.SetObject(); | ||
| rapidjson::Value(key.c_str(), key.size(), results.GetAllocator()); |
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.
is here no problems before ?
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.
No, IIUC it just creates an useless JSON value and drops it immediately.
amorynan
left a comment
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
|
run buildall |
|
TeamCity be ut coverage result: |
|
TPC-H test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
Proposed changes
This PR partially resolves #28965 by applying some trivial patches. Either by removing unncessary variable usage or using correct variable which has the data ownership. Similiar fixes are grouped in the same commit.
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...