You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by "RussellSpitzer (via GitHub)" <gi...@apache.org> on 2025/02/11 23:15:20 UTC
[PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
RussellSpitzer opened a new pull request, #12230:
URL: https://github.com/apache/iceberg/pull/12230
(no comment)
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "singhpk234 (via GitHub)" <gi...@apache.org>.
singhpk234 commented on code in PR #12230:
URL: https://github.com/apache/iceberg/pull/12230#discussion_r1952049522
##########
format/spec.md:
##########
@@ -392,7 +392,7 @@ In v3 and later, an Iceberg table can track row lineage fields for all newly cre
These fields are assigned and updated by inheritance because the commit sequence number and starting row ID are not assigned until the snapshot is successfully committed. Inheritance is used to allow writing data and manifest files before values are known so that it is not necessary to rewrite data and manifest files when an optimistic commit is retried.
-When row lineage is enabled, new snapshots cannot include [Equality Deletes](#equality-delete-files). Row lineage is incompatible with equality deletes because lineage values must be maintained, but equality deletes are used to avoid reading existing data before writing changes.
+Row lineage does not track updates for rows updated because of [Equality Deletes](#equality-delete-files). Rows updated via an equality delete are always treated as if the row was completely removed and a unique new row was created.
Review Comment:
[optional] May be rephrase the last line in suggestion above : An update via equality delete should
always be treated as if the existing row was completely removed and a unique new row was added.
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "pvary (via GitHub)" <gi...@apache.org>.
pvary commented on code in PR #12230:
URL: https://github.com/apache/iceberg/pull/12230#discussion_r1952013431
##########
format/spec.md:
##########
@@ -1766,4 +1766,4 @@ The Geometry and Geography class hierarchy and its Well-known text (WKT) and Wel
Points are always defined by the coordinates X, Y, Z (optional), and M (optional), in this order. X is the longitude/easting, Y is the latitude/northing, and Z is usually the height, or elevation. M is a fourth optional dimension, for example a linear reference value (e.g., highway milepost value), a timestamp, or some other value as defined by the CRS.
-The version of the OGC standard first used here is 1.2.1, but future versions may also used if the WKB representation remains wire-compatible.
\ No newline at end of file
+The version of the OGC standard first used here is 1.2.1, but future versions may also used if the WKB representation remains wire-compatible.
Review Comment:
What happened here?
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "aokolnychyi (via GitHub)" <gi...@apache.org>.
aokolnychyi commented on code in PR #12230:
URL: https://github.com/apache/iceberg/pull/12230#discussion_r1966211402
##########
format/spec.md:
##########
@@ -392,8 +392,7 @@ In v3 and later, an Iceberg table can track row lineage fields for all newly cre
These fields are assigned and updated by inheritance because the commit sequence number and starting row ID are not assigned until the snapshot is successfully committed. Inheritance is used to allow writing data and manifest files before values are known so that it is not necessary to rewrite data and manifest files when an optimistic commit is retried.
-When row lineage is enabled, new snapshots cannot include [Equality Deletes](#equality-delete-files). Row lineage is incompatible with equality deletes because lineage values must be maintained, but equality deletes are used to avoid reading existing data before writing changes.
-
+Row lineage does not track lineage for rows updated via [Equality Deletes](#equality-delete-files), because engines using equality deletes avoid reading existing data before writing changes and can't provide the original row_id for the new rows. These updates are always treated as if the existing row was completely removed and a unique new row was added.
Review Comment:
`the original row_id` -> `the original row ID`?
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "pvary (via GitHub)" <gi...@apache.org>.
pvary commented on code in PR #12230:
URL: https://github.com/apache/iceberg/pull/12230#discussion_r1952054468
##########
format/spec.md:
##########
@@ -392,7 +392,7 @@ In v3 and later, an Iceberg table can track row lineage fields for all newly cre
These fields are assigned and updated by inheritance because the commit sequence number and starting row ID are not assigned until the snapshot is successfully committed. Inheritance is used to allow writing data and manifest files before values are known so that it is not necessary to rewrite data and manifest files when an optimistic commit is retried.
-When row lineage is enabled, new snapshots cannot include [Equality Deletes](#equality-delete-files). Row lineage is incompatible with equality deletes because lineage values must be maintained, but equality deletes are used to avoid reading existing data before writing changes.
+Row lineage does not track updates for rows updated because of [Equality Deletes](#equality-delete-files). Rows updated via an equality delete are always treated as if the row was completely removed and a unique new row was created.
Review Comment:
Maybe it is too technical, but equality delete doesn't have to do anything with row lineage. The engines are to blame which doesn't populate the old rowId in the new version of the row.
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "pvary (via GitHub)" <gi...@apache.org>.
pvary commented on code in PR #12230:
URL: https://github.com/apache/iceberg/pull/12230#discussion_r1953883726
##########
format/spec.md:
##########
@@ -392,7 +392,7 @@ In v3 and later, an Iceberg table can track row lineage fields for all newly cre
These fields are assigned and updated by inheritance because the commit sequence number and starting row ID are not assigned until the snapshot is successfully committed. Inheritance is used to allow writing data and manifest files before values are known so that it is not necessary to rewrite data and manifest files when an optimistic commit is retried.
-When row lineage is enabled, new snapshots cannot include [Equality Deletes](#equality-delete-files). Row lineage is incompatible with equality deletes because lineage values must be maintained, but equality deletes are used to avoid reading existing data before writing changes.
+Row lineage does not track lineage for rows updated via [Equality Deletes](#equality-delete-files), because equality deletes avoid reading existing data before writing changes. An update via equality delete should always be treated as if the existing row was completely removed and a unique new row was added.
Review Comment:
What about:
Row lineage does not track lineage for rows updated via [Equality Deletes](#equality-delete-files), because engines using equality deletes avoid reading existing data before writing changes and don't provide the row_id for the new rows. These updates are always treated as if the existing row was completely removed and a unique new row was added.
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "RussellSpitzer (via GitHub)" <gi...@apache.org>.
RussellSpitzer commented on code in PR #12230:
URL: https://github.com/apache/iceberg/pull/12230#discussion_r1953360394
##########
format/spec.md:
##########
@@ -1766,4 +1766,4 @@ The Geometry and Geography class hierarchy and its Well-known text (WKT) and Wel
Points are always defined by the coordinates X, Y, Z (optional), and M (optional), in this order. X is the longitude/easting, Y is the latitude/northing, and Z is usually the height, or elevation. M is a fourth optional dimension, for example a linear reference value (e.g., highway milepost value), a timestamp, or some other value as defined by the CRS.
-The version of the OGC standard first used here is 1.2.1, but future versions may also used if the WKB representation remains wire-compatible.
\ No newline at end of file
+The version of the OGC standard first used here is 1.2.1, but future versions may also used if the WKB representation remains wire-compatible.
Review Comment:
Ugh my editor keeps doing endline changes here. I'll redo the change in vim
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "pvary (via GitHub)" <gi...@apache.org>.
pvary commented on code in PR #12230:
URL: https://github.com/apache/iceberg/pull/12230#discussion_r1953883726
##########
format/spec.md:
##########
@@ -392,7 +392,7 @@ In v3 and later, an Iceberg table can track row lineage fields for all newly cre
These fields are assigned and updated by inheritance because the commit sequence number and starting row ID are not assigned until the snapshot is successfully committed. Inheritance is used to allow writing data and manifest files before values are known so that it is not necessary to rewrite data and manifest files when an optimistic commit is retried.
-When row lineage is enabled, new snapshots cannot include [Equality Deletes](#equality-delete-files). Row lineage is incompatible with equality deletes because lineage values must be maintained, but equality deletes are used to avoid reading existing data before writing changes.
+Row lineage does not track lineage for rows updated via [Equality Deletes](#equality-delete-files), because equality deletes avoid reading existing data before writing changes. An update via equality delete should always be treated as if the existing row was completely removed and a unique new row was added.
Review Comment:
What about:
Row lineage does not track lineage for rows updated via [Equality Deletes](#equality-delete-files), because engines using equality deletes avoid reading existing data before writing changes, and don't provide the row_id for the new rows. These updates are always treated as if the existing row was completely removed and a unique new row was added.
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "pvary (via GitHub)" <gi...@apache.org>.
pvary commented on code in PR #12230:
URL: https://github.com/apache/iceberg/pull/12230#discussion_r1953883726
##########
format/spec.md:
##########
@@ -392,7 +392,7 @@ In v3 and later, an Iceberg table can track row lineage fields for all newly cre
These fields are assigned and updated by inheritance because the commit sequence number and starting row ID are not assigned until the snapshot is successfully committed. Inheritance is used to allow writing data and manifest files before values are known so that it is not necessary to rewrite data and manifest files when an optimistic commit is retried.
-When row lineage is enabled, new snapshots cannot include [Equality Deletes](#equality-delete-files). Row lineage is incompatible with equality deletes because lineage values must be maintained, but equality deletes are used to avoid reading existing data before writing changes.
+Row lineage does not track lineage for rows updated via [Equality Deletes](#equality-delete-files), because equality deletes avoid reading existing data before writing changes. An update via equality delete should always be treated as if the existing row was completely removed and a unique new row was added.
Review Comment:
What about:
-------
Row lineage does not track lineage for rows updated via [Equality Deletes](#equality-delete-files), because engines using equality deletes avoid reading existing data before writing changes, and don't provide the row_id for the new rows. These updates are always treated as if the existing row was completely removed and a unique new row was added.
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "RussellSpitzer (via GitHub)" <gi...@apache.org>.
RussellSpitzer commented on code in PR #12230:
URL: https://github.com/apache/iceberg/pull/12230#discussion_r1953375995
##########
format/spec.md:
##########
@@ -1766,4 +1766,4 @@ The Geometry and Geography class hierarchy and its Well-known text (WKT) and Wel
Points are always defined by the coordinates X, Y, Z (optional), and M (optional), in this order. X is the longitude/easting, Y is the latitude/northing, and Z is usually the height, or elevation. M is a fourth optional dimension, for example a linear reference value (e.g., highway milepost value), a timestamp, or some other value as defined by the CRS.
-The version of the OGC standard first used here is 1.2.1, but future versions may also used if the WKB representation remains wire-compatible.
\ No newline at end of file
+The version of the OGC standard first used here is 1.2.1, but future versions may also used if the WKB representation remains wire-compatible.
Review Comment:
Ok looks like there wasn't a newline here before. I may have accidentally removed it when I fixed a typo here within the github editor in a different commit.
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "stevenzwu (via GitHub)" <gi...@apache.org>.
stevenzwu commented on code in PR #12230:
URL: https://github.com/apache/iceberg/pull/12230#discussion_r1951840824
##########
format/spec.md:
##########
@@ -392,7 +392,7 @@ In v3 and later, an Iceberg table can track row lineage fields for all newly cre
These fields are assigned and updated by inheritance because the commit sequence number and starting row ID are not assigned until the snapshot is successfully committed. Inheritance is used to allow writing data and manifest files before values are known so that it is not necessary to rewrite data and manifest files when an optimistic commit is retried.
-When row lineage is enabled, new snapshots cannot include [Equality Deletes](#equality-delete-files). Row lineage is incompatible with equality deletes because lineage values must be maintained, but equality deletes are used to avoid reading existing data before writing changes.
+Row lineage does not track updates for rows updated because of [Equality Deletes](#equality-delete-files). Rows updated via an equality delete are always treated as if the row was completely removed and a unique new row was created.
Review Comment:
wonder if this is a bit more clear
```
Row lineage does not track lineage for rows updated via [Equality Deletes](#equality-delete-files),
because equality deletes avoid reading existing data before writing changes. A equality delete should
always be treated as if the existing row was completely removed and a unique new row was added.
```
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "RussellSpitzer (via GitHub)" <gi...@apache.org>.
RussellSpitzer commented on PR #12230:
URL: https://github.com/apache/iceberg/pull/12230#issuecomment-2679381223
Merged! Thanks everyone - @aokolnychyi , @rdblue , @huaxingao , @Fokko , @pvary , @stevenzwu , @singhpk234 for reviewing!
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "stevenzwu (via GitHub)" <gi...@apache.org>.
stevenzwu commented on code in PR #12230:
URL: https://github.com/apache/iceberg/pull/12230#discussion_r1951840824
##########
format/spec.md:
##########
@@ -392,7 +392,7 @@ In v3 and later, an Iceberg table can track row lineage fields for all newly cre
These fields are assigned and updated by inheritance because the commit sequence number and starting row ID are not assigned until the snapshot is successfully committed. Inheritance is used to allow writing data and manifest files before values are known so that it is not necessary to rewrite data and manifest files when an optimistic commit is retried.
-When row lineage is enabled, new snapshots cannot include [Equality Deletes](#equality-delete-files). Row lineage is incompatible with equality deletes because lineage values must be maintained, but equality deletes are used to avoid reading existing data before writing changes.
+Row lineage does not track updates for rows updated because of [Equality Deletes](#equality-delete-files). Rows updated via an equality delete are always treated as if the row was completely removed and a unique new row was created.
Review Comment:
wonder if this is a bit more clear
```
Row lineage does not track lineage for rows updated via [Equality Deletes](#equality-delete-files), because equality deletes avoid reading existing data before writing changes. A equality delete should always be treated as if the existing row was completely removed and a unique new row was added.
```
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "RussellSpitzer (via GitHub)" <gi...@apache.org>.
RussellSpitzer commented on PR #12230:
URL: https://github.com/apache/iceberg/pull/12230#issuecomment-2654818937
@stevenzwu , @pvary + @singhpk234 - Wording Updated
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "pvary (via GitHub)" <gi...@apache.org>.
pvary commented on code in PR #12230:
URL: https://github.com/apache/iceberg/pull/12230#discussion_r1953883726
##########
format/spec.md:
##########
@@ -392,7 +392,7 @@ In v3 and later, an Iceberg table can track row lineage fields for all newly cre
These fields are assigned and updated by inheritance because the commit sequence number and starting row ID are not assigned until the snapshot is successfully committed. Inheritance is used to allow writing data and manifest files before values are known so that it is not necessary to rewrite data and manifest files when an optimistic commit is retried.
-When row lineage is enabled, new snapshots cannot include [Equality Deletes](#equality-delete-files). Row lineage is incompatible with equality deletes because lineage values must be maintained, but equality deletes are used to avoid reading existing data before writing changes.
+Row lineage does not track lineage for rows updated via [Equality Deletes](#equality-delete-files), because equality deletes avoid reading existing data before writing changes. An update via equality delete should always be treated as if the existing row was completely removed and a unique new row was added.
Review Comment:
What about:
```
Row lineage does not track lineage for rows updated via [Equality Deletes](#equality-delete-files), because engines using equality deletes avoid reading existing data before writing changes, and don't provide the row_id for the new rows. These updates are always treated as if the existing row was completely removed and a unique new row was added.
```
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "pvary (via GitHub)" <gi...@apache.org>.
pvary commented on code in PR #12230:
URL: https://github.com/apache/iceberg/pull/12230#discussion_r1953883726
##########
format/spec.md:
##########
@@ -392,7 +392,7 @@ In v3 and later, an Iceberg table can track row lineage fields for all newly cre
These fields are assigned and updated by inheritance because the commit sequence number and starting row ID are not assigned until the snapshot is successfully committed. Inheritance is used to allow writing data and manifest files before values are known so that it is not necessary to rewrite data and manifest files when an optimistic commit is retried.
-When row lineage is enabled, new snapshots cannot include [Equality Deletes](#equality-delete-files). Row lineage is incompatible with equality deletes because lineage values must be maintained, but equality deletes are used to avoid reading existing data before writing changes.
+Row lineage does not track lineage for rows updated via [Equality Deletes](#equality-delete-files), because equality deletes avoid reading existing data before writing changes. An update via equality delete should always be treated as if the existing row was completely removed and a unique new row was added.
Review Comment:
What about:
Row lineage does not track lineage for rows updated via [Equality Deletes](#equality-delete-files), because engines using equality deletes avoid reading existing data before writing changes and can't provide the original row_id for the new rows. These updates are always treated as if the existing row was completely removed and a unique new row was added.
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [PR] Spec: Allow Equality Deletes with Row Lineage and Define Behavior [iceberg]
Posted by "RussellSpitzer (via GitHub)" <gi...@apache.org>.
RussellSpitzer merged PR #12230:
URL: https://github.com/apache/iceberg/pull/12230
--
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.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org