Re: AutoCompletion Suggester - Duplicate record in suggestion return

2015-03-20 Thread Xavier TROMP 
Hello everyone,

I have the same problem using ES 1.4.4.

Did someone came up with a better solution ?

Any help would be greatly appreciated.

Thank you,
Xavier

On Monday, December 1, 2014 at 11:21:14 AM UTC+1, Tom wrote:
>
> Hi,
>
> i still have same problems with completion suggest duplicates of old and 
> updates data using ES 1.4.x
> Only way that fixed it so far was using _optimize?max_num_segments=1 which 
> has performance and maybe other impacts i assume.
>
> Is there another solution than _optimize?max_num_segments=1?
>
> Thx
> Tom
>
>
> Am Montag, 28. April 2014 11:21:49 UTC+2 schrieb Kaspars Sprogis:
>>
>> Hi,
>>
>> I have exactly same problem.
>> I resolved duplicates and appearance of deleted items by running 
>> "_optimize?only_expunge_deletes=true" on daily basis.
>>
>> However i have still problem with updates. Even if data have been updated 
>> for items in index, they still show old data when searching.
>> Only solution i found is running: "_optimize?max_num_segments=1'".
>>
>> However i have quite a lot of updates and this get me worried, because of 
>> Alexander's note:
>>
>>> if you do regular updates on that index, you should not update down to 
>>> one single segment
>>
>>
>> Alexander Reelsen, could you please advise, why we shouldn't do that or 
>> does this create some permanent damage for optimization logic or does it 
>> affects performance for search later?
>> What should we do instead?
>>
>> Thank you.
>>
>> On Wednesday, April 23, 2014 1:52:16 AM UTC+3, Alexander Reelsen wrote:
>>>
>>> Hey
>>>
>>> if you do regular updates on that index, you should not update down to 
>>> one single segment. Do you have an example, where the updates do not work 
>>> as expected?
>>>
>>>
>>> --Alex
>>>
>>>
>>> On Tue, Apr 22, 2014 at 10:51 AM, kidkid  wrote:
>>>
 Hey Alexander,
 Thanks for your reply.
 Currently I also manual do optimize by running optimize: 
 host:9200/completion_index/_optimize?max_num_segments=1 
 I think it's a work around solution. I would like to make it better.

 Sometime, I also have problem with update payload, when I change 
 payload, the completion is not change too.


 On Monday, April 21, 2014 7:26:13 PM UTC+7, Alexander Reelsen wrote:

> Hey,
>
> the output is used to unify the search results, otherwise the input is 
> used. The payload itself is just meta information.
> The main reason, why you see the suggestion twice is, that even though 
> a document is deleted and cannot be found anymore, the suggest data 
> structures are only cleaned up during merges/optimizations. Running 
> optimize should fix this.
>
> Makes sense?
>
>
> --Alex
>
>
>
> On Sun, Apr 13, 2014 at 12:49 PM, kidkid  wrote:
>
>> I have figure out the problem.
>> The main problem is I have used the same output for all input then ES 
>> have been wrong in this case.
>>
>> I still trying to improve the performance. I am just test on 64Gb Ram 
>> server (32Gb for ES 1.0.1) 24 core.
>> Have only 2 record but it took me 3ms to suggest.
>>
>>
>>
>>
>>
>>
>> On Sunday, April 13, 2014 4:53:21 PM UTC+7, kidkid wrote:
>>>
>>> There are something really strange.
>>> I don't know whether anyone have worked with this such feature or 
>>> it's just not-stable feature.
>>> If we do index same input, and different output,payload, then only 
>>> one result found.
>>>
>>> Do anyone tell me how could I fix it ?
>>>
>>>
>>>  -- 
>> You received this message because you are subscribed to the Google 
>> Groups "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, 
>> send an email to elasticsearc...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/elasticsearch/f6547a58-c002-4ff3-80c9-2052e1d14ddd%
>> 40googlegroups.com 
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  -- 
 You received this message because you are subscribed to the Google 
 Groups "elasticsearch" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to elasticsearc...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/elasticsearch/b3bf74ad-c729-4e78-9ebd-364c6c000819%40googlegroups.com
  
 
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsea

Re: AutoCompletion Suggester - Duplicate record in suggestion return

2014-12-01 Thread Tom 
Hi,

i still have same problems with completion suggest duplicates of old and 
updates data using ES 1.4.x
Only way that fixed it so far was using _optimize?max_num_segments=1 which 
has performance and maybe other impacts i assume.

Is there another solution than _optimize?max_num_segments=1?

Thx
Tom


Am Montag, 28. April 2014 11:21:49 UTC+2 schrieb Kaspars Sprogis:
>
> Hi,
>
> I have exactly same problem.
> I resolved duplicates and appearance of deleted items by running 
> "_optimize?only_expunge_deletes=true" on daily basis.
>
> However i have still problem with updates. Even if data have been updated 
> for items in index, they still show old data when searching.
> Only solution i found is running: "_optimize?max_num_segments=1'".
>
> However i have quite a lot of updates and this get me worried, because of 
> Alexander's note:
>
>> if you do regular updates on that index, you should not update down to 
>> one single segment
>
>
> Alexander Reelsen, could you please advise, why we shouldn't do that or 
> does this create some permanent damage for optimization logic or does it 
> affects performance for search later?
> What should we do instead?
>
> Thank you.
>
> On Wednesday, April 23, 2014 1:52:16 AM UTC+3, Alexander Reelsen wrote:
>>
>> Hey
>>
>> if you do regular updates on that index, you should not update down to 
>> one single segment. Do you have an example, where the updates do not work 
>> as expected?
>>
>>
>> --Alex
>>
>>
>> On Tue, Apr 22, 2014 at 10:51 AM, kidkid  wrote:
>>
>>> Hey Alexander,
>>> Thanks for your reply.
>>> Currently I also manual do optimize by running optimize: 
>>> host:9200/completion_index/_optimize?max_num_segments=1 
>>> I think it's a work around solution. I would like to make it better.
>>>
>>> Sometime, I also have problem with update payload, when I change 
>>> payload, the completion is not change too.
>>>
>>>
>>> On Monday, April 21, 2014 7:26:13 PM UTC+7, Alexander Reelsen wrote:
>>>
 Hey,

 the output is used to unify the search results, otherwise the input is 
 used. The payload itself is just meta information.
 The main reason, why you see the suggestion twice is, that even though 
 a document is deleted and cannot be found anymore, the suggest data 
 structures are only cleaned up during merges/optimizations. Running 
 optimize should fix this.

 Makes sense?


 --Alex



 On Sun, Apr 13, 2014 at 12:49 PM, kidkid  wrote:

> I have figure out the problem.
> The main problem is I have used the same output for all input then ES 
> have been wrong in this case.
>
> I still trying to improve the performance. I am just test on 64Gb Ram 
> server (32Gb for ES 1.0.1) 24 core.
> Have only 2 record but it took me 3ms to suggest.
>
>
>
>
>
>
> On Sunday, April 13, 2014 4:53:21 PM UTC+7, kidkid wrote:
>>
>> There are something really strange.
>> I don't know whether anyone have worked with this such feature or 
>> it's just not-stable feature.
>> If we do index same input, and different output,payload, then only 
>> one result found.
>>
>> Do anyone tell me how could I fix it ?
>>
>>
>>  -- 
> You received this message because you are subscribed to the Google 
> Groups "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to elasticsearc...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/elasticsearch/f6547a58-c002-4ff3-80c9-2052e1d14ddd%
> 40googlegroups.com 
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "elasticsearch" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to elasticsearc...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/elasticsearch/b3bf74ad-c729-4e78-9ebd-364c6c000819%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/bf7ccf72-d65c-4e1c-a6ec-b3a11c56f834%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AutoCompletion Suggester - Duplicate record in suggestion return

2014-08-26 Thread alistairj 
Hi Alexander,

If I may, I have a follow-up question to your response here. How does the 
completion suggester behave with fields such as payload and score when it 
is unifying the response based on output ?? Are scores increased based on 
this combination? if payloads are different, which ones are returned?

Thanks for you help!

Alistair


On Monday, April 21, 2014 2:26:13 PM UTC+2, Alexander Reelsen wrote:
>
> Hey,
>
> the output is used to unify the search results, otherwise the input is 
> used. The payload itself is just meta information.
> The main reason, why you see the suggestion twice is, that even though a 
> document is deleted and cannot be found anymore, the suggest data 
> structures are only cleaned up during merges/optimizations. Running 
> optimize should fix this.
>
> Makes sense?
>
>
> --Alex
>
>
>
> On Sun, Apr 13, 2014 at 12:49 PM, kidkid > 
> wrote:
>
>> I have figure out the problem.
>> The main problem is I have used the same output for all input then ES 
>> have been wrong in this case.
>>
>> I still trying to improve the performance. I am just test on 64Gb Ram 
>> server (32Gb for ES 1.0.1) 24 core.
>> Have only 2 record but it took me 3ms to suggest.
>>
>>
>>
>>
>>
>>
>> On Sunday, April 13, 2014 4:53:21 PM UTC+7, kidkid wrote:
>>>
>>> There are something really strange.
>>> I don't know whether anyone have worked with this such feature or it's 
>>> just not-stable feature.
>>> If we do index same input, and different output,payload, then only one 
>>> result found.
>>>
>>> Do anyone tell me how could I fix it ?
>>>
>>>
>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/f6547a58-c002-4ff3-80c9-2052e1d14ddd%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/13c35309-a55b-45d7-ba37-bd7bb44e6f20%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AutoCompletion Suggester - Duplicate record in suggestion return

2014-05-20 Thread kidkid 
Do anyone figure out how to fix this error ?

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/34f04485-6006-4bdd-b45c-4cef3bea2e06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AutoCompletion Suggester - Duplicate record in suggestion return

2014-04-28 Thread kidkid 
Hi Alexander Reelsen,
Just do at my example above. When you do update on payload or do reindex 
(with same doc id, same input, different output or payload) then the 
completion will work funny. 
Sometime it suggest updated document, some time it suggest old document.

Currently, I need to use _optimize?... to refresh FST. I don't know if 
there have anyway to refresh it better.

I do update 5-10 per second, and I think it's fine with 
"max_num_segments=1".

I really appreciate your help, thanks in advance.



On Wednesday, April 23, 2014 5:52:16 AM UTC+7, Alexander Reelsen wrote:
>
> Hey
>
> if you do regular updates on that index, you should not update down to one 
> single segment. Do you have an example, where the updates do not work as 
> expected?
>
>
> --Alex
>
>
> On Tue, Apr 22, 2014 at 10:51 AM, kidkid  >wrote:
>
>> Hey Alexander,
>> Thanks for your reply.
>> Currently I also manual do optimize by running optimize: 
>> host:9200/completion_index/_optimize?max_num_segments=1 
>> I think it's a work around solution. I would like to make it better.
>>
>> Sometime, I also have problem with update payload, when I change payload, 
>> the completion is not change too.
>>
>>
>> On Monday, April 21, 2014 7:26:13 PM UTC+7, Alexander Reelsen wrote:
>>
>>> Hey,
>>>
>>> the output is used to unify the search results, otherwise the input is 
>>> used. The payload itself is just meta information.
>>> The main reason, why you see the suggestion twice is, that even though a 
>>> document is deleted and cannot be found anymore, the suggest data 
>>> structures are only cleaned up during merges/optimizations. Running 
>>> optimize should fix this.
>>>
>>> Makes sense?
>>>
>>>
>>> --Alex
>>>
>>>
>>>
>>> On Sun, Apr 13, 2014 at 12:49 PM, kidkid  wrote:
>>>
 I have figure out the problem.
 The main problem is I have used the same output for all input then ES 
 have been wrong in this case.

 I still trying to improve the performance. I am just test on 64Gb Ram 
 server (32Gb for ES 1.0.1) 24 core.
 Have only 2 record but it took me 3ms to suggest.






 On Sunday, April 13, 2014 4:53:21 PM UTC+7, kidkid wrote:
>
> There are something really strange.
> I don't know whether anyone have worked with this such feature or it's 
> just not-stable feature.
> If we do index same input, and different output,payload, then only one 
> result found.
>
> Do anyone tell me how could I fix it ?
>
>
>  -- 
 You received this message because you are subscribed to the Google 
 Groups "elasticsearch" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to elasticsearc...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/elasticsearch/f6547a58-c002-4ff3-80c9-2052e1d14ddd%
 40googlegroups.com
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/b3bf74ad-c729-4e78-9ebd-364c6c000819%40googlegroups.com
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/c26b0711-8422-4741-a613-0c16c0b04c21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AutoCompletion Suggester - Duplicate record in suggestion return

2014-04-28 Thread Kaspars Sprogis 
Hi,

I have exactly same problem.
I resolved duplicates and appearance of deleted items by running 
"_optimize?only_expunge_deletes=true" on daily basis.

However i have still problem with updates. Even if data have been updated 
for items in index, they still show old data when searching.
Only solution i found is running: "_optimize?max_num_segments=1'".

However i have quite a lot of updates and this get me worried, because of 
Alexander's note:

> if you do regular updates on that index, you should not update down to one 
> single segment


Alexander Reelsen, could you please advise, why we shouldn't do that or 
does this create some permanent damage for optimization logic or does it 
affects performance for search later?
What should we do instead?

Thank you.

On Wednesday, April 23, 2014 1:52:16 AM UTC+3, Alexander Reelsen wrote:
>
> Hey
>
> if you do regular updates on that index, you should not update down to one 
> single segment. Do you have an example, where the updates do not work as 
> expected?
>
>
> --Alex
>
>
> On Tue, Apr 22, 2014 at 10:51 AM, kidkid  >wrote:
>
>> Hey Alexander,
>> Thanks for your reply.
>> Currently I also manual do optimize by running optimize: 
>> host:9200/completion_index/_optimize?max_num_segments=1 
>> I think it's a work around solution. I would like to make it better.
>>
>> Sometime, I also have problem with update payload, when I change payload, 
>> the completion is not change too.
>>
>>
>> On Monday, April 21, 2014 7:26:13 PM UTC+7, Alexander Reelsen wrote:
>>
>>> Hey,
>>>
>>> the output is used to unify the search results, otherwise the input is 
>>> used. The payload itself is just meta information.
>>> The main reason, why you see the suggestion twice is, that even though a 
>>> document is deleted and cannot be found anymore, the suggest data 
>>> structures are only cleaned up during merges/optimizations. Running 
>>> optimize should fix this.
>>>
>>> Makes sense?
>>>
>>>
>>> --Alex
>>>
>>>
>>>
>>> On Sun, Apr 13, 2014 at 12:49 PM, kidkid  wrote:
>>>
 I have figure out the problem.
 The main problem is I have used the same output for all input then ES 
 have been wrong in this case.

 I still trying to improve the performance. I am just test on 64Gb Ram 
 server (32Gb for ES 1.0.1) 24 core.
 Have only 2 record but it took me 3ms to suggest.






 On Sunday, April 13, 2014 4:53:21 PM UTC+7, kidkid wrote:
>
> There are something really strange.
> I don't know whether anyone have worked with this such feature or it's 
> just not-stable feature.
> If we do index same input, and different output,payload, then only one 
> result found.
>
> Do anyone tell me how could I fix it ?
>
>
>  -- 
 You received this message because you are subscribed to the Google 
 Groups "elasticsearch" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to elasticsearc...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/elasticsearch/f6547a58-c002-4ff3-80c9-2052e1d14ddd%
 40googlegroups.com
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/b3bf74ad-c729-4e78-9ebd-364c6c000819%40googlegroups.com
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/3b03ab59-e642-42d8-ab11-86f4589d8bec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AutoCompletion Suggester - Duplicate record in suggestion return

2014-04-22 Thread Alexander Reelsen 
Hey

if you do regular updates on that index, you should not update down to one
single segment. Do you have an example, where the updates do not work as
expected?


--Alex


On Tue, Apr 22, 2014 at 10:51 AM, kidkid  wrote:

> Hey Alexander,
> Thanks for your reply.
> Currently I also manual do optimize by running optimize:
> host:9200/completion_index/_optimize?max_num_segments=1
> I think it's a work around solution. I would like to make it better.
>
> Sometime, I also have problem with update payload, when I change payload,
> the completion is not change too.
>
>
> On Monday, April 21, 2014 7:26:13 PM UTC+7, Alexander Reelsen wrote:
>
>> Hey,
>>
>> the output is used to unify the search results, otherwise the input is
>> used. The payload itself is just meta information.
>> The main reason, why you see the suggestion twice is, that even though a
>> document is deleted and cannot be found anymore, the suggest data
>> structures are only cleaned up during merges/optimizations. Running
>> optimize should fix this.
>>
>> Makes sense?
>>
>>
>> --Alex
>>
>>
>>
>> On Sun, Apr 13, 2014 at 12:49 PM, kidkid  wrote:
>>
>>> I have figure out the problem.
>>> The main problem is I have used the same output for all input then ES
>>> have been wrong in this case.
>>>
>>> I still trying to improve the performance. I am just test on 64Gb Ram
>>> server (32Gb for ES 1.0.1) 24 core.
>>> Have only 2 record but it took me 3ms to suggest.
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sunday, April 13, 2014 4:53:21 PM UTC+7, kidkid wrote:

 There are something really strange.
 I don't know whether anyone have worked with this such feature or it's
 just not-stable feature.
 If we do index same input, and different output,payload, then only one
 result found.

 Do anyone tell me how could I fix it ?


  --
>>> You received this message because you are subscribed to the Google
>>> Groups "elasticsearch" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to elasticsearc...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/elasticsearch/f6547a58-c002-4ff3-80c9-2052e1d14ddd%
>>> 40googlegroups.com
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/b3bf74ad-c729-4e78-9ebd-364c6c000819%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAGCwEM8RaaN69kcBQTTbkXfV7RL8fkR0Y8PAuK7jR-Jdma3VGw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AutoCompletion Suggester - Duplicate record in suggestion return

2014-04-22 Thread kidkid 
Hey Alexander,
Thanks for your reply.
Currently I also manual do optimize by running optimize: 
host:9200/completion_index/_optimize?max_num_segments=1 
I think it's a work around solution. I would like to make it better.

Sometime, I also have problem with update payload, when I change payload, 
the completion is not change too.


On Monday, April 21, 2014 7:26:13 PM UTC+7, Alexander Reelsen wrote:
>
> Hey,
>
> the output is used to unify the search results, otherwise the input is 
> used. The payload itself is just meta information.
> The main reason, why you see the suggestion twice is, that even though a 
> document is deleted and cannot be found anymore, the suggest data 
> structures are only cleaned up during merges/optimizations. Running 
> optimize should fix this.
>
> Makes sense?
>
>
> --Alex
>
>
>
> On Sun, Apr 13, 2014 at 12:49 PM, kidkid  >wrote:
>
>> I have figure out the problem.
>> The main problem is I have used the same output for all input then ES 
>> have been wrong in this case.
>>
>> I still trying to improve the performance. I am just test on 64Gb Ram 
>> server (32Gb for ES 1.0.1) 24 core.
>> Have only 2 record but it took me 3ms to suggest.
>>
>>
>>
>>
>>
>>
>> On Sunday, April 13, 2014 4:53:21 PM UTC+7, kidkid wrote:
>>>
>>> There are something really strange.
>>> I don't know whether anyone have worked with this such feature or it's 
>>> just not-stable feature.
>>> If we do index same input, and different output,payload, then only one 
>>> result found.
>>>
>>> Do anyone tell me how could I fix it ?
>>>
>>>
>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/f6547a58-c002-4ff3-80c9-2052e1d14ddd%40googlegroups.com
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/b3bf74ad-c729-4e78-9ebd-364c6c000819%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AutoCompletion Suggester - Duplicate record in suggestion return

2014-04-21 Thread Alexander Reelsen 
Hey,

the output is used to unify the search results, otherwise the input is
used. The payload itself is just meta information.
The main reason, why you see the suggestion twice is, that even though a
document is deleted and cannot be found anymore, the suggest data
structures are only cleaned up during merges/optimizations. Running
optimize should fix this.

Makes sense?


--Alex



On Sun, Apr 13, 2014 at 12:49 PM, kidkid  wrote:

> I have figure out the problem.
> The main problem is I have used the same output for all input then ES have
> been wrong in this case.
>
> I still trying to improve the performance. I am just test on 64Gb Ram
> server (32Gb for ES 1.0.1) 24 core.
> Have only 2 record but it took me 3ms to suggest.
>
>
>
>
>
>
> On Sunday, April 13, 2014 4:53:21 PM UTC+7, kidkid wrote:
>>
>> There are something really strange.
>> I don't know whether anyone have worked with this such feature or it's
>> just not-stable feature.
>> If we do index same input, and different output,payload, then only one
>> result found.
>>
>> Do anyone tell me how could I fix it ?
>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/f6547a58-c002-4ff3-80c9-2052e1d14ddd%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAGCwEM-yu%3DzB0Zf4Ra%3DAJTz0uUkR4ASGeBDkkdFaDKYmP9VCTQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AutoCompletion Suggester - Duplicate record in suggestion return

2014-04-13 Thread kidkid 
I have figure out the problem.
The main problem is I have used the same output for all input then ES have 
been wrong in this case.

I still trying to improve the performance. I am just test on 64Gb Ram 
server (32Gb for ES 1.0.1) 24 core.
Have only 2 record but it took me 3ms to suggest.





On Sunday, April 13, 2014 4:53:21 PM UTC+7, kidkid wrote:
>
> There are something really strange.
> I don't know whether anyone have worked with this such feature or it's 
> just not-stable feature.
> If we do index same input, and different output,payload, then only one 
> result found.
>
> Do anyone tell me how could I fix it ?
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/f6547a58-c002-4ff3-80c9-2052e1d14ddd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AutoCompletion Suggester - Duplicate record in suggestion return

2014-04-13 Thread kidkid 
There are something really strange.
I don't know whether anyone have worked with this such feature or it's just 
not-stable feature.
If we do index same input, and different output,payload, then only one 
result found.

Do anyone tell me how could I fix it ?


-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/f5518627-f29d-4864-9b9f-003675e257ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AutoCompletion Suggester - Duplicate record in suggestion return

2014-04-11 Thread kidkid 
Hi,
It's really fun because when I added output field it work like a charm.
Completion is built in FST, so how could "output" field affect the result ? 

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/7f98b542-e862-4654-bed7-a31c297d795d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.