kfaraz commented on issue #16945: URL: https://github.com/apache/druid/issues/16945#issuecomment-2367182769
I see, thanks for the clarification, @asdf2014 . So you want to add a validation on the input time interval while persisting the task payload itself. I am not entirely sure if we can always safeguard against users making such mistakes. The surface area is too large. It is always possible to validate things which are semantically incorrect for Druid. But something which is inadvisable only for a certain use case should ideally be validated on the application side itself. That said, it does make sense for an admin to allow users to perform only valid actions. To that effect, the admin could specify a property called say `validYearRange` or `validIntervalRange` in `common.runtime.properties`, which would then be used to validate all task payloads. But then again, I am averse to adding a new config for every new validation that we have to perform. cc: @abhishekagarwal87 , what are your thoughts on such validations? -- 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]
