You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by "Fokko (via GitHub)" <gi...@apache.org> on 2024/02/09 18:25:26 UTC
[I] Merge into / Upsert [iceberg-python]
Fokko opened a new issue, #402:
URL: https://github.com/apache/iceberg-python/issues/402
### Feature Request / Improvement
Have an API to efficiently perform an upsert
--
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.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: [I] Merge into / Upsert [iceberg-python]
Posted by "corleyma (via GitHub)" <gi...@apache.org>.
corleyma commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2000597425
Note from Slack: to work in the larger-file usecases where folks are using PySpark/Spark, I think this would need to play well with pyarrow streaming read/write functionality, so that one could do atomic upsert of batches without having to read all the data into memory at once.
I call this out because current write functionality works with pyarrow Tables, which are fully materialized in memory. Working with larger data might include making the pyiceberg write APIs work with `Iterator[RecordBatch]` and friends (as returned by pyarrow Datasets/Scanner) in addition to pyarrow Tables.
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "sungwy (via GitHub)" <gi...@apache.org>.
sungwy commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2271531980
@ev2900 agreed :) I've added that Issue above (#1008) to address that
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "kevinjqliu (via GitHub)" <gi...@apache.org>.
kevinjqliu commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2688531149
yes we have plans to improve upsert functionalities. The current implementation was a first pass to support the minimal functionalities of upsert :)
I can open a new issue to track features we'd want to improve upsert. I think Delta's merge functionality is a great reference
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "Fokko (via GitHub)" <gi...@apache.org>.
Fokko closed issue #402: Merge into / Upsert
URL: https://github.com/apache/iceberg-python/issues/402
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "ev2900 (via GitHub)" <gi...@apache.org>.
ev2900 commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2271530014
Let me take a look at this. It would be very helpful if there was an example
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "Fokko (via GitHub)" <gi...@apache.org>.
Fokko commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2661086172
@soumilshah1995 Good one, let me add an example.
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "soumilshah1995 (via GitHub)" <gi...@apache.org>.
soumilshah1995 commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2661067357
Hi can you please help us with some example code ?
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "syun64 (via GitHub)" <gi...@apache.org>.
syun64 commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2164079178
Hi @corleyma - I opened up this PR to address your comment here by [introducing a scan API that will return a RecordBatchReader](https://github.com/apache/iceberg-python/pull/786). It's pending some resolutions with related issues, but it's _almost_ complete. Would appreciate your feedback if you are interested in using this API 🙂
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "akelsaman (via GitHub)" <gi...@apache.org>.
akelsaman commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2958773714
I couldn't find "on a.key=b.key" expression and documentation "https://py.iceberg.apache.org/api/#upsert" mentioned that "PyIceberg will automatically detect which rows need to be updated, inserted or can simply be ignored."
I don't know the impact on big/large/huge tables.
Also I want to make sure how it works and if it's Metadata-Based Pruning to only read required files in batches ?
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "Fokko (via GitHub)" <gi...@apache.org>.
Fokko commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2661107309
@soumilshah1995 I've raised a PR here https://github.com/apache/iceberg-python/pull/1665
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "sungwy (via GitHub)" <gi...@apache.org>.
sungwy commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2261562035
> Hello, thanks for all the great work!
>
>
>
> Now that version `0.7.0` is released, I was wondering where can I find some documentation covering how to write to a partitioned table.
>
>
>
> Thanks a lot!
Hi @Milias you can create a table with a partition by following the documentation here on [Creating a table](https://py.iceberg.apache.org/api/#create-a-table).
I realize we could have had an explicit section on creating and writing to a partitioned table under **Write to a Table section**. Currently, we support partitioned writes for IdentityTransform and TimeTransform (Year, Month, Day, Hour) partitions. Please let us know if that works for you!
Sung
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "sungwy (via GitHub)" <gi...@apache.org>.
sungwy commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2371902578
Hi @Minfante377 sorry for the delayed response, and thank you for the interest!
Unfortunately, this is still an open issue on PyIceberg with no assignee. MERGE INTO with the column matching semantics like:
`MERGE INTO table t using (SELECT ...) s ON t.id = s.id`
is unfortunately a bit complicated to support efficiently, so I've been trying to make time to look at it in depth. And unfortunately I haven't had the time for this specific issue.
Would you be interested in making a contribution?
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "sungwy (via GitHub)" <gi...@apache.org>.
sungwy commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2262744645
I think you must be referring to dynamic overwrite / replace partition API that detects the partitions of the given input and replaces it. This feature is actually still in progress on this PR: https://github.com/apache/iceberg-python/pull/931
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "Fokko (via GitHub)" <gi...@apache.org>.
Fokko commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2898895243
@zero-element @steven-luabase Have you [looked into `union-by-name`](https://py.iceberg.apache.org/api/#union-by-name)? This will allow for schema evolution. You could wrap it in the same transaction.
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "Fokko (via GitHub)" <gi...@apache.org>.
Fokko closed issue #402: Merge into / Upsert
URL: https://github.com/apache/iceberg-python/issues/402
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "Milias (via GitHub)" <gi...@apache.org>.
Milias commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2262576205
Hey @sungwy, thanks for the quick answer!
I was already making use of writing support and indeed had seen that section of the documentation. Right now I prepared a very quick test of writing to a table partitioned with `IdentityTransform`. Then, `.append` and `.overwrite` work as expected, that is, they either append new data to the appropriate partitions and replace the whole table, respectively.
After this I'm left wondering how can individual partitions be replaced. Maybe this functionality is not yet supported, with writes to partitioned table being only the first step. To give an example of what I mean, taking the table from the example in the documentation:
```python
import pyarrow as pa
df = pa.Table.from_pylist(
[
{"city": "Amsterdam", "lat": 52.371807, "long": 4.896029, "index": 1},
{"city": "San Francisco", "lat": 37.773972, "long": -122.431297, "index": 1},
{"city": "Drachten", "lat": 53.11254, "long": 6.0989, "index": 2},
{"city": "Paris", "lat": 48.864716, "long": 2.349014, "index": 2},
],
schema=schema_to_pyarrow(tbl.schema())
)
tbl.overwrite(df)
```
With table:
```python
schema = Schema(
NestedField(1, "city", StringType(), required=False),
NestedField(2, "lat", DoubleType(), required=False),
NestedField(3, "long", DoubleType(), required=False),
NestedField(4, "index", IntegerType(), required=True),
)
partition_spec = PartitionSpec(
PartitionField(source_id=4, field_id=1000, transform=IdentityTransform(), name="index_partition"),
)
tbl = catalog.create_table("public.cities", schema=schema, partition_spec=partition_spec)
```
Then, if we add a few more rows:
```python
df2 = pa.Table.from_pylist(
[
{"city": "Amsterdam", "lat": 52.371807, "long": 4.896029, "index": 1},
{"city": "Null Island", "lat": 0.0, "long": 0.0, "index": 3},
],
schema=schema_to_pyarrow(tbl.schema())
)
```
Then, when doing `tbl.overwrite(df2)` I would like to have some way of indicating that partition with `index = 2` should be left as-is.
It is very possible that I misunderstood the precise scope of write support to partitioned tables, since this issue #402 is still open. But in case that it is already possible to overwrite specific partitions, that's the piece of information I was searching for.
Thanks a lot again :smiley:
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "Minfante377 (via GitHub)" <gi...@apache.org>.
Minfante377 commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2322949632
Any updates on this one? I'm good with overwrite + overwrite filters for now but for tables where columns are populated by different sources it would be awesome to have full `MERGE INTO` support and to be able to select which columns to update
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "tusharchou (via GitHub)" <gi...@apache.org>.
tusharchou commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2572824642
@sungwy I would like to pick this up 😄
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "steven-luabase (via GitHub)" <gi...@apache.org>.
steven-luabase commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2898885350
@kevinjqliu which issue is tracking upsert improvements? Looking to subscribe to it and keep tabs on progress. We may be looking at a similar use case in the future as @zero-element to support merging of different schemas
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "sungwy (via GitHub)" <gi...@apache.org>.
sungwy commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2271507538
Hi @ev2900 - would using the `overwrite` feature by specifying the boolean expression on which to upsert work for your use case?
https://github.com/apache/iceberg-python/blob/main/pyiceberg/table/__init__.py#L479-L483
I realize we don't have an example of invoking an `overwrite` without the `overwrite_filter` specified. I'll raise an issue to track adding this explicitly into our API documentation. https://github.com/apache/iceberg-python/issues/1008
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "ev2900 (via GitHub)" <gi...@apache.org>.
ev2900 commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2271487358
Any update on if there is an API for merge into / upsert?
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "Milias (via GitHub)" <gi...@apache.org>.
Milias commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2261555662
Hello, thanks for all the great work!
Now that version `0.7.0` is released, I was wondering where can I find some documentation covering how to write to a partitioned table.
Thanks a lot!
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "Milias (via GitHub)" <gi...@apache.org>.
Milias commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2264079323
That PR looks exactly like what I am asking for, yes! Thank you very much for pointing it out. I will keep an eye on it.
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "zero-element (via GitHub)" <gi...@apache.org>.
zero-element commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2899785059
> [@zero-element](https://github.com/zero-element) [@steven-luabase](https://github.com/steven-luabase) Have you [looked into `union-by-name`](https://py.iceberg.apache.org/api/#union-by-name)? This will allow for schema evolution. You could wrap it in the same transaction.你是否查看了 `union-by-name` ?这将允许模式演化。你可以将它包装在同一个事务中。
@Fokko It seems that union_by_name is primarily used for schema alignment rather than for upserting data from another table into an existing one. I'm not sure if I've misunderstood anything, but the latter is what I actually need.
--
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: [I] Merge into / Upsert [iceberg-python]
Posted by "zero-element (via GitHub)" <gi...@apache.org>.
zero-element commented on issue #402:
URL: https://github.com/apache/iceberg-python/issues/402#issuecomment-2688328421
It appears that the [current implementation of upsert ](https://github.com/apache/iceberg-python/blame/0fbf6e2a97ce4724984ac09611d1b0eedc1bf914/pyiceberg/table/__init__.py#L1181)only supports merging tables with the same (or compatible) schema. Is there any possibility that we could implement a merge operation for tables with different schemas, similar to Delta Lake's [merge functionality ](https://delta-io.github.io/delta-rs/api/delta_table/delta_table_merger/#deltalake.table.TableMerger.when_matched_update_all)?
--
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