- 
                Notifications
    
You must be signed in to change notification settings  - Fork 25.6k
 
Allow skip shards with _tier and _index in ES|QL #123728
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
Conversation
| 
           Pinging @elastic/es-analytical-engine (Team:Analytics)  | 
    
| 
           Hi @dnhatn, I've created a changelog YAML for you.  | 
    
…t {p0=search.vectors/41_knn_search_bbq_hnsw/Test knn search} elastic#123727
    20ac10c    to
    1653556      
    Compare
  
    | 
               | 
          ||
| public static QueryBuilder canMatchFilter(PhysicalPlan plan) { | ||
| // metadata field like _index, _tier | ||
| return detectFilter(plan, f -> CAN_MATCH_FIELDS.contains(f) || f.startsWith("_")); | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this might pull in other fields starting with _ , such as _score or other user defined functions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. To what degree the filter inside can match though be generified?
| 
           Thanks Costin. I've updated the list of supported field names in 89b5ad9.  | 
    
This change adds support for skipping shards with event.ingested fields and metadata fields (_tier, _index). This should allow ES|QL to skip unmatched shards and avoid sending requests to the data nodes.
          💔 Backport failed
 You can use sqren/backport to manually backport by running   | 
    
This change adds support for skipping shards with event.ingested fields and metadata fields (_tier, _index). This should allow ES|QL to skip unmatched shards and avoid sending requests to the data nodes. (cherry picked from commit cdd4df5)
This change adds support for skipping shards with event.ingested fields and metadata fields (_tier, _index). This should allow ES|QL to skip unmatched shards and avoid sending requests to the data nodes. (cherry picked from commit cdd4df5)
This change adds support for skipping shards with
event.ingestedfields and metadata fields (_tier, _index). This should allow ES|QL to skip unmatched shards and avoid sending requests to the data nodes.