Dataset error for tmp.UNTITLED

Every time while running a query i am getting below error.

[qtp367698638-8140] DEBUG c.d.d.s.d.DatasetVersionMutator - dataset error for tmp.UNTITLED
com.dremio.service.namespace.NamespaceNotFoundException:
at com.dremio.service.namespace.NamespaceServiceImpl.getEntitiesOnPath(NamespaceServiceImpl.java:1520) ~[dremio-services-namespace-3.3.1-201907291852280797-df23756.jar:3.3.1-201907291852280797-df23756]
at com.dremio.service.namespace.NamespaceServiceImpl.getEntity(NamespaceServiceImpl.java:799) ~[dremio-services-namespace-3.3.1-201907291852280797-df23756.jar:3.3.1-201907291852280797-df23756]
at com.dremio.service.namespace.NamespaceServiceImpl.getDataset(NamespaceServiceImpl.java:866)

Could you post the full stack trace? The error implies that the query is referencing a dataset that doesn’t exist.

Was this ever resolved? We’re getting the same thing:

2021-09-24 14:08:04,508 [qtp1149103230-176] DEBUG c.d.d.s.d.DatasetVersionMutator - dataset error for tmp.UNTITLED
com.dremio.service.namespace.NamespaceNotFoundException: one or more elements on the path are not found in namespace: tmp.UNTITLED

This is Dremio v17 in an EKS cluster deployed via Helm.

Also seeing errors such as this:

2021-09-24 14:07:53,037 [FABRIC-rpc-event-queue] DEBUG c.dremio.exec.store.dfs.PDFSProtocol - File /opt/dremio/data/pdfs/results/1eb2243b-79f5-45b1-03b1-cf44e311c600 does not exist

@adonahue Can you please upload the query profile

As an FYI, we were having the same problem here, but the properties specified herein did not resolve the issue; it seems somewhere in the code Dremio’s calling an AWS API that reaches out to sts.amazonaws.com, which has no region, and thus no endpoint. We ended up having to whitelist endpoint for Dremio to work.

On another note, it was taking almost 90 minutes for a timeout there to be reported. Is there a way to adjust that so an issue such as this is more quickly reported by Dremio?

Hi any updates on the error, facing the same

Stack: nessie, MinIO