gianm commented on a change in pull request #12321:
URL: https://github.com/apache/druid/pull/12321#discussion_r828478955
##########
File path: web-console/src/views/ingestion-view/ingestion-view.tsx
##########
@@ -244,6 +247,8 @@ ORDER BY "rank" DESC, "created_time" DESC`;
hiddenSupervisorColumns: new LocalStorageBackedVisibility(
LocalStorageKeys.SUPERVISOR_TABLE_COLUMN_SELECTION,
),
+
+ preferOverlord: true,
Review comment:
I'm just catching up here, but why does using the Overlord API cause
less stress on the metadata store than using SQL? Under the hood, I believe
that the SQL sys.tasks table would be making Overlord API calls anyway.
So I guess the calls are different. But: how are they different?
Ideally I'd like to take that knowledge and use it to make the sys.tasks
implementation more efficient.
Also, does using the Overlord API directly have any implications for
functionality? (Is it reduced in some way?)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
