Skip to content

Added UI support for waitTillSegmentsLoad#15110

Merged
abhishekagarwal87 merged 5 commits intoapache:masterfrom
lorem--ipsum:waitTillSegmentsLoad-ui
Oct 11, 2023
Merged

Added UI support for waitTillSegmentsLoad#15110
abhishekagarwal87 merged 5 commits intoapache:masterfrom
lorem--ipsum:waitTillSegmentsLoad-ui

Conversation

@lorem--ipsum
Copy link
Copy Markdown
Contributor

This relies on the work done in #14322 and #15076. It allows the user to set waitTillSegmentsLoad in the query context (if they want, else it defaults to true) and shows the results in the UI :
image

@abhishekagarwal87 abhishekagarwal87 added this to the 28.0 milestone Oct 9, 2023
Copy link
Copy Markdown
Contributor

@adarshsanjeev adarshsanjeev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR! The changes look good, but I had a few suggestions

public getSegmentStatusDescription() {
const { segmentStatus } = this;

switch (segmentStatus) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this also display the segments breakdown after ingestion? This information should be available in the same place

"totalSegments": 1,
"usedSegments": 1,
"precachedSegments": 0,
"onDemandSegments": 0,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also show the time for the query part and ingestion part separately, so that any user can know the actual time taken for the query and won't mistake it as druid being slow. This information should also be available in segmentLoadStatus and its parent object.

@adarshsanjeev
Copy link
Copy Markdown
Contributor

I think we should also disable the current sql check, since it would be no longer needed
Screenshot 2023-10-10 at 11 00 48 AM

@lorem--ipsum
Copy link
Copy Markdown
Contributor Author

Thanks for the feedback, I've added mroe details in the "Details" dialog:
image
image

Copy link
Copy Markdown
Member

@clintropolis clintropolis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤘

Copy link
Copy Markdown
Contributor

@adarshsanjeev adarshsanjeev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the changes!

@abhishekagarwal87 abhishekagarwal87 merged commit dba0246 into apache:master Oct 11, 2023
@lorem--ipsum lorem--ipsum deleted the waitTillSegmentsLoad-ui branch October 13, 2023 22:37
LakshSingla pushed a commit to LakshSingla/druid that referenced this pull request Oct 14, 2023
This relies on the work done in apache#14322 and apache#15076. It allows the user to set waitTillSegmentsLoad in the query context (if they want, else it defaults to true) and shows the results in the UI :
LakshSingla added a commit that referenced this pull request Oct 16, 2023
This relies on the work done in #14322 and #15076. It allows the user to set waitTillSegmentsLoad in the query context (if they want, else it defaults to true) and shows the results in the UI :

Co-authored-by: Sébastien <sebastien@imply.io>
ektravel pushed a commit to ektravel/druid that referenced this pull request Oct 16, 2023
This relies on the work done in apache#14322 and apache#15076. It allows the user to set waitTillSegmentsLoad in the query context (if they want, else it defaults to true) and shows the results in the UI :
CaseyPan pushed a commit to CaseyPan/druid that referenced this pull request Nov 17, 2023
This relies on the work done in apache#14322 and apache#15076. It allows the user to set waitTillSegmentsLoad in the query context (if they want, else it defaults to true) and shows the results in the UI :
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants