You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change query plan capnp to use structured data (#4611)
This PR changes the CAPNP format not to serialize the JSON dump of the
Query Plan, but to serialize just the required info from the Cloud
server (only `Query strategy` for now).
It also fixes a couple of issues found during testing, the most
ambiguous being:
- Part of the information Query Plan prints to the user is `VFS.Backend`
. For local queries that’s trivial to get from parsing the array URI.
For remote ones, it’s feasible again to get it from URI if it’s of the
form `tiledb://<namespace>/<backend>://<bucket>/<array_name>` but not if
it’s in form `tiledb://<namespace>/<array-name>`.
To address this for now I am printing `Unknown` as `VFS.Backend` for
such array URIs but I am open to better ideas.
example QueryPlan output:
```
"TileDB Query Plan": {
"Array.Type": "sparse",
"Array.URI": "tiledb://unit/s3://tiledb-ypatia/scratch/aov2w20",
"Query.Attributes": [
"value"
],
"Query.Dimensions": [
"__tiledb_rows"
],
"Query.Layout": "global-order",
"Query.Strategy.Name": "SparseGlobalOrderReader",
"VFS.Backend": "s3"
}
```
---
TYPE: NO_HISTORY
DESC: Change query plan capnp to use structured data
0 commit comments