Heads up I just spoke more with about the

Question

Heads up I just spoke more with < John Darrington> about the need for an alternative lock client He is going to explore making dynamodb lock into distributed lock and put dynamodb behind a feature so that postgres can also sit behind a feature That way our use of `LockClient` in the S3 storage layer can remain generic and we can start to support alternative locking implementations

Will Jones · Answer

Is this a separate effort from <https github com delta io delta rs issues 1333>

Will Jones · Answer

Oh nvm looks like they are coordinating in a different thread

Will Jones · Answer

Just want to make sure we don t have a concurrent writers conflict on PRs slightly smiling face

rtyler · Answer

< Will Jones> I haven t been paying too much attention to what < Nick Karpov> has proposed across client mechanisms To me what < John Darrington> is working towards is more about making the dynamodb lock crate more versatile and not necessarily changing any locking semantics in the `deltalake` crate itself

John Darrington · Answer

Correct I m not saying planning on touching anything but that crate