Elasticsearch Index Engine

Excerpt from the Elastic search API:
http://www.elasticsearch.org/guide/reference/api/admin-indices-refresh/

It says:

The refresh API allows to explicitly refresh one or more index, making all
operations performed since the last refresh available for search. The
(near) real-time capabilities depend on the index engine used. For example,
the robin one requires refresh to be called
, but by default a refresh is
scheduled periodically.

I wanted to ask that do we've any other index engine other than robin where
i can try out the refresh capabilities.

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.
For more options, visit https://groups.google.com/groups/opt_out.

ha! this brings back memories, whe ES was created the idea was that it would possibly have multiple engines in a similar manner to other systems. in practice, it ended up having a single implementation, called robin, which us e lucene NRT (near real time search) support, requiring to refresh an index in order to make the latest changes available for search (this is done automatically in ES by default every second)

On Fri, May 31, 2013 at 3:55 PM, Ankit Jain ankitjaincs06@gmail.com
wrote:

Excerpt from the Elastic search API:
http://www.elasticsearch.org/guide/reference/api/admin-indices-refresh/
It says:
The refresh API allows to explicitly refresh one or more index, making all
operations performed since the last refresh available for search. The
(near) real-time capabilities depend on the index engine used. For example,
the robin one requires refresh to be called
, but by default a refresh is
scheduled periodically.
I wanted to ask that do we've any other index engine other than robin where
i can try out the refresh capabilities.
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.
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.
For more options, visit https://groups.google.com/groups/opt_out.

Hi Kimchy,

Thanks for the reply.

If we will use memory store, then after how much time, the in memory data
is available for search?.

Also, after how much time, the data will be flushed into disk?.

Thanks,
Ankit

On Saturday, 1 June 2013 06:47:38 UTC+5:30, kimchy wrote:

ha! this brings back memories, whe ES was created the idea was that it
would possibly have multiple engines in a similar manner to other systems.
in practice, it ended up having a single implementation, called robin,
which us e lucene NRT (near real time search) support, requiring to refresh
an index in order to make the latest changes available for search (this is
done automatically in ES by default every second)

On Fri, May 31, 2013 at 3:55 PM, Ankit Jain <ankitj...@gmail.com<javascript:>

wrote:

Excerpt from the Elastic search API:
http://www.elasticsearch.org/guide/reference/api/admin-indices-refresh/

It says:

The refresh API allows to explicitly refresh one or more index, making
all operations performed since the last refresh available for search. The
(near) real-time capabilities depend on the index engine used. For example,
the robin one requires refresh to be called
, but by default a refresh
is scheduled periodically.

I wanted to ask that do we've any other index engine other than robin
where i can try out the refresh capabilities.

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:>.
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.
For more options, visit https://groups.google.com/groups/opt_out.