You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "ruanwenjun (via GitHub)" <gi...@apache.org> on 2025/01/01 03:05:51 UTC
[I] [Improvement] Subworkflow task use t_ds_task_instance_context store runtime context [dolphinscheduler]
ruanwenjun opened a new issue, #16938:
URL: https://github.com/apache/dolphinscheduler/issues/16938
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
All task should use t_ds_task_instance_context to store it's runtime context, once it's runtime context changed, it should tell master to update it's runtime context, and when task failover should copy runtime context to new task instance which is generated by failover and provide it's runtime context to do failover.
### Are you willing to submit a 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
Re: [I] [Improvement] Subworkflow task use t_ds_task_instance_context store runtime context [dolphinscheduler]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #16938:
URL: https://github.com/apache/dolphinscheduler/issues/16938#issuecomment-2722998684
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
--
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
Re: [I] [Improvement] Subworkflow task use t_ds_task_instance_context store runtime context [dolphinscheduler]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #16938:
URL: https://github.com/apache/dolphinscheduler/issues/16938#issuecomment-2649554182
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
--
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
Re: [I] [Improvement] Subworkflow task use t_ds_task_instance_context store runtime context [dolphinscheduler]
Posted by "ruanwenjun (via GitHub)" <gi...@apache.org>.
ruanwenjun commented on issue #16938:
URL: https://github.com/apache/dolphinscheduler/issues/16938#issuecomment-2579325105
The `TaskInstanceContext` is serialized as JSON string, this class contains
the context used or generated by task instance, is an interface, each task
can have its own type.
On Fri, Jan 3, 2025 at 5:13 PM lile ***@***.***> wrote:
> May I ask, will you also write the calculated date parameters into
> t_ds_task_instance_context?
> And would you do it in the form of fields or JSON?
>
> Lately, I've been thinking about how to optimize the logic where DEPENDENT
> task uses scheduleTime.
> The tricky parts right now are database efficiency issues and business
> continuity problems caused by new objects and logic, especially the latter,
> which will make upgrades quite challenging for 24/7 operation scenarios.
>
> So, could you please give a hint about the next design step?
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/dolphinscheduler/issues/16938#issuecomment-2568911077>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AFLAR2VHDLWJCJ3F6SN6CJ32IZID5AVCNFSM6AAAAABUOFWNX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRYHEYTCMBXG4>
> .
> You are receiving this because you were assigned.Message ID:
> ***@***.***>
>
--
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
Re: [I] [Improvement] Subworkflow task use t_ds_task_instance_context store runtime context [dolphinscheduler]
Posted by "reele (via GitHub)" <gi...@apache.org>.
reele commented on issue #16938:
URL: https://github.com/apache/dolphinscheduler/issues/16938#issuecomment-2568911077
May I ask, will you also write the calculated date parameters into `t_ds_task_instance_context`?
And would you do it in the form of fields or JSON?
Lately, I've been thinking about how to optimize the logic where `DEPENDENT` task uses `scheduleTime`.
The tricky parts right now are database efficiency issues and business continuity problems caused by new objects and logic, especially the latter, which will make upgrades quite challenging for 24/7 operation scenarios.
So, could you please give a hint about the next design step?
--
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