Comments (13)
I did not implement it in 1.0
because it seemed like a non-essential feature we also did not have good API ideas for. Now it's time. Hopefully in 1.1
. I agree that it can learn a lot from what is done for #11.
from elastisch.
Also, feel free to take a crack at it, following #11 implementation as a guideline.
from elastisch.
I think I will wait for you to release the native client support, this could prevent doing the work twice (I could be wrong, I am not really familiar with Elastisch codebase). But yeah I agree it's really not something essential, just something missing (I have no use for it personally).
from elastisch.
I have a need for multi search. Is anyone working on this?
from elastisch.
Not that I'm aware of.
from elastisch.
Ok, I'll have a go at it
from elastisch.
I finally got around to looking into this today. I made a first draft modelled after the bulk API:
https://github.com/boutros/elastisch/commits/multi-search
Example usage:
(require '[clojurewerkz.elastisch.rest.multi :as multi]
'[clojurewerkz.elastisch.query :as query]
'[clojurewerkz.elastisch.rest :as esr])
(def queries-with-headers
[{:index "people"} {:query (query/match-all) :size 1}
{:index "articles"} {:query (query/match-all) :size 1}])
(esr/connect "http://localhost:9200")
(multi/search queries-with-headers)
=> {:responses [...]}
The headers must be interleaved with the queries. Maybe we should make helper functions for when headers are empty/not needed? eg. when using the multi/search-with-index
version, when all queries targets the same index.
I haven't worked with the native client yet, but I assume it easily can be done. Should add some tests and docs too. Anyway, the supplied solution fulfills my needs, but please let me know what else is missing.
I'm neither a Clojure nor Elasticsearch expert, so I'd appreciate if someone could see if this make sense.
from elastisch.
Looks like a good starting point. I have a question: what keys will be present in the returned map? Can we simply return a list/sequence or the map is necessary for some reason?
Thank you!
from elastisch.
:responses
is the only key in the result map, so you are right it would be better to just return the seq of the query responses. The only exception would be if the requests fails completely, in which case an object with an error message will be returned instead, according to the ES docs: http://www.elasticsearch.org/guide/reference/api/multi-search/
I have never experienced such failure. I couldnt really find how failures in general are handled in Elastisch - is it mainly left to the user to deal with?
The order of the responses matches the order of queries, so that's how you identify which is which.
from elastisch.
Non-2xx or 3xx responses will result in an exception.
from elastisch.
Right, so then the search functions only have to consider the "happy path", and can safely discard the map and simply return a vector of the responses.
I'll write some test cases and docs tomorrow
from elastisch.
Thank you!
from elastisch.
Fixed for HTTP client with #33.
from elastisch.
Related Issues (20)
- Enable the use of Elastic Shield HOT 9
- _version_type ignored in native bulk HOT 2
- Native get-mapping ignores index name in 2-arity version, returns all index mappings HOT 2
- doc link is dead HOT 1
- Node info endpoint HOT 4
- HTTP API nodes stats endpoint - unable to select specific groups of stats
- Support Elasticsearch 6.x (and 5.x to the extent it makes sense) HOT 17
- Delete by query is not working with HTTP (wrong url?) HOT 3
- Index creation failure in Elasticsearch 5.X HOT 1
- Async version of the REST API HOT 5
- Fix Delete By Query for Elasticsearch 5 HOT 4
- rest.index/refresh fails for Elasticsearch 5 HOT 5
- How can i change port number at which the queries are sent? HOT 1
- Update doc string for search HOT 1
- Cannot create a new index HOT 1
- HTTP client should be configured to use {:content-type :json} by default HOT 1
- Support clojure 1.10.0 HOT 6
- 3.0.1 release date? HOT 3
- Elasticsearch 7.x support? HOT 1
- Unable to create index
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from elastisch.