-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[refactor](readability) Refactor MemTableFlushExecutor::create_flush_token to improve readability && Add default type guard #30554
[refactor](readability) Refactor MemTableFlushExecutor::create_flush_token to improve readability && Add default type guard #30554
Conversation
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
TPC-H: Total hot run time: 37389 ms
|
TPC-DS: Total hot run time: 172528 ms
|
ClickBench: Total hot run time: 31.37 s
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
|
TeamCity be ut coverage result: |
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
PR approved by at least one committer and no changes requested. |
readability && Add default type guard Signed-off-by: Jack Drogon <jack.xsuperman@gmail.com>
3e55df2
to
83b94de
Compare
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
TeamCity be ut coverage result: |
TPC-H: Total hot run time: 36776 ms
|
TPC-DS: Total hot run time: 172237 ms
|
ClickBench: Total hot run time: 30.98 s
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
|
readability && Add default type guard Signed-off-by: Jack Drogon <jack.xsuperman@gmail.com>
readability && Add default type guard Signed-off-by: Jack Drogon <jack.xsuperman@gmail.com>
readability && Add default type guard Signed-off-by: Jack Drogon <jack.xsuperman@gmail.com>
Proposed changes
Refactor MemTableFlushExecutor::create_flush_token to improve readability && Add default type guard
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...