Answer: On the failing cluster we had accidently same node names for two
nodes. After fixing that everything is fine.
I am wondering: Shouldn't ES come up with some kind of warning when same
node name is used twice in a cluster or do names haven't to be unique
actually?
Am Montag, 27. Oktober 2
Addendum: And against a 1.3.2 cluster with 2 nodes it works as expected,
but not in 1.3.4 ?
Am Montag, 27. Oktober 2014 15:09:10 UTC+1 schrieb Tom:
>
> I ran into same "caching" problem with latest ES 1.3.4.
> I updated documents which just hold completion field to use with
> completion sug
I ran into same "caching" problem with latest ES 1.3.4.
I updated documents which just hold completion field to use with completion
suggester, even if i deleted docs via id and they can't be found via
_search endpoint anymore i still get suggests for those deleted documents.
I use a cluster with
Hi,
twitter typeahead is autocomplete library which is broadly used to
implement such features on websits. It allows to fetch remote suggests via
AJAX which is the way how I use it. The AJAX query has the value the user
searched for , in below case I typed "j" in the search bar. The typeahead
Hey,
most likely I didnt get your use-case. But something like twitter typeahead
would return a twitter handle as output, which is unique? Or something like
"@spinscale | Alexander Reelsen", which is unique as well. Not sure what
kind of output you want to return which is not unique. If you are se
Hi,
then I am not sure if the suggester is the right tool to use for my use
case. This is how I want to use ES:
* I have model where are users, tags and groups. All of them can have the
same values. The values searched are single word tokens no sentences
* The search would be done using the twi
Hey Jorge,
you can have two exact the same inputs. However, those need to have a
different output in order to occur as different suggestions (as those are
important for the data being returned).
--Alex
On Sat, Feb 8, 2014 at 4:02 AM, Jorge Sanchez wrote:
> Hi,
>
> really appreciate that you
Hi,
really appreciate that you are looking into this. I got it working with
elasticsearch-1.0.0.RC2
release. I don't know what was wrong with 0.90. Now the deletes and updates
are ok anyway I have a question. If there are two documents with "exactly"
the same input - in my case i put two docum
Jorge,
I ran your sequence and I got these results which look correct:
{
"_shards" : {
"total" : 5,
"successful" : 5,
"failed" : 0
},
"user-suggest" : [ {
"text" : "j",
"offset" : 0,
"length" : 1,
"options" : [ {
"text" : "jorge",
"score" : 1.0, "payl
Hi,
here is the sequence:
put /gruppu
post /gruppu/user/_mapping
{
"user" : {
"properties" : {
"name" : { "type" : "string" },
"suggest" : { "type" : "completion",
"index_analyzer" : "simple",
"search_analyzer" :
Strange, I tried it on 0.90.10 and it works as expected also. Can you
please post the complete sequence of steps (exact commands starting with an
empty cluster) from beginning to end so that I can try it and see if I can
reproduce your problem? Thanks.
--
You received this message because you
Hi,
I have this following version:
elasticsearch-0.90.10
PS: I can open the server with public IP to be reachable from internet if
you would like to see that behavior yourself.
Regards,
Jorge
Dne pátek, 7. února 2014 12:25:13 UTC-6 Binh Ly napsal(a):
>
> Jorge,
>
> May I ask what version of E
Jorge,
May I ask what version of ES are you using? I just tried this on 1.0 RC 2
and the updates/deletes seem to be working properly as expected.
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receivin
Hello,
I am using completion suggester for user search on my website. I basically
followed the howto from elasticsearch webpage.
Created the mapping:
post /gruppu/user/_mapping
{
"user" : {
"properties" : {
"name" : { "type" : "string" },
"suggest" : { "type" :
14 matches
Mail list logo
