Ability to do NOT(keyX:ValueY) queries
See original GitHub issueA key feature for job manager is an ability to ‘archive’ a job so that it no longer shows in the UI when you don’t want to see it anymore. Say it was a failure and you have dealt with the failure. You don’t need to see it every time you look at recently failed jobs if you’ve dealt with it. The idea for implementing this was to have a label key called “flag” and have a value “archived” that we could apply to jobs a user wants to archive. The part we are struggling with is how to filter those out of view in the UI. If it’s not difficult, the best way would be to be able to do queries where we say “show me all the jobs that match this query and do not have the label flag:archived
attached to them”
Is this something that would be possible?
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
NoSQL database types explained: Key-value store - TechTarget
Read about the benefits of a key-value store -- a simple NoSQL database used to store, retrieve and remove data.
Read more >What exactly are keys, queries, and values in attention ...
The key/value/query formulation of attention is from the paper Attention Is All You Need. How should one understand the queries, keys, ...
Read more >Intro To Key-value Stores | Severalnines
In this blog post, we will go through key-value stores, the advantages & disadvantages, some of the use cases as well as some...
Read more >Understanding Key-Value Databases - DATAVERSITY
“Pure” key-value databases do not use a query language, but they do offer a way to retrieve, save, and delete data by using...
Read more >The pros and cons of different data formats: key-values vs tuples
Key -Value Store · Optimized only for data with single key and value. A parser is required to store multiple values. · Not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Makes sense, thanks for the explanation (asking “why?” is often a great way to get context).
Hi @kbergin, is the label
flag:archived
applied to root workflows or both root and it’s subworkflows?