Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Realtime GET #1060

Closed
kimchy opened this issue Jun 24, 2011 · 9 comments
Closed

Realtime GET #1060

kimchy opened this issue Jun 24, 2011 · 9 comments

Comments

@kimchy
Copy link
Member

kimchy commented Jun 24, 2011

Realtime GET support allows to get a document once indexed regardless of the "refresh rate" of the index. It is enabled by default.

In order to disable realtime GET, one can either set realtime parameter to false, or globally default it to by setting the action.get.realtime to false in the node configuration.

Realtime GET and stored fields

When getting a document, one can specify fields to fetch from it. They will, when possible, be fetched as stored fields (fields mapped as stored in the mapping). When using realtime GET, there is no notion of stored fields (at least for a period of time, basically, until the next flush), so they will be extracted from the source itself (note, even if source is not enabled). It is a good practice to assume that the fields will be loaded from source when using realtime GET, even if the fields are stored.

@kimchy kimchy closed this as completed in 72ee0aa Jun 24, 2011
@jordansissel
Copy link
Contributor

Dude. Awesome.

@stephanebastian
Copy link

+1. I'll definitely give it a spin today
Thanks Shay.

@mahendra
Copy link
Contributor

Definitely, ES is getting more closer to CouchDB :-)

@kimchy
Copy link
Member Author

kimchy commented Jun 24, 2011

@stephane-bastian cool, would love an early feedback on this

@aparo
Copy link

aparo commented Jun 25, 2011

Kimchy this feature is fantastic, now we can use it as a better datastore.

@talsalmona
Copy link

Great!

@oravecz
Copy link

oravecz commented Jun 27, 2011

Does this mean a fetch by id will return this "soon to be indexed" document, or will it be part of any query result which includes the document?

@kimchy
Copy link
Member Author

kimchy commented Jun 27, 2011

When a document is indexed, its indexed, its not "soon to be indexed". When it becomes visible for search is the question (and thats the async refresh). Fetch by Id will work even if it has not been refreshed yet.

@stephanebastian
Copy link

Hi Shay,
Unfortunately I got sidetracked by some higher priority tasks. Things are settling down and I hope to test the RT get feature today or tomorrow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants