I'm using the completion feature on 0.90.9. I've a document which I index
with multiple inputs and suggest based search works ok. Then I deleted that
doc and re-create it with different inputs, and it still being returned
with the first search I did, although I examined the doc (head plugin) and
the input field is indeed updated, which does not match that search. Any
flush need to issued after updates? Does the suggest API explains the
results?
I'm using the completion feature on 0.90.9. I've a document which I index
with multiple inputs and suggest based search works ok. Then I deleted that
doc and re-create it with different inputs, and it still being returned
with the first search I did, although I examined the doc (head plugin) and
the input field is indeed updated, which does not match that search. Any
flush need to issued after updates? Does the suggest API explains the
results?
Did that, still returns the incorrect results. Just to be sure, I even
changed the output field, and again - although seen when I examine the doc
(head plugin), the api ( REST and JAVA concreteOption.getText().toString()
) returns the old name. Is it possible to delete the data structure
directly from the fs?
On Monday, January 27, 2014 3:58:08 PM UTC+2, Alexander Reelsen wrote:
Hey,
can you try running an optimize with expunge deletes set?
On Mon, Jan 27, 2014 at 2:22 PM, barak <barak...@gmail.com <javascript:>>wrote:
Hi,
I'm using the completion feature on 0.90.9. I've a document which I index
with multiple inputs and suggest based search works ok. Then I deleted that
doc and re-create it with different inputs, and it still being returned
with the first search I did, although I examined the doc (head plugin) and
the input field is indeed updated, which does not match that search. Any
flush need to issued after updates? Does the suggest API explains the
results?
So not a clue? I've opened an issue for that on github, but I guess it
might takes some time... Any workaround I can use?
On Monday, January 27, 2014 4:13:58 PM UTC+2, barak wrote:
Did that, still returns the incorrect results. Just to be sure, I even
changed the output field, and again - although seen when I examine the doc
(head plugin), the api ( REST and JAVA concreteOption.getText().toString()
) returns the old name. Is it possible to delete the data structure
directly from the fs?
On Monday, January 27, 2014 3:58:08 PM UTC+2, Alexander Reelsen wrote:
Hey,
can you try running an optimize with expunge deletes set?
I'm using the completion feature on 0.90.9. I've a document which I
index with multiple inputs and suggest based search works ok. Then I
deleted that doc and re-create it with different inputs, and it still being
returned with the first search I did, although I examined the doc (head
plugin) and the input field is indeed updated, which does not match that
search. Any flush need to issued after updates? Does the suggest API
explains the results?
I did some tests and the only thing I could come up with, is that if you
delete a document, but do not run optimize, you will get old data back. If
you index the new document, but you do not refresh after indexing it, you
will get back the old result until the next automatic refresh happened.
So not a clue? I've opened an issue for that on github, but I guess it
might takes some time... Any workaround I can use?
On Monday, January 27, 2014 4:13:58 PM UTC+2, barak wrote:
Did that, still returns the incorrect results. Just to be sure, I even
changed the output field, and again - although seen when I examine the doc
(head plugin), the api ( REST and JAVA concreteOption.getText().toString()
) returns the old name. Is it possible to delete the data structure
directly from the fs?
On Monday, January 27, 2014 3:58:08 PM UTC+2, Alexander Reelsen wrote:
Hey,
can you try running an optimize with expunge deletes set?
I'm using the completion feature on 0.90.9. I've a document which I
index with multiple inputs and suggest based search works ok. Then I
deleted that doc and re-create it with different inputs, and it still being
returned with the first search I did, although I examined the doc (head
plugin) and the input field is indeed updated, which does not match that
search. Any flush need to issued after updates? Does the suggest API
explains the results?
The very odd thing is that I just tried running these use cases with the
hotels example and it works perfect! So apparently there is no bug on ES
side, so I guess I did things wrong. With that in mind, are there some logs
I can activate to find out why those docs returned although not matching
the inputs?Also tried refresh, optimize, etc. I guess deleting all data and
starting all over again will solve it, I just want to find out what I did
wrong so I'll try to avoid it in the future...
Thanks.
On Tuesday, January 28, 2014 10:43:54 AM UTC+2, Alexander Reelsen wrote:
I did some tests and the only thing I could come up with, is that if you
delete a document, but do not run optimize, you will get old data back. If
you index the new document, but you do not refresh after indexing it, you
will get back the old result until the next automatic refresh happened.
--Alex
--Alex
On Mon, Jan 27, 2014 at 8:44 PM, barak <barak...@gmail.com <javascript:>>wrote:
So not a clue? I've opened an issue for that on github, but I guess it
might takes some time... Any workaround I can use?
On Monday, January 27, 2014 4:13:58 PM UTC+2, barak wrote:
Did that, still returns the incorrect results. Just to be sure, I even
changed the output field, and again - although seen when I examine the doc
(head plugin), the api ( REST and JAVA concreteOption.getText().toString()
) returns the old name. Is it possible to delete the data structure
directly from the fs?
On Monday, January 27, 2014 3:58:08 PM UTC+2, Alexander Reelsen wrote:
Hey,
can you try running an optimize with expunge deletes set?
I'm using the completion feature on 0.90.9. I've a document which I
index with multiple inputs and suggest based search works ok. Then I
deleted that doc and re-create it with different inputs, and it still being
returned with the first search I did, although I examined the doc (head
plugin) and the input field is indeed updated, which does not match that
search. Any flush need to issued after updates? Does the suggest API
explains the results?
nothing, which comes to my mind now. If you manage to reproduce it, please
dont hesitate to create a github issue though in order to track it down.
Thanks!
The very odd thing is that I just tried running these use cases with the
hotels example and it works perfect! So apparently there is no bug on ES
side, so I guess I did things wrong. With that in mind, are there some logs
I can activate to find out why those docs returned although not matching
the inputs?Also tried refresh, optimize, etc. I guess deleting all data and
starting all over again will solve it, I just want to find out what I did
wrong so I'll try to avoid it in the future...
Thanks.
On Tuesday, January 28, 2014 10:43:54 AM UTC+2, Alexander Reelsen wrote:
I did some tests and the only thing I could come up with, is that if you
delete a document, but do not run optimize, you will get old data back. If
you index the new document, but you do not refresh after indexing it, you
will get back the old result until the next automatic refresh happened.
So not a clue? I've opened an issue for that on github, but I guess it
might takes some time... Any workaround I can use?
On Monday, January 27, 2014 4:13:58 PM UTC+2, barak wrote:
Did that, still returns the incorrect results. Just to be sure, I even
changed the output field, and again - although seen when I examine the doc
(head plugin), the api ( REST and JAVA concreteOption.getText().toString()
) returns the old name. Is it possible to delete the data structure
directly from the fs?
On Monday, January 27, 2014 3:58:08 PM UTC+2, Alexander Reelsen wrote:
Hey,
can you try running an optimize with expunge deletes set?
I'm using the completion feature on 0.90.9. I've a document which I
index with multiple inputs and suggest based search works ok. Then I
deleted that doc and re-create it with different inputs, and it still being
returned with the first search I did, although I examined the doc (head
plugin) and the input field is indeed updated, which does not match that
search. Any flush need to issued after updates? Does the suggest API
explains the results?
--
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/13ab2569-038a-4b68-a252-d8ade2c9ca2d% 40googlegroups.com.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
