When you use the parameter "use_current_task" the dataset and the resulting task will be the same (same id). So to retrieve this dataset for using it into another task, use Task.get(...) to retrieve its id.
Then when you will need it into another task, simply retrieve it from within that task by using Dataset.get(dataset_id=...)
Is there any particular reason why not to create the dataset ? I mean, you need to use it in different tasks, so it could make sense to create it , for it to exist on its own, and then to use it at will in any task, by simply retrieving its id (using Dataset.get)
Makes sense ?
Say I have Task A that works with some dataset (which is not hard-coded, but perhaps e.g. self-defined by the task itself).
I'd now like to clone Task A and modify some stuff, but still use the same dataset (no need to recreate it, but since it's not hard-coded, I have to maintain a reference somewhere to the dataset ID).
Dataset SDK offers
use_current_task , I would have also expected there to be something like