-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[chore](enhance) Added order by create_time for show routine load #40783
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. Since 2024-03-18, the Document has been moved to doris-website. |
|
run buildall |
TPC-H: Total hot run time: 42554 ms |
TPC-DS: Total hot run time: 199010 ms |
ClickBench: Total hot run time: 31.1 s |
|
run P0 |
|
run P0 Regression |
|
run Doris Regression |
|
run P0 Regression (Doris Regression) |
|
run p0 |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
dataroaring
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.
reverse order is much better?
No, I think the average user would want to see information about the newly created task, for example I just created a task and if there are 100 historical tasks I need to scroll up many pages |
@dataroaring In addition, I will add the order by and limit syntax in the future to give users more choices |
according to your example in commit msg, the newest is put at the end. |
dataroaring
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
…0783) ## Proposed changes Issue Number: close #xxx <!--Describe your changes.--> <img width="674" alt="image" src="https://github.com/user-attachments/assets/b55cdb48-9108-4d55-9112-7e401cdbba07">
Proposed changes
Issue Number: close #xxx