You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added/modified:
I propose the addition of a new endpoint that accepts a list of rule IDs to be deleted in a single API call. This would allow users to perform bulk deletions without having to make multiple individual requests, thereby reducing network overhead and improving system performance.
Why is this needed:
As a user of ekuiper, I often find the need to efficiently delete multiple rules through a REST API. Currently, the system only supports the deletion of individual rules through the API. To enhance the usability and efficiency of ekuiper, it would be beneficial to introduce a new REST API endpoint that allows for the simultaneous deletion of multiple rules.
The text was updated successfully, but these errors were encountered:
You can loop through rules to send delete request. Actually, if we implement that, it is almost the same, just to loop and delete. So I doubt if this is needed.
Thank you for your answer.
I think it can be very helpful to reduce http trafic and avoid exceeding rate limit of eKuiper itself (if configured) or API Gateway
What would you like to be added/modified:
I propose the addition of a new endpoint that accepts a list of rule IDs to be deleted in a single API call. This would allow users to perform bulk deletions without having to make multiple individual requests, thereby reducing network overhead and improving system performance.
Why is this needed:
As a user of ekuiper, I often find the need to efficiently delete multiple rules through a REST API. Currently, the system only supports the deletion of individual rules through the API. To enhance the usability and efficiency of ekuiper, it would be beneficial to introduce a new REST API endpoint that allows for the simultaneous deletion of multiple rules.
The text was updated successfully, but these errors were encountered: