jackye1995 closed issue #9604: InMemoryCatalog's FiloIO in memory map isn't
persistent in RestCatalog
URL: https://github.com/apache/iceberg/issues/9604
--
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
jbonofre commented on issue #9604:
URL: https://github.com/apache/iceberg/issues/9604#issuecomment-1941643985
It makes sense to improve the `TestRESTCatalog` with `InMemoryCatalog`
backend.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
nastra commented on issue #9604:
URL: https://github.com/apache/iceberg/issues/9604#issuecomment-1940527159
+1 to fixing the behavior in `TestRESTCatalog` when using `InMemoryCatalog`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to G
geruh commented on issue #9604:
URL: https://github.com/apache/iceberg/issues/9604#issuecomment-1939743479
Synced with @nastra through Slack.
This is unexpected behavior, the `RESTCatalog` used to be backed by the
`JdbcCatalog` where the ResolvingFileIO knew how to handle this Catalo
geruh commented on issue #9604:
URL: https://github.com/apache/iceberg/issues/9604#issuecomment-1928799128
Based on my current understanding, the `InMemoryCatalog` serves as the
supporting catalog for the RESTCatalog. When a table is created the
RESTTableOperations, returns a ResolvingFileI
nastra commented on issue #9604:
URL: https://github.com/apache/iceberg/issues/9604#issuecomment-1920734964
I don't think this was intended behavior.
> It seems that when instantiating the RESTCatalog, a new InMemoryFileIO
instance is also created separately.
Could you point ou
geruh opened a new issue, #9604:
URL: https://github.com/apache/iceberg/issues/9604
### Query engine
None
### Question
We are seeing some unexpected behavior when testing the `RESTCatalog`. The
`RESTCatalog` is intended to use an `InMemoryCatalog` for testing purposes. I
