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
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?
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
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
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
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
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,
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 zkid...@gmail.com wrote:
Hey Alexander,
Thanks for your reply.
Currently I also
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
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
Hi All,
I have problem with AutoCompletion Suggester.
When I index same word in record, AutoCompletion will return duplicate that
record,
Here is restful:
curl -X PUT 10.30.58.105:9200/completion
curl -X DELETE 10.30.58.105:9200/completion/song
curl -X PUT
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
12 matches
Mail list logo
