o19s/elasticsearch-learning-to-rank

`_msearch` support when logging features

Open

#305 opened on May 9, 2020

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Java (366 forks)batch import
help wanted

Repository metrics

Stars
 (1,456 stars)
PR merge metrics
 (Avg merge 42d 4h) (2 merged PRs in 30d)

Description

Howdy! When logging features it sure would be faster to get to use the msearch api, though what's documented in the examples is just search. When trying to use that, hit:

~/.local/lib/python3.7/site-packages/elasticsearch/connection/base.py in _raise_error(self, status_code, raw_data)
    176
    177         raise HTTP_EXCEPTIONS.get(status_code, TransportError)(
--> 178             status_code, error_message, additional_info
    179         )

RequestError: RequestError(400, 'illegal_argument_exception', 'key [ext] is not supported in the metadata section')

Contributor guide

Research direction
Investigate how to use the msearch API with the 'ext' section in Elasticsearch query DSL. Review the logging feature plugin code to see how it currently handles single searches and adapt it to support multi search requests.
Tech stack
javapythonelasticsearch
Domain
backendsearchmachine learning
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
ElasticsearchPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65