-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Improved percolation api #4317
Copy link
Copy link
Closed
Labels
:Search Relevance/PercolatorReverse search: find queries that match a documentReverse search: find queries that match a document>enhancementTeam:Search RelevanceMeta label for the Search Relevance team in ElasticsearchMeta label for the Search Relevance team in Elasticsearchhelp wantedadoptmeadoptme
Metadata
Metadata
Assignees
Labels
:Search Relevance/PercolatorReverse search: find queries that match a documentReverse search: find queries that match a document>enhancementTeam:Search RelevanceMeta label for the Search Relevance team in ElasticsearchMeta label for the Search Relevance team in Elasticsearchhelp wantedadoptmeadoptme
Type
Fields
Give feedbackNo fields configured for issues without a type.
Hey guys,
I was working with the percolator earlier today, and I thought of a nice way to improve its api. So, right now, if I register a query using the percolator:
and I percolate a matching document
I get something of the effect back:
Which a fine way of doing things, but I think it'd be nicer to be able to register metadata along with the query. So, something of the effect:
If a document matched, I'd get something like this back:
Currently, if I need to store more information about a query, I need to do hacks, such as concatenating strings with all the information I want to get back from that match (example: "campaign:1-id:1-name:kuku") to use as the id of that document, but that has drawbacks.
What do you guys think?