You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "llphxd (via GitHub)" <gi...@apache.org> on 2026/07/08 13:26:52 UTC
[I] [Feature][API][UI] Add a read-only task search to locate which workflow a task belongs to [dolphinscheduler]
llphxd opened a new issue, #18402:
URL: https://github.com/apache/dolphinscheduler/issues/18402
### 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
In [DSIP-59](https://github.com/apache/dolphinscheduler/issues/16394) the standalone Task Definition page was removed from the project menu, along with its backend list/search endpoints. This was a reasonable architectural decision.
However, that removal also deleted the only entry point to answer a very common operational question:
▎ "Given a task name, which workflow(s) does it belong to?"
I'm not asking to bring back the old management page (create / edit / run standalone tasks). I'm asking for a read-only search that maps a task name to its parent workflow(s).
Use case
In big-data environments, task names usually follow strict naming conventions (e.g. one task per table, task name ≈ table name). Operators frequently need to start from a task/table name and jump to the workflow that owns it — for troubleshooting, impact analysis, or verifying a migration. After DSIP-59 there is no UI or REST entry for this, even though the relationship is still fully present in the metadata DB:
'''
SELECT p.name AS project, wd.name AS workflow, wd.code AS workflow_code,
td.name AS task, td.task_type
FROM t_ds_task_definition td
JOIN t_ds_workflow_task_relation wtr ON td.code = wtr.post_task_code
JOIN t_ds_workflow_definition wd ON wtr.workflow_definition_code = wd.code
AND wtr.project_code = wd.project_code
JOIN t_ds_project p ON wd.project_code = p.code
WHERE td.name LIKE CONCAT('%', ?, '%');
'''
The data is there; only the entry point is missing.
Why the existing Task Instance page is not enough
The Task Instance page can partially help, but it can only surface tasks that have executed. It cannot locate:
- tasks that have never run (newly created, or never scheduled);
- tasks whose instances have already been purged by retention / periodic cleanup;
- the current definition of a recently modified task — instances reflect the historical version captured at run time, not the latest task definition.
So Task Instance search misses exactly the cases where "find the owning workflow by name" is most needed.
Proposal (read-only, aligned with DSIP-59)
- Add a lightweight, read-only task search page under the project's Task submenu (next to Task Instance).
- Input: task name (fuzzy match), scoped to the current project.
- Output: a paginated list of task name | task type | owning workflow (clickable link)n jump straight into the workflow.
- Backend: a single read-only paginated query endpoint (the relation already exists via t_ds_workflow_task_relation); no write paths, no standalone-task creation — so it does not reintroduce the orphan-task problem DSIP-59 solved.
### Use case
_No response_
### Related issues
[DSIP-59](https://github.com/apache/dolphinscheduler/issues/16394)
### 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] [Feature][API][UI] Add a read-only task search to locate which workflow a task belongs to [dolphinscheduler]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #18402:
URL: https://github.com/apache/dolphinscheduler/issues/18402#issuecomment-5447932103
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] [Feature][API][UI] Add a read-only task search to locate which workflow a task belongs to [dolphinscheduler]
Posted by "zhang-arvin (via GitHub)" <gi...@apache.org>.
zhang-arvin commented on issue #18402:
URL: https://github.com/apache/dolphinscheduler/issues/18402#issuecomment-5480048167
I would like to work on this issue.
--
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] [Feature][API][UI] Add a read-only task search to locate which workflow a task belongs to [dolphinscheduler]
Posted by "SbloodyS (via GitHub)" <gi...@apache.org>.
SbloodyS commented on issue #18402:
URL: https://github.com/apache/dolphinscheduler/issues/18402#issuecomment-5098837127
+1, this is a good proposal. Howerer, Fuzzy query using `like` in database will lead to index invalidation, which is not a good way.
--
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] [Feature][API][UI] Add a read-only task search to locate which workflow a task belongs to [dolphinscheduler]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #18402: [Feature][API][UI] Add a read-only task search to locate which workflow a task belongs to
URL: https://github.com/apache/dolphinscheduler/issues/18402
--
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] [Feature][API][UI] Add a read-only task search to locate which workflow a task belongs to [dolphinscheduler]
Posted by "llphxd (via GitHub)" <gi...@apache.org>.
llphxd commented on issue #18402:
URL: https://github.com/apache/dolphinscheduler/issues/18402#issuecomment-5101486826
> +1, this is a good proposal. Howerer, Fuzzy query using `like` in database will lead to index invalidation, which is not a good way.
Thanks @SbloodyS , that's a fair concern.But as far as I can tell, this is pretty much how name search already works across DS today:
workflow instances, task instances, workflow definitions, and the task group queue all
use a plain `name LIKE '%...%'`. So reusing the same approach here felt like the most consistent option rather than introducing something new.
There's also `TaskDefinitionMapper#filterTaskDefinition`, which already does exactly this
query and has been unused since [DSIP-59](https://github.com/apache/dolphinscheduler/issues/16394) — seems like a natural fit to just reuse.
--
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] [Feature][API][UI] Add a read-only task search to locate which workflow a task belongs to [dolphinscheduler]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #18402:
URL: https://github.com/apache/dolphinscheduler/issues/18402#issuecomment-6430846192
This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.
--
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] [Feature][API][UI] Add a read-only task search to locate which workflow a task belongs to [dolphinscheduler]
Posted by "yykaue (via GitHub)" <gi...@apache.org>.
yykaue commented on issue #18402:
URL: https://github.com/apache/dolphinscheduler/issues/18402#issuecomment-5711160381
/assign
--
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] [Feature][API][UI] Add a read-only task search to locate which workflow a task belongs to [dolphinscheduler]
Posted by "yykaue (via GitHub)" <gi...@apache.org>.
yykaue commented on issue #18402:
URL: https://github.com/apache/dolphinscheduler/issues/18402#issuecomment-5727790726
Thanks @SbloodyS for the feedback on #18654. I jumped into the PR too early. I'd like to work out the approach here first before updating it.
The idea is to let users search for a task name within a project and open the workflow that owns it. This would use task definitions, so it would also find tasks that have never run or whose instances have been cleaned up. It would stay read-only and use the existing project read permissions.
There are three decisions I would like to discuss:
1. **Search behavior and performance**
I agree that `LIKE '%keyword%'` raises a performance concern. Existing uses of this pattern elsewhere do not establish that it is suitable for this query. Project scoping and pagination also do not guarantee an inexpensive query, especially when counting distinct results.
Is substring matching required for the first version, or would exact/prefix matching be acceptable? Once the matching semantics are agreed upon, I can provide MySQL and PostgreSQL execution plans and benchmarks on representative large-project data, including the count query, to evaluate whether index changes are needed.
2. **UI entry point**
The issue proposes a lightweight Task Search page next to Task Instance. Would maintainers prefer this entry point, or a task-name filter within the existing Workflow Definition page?
The functionality would remain read-only and preserve the workflow-centered model introduced by DSIP-59.
3. **Task version semantics**
I propose searching the task versions referenced by current workflow definitions. For example, if a current workflow references task version 1 while version 2 exists, the result would show the name from version 1 so that it matches the linked workflow.
--
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] [Feature][API][UI] Add a read-only task search to locate which workflow a task belongs to [dolphinscheduler]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #18402:
URL: https://github.com/apache/dolphinscheduler/issues/18402#issuecomment-6257275553
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