kevinjqliu commented on issue #293: URL: https://github.com/apache/iceberg-python/issues/293#issuecomment-1904641372
@Fokko Didn't know the in-memory sqlite option was available! That's awesome. I was able to read/write using the `SqlCatalog`. Metadata is saved in memory using sqlite and data is saved on disk. Pulling out [your comment in #289](https://github.com/apache/iceberg-python/pull/289#issuecomment-1903442816) > Thanks for working on this @kevinjqliu. The issues was created a long time ago, before we had the SqlCatalog with sqlite support. Sqlite can also work [in memory](https://www.sqlite.org/inmemorydb.html) rendering the `InMemoryCatalog` obsolete. Having two in-memory implementations in the codebase adds additional complexity in the codebase. My suggestion would be to replace the MemoryCatalog with the SqlCatalog. WDYT? I agree that we don't need 2 in-memory catalog implementations. Let me see if I can repurpose #289 -- 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-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
