You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2022/12/28 08:05:04 UTC
[GitHub] [dolphinscheduler] wcmolin opened a new issue, #13292: [Bug] [Api] When serial complement is a process configured with timing scheduling, an error will occur when selecting a time that is not within the timing range
wcmolin opened a new issue, #13292:
URL: https://github.com/apache/dolphinscheduler/issues/13292
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When serial complement is a process configured with timing scheduling, an error will occur when selecting a time that is not within the timing range. The schedule time field of the complement process instance is empty
### What you expected to happen
Needs at least an error message like parallel complement
### How to reproduce
Refer to the figure below to configure a shell task for printing time, configure the timing schedule at 8:00 on the 1st of each month, choose `Complement Data`, select the time access as December 27 to December 28, and select `Serial execution` as the mode of execution
### Anything else
_No response_
### Version
2.0.x
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
--
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: commits-unsubscribe@dolphinscheduler.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [dolphinscheduler] wcmolin commented on issue #13292: [Bug] [Api] When serial complement is a process configured with timing scheduling, an error will occur when selecting a time that is not within the timing range
Posted by GitBox <gi...@apache.org>.
wcmolin commented on issue #13292:
URL: https://github.com/apache/dolphinscheduler/issues/13292#issuecomment-1366570563
> I had a similar problem. dolphinscheduler version:3.1.1
>
> Set the timing for the task. crontab: 0 0 10,22 * * ? * Operation Task To perform the supplementary number. The supplementary number time is 2022-12-20——2022-12-22
>
> The work flow of the complement is executed like this: 2022-12-20 10:00:00 2022-12-20 22:00:00 2022-12-21 10:00:00 2022-12-21 22:00:00 Will use crontab time to execute, not the complement time. And complementEndDate also has no trigger complement
>
> The expected effect should be: 2022-12-20 00:00:00 2022-12-21 00:00:00 2022-12-22 00:00:00
The problem you describe is not a bug, it is the function
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [dolphinscheduler] Sky-Gu commented on issue #13292: [Bug] [Api] When serial complement is a process configured with timing scheduling, an error will occur when selecting a time that is not within the timing range
Posted by GitBox <gi...@apache.org>.
Sky-Gu commented on issue #13292:
URL: https://github.com/apache/dolphinscheduler/issues/13292#issuecomment-1366498810
I had a similar problem.
Set the timing for the task. crontab: 0 0 10,22 * * ? *
Operation Task To perform the supplementary number. The supplementary number time is 2022-12-20——2022-12-22
The work flow of the complement is executed like this:
2022-12-20 10:00:00
2022-12-20 22:00:00
2022-12-21 10:00:00
2022-12-21 22:00:00
Will be executed at the scheduled time, not the complement time. And complementEndDate also has no trigger complement
The expected effect should be:
2022-12-20 00:00:00
2022-12-21 00:00:00
2022-12-22 00:00:00
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [dolphinscheduler] Sky-Gu commented on issue #13292: [Bug] [Api] When serial complement is a process configured with timing scheduling, an error will occur when selecting a time that is not within the timing range
Posted by GitBox <gi...@apache.org>.
Sky-Gu commented on issue #13292:
URL: https://github.com/apache/dolphinscheduler/issues/13292#issuecomment-1366624311
> > I had a similar problem. dolphinscheduler version:3.1.1
> > Set the timing for the task. crontab: 0 0 10,22 * * ? * Operation Task To perform the supplementary number. The supplementary number time is 2022-12-20——2022-12-22
> > The work flow of the complement is executed like this: 2022-12-20 10:00:00 2022-12-20 22:00:00 2022-12-21 10:00:00 2022-12-21 22:00:00 Will use crontab time to execute, not the complement time. And complementEndDate also has no trigger complement
> > The expected effect should be: 2022-12-20 00:00:00 2022-12-21 00:00:00 2022-12-22 00:00:00
>
> The problem you describe is not a bug, it is the function
If the time range of the complement is a single day, for example:2022-12-24——2022-12-24, this effect does not occur
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [dolphinscheduler] JinyLeeChina closed issue #13292: [Bug] [Api] When serial complement is a process configured with timing scheduling, an error will occur when selecting a time that is not within the timing range
Posted by GitBox <gi...@apache.org>.
JinyLeeChina closed issue #13292: [Bug] [Api] When serial complement is a process configured with timing scheduling, an error will occur when selecting a time that is not within the timing range
URL: https://github.com/apache/dolphinscheduler/issues/13292
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #13292: [Bug] [Api] When serial complement is a process configured with timing scheduling, an error will occur when selecting a time that is not within the timing range
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #13292:
URL: https://github.com/apache/dolphinscheduler/issues/13292#issuecomment-1366449502
Thank you for your feedback, we have received your issue, Please wait patiently for a reply.
* In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
* If you haven't received a reply for a long time, you can [join our slack](https://s.apache.org/dolphinscheduler-slack) and send your question to channel `#troubleshooting`
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [dolphinscheduler] wcmolin commented on issue #13292: [Bug] [Api] When serial complement is a process configured with timing scheduling, an error will occur when selecting a time that is not within the timing range
Posted by GitBox <gi...@apache.org>.
wcmolin commented on issue #13292:
URL: https://github.com/apache/dolphinscheduler/issues/13292#issuecomment-1371955954
> > > I had a similar problem. dolphinscheduler version:3.1.1
> > > Set the timing for the task. crontab: 0 0 10,22 * * ? * Operation Task To perform the supplementary number. The supplementary number time is 2022-12-20——2022-12-22
> > > The work flow of the complement is executed like this: 2022-12-20 10:00:00 2022-12-20 22:00:00 2022-12-21 10:00:00 2022-12-21 22:00:00 Will use crontab time to execute, not the complement time. And complementEndDate also has no trigger complement
> > > The expected effect should be: 2022-12-20 00:00:00 2022-12-21 00:00:00 2022-12-22 00:00:00
> >
> >
> > The problem you describe is not a bug, it is the function
>
> If the time range of the complement is a single day, for example:2022-12-24——2022-12-24, this effect does not occur
This is true in this case
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org