You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 2-arity version of clojurewerkz.elastisch.native.index/get-mapping ignores the index-name parameter, and would have no way of retrieving mappings for the specified index-name. But beside simply returning a map of all indices, it seems that the map contains duplicate data, with cases like the following (in my example): :locindex {:mappings {:get-together {:mappings {: ... } where locindex and get-together are separate indices.
To demonstrate, I've included output which contains the value returned from (get-mapping conn "testidx") to demonstrate the previously described behavior; output
from the 3-arity version of the function which correctly returns the index and mapping requested; and finally, the browser output
from getting http://localhost:9200/textidx, which shows that there is only one mapping in this index.
The expected behavior would be that calling get-mapping with the connection information and an index name only, should return a map of the index and all mappings it contains. Instead, the response is what is described above, which is all indices, plus duplicate data that makes it impossible to know what is actually a mapping in the index.
The text was updated successfully, but these errors were encountered:
I'm going to close this as it's quite old, I'm no longer actively using elastisch, and it is clearly not something anyone else really needs at the moment.
The 2-arity version of
clojurewerkz.elastisch.native.index/get-mapping
ignores theindex-name
parameter, and would have no way of retrieving mappings for the specifiedindex-name
. But beside simply returning a map of all indices, it seems that the map contains duplicate data, with cases like the following (in my example)::locindex {:mappings {:get-together {:mappings {: ... }
wherelocindex
andget-together
are separate indices.To demonstrate, I've included
output which contains the value returned from
(get-mapping conn "testidx")
to demonstrate the previously described behavior;output
from the 3-arity version of the function which correctly returns the index and mapping requested; and finally, the
browser output
from getting
http://localhost:9200/textidx
, which shows that there is only one mapping in this index.The expected behavior would be that calling
get-mapping
with the connection information and an index name only, should return a map of the index and all mappings it contains. Instead, the response is what is described above, which is all indices, plus duplicate data that makes it impossible to know what is actually a mapping in the index.The text was updated successfully, but these errors were encountered: