Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When listing jobs via API allow a filter to be provided to return a subset #243

Open
gra-moore opened this issue May 27, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@gra-moore
Copy link
Contributor

At the moment the client is doing job filtering but in the case where there are many jobs it would be more effective to do this server side. This task needs refinement with a specification of the filters that can be applied. Suggest looking at the mim cli and filters there for initial proposal.

@gra-moore gra-moore added the enhancement New feature or request label May 27, 2023
@gra-moore
Copy link
Contributor Author

Suggest we adopt an OData url query approach to filters:

?filter=title=myjob

And then include all the filters as described in mim as of now:

┃ title=mystringhere
┃ tags=mytag
┃ id=myidstring
┃ paused=true
┃ source=dataset
┃ sink=http
┃ transform=javascript
┃ error=my error message
┃ duration>10s or duration<30ms
┃ lastrun<2020-11-19T14:56:17+01:00 or lastrun>2020-11-19T14:56:17+01:00
┃ triggers=@every 60 or triggers=fullsync or triggers=person.Crm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant