When i do a search query using http://***...:9200/tournament/master/_search?q=995
i get multiple results(not sure why). The result(s) i get are:
* _index: "tournament"
* _type: "master"
* _id: "995"
*
-
_source: {
o tournamentid: 995
o startdate: "2010-07-19T18:30:00.000Z"
o enddate: "2010-07-22T18:30:00.000Z"
o initiator: "system-gen"
o largeimage: 1735
o thumbimage: 1130
o gamename: "Avoid Responsibility"
o gamedescription: "
It's your chance to keep the responsibilities at bay.This is
your destiny
"
}
And when i do a refresh i get:
* _index: "tournament"
* _type: "master"
* _id: "995"
*
-
_source: {
o tournamentid: 995
startdate: "2010-07-20T07:35:00.000Z"
enddate: "2010-07-23T07:35:00.000Z"
o initiator: "system-gen"
o largeimage: 1735
o thumbimage: 1130
o gamename: "Avoid Responsibility"
o gamedescription: "<body> <p><font face="Tahoma"
size="1">It's your chance to keep the responsibilities at bay.This is
your destiny
elasticsearch results are near real time, not full real time, this means
that if you update a document with the same id, that update will only be
"visible" after a certain period (or once you call refresh, which is an
expensive operations potentially, should not be called for every request).
When i do a search query using http:// ..*.**:9200/tournament/master/_search?q=995
i get multiple results(not sure why). The result(s) i get are:
_index: "tournament"
_type: "master"
_id: "995"
_source: {
o tournamentid: 995
o startdate: "2010-07-19T18:30:00.000Z"
o enddate: "2010-07-22T18:30:00.000Z"
o initiator: "system-gen"
o largeimage: 1735
o thumbimage: 1130
o gamename: "Avoid Responsibility"
o gamedescription: "
It's your chance to keep the responsibilities at bay.This is
your destiny
"
}
And when i do a refresh i get:
_index: "tournament"
_type: "master"
_id: "995"
_source: {
o tournamentid: 995
startdate: "2010-07-20T07:35:00.000Z"
enddate: "2010-07-23T07:35:00.000Z"
o initiator: "system-gen"
o largeimage: 1735
o thumbimage: 1130
o gamename: "Avoid Responsibility"
o gamedescription: "
It's your chance to keep the responsibilities at bay.This is
your destiny
Curious, how about if
org.elasticsearch.action.index.IndexRequest#operationThreaded(..) is set to
'true', will it assure that after
org.elasticsearch.action.ActionFuture#actionGet() finishes execution that
the index will be updated already?
elasticsearch results are near real time, not full real time, this means
that if you update a document with the same id, that update will only be
"visible" after a certain period (or once you call refresh, which is an
expensive operations potentially, should not be called for every request).
When i do a search query using http:// ..*.**:9200/tournament/master/_search?q=995
i get multiple results(not sure why). The result(s) i get are:
_index: "tournament"
_type: "master"
_id: "995"
_source: {
o tournamentid: 995
o startdate: "2010-07-19T18:30:00.000Z"
o enddate: "2010-07-22T18:30:00.000Z"
o initiator: "system-gen"
o largeimage: 1735
o thumbimage: 1130
o gamename: "Avoid Responsibility"
o gamedescription: "
It's your chance to keep the responsibilities at bay.This is
your destiny
"
}
And when i do a refresh i get:
_index: "tournament"
_type: "master"
_id: "995"
_source: {
o tournamentid: 995
startdate: "2010-07-20T07:35:00.000Z"
enddate: "2010-07-23T07:35:00.000Z"
o initiator: "system-gen"
o largeimage: 1735
o thumbimage: 1130
o gamename: "Avoid Responsibility"
o gamedescription: "
It's your chance to keep the responsibilities at bay.This is
your destiny
Thanks for your reply. The document was updated some 3 hrs before i checked
for this behavior. The strange thing here is when i refresh the page
continuously(say 5 times) the data remains constant, but when i come back
and refresh the page the date record changes again.
elasticsearch results are near real time, not full real time, this means
that if you update a document with the same id, that update will only be
"visible" after a certain period (or once you call refresh, which is an
expensive operations potentially, should not be called for every request).
When i do a search query using http:// ..*.**:9200/tournament/master/_search?q=995
i get multiple results(not sure why). The result(s) i get are:
_index: "tournament"
_type: "master"
_id: "995"
_source: {
o tournamentid: 995
o startdate: "2010-07-19T18:30:00.000Z"
o enddate: "2010-07-22T18:30:00.000Z"
o initiator: "system-gen"
o largeimage: 1735
o thumbimage: 1130
o gamename: "Avoid Responsibility"
o gamedescription: "
It's your chance to keep the responsibilities at bay.This is
your destiny
"
}
And when i do a refresh i get:
_index: "tournament"
_type: "master"
_id: "995"
_source: {
o tournamentid: 995
startdate: "2010-07-20T07:35:00.000Z"
enddate: "2010-07-23T07:35:00.000Z"
o initiator: "system-gen"
o largeimage: 1735
o thumbimage: 1130
o gamename: "Avoid Responsibility"
o gamedescription: "
It's your chance to keep the responsibilities at bay.This is
your destiny
Maybe its caching done on the client side? Do you use the REST API using
javascript? Maybe I should add a no cache header or something to the
response.
Thanks for your reply. The document was updated some 3 hrs before i checked
for this behavior. The strange thing here is when i refresh the page
continuously(say 5 times) the data remains constant, but when i come back
and refresh the page the date record changes again.
elasticsearch results are near real time, not full real time, this means
that if you update a document with the same id, that update will only be
"visible" after a certain period (or once you call refresh, which is an
expensive operations potentially, should not be called for every request).
When i do a search query using http:// ..*.**:9200/tournament/master/_search?q=995
i get multiple results(not sure why). The result(s) i get are:
_index: "tournament"
_type: "master"
_id: "995"
_source: {
o tournamentid: 995
o startdate: "2010-07-19T18:30:00.000Z"
o enddate: "2010-07-22T18:30:00.000Z"
o initiator: "system-gen"
o largeimage: 1735
o thumbimage: 1130
o gamename: "Avoid Responsibility"
o gamedescription: "
It's your chance to keep the responsibilities at bay.This is
your destiny
"
}
And when i do a refresh i get:
_index: "tournament"
_type: "master"
_id: "995"
_source: {
o tournamentid: 995
startdate: "2010-07-20T07:35:00.000Z"
enddate: "2010-07-23T07:35:00.000Z"
o initiator: "system-gen"
o largeimage: 1735
o thumbimage: 1130
o gamename: "Avoid Responsibility"
o gamedescription: "
It's your chance to keep the responsibilities at bay.This is
your destiny
We are not doing anything client side. What we are doing is a bulk update of
data from MySql to Elasticsearch. Do i need to take care of anything while
i do bulk updates?. Is it due to data getting replicating in multiple
shards() and maybe the shards have different data in them?. My schema for
shards look like this:
Maybe its caching done on the client side? Do you use the REST API using
javascript? Maybe I should add a no cache header or something to the
response.
Thanks for your reply. The document was updated some 3 hrs before i
checked for this behavior. The strange thing here is when i refresh the page
continuously(say 5 times) the data remains constant, but when i come back
and refresh the page the date record changes again.
elasticsearch results are near real time, not full real time, this means
that if you update a document with the same id, that update will only be
"visible" after a certain period (or once you call refresh, which is an
expensive operations potentially, should not be called for every request).
When i do a search query using http:// ..*.**:9200/tournament/master/_search?q=995
i get multiple results(not sure why). The result(s) i get are:
_index: "tournament"
_type: "master"
_id: "995"
_source: {
o tournamentid: 995
o startdate: "2010-07-19T18:30:00.000Z"
o enddate: "2010-07-22T18:30:00.000Z"
o initiator: "system-gen"
o largeimage: 1735
o thumbimage: 1130
o gamename: "Avoid Responsibility"
o gamedescription: "
It's your chance to keep the responsibilities at bay.This is
your destiny
"
}
And when i do a refresh i get:
_index: "tournament"
_type: "master"
_id: "995"
_source: {
o tournamentid: 995
startdate: "2010-07-20T07:35:00.000Z"
enddate: "2010-07-23T07:35:00.000Z"
o initiator: "system-gen"
o largeimage: 1735
o thumbimage: 1130
o gamename: "Avoid Responsibility"
o gamedescription: "
It's your chance to keep the responsibilities at bay.This is
your destiny
We are not doing anything client side. What we are doing is a bulk update
of data from MySql to Elasticsearch. Do i need to take care of anything
while i do bulk updates?. Is it due to data getting replicating in multiple
shards() and maybe the shards have different data in them?. My schema for
shards look like this:
Maybe its caching done on the client side? Do you use the REST API using
javascript? Maybe I should add a no cache header or something to the
response.
Thanks for your reply. The document was updated some 3 hrs before i
checked for this behavior. The strange thing here is when i refresh the page
continuously(say 5 times) the data remains constant, but when i come back
and refresh the page the date record changes again.
elasticsearch results are near real time, not full real time, this means
that if you update a document with the same id, that update will only be
"visible" after a certain period (or once you call refresh, which is an
expensive operations potentially, should not be called for every request).
When i do a search query using http:// ..*.**:9200/tournament/master/_search?q=995
i get multiple results(not sure why). The result(s) i get are:
_index: "tournament"
_type: "master"
_id: "995"
_source: {
o tournamentid: 995
o startdate: "2010-07-19T18:30:00.000Z"
o enddate: "2010-07-22T18:30:00.000Z"
o initiator: "system-gen"
o largeimage: 1735
o thumbimage: 1130
o gamename: "Avoid Responsibility"
o gamedescription: "
It's your chance to keep the responsibilities at bay.This is
your destiny
"
}
And when i do a refresh i get:
_index: "tournament"
_type: "master"
_id: "995"
_source: {
o tournamentid: 995
startdate: "2010-07-20T07:35:00.000Z"
enddate: "2010-07-23T07:35:00.000Z"
o initiator: "system-gen"
o largeimage: 1735
o thumbimage: 1130
o gamename: "Avoid Responsibility"
o gamedescription: "
It's your chance to keep the responsibilities at bay.This is
your destiny
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.