iceberg-rust icon indicating copy to clipboard operation
iceberg-rust copied to clipboard

feat: support update for memory catalog

Open ZENOTME opened this issue 10 months ago • 2 comments

To add runnable update example #999, we should support update forthe memory catalog first.

ZENOTME avatar Feb 24 '25 12:02 ZENOTME

cc @Xuanwo @liurenjie1024 @fqaiser94

ZENOTME avatar Feb 24 '25 12:02 ZENOTME

Thanks @ZENOTME for this pr. The reason we don't add update table support before is that currently the table transaction api is not complete yet, and we should not add this in catalog in such a way.

Hi @liurenjie1024, I'm confused why we don't add update table support before transaction api is not complete yet. Which transaction API should we support first?🤔 According to my understanding, the update table implementation of the catalog is decoupled with the transaction API.

I notice that for the other catalog, except RestCatalog. Their update behaviour based on the MetastoreCatalog. MetastoreCatalog will provide a unified way to write metadata file. Is your mean is that we should complete MetasoreCatalog first?

ZENOTME avatar Mar 06 '25 09:03 ZENOTME