Configuration and source management

Use the default strategy for initial source verification. Test optional settings separately using Tune lakehouse queries. Where an option supports shadow mode, it records a proposed strategy without selecting it for execution.

Parquet is the active source format. Local source paths refer to files accessible by the server account. Object-store registration metadata alone does not establish that a particular remote source can be read by the deployed runtime; verify access and a source-backed result before relying on it.

Credential fields hold a reference: none, an environment handle, a named profile, or an external secret-store reference. Provision the actual secret separately on the server. Never put secret values into a source URI or catalog properties.

Review source and target keys, direction, properties, lineage, and expected results before publishing a mapping. A published mapping exposes a view over external data. Querying that view leaves source files unchanged.

Coordinate concurrent catalog edits using the available expected-hash checks. Refresh manifests after source changes and repeat representative queries. Keep the original source versions when audit or reproducibility requirements depend on them.

A disabled feature, invalid credential reference, stale catalog hash, or invalid mapping produces a diagnostic that should be resolved before retrying. If a query reports diagnostic fixture fallback, follow Register, review, and query Parquet to verify a supported source-backed query.

Back up catalog state and externally managed Parquet data under their respective storage policies. See Back up and restore a standalone database.