Skip to content

Clarify a few points #62

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions guides/datasets/ingest.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,10 @@ This page guides you through the process of ingesting data into a Tilebox datase
dataset available as file in the [GeoParquet](https://geoparquet.org/) format, you'll go through the process of
ingesting that data into Tilebox as a [Timeseries](/datasets/types/timeseries) dataset.

<Note>
If you have your data in a different format, check out the [Ingesting from common file formats](/guides/datasets/ingest-format) examples of how to ingest it.
</Note>

## Related documentation

<CardGroup cols={2}>
Expand Down
2 changes: 2 additions & 0 deletions workflows/concepts/tasks.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -169,6 +169,8 @@ task := &ParentTask{numSubtasks: 5}

In this example, a `ParentTask` submits `ChildTask` tasks as subtasks. The number of subtasks to be submitted is based on the `num_subtasks` attribute of the `ParentTask`. The `submit_subtask` method takes an instance of a task as its argument, meaning the task to be submitted must be instantiated with concrete parameters first.

Parent task do not have access to results of subtasks, instead, tasks can use [shared caching](/workflows/caches#storing-and-retrieving-data) to share data between tasks.

<Info>
By submitting a task as a subtask, its execution is scheduled as part of the same job as the parent task. Compared to just directly invoking the subtask's `execute` method, this allows the subtask's execution to occur on a different machine or in parallel with other subtasks. To learn more about how tasks are executed, see the section on [task runners](/workflows/concepts/task-runners).
</Info>
Expand Down