Skip to content

Use KeyLike for partial uid lookups - #81

Open
genematx wants to merge 1 commit into
bluesky:mainfrom
genematx:support-key-like
Open

genematx wants to merge 1 commit into
bluesky:mainfrom
genematx:support-key-like

Conversation

@genematx

Copy link
Copy Markdown
Contributor

A partial uid lookup used Like on the start.uid metadata field, which no index can serve, so it scanned every run in the catalog. A run's node key is its uid, so match on the key with KeyLike instead, which uses the catalog's key column. Closes #79.

Fall back to Like when the server does not advertise the key_like query: such a server silently ignores the filter and returns every run. Require tiled >=0.2.22, which introduces KeyLike.

A partial uid lookup used Like on the start.uid metadata field, which
no index can serve, so it scanned every run in the catalog. A run's
node key is its uid, so match on the key with KeyLike instead, which
uses the catalog's key column. Closes bluesky#79.

Fall back to Like when the server does not advertise the key_like
query: such a server silently ignores the filter and returns every
run. Require tiled >=0.2.22, which introduces KeyLike.

CatalogOfBlueskyRuns.search prefixes a query's key with 'start.' to
default to the RunStart document; exempt KeyLike and KeyLookup, whose
key is the node key, not a metadata path.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use new KeyLike to optimize partial UID lookups

2 participants