Yao-MR opened a new issue #5544:
URL: https://github.com/apache/dolphinscheduler/issues/5544
**Describe the feature**
As we all know, the task registered in the dolphinscheduler is trigger by
the dag of the workflow,
in other words, the task is triggered by the flow which is defined by the
user, and we also can call it as the task Lineage
however, the dolphinscheduler is defined as a big data task scheduler, so
the data is a very impotant,
and in other world, we regard the task as the source, and the the reasonable
Scenario is that the data task is the
'task' triggered in the schedule
**Is your feature request related to a problem? Please describe.**
so maybe, we should support the data lineage between the task and in the
task,
and give the option to support the data lineage schedule
**Describe the solution you'd like**
i think the first step is to define and extract the data lineage of user's
task
**Describe alternatives you've considered**
in my opinion the task can be divided in to two class:
one is the no sql task, we can easily extract the source lineage
the other is the sql, maybe we need to extract the source data
lineage from the sql
--
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.
For queries about this service, please contact Infrastructure at:
[email protected]
