Thank you for quick answer.
I set "index.store.type" to "memory" in context of whole node and
additionally during creation of particular index.
And the problem is that directories are still created, and they
contain files translog-* and node.lock.
Is there a possibility to disable creation of those files also?
I set also "gateway.type" to "none" and sometimes despite of this
setting (and index.store.type=memory) I have an exception:
org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [1/
not recovered from gateway];
On Dec 15, 5:06 am, Shay Banon shay.ba...@elasticsearch.com wrote:
In general, to further configure ES when embedded in Java App is either by passing settings programmatically to the NodeBuilder, or having an elasticsearch.(yml|json) configuration within the classpath under / or /config.
In order to change the data directory location, set the
path.data setting to the location you want it to be stored at.
In order to have the index be stored in memory (and not survive restarts), set
You can define template mappings.
On Tuesday, December 14, 2010 at 6:05 PM, Wojciech Durczyński wrote:
I'm using Elastic Search Java API so that Elastic Search nodes can be
embedded in my application.
And I have some questions:
- How to change default data directory, where node stores its data?
It is always created in current working directory as "data". Is there
a setting to control this behaviour?
- How to disable gateway/translogs/data storing completely (using
java API), so that Elastic Search won't create any directories on hard
drive and keep everything in memory only?
- Is there a possibility of defining recursive data mapping? I'd like
to store in index an object, which can contain other objects of the
same type as properties, and they also can contain these objects as