Preflight checks for Dremio
Before crawling Dremio, you can run preflight checks to check for any permissions or configuration issues before running the crawler. The following preflight checks are performed:
The checks run in order, and each depends on the previous one passing—if connection validation fails, the authentication and permissions checks are skipped.
Connection validation
This check verifies connectivity to the Dremio instance by making an unauthenticated HTTPS request to the specified host and port. TLS verification is always enabled.
✅ Connection successful
❌ Connection failed: <error-message>
Authentication check
This check verifies that the provided credentials (username/password or Personal Access Token) are valid by authenticating with the Dremio REST API. It also detects the Dremio edition (Community or Enterprise).
✅ Authentication successful
❌ Authentication failed: <error-message>
Permissions validation
This check verifies that the authenticated user can actually read the catalog, not just that a token is valid. It reads the top-level containers—scoped to the spaces and sources you selected with the include/exclude filters—and then samples datasets beneath each one to confirm they're readable.
A container is flagged as inaccessible when a significant share of the sampled datasets return permission or server errors. This catches the common case where the top level lists fine but the datasets underneath aren't granted to the crawling user, so you can fix grants before the crawl rather than after.
✅ Permissions validated
❌ Permissions insufficient: <error-message> (lists the inaccessible spaces or sources)