Jev query route compatibility compares two query requirements with a supplied engine configuration. The live window asks whether both can share one configured route, need separate routes, contain an unsupported requirement or need more input. Its output is a local compatibility note, not an executed query plan.
The three profiles are fictional and deliberately narrow. One accepts selective single-table reads, one accepts large multi-table aggregates and one accepts geospatial filters on a single table. None accepts writes. These are local declared scopes, not statements about any commercial engine. The model interprets the briefs against those scopes without predicting latency or cost.
An API-collected post describing Jev-based routing among configured query engines inspired this demonstration. The source mentions Iceberg as the shared table foundation. The official Iceberg documentation supplies table-format context; it does not define our fictional engine profiles or prove their capabilities. This page contributes an original two-request compatibility check with retained API observations.
Compare the shared-read, split-workload and missing-second examples. Two requests can each be supported without sharing an engine. A shared data format also does not establish that every configured route supports every operator. The window keeps those distinctions visible before an application decides how to dispatch work. No SQL text, database credential or network connection is required.