micomahesh1982 commented on issue #16030:
URL: https://github.com/apache/druid/issues/16030#issuecomment-1985073842

   I see one more thing here,  I see most of the time 1 segment for ALL
   granules then I can hardcode the interval: -146136543-09-08T08:23:32.
   096Z/146140482-04-24T15:36:27.903Z however one more scenario, If
   multiple segments (for 10 millions then 2 intervals) ALL granular then how
   do the interval values?
   
   On Thu, Mar 7, 2024 at 7:25 PM Mahesha Nayak ***@***.***> wrote:
   
   > Thank you for your email however I’m not sure how to dynamically delete
   > the ALL granular segments.
   >
   > Thanks,
   >
   > Regards,
   > Mahesha S
   > Cell:8015127140
   >
   >
   > On Thu, Mar 7, 2024 at 6:59 PM Abhishek Radhakrishnan <
   > ***@***.***> wrote:
   >
   >> Ah, I think I see what's happening - you have an ALL granularity segment
   >> that spans -146136543-09-08T08:23:32.096Z/146140482-04-24T15:36:27.903Z.
   >> In the kill task payload noted above, you have "interval":
   >> "1000-01-01T00:00:00.000Z/2999-12-31T00:00:00.000Z". The kill interval
   >> doesn't cover the ALL granularity eternity interval, so the kill task 
won't
   >> delete the unused eternity segment.
   >>
   >> In the kill task modal, when you click "Delete unused segments (issue
   >> kill task)", you can provide the interval:
   >> -146136543-09-08T08:23:32.096Z/146140482-04-24T15:36:27.903Z, and that
   >> should delete the eternity segment. Then you should see that the 
datasource
   >> is completely gone.
   >>
   >> Also, as a side note, the sys.segments table only shows used segments.
   >> Currently, the only way to view unused segments is directly in the 
metadata
   >> store: SELECT * FROM druid_segments WHERE datasource = 'temp1' AND used
   >> = false;.
   >>
   >> Let us know if that helps @micomahesh1982
   >> <https://github.com/micomahesh1982>. Thanks!
   >>
   >> —
   >> Reply to this email directly, view it on GitHub
   >> <https://github.com/apache/druid/issues/16030#issuecomment-1984959260>,
   >> or unsubscribe
   >> 
<https://github.com/notifications/unsubscribe-auth/AZEDLGCTSYE2G5U2OVNNYL3YXESQXAVCNFSM6AAAAABEDGFAK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUHE2TSMRWGA>
   >> .
   >> You are receiving this because you were mentioned.Message ID:
   >> ***@***.***>
   >>
   >
   
   -- 
   Regards,
   Mahesha S
   Cell:8015127140
   


-- 
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]

Reply via email to