kevinjqliu commented on issue #13366: URL: https://github.com/apache/iceberg/issues/13366#issuecomment-2994426955
> I was under the assumption that SQLite would handle concurrency from the same process. Yea i think this is a quirk of the sqlite in-memory db. From https://www.sqlite.org/inmemorydb.html, ``` Every :memory: database is distinct from every other. So, opening two database connections each with the filename ":memory:" will create two independent in-memory databases. ``` The database is created per connection. ``` However, the same in-memory database can be opened by two or more database connections as follows: rc = sqlite3_open("file::memory:?cache=shared", &db); Or, ATTACH DATABASE 'file::memory:?cache=shared' AS aux1; This allows separate database connections to share the same in-memory database. ``` But with "shared cache" enabled, multiple connections can access the same database 🤷 > Another option would be to limit the concurrency to 1 to avoid race conditions completely, since SQLite is purely for testing purposes. thats a good option too. let me test that out -- 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
