sajjad-moradi commented on issue #10237:
URL: https://github.com/apache/pinot/issues/10237#issuecomment-1428913999
@Jackie-Jiang In our clusters, whenever a consuming segment was deleted, it
was a result of a user error. So we prefer to not delete consuming segments.
That being said, I see your point of using delete endpoint for deleting some
consuming segments being in weird state.
What do you think of adding an extra flag indicating force-deleting a
consuming segment?
```
DELETE /segments/{tableName}/{segmentName}
returns 400 if the segment is in consuming state, with error saying
“{segmentName} is in consuming state. If you need to delete the consuming
segment, provide ‘forceDeleteConsumingSegment’ parameter”.
DELETE /segments/{tableName}/{segmentName}?forceDeleteConsumingSegment=true
```
--
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: commits-unsubscr...@pinot.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org
