Hi Druid experts! Wanted to get some feedback around a potential behavior change for the
/druid/indexer/v1/supervisor endpoint. The current behavior when an ingestion spec is submitted is to
stop then start the supervisor. Regardless of whether the underlying spec actually changed, the supervisor is always restarted. The behavior change we wanted to introduce is to first check if the spec has changed. If it hasn't, then do nothing. Otherwise just proceed with the existing behavior. Our use case is that we have some automation which hits the supervisor endpoint to update the schema in the ingestion spec. It's often unclear which specs have changed, so we would like to be able to just submit all of them to the supervisor endpoint and have it be restarted only if the spec has changed. Please let me know your thoughts, and happy to contribute if we think this is valid behavior