Closed sebastienPinel closed 1 week ago
Can you elaborate why this is a bug in Nessie and not in StarRocks?
Not sure if that's a Nessie or StarRocks bug. We tried with Tabular rest catalog adapter which is using a JdbcCatalog and in-memory and this property is present in this case.
I believe this was discussed in Nessie's Zulip chat.
Apparently running ALTER DATABASE your.db SET LOCATION 'your.location'
(e.g. via Spark) should allow StarRocks to proceed.
If Spark is too much of a trouble to set up, the same property can be set via Nessie REST API, but the exact commands will be a bit more complex. Feel free to open a thread about that in Zulip and I'm sure we can figure something out.
@sebastienPinel can you check against Nessie 0.95.0?
@snazy I checked and the "location" property is present now. It should work with StarRocks now. I don't have time to check using StarRocks but if I go back to it, I'll keep you posted !
What happened
I was experimenting with StarRocks and trying to use Nessie Rest API for Catalog. When trying to request to a specific DB (namespace), I have the following stacktrace:
Digging into StarRocks code, I found that the nessie response from /iceberg/v1/{prefix}/namespaces/{namespace} is missing the location property (we only have owner one).
How to reproduce it
Nessie server type (docker/uber-jar/built from source) and version
docker
Client type (Ex: UI/Spark/pynessie ...) and version
Starrocks
Additional information
No response