Completion - updated inputs are not reflected


(Barak Yaish) #1

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?

Thanks.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/741ebbf0-2a9d-464c-8946-ca1d13da5ff3%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Alexander Reelsen) #2

Hey,

can you try running an optimize with expunge deletes set?

http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-optimize.html

curl -XPOST '
http://localhost:9200/twitter/_optimize?only_expunge_deletes=true'

--Alex

On Mon, Jan 27, 2014 at 2:22 PM, barak barak.yaish@gmail.com 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?

Thanks.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/741ebbf0-2a9d-464c-8946-ca1d13da5ff3%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGCwEM_-w8ZNu1gypgkr2QfcJ_BqmGBnnAAC2wXnU%2BxGUpdqxA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Barak Yaish) #3

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?

http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-optimize.html

curl -XPOST '
http://localhost:9200/twitter/_optimize?only_expunge_deletes=true'

--Alex

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?

Thanks.

--
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 <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/741ebbf0-2a9d-464c-8946-ca1d13da5ff3%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7b26fd66-0b77-478b-ac40-b9e40ddc651e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Barak Yaish) #4

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?

http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-optimize.html

curl -XPOST '
http://localhost:9200/twitter/_optimize?only_expunge_deletes=true'

--Alex

On Mon, Jan 27, 2014 at 2:22 PM, barak barak...@gmail.com 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?

Thanks.

--
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/741ebbf0-2a9d-464c-8946-ca1d13da5ff3%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/13ab2569-038a-4b68-a252-d8ade2c9ca2d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Alexander Reelsen) #5

Hey,

can you post a gist with a full reproduction? See
http://www.elasticsearch.org/help

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.yaish@gmail.com 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?

http://www.elasticsearch.org/guide/en/elasticsearch/
reference/current/indices-optimize.html

curl -XPOST 'http://localhost:9200/twitter/optimize?only
expunge_deletes=true'

--Alex

On Mon, Jan 27, 2014 at 2:22 PM, barak barak...@gmail.com 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?

Thanks.

--
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/741ebbf0-2a9d-464c-8946-ca1d13da5ff3%
40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/13ab2569-038a-4b68-a252-d8ade2c9ca2d%40googlegroups.com
.

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

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9KRgWbbvSWp54obYEz%3DgqAcKYzAAqbRu8DUui3FZ58Fw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Barak Yaish) #6

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... :slight_smile:

Thanks.

On Tuesday, January 28, 2014 10:43:54 AM UTC+2, Alexander Reelsen wrote:

Hey,

can you post a gist with a full reproduction? See
http://www.elasticsearch.org/help

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?

http://www.elasticsearch.org/guide/en/elasticsearch/
reference/current/indices-optimize.html

curl -XPOST 'http://localhost:9200/twitter/optimize?only
expunge_deletes=true'

--Alex

On Mon, Jan 27, 2014 at 2:22 PM, barak barak...@gmail.com 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?

Thanks.

--
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/741ebbf0-2a9d-464c-8946-ca1d13da5ff3%
40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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 <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/13ab2569-038a-4b68-a252-d8ade2c9ca2d%40googlegroups.com
.

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

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e107281e-809e-4b9b-bbc2-7c211991d514%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Alexander Reelsen) #7

Hey

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!

--Alex

On Tue, Jan 28, 2014 at 10:42 AM, barak barak.yaish@gmail.com wrote:

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... :slight_smile:

Thanks.

On Tuesday, January 28, 2014 10:43:54 AM UTC+2, Alexander Reelsen wrote:

Hey,

can you post a gist with a full reproduction? See
http://www.elasticsearch.org/help

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 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?

http://www.elasticsearch.org/guide/en/elasticsearch/referenc
e/current/indices-optimize.html

curl -XPOST 'http://localhost:9200/twitter/optimize?only_expunge
deletes=true'

--Alex

On Mon, Jan 27, 2014 at 2:22 PM, barak barak...@gmail.com 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?

Thanks.

--
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/741ebbf0-2a9d-464c-8946-ca1d13da5ff3%40goo
glegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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.

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

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/e107281e-809e-4b9b-bbc2-7c211991d514%40googlegroups.com
.

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

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGCwEM_M%2BpuvJr08Wjjd5p%2BUXV_Segkkvu324nfdrt74f%2BuGOw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #8