mistercrunch commented on PR #36368: URL: https://github.com/apache/superset/pull/36368#issuecomment-3873033421
> I did some testing to see if supporting direct Celery scheduling with the new task decorator would be possible, but it added a lot of dangerous complexity to the already complex internals of the feature, so ultimately I decided against it. Sounds reasonable. Main thing I'm slightly worried about is multiple execution paths for extended periods of time on the repo. Would love to have all tasks go through the same general codepaths/decorators/abstractions, even if some tasks don't provide the same guarantees (dedup on/off, database tracking on/off, ...). -- 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]
