topic Delta table Concurrent Updates for Non-partitioned tables in Data Engineering

Delta table Concurrent Updates for Non-partitioned tables

Phani1 — Wed, 28 Sep 2022 16:45:35 GMT

When we implemented the concurrent updates on a table which do not have a partition column we ran into ConcurrentAppendException [ensured where the condition is different for each concurrent update statement]

So do we need to go by partition approach along with filter criteria for each transaction and ensure do not any have conflicts while doing updates?

Is there any alternate way for the non-partitioned tables which has less number of records and have to perform concurrent updates?

Re: Delta table Concurrent Updates for Non-partitioned tables

Hubert-Dudek — Wed, 28 Sep 2022 19:14:21 GMT

Please check that both streaming queries don't use the same checkpoint,
Auto increment id can also make problems as it is kept in schema
Schema evolution also can make problems

Re: Delta table Concurrent Updates for Non-partitioned tables

Phani1 — Thu, 29 Sep 2022 06:13:50 GMT

Thanks for your reply,

In the case of Non-Streaming data and Un-Partitioned Table, it is a simple delta table and performing parallel updates based on different filter criteria. Can you suggest what is a better way to handle to avoid Concurrent Append/Update Exceptions?