Hello all,
I added two nessie catalogs in the dremio oss ui. Each one is isolated into their own azure adsl2 blob containers.
When I view them in the dremio UI they both show as having a view that really only exists in one of the catalogs. I have confirmed this by looking at the blob containers as well.
Can anyone shed some light on what might be causing this and how I can fix it? Thanks!
Hi,
having exactly the same problem. It seems UI mixes all folders of all catalogs together.
Not sure, but I think the answer might be to have a new nessie instance for each catalog.
@abksunited Can you please send over the Nessie URI from both sources?
In my case it‘s just two different S3 buckets (minio). And no matter what I write in settings it‘s always same as it doesn’t read/use that setting…
Similar for me. Was using the same Nessie instance deployed in kubernetes. Within dremio each Nessie catalog was pointed to a diff azure adls gen 2 bucket.
http://172.291.81:19120/api/v2 - Nessie endpoint
So it’s not in UI only, also when connecting with JDBC.
I’ve created the following catalogs/folders:
So this is a big mystery, you can specify the S3 bucket (and folder) in the Nessie source settings, but it has no effect. OTOH, you cannot leave it empty…
@rbecher Let me look into this and get back to you
One more thing: when creating tables, they appear in the right bucket from that setting.
Nessie endpoint is the catalog, catalog shows all entries it has. Can you have Nessie UI or CLI against your Nessie Servers, the relationship would become more apparent
I agree that it seems to be causing confusion. We are looking to see if we can add something in this section to indicate that a different storage containers don’t mean that they are unique catalogs.
That is ok, but a Dremio Nessie source should filter down the Nessie folders on the setting AWS root path…
