Skip to content
This repository has been archived by the owner on Jun 2, 2022. It is now read-only.

Prototype Resource Query API (/find) #683

Closed
MikaelSmith opened this issue Jan 13, 2020 · 2 comments
Closed

Prototype Resource Query API (/find) #683

MikaelSmith opened this issue Jan 13, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request
Projects

Comments

@MikaelSmith
Copy link
Contributor

MikaelSmith commented Jan 13, 2020

Add a /find endpoint that implements selecting a set of entries based on a predicate query language. This should become the intermediate format used to implement queries from the find command, with predicate matching moved to the server.

Detailed spec to be added later.

@MikaelSmith MikaelSmith created this issue from a note in ROADMAP (Ready) Jan 13, 2020
@ekinanp
Copy link
Contributor

ekinanp commented Jan 13, 2020

Future work could remove fullmeta and have the schema figure out which metadata to use. For example, given something like

find -m .tags

we'd get tags as the parsed key. Logic would then be:

  • If tags is valid key sequence in partial metadata schema, then use that. Otherwise, if tags is a valid key sequence in full metadata schema, use that. Otherwise, it is an invalid key sequence.

@MikaelSmith MikaelSmith moved this from Ready to In Progress in ROADMAP Jan 22, 2020
@ekinanp
Copy link
Contributor

ekinanp commented Jan 27, 2020

We'll also need to document this stuff on the website, least the RQL grammar in detail.

@MikaelSmith MikaelSmith added the enhancement New feature or request label Mar 3, 2020
@MikaelSmith MikaelSmith moved this from In Progress to Done in ROADMAP Mar 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

2 participants