What is V-Order in Fabric?
Why C is the answer
A write-time optimization for Parquet that improves reads
V-Order is a write-time optimization for Delta Parquet files.
In detail
- V-Order is a write-time Parquet optimization that improves reads.
- It costs a little at write time, in return for reads.
Use case
An illustrative scenario, not a real incident.
A report over a large table reads faster after files are written with V-Order, and the files are still standard Parquet.
See it in different ways
flowchart LR A["Many small files"] --> B["OPTIMIZE compacts them"] B --> C["VACUUM removes unreferenced files"] C --> D["Faster reads"]
stateDiagram-v2 [*] --> SmallFiles: many small writes SmallFiles --> Compact: OPTIMIZE Compact --> Sorted: V-Order or Z-Order Sorted --> Cleaned: VACUUM removes unreferenced files Cleaned --> SmallFiles: more writes
flowchart LR S0["Write Parquet"] --> S1["V-Order applied"] --> S2["Faster reads"]
Key point: V-Order optimizes Parquet at write time.
Why the other options are wrong
- A. A method of promoting content between stages
- It does not promote content.
- B. A KQL function for time windows
- It is not a KQL function.
- D. A workspace role for data viewers
- It is not a role.