Skip to content

Place Updating data section on the same level as Procedures section #17872

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

Merged
ebyhr merged 1 commit into from
Jun 13, 2023
Merged

Place Updating data section on the same level as Procedures section #17872

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
50 changes: 25 additions & 25 deletions docs/src/main/sphinx/connector/delta-lake.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -478,31 +478,6 @@ Flush metadata cache
Flushes metadata cache entries of a specific table.
Procedure requires passing named parameters.

.. _delta-lake-write-support:

Updating data
"""""""""""""

You can use the connector to :doc:`/sql/insert`, :doc:`/sql/delete`,
:doc:`/sql/update`, and :doc:`/sql/merge` data in Delta Lake tables.

Write operations are supported for tables stored on the following systems:

* Azure ADLS Gen2, Google Cloud Storage

Writes to the Azure ADLS Gen2 and Google Cloud Storage are
enabled by default. Trino detects write collisions on these storage systems
when writing from multiple Trino clusters, or from other query engines.

* S3 and S3-compatible storage

Writes to :doc:`Amazon S3 <hive-s3>` and S3-compatible storage must be enabled
with the ``delta.enable-non-concurrent-writes`` property. Writes to S3 can
safely be made from multiple Trino clusters; however, write collisions are not
detected when writing concurrently from other Delta Lake engines. You need to
make sure that no concurrent data modifications are run to avoid data
corruption.

.. _delta-lake-vacuum:

``VACUUM``
Expand Down Expand Up @@ -531,6 +506,31 @@ measure to ensure that files are retained as expected. The minimum value for
this property is ``0s``. There is a minimum retention session property as well,
``vacuum_min_retention``.

.. _delta-lake-write-support:

Updating data
^^^^^^^^^^^^^

You can use the connector to :doc:`/sql/insert`, :doc:`/sql/delete`,
:doc:`/sql/update`, and :doc:`/sql/merge` data in Delta Lake tables.

Write operations are supported for tables stored on the following systems:

* Azure ADLS Gen2, Google Cloud Storage

Writes to the Azure ADLS Gen2 and Google Cloud Storage are
enabled by default. Trino detects write collisions on these storage systems
when writing from multiple Trino clusters, or from other query engines.

* S3 and S3-compatible storage

Writes to :doc:`Amazon S3 <hive-s3>` and S3-compatible storage must be enabled
with the ``delta.enable-non-concurrent-writes`` property. Writes to S3 can
safely be made from multiple Trino clusters; however, write collisions are not
detected when writing concurrently from other Delta Lake engines. You need to
make sure that no concurrent data modifications are run to avoid data
corruption.

.. _delta-lake-data-management:

Data management
Expand Down