DATA LAKES AND LAKEHOUSES


Unstructured data in the lakehouse: files stay on storage while Diskover delivers one row per file, with owner, project, age, and tags

Gartner puts unstructured data at 70% to 90% of enterprise data. It sits in files on network storage, object storage, and clouds, outside the tables your analysts and AI tools query. Copying all of it into the lake brings duplicates, stale versions, and restricted files along with the useful ones.

Files become queryable.

File metadata arrives as rows, so analysts use the SQL and BI tools they already know.

Lower storage and compute costs.

Files are never copied into the lakehouse, and only the curated set flows, so you pay for the rows that matter.

Traceable AI datasets.

Each row keeps its path and tags, so teams can always see which files fed a model, report or project.

Core fields.

name, path, type, size, owner, group, and created, modified, and accessed dates, and more.

Business context.

project, client, department, workflow stage, and the details plugins read from file headers.

Decisions.

tags such as approved, archive candidate, or retention class, applied manually or automatically by rules.

Keep the lake itself in shape.

Dell Technologies, a technological partner of Diskover Data
Snowflake logo, a technology partner of Diskover Data
Diskover sends metadata about your files as rows, not the files. The file content stays on your storage until a workflow or a query calls for it.
The Dell Data Lakehouse and Snowflake through partner integrations, and any platform that reads Parquet files or calls a REST API, including cloud analytics services.
Define the set with a catalog query on any metadata field, including tags, for example, approved files from one project in the last year. The Snowflake app and scheduled reports deliver only that set, and the delivery follows the rules as files change. A full Parquet export sends every scanned file, with the fields you choose.
Delivery runs after each scan or on the schedule you set, so the rows follow your storage as it changes.
A data lake stores raw files. A data lakehouse adds tables and queries on top of that storage. Diskover helps with both: it keeps the lake clean and sends the lakehouse curated rows.
Files like images, videos, and documents don’t fit in tables, so you bring their metadata instead. Diskover scans your storage, adds business context and tags, and delivers the files you choose as rows with their metadata, such as path, owner, project, and tags. The files stay where they are. Your lakehouse gets a clean table it can query and join with other business data. Learn the difference between a data lake and a lakehouse.
Scroll to Top