Skip to content
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.

Sign up for GitHub

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

[Docs] Remove broken link from Understand How Flyte Handles Data page (for new monodocs site) (second attempt) #4757

Merged
merged 2 commits into from
Jan 26, 2024
Merged

[Docs] Remove broken link from Understand How Flyte Handles Data page (for new monodocs site) (second attempt) #4757

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1a01f33
remove broken link
Jan 22, 2024
e854ed5
fix formatting
Jan 22, 2024
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
2 changes: 1 addition & 1 deletion docs/concepts/data_management.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -168,7 +168,7 @@ Between Tasks
Bringing in Your Own Datastores for Raw Data
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Flytekit has a pluggable `data persistence layer <https://docs.flyte.org/projects/flytekit/en/latest/data.extend.html>`__.
Flytekit has a pluggable data persistence layer.
This is driven by PROTOCOL.
For example, it is theoretically possible to use S3 ``s3://`` for metadata and GCS ``gcs://`` for raw data. It is also possible to create your own protocol ``my_fs://``, to change how data is stored and accessed.
But for Metadata, the data should be accessible to Flyte control plane.
Expand Down
Loading