Feature #90988
open
TYPO3 Reset Scheduler
0%
Description
Add an Interface like "RestProviderInterface" witch an method "rest".
This interface tels TYPO3 to show an reset button at the Scheduler Task, by clicking it the "rest" method will be called.
This come in quied handy for e.G. indexing or calculation taks wich must be resume in cases like code changes or updates. (e.G. Solr oder indexer)
Updated by Georg Ringer about 4 years ago
- Status changed from New to Needs Feedback
Thanks for creating this issue. However I don't see the need for such thing. E.g. solr ships a reset command which works perfectly fine and which can be triggered as well.
- What would be the benefit by having such button
- How would also such reset button be triggered regularly without UI?
we try to get rid of having state in such task classes and move to more something like https://github.com/helhum/typo3-crontab which would allow to ship & deploy tasks.
Therefore I would opt for rejecting this issuee. What do you think?
Updated by Timo Poppinga about 4 years ago
I did have a quick look at https://github.com/helhum/typo3-crontab, the concept to make tasks config deployable is 100% right and a need! ;-)
Point is: There are mainly tow think I do handle with Tasks/Command:
1. Commands: An mostly fast singel running Console-Task. Mostly triggers by the webmaster on the server. It do some thing like adding an user, cache clear, export db and so on.
For this I do use the symfony commands.
2. Tasks: Doing regular and mutiple work. Like e.g: cache warm up, solar-indexing sending mails notifications, calculate statistics.
This Task mostly need longer running time and are splited into smaler batches
For this I do use the TYPO3 schedule tasks
How do I differentiate them. I like to point for example an "cache warm up" picture:
If I warm up one page it is most likely an command.
If I warm up all pages I do have an Task witch triggers for all pages the page warm up command.
So for me command und task are different, because for me a task works more like an batch job.
For commands an "reset button" make not really sense.
For tasks it is really handy e.g. Solr (you are right they do have an reset function, but would it not be nice if you do have it as an core feature like the process bar. BTW: how would the process bar work in an stateless concept)
I can as well imagine and rest button for cache warmup, prerandering, calculations a.s.o
The "rest button" should be integrated in the UI like the prosess bar.
May we should rename task in batch job