This message was deleted.
# general
s
This message was deleted.
s
Do you mean the Query view in the console does not show the new datasource? I've seen this, particularly if the ingestion was done through an API, but it is usually resolved clicking out of the query view and back in.
Also, after an ingestion publishes segments into Deep Storage, the coordinator will recognize the new segments and tables in its next cycle. The next coordinator cycle might be up to a minute away (by default), so it can take a minute for the coordinator to recognize and send instructions to the historicals to load the new segments.
s
yes, we tried force refresh the browser and reopened the browser. but we are still not seeing the newly created datassource
we observed the segments are 100 % for this datasource
s
That's odd. The query that the UI uses to do this refresh is:
Copy code
SELECT
datasource,
COUNT(*) FILTER (WHERE is_active = 1) AS num_segments,
COUNT(*) FILTER (WHERE is_published = 1 AND is_overshadowed = 0 AND replication_factor = 0) AS num_zero_replica_segments,
COUNT(*) FILTER (WHERE is_published = 1 AND is_overshadowed = 0 AND is_available = 0 AND replication_factor > 0) AS num_segments_to_load,
COUNT(*) FILTER (WHERE is_available = 1 AND is_active = 0) AS num_segments_to_drop,
SUM("size") FILTER (WHERE is_active = 1) AS total_data_size,
MIN("num_rows") FILTER (WHERE is_available = 1 AND is_realtime = 0) AS min_segment_rows,
AVG("num_rows") FILTER (WHERE is_available = 1 AND is_realtime = 0) AS avg_segment_rows,
MAX("num_rows") FILTER (WHERE is_available = 1 AND is_realtime = 0) AS max_segment_rows,
SUM("num_rows") FILTER (WHERE is_active = 1) AS total_rows,
CASE WHEN SUM("num_rows") FILTER (WHERE is_available = 1) <> 0 THEN (SUM("size") FILTER (WHERE is_available = 1) / SUM("num_rows") FILTER (WHERE is_available = 1)) ELSE 0 END AS avg_row_size,
SUM("size" * "num_replicas") FILTER (WHERE is_active = 1) AS replicated_size
FROM sys.segments
GROUP BY datasource
ORDER BY datasource
If you run this query directly, do you see the datasource?
s
yes. we can see the datasource is being returned with this query
but when i do, select * from that datasource. it shows datasource not found
we are using druid 27
s
just a thought... could it be a case sensitivity thing? Can you see the datasource listed on the left schema panel?