A large tree is hard to scan. The search box finds any item by name and jumps to it, and the Filter button narrows the tree to the folders, types, datasources or deployment states you pick. Both sit in the tree panel; The Lake screen covers the rest of the workspace.
Results are grouped by item type: Datasources, Databases, Schemas, Tables, Columns, Workflows and Folders. Each result shows the path of its parents under its name. Search covers the whole tree, not only the rows you have expanded, and matches both the name of an item and the label shown in the tree.
Within a group, closer matches come first: an exact name, then items that start with your text, then items that contain it. The list shows at most 50 results. The count beside the box shows how many matches it found; at the limit it reads 50+ and the list ends with Showing first 50 results. Type more to narrow the list. If nothing matches, the list shows No results for followed by your text. The X in the box clears the search.
A number beside Filter shows how many filter categories you have set, from one to four. Each category counts once, no matter how many options you pick inside it.
| Category | What it lists |
|---|---|
| Folder | The folders that hold at least one datasource. Empty folders are not listed. |
| Type | The source types of your datasources. |
| Datasource | Your datasources, narrowed by the folders and types you pick. |
| Deploy | Deployed and Not deployed; each option appears only while something in your scope is in that state. |
Choices cascade. When you pick a folder, Type and Datasource choices that have nothing in it are removed; when you pick a type, datasources that no longer match are removed. If a Deploy choice stops applying, it clears itself.
The pane has a Search filters... box that narrows the options of the category you are in; when nothing matches it says No matches. A category with nothing to show says so: No folders, No types, No datasources, or No datasources match when your folder or type choices already narrow the pool.
With a Deployed or Not deployed filter on, tree actions act on tables only: Delete skips the datasources, databases, schemas and folders in your selection.
Your filters stay on while you work. They are kept for the session, so a reload does not lose them.
It counts the filter categories you have set, not the number of options inside them: with folders and datasources picked it reads 2. The number disappears when you clear every filter.
No. Every option you click applies at once, so the tree updates as you choose. Click Reset to clear every filter.
Filter choices cascade. When you pick a folder, Type and Datasource choices that have nothing in it are removed; when you pick a type, datasources that no longer match are removed. Widen the earlier choice and pick them again if you need them.
The Deployed and Not deployed options appear only while your scope has tables in that state. If the state your filter was set to disappears, the filter clears itself.
The Folder list offers only folders that hold at least one datasource. Move a datasource into the folder and it appears. See Batch edit and organise.
Yes. Search covers the whole tree, not only the rows you have expanded, so a match inside a collapsed branch is still listed.
The list is capped at 50 results. At the limit, the count beside the box reads 50+ and the list ends with Showing first 50 results. Type more characters to narrow it down.
Yes. Columns is one of the result groups. Search checks both the name of an item and the label shown in the tree, so either spelling finds it.
The tree expands the collapsed parents, scrolls to the item and briefly highlights it, so you can see where it lives. See The Lake tree for how items are nested.
No. Filters are kept for the session, so a reload does not lose them, but a new session starts with none.
While a Deployed or Not deployed filter is on, tree actions act on tables only. Delete skips the datasources, databases, schemas and folders in your selection; click Reset to clear the filter and delete them.