Put mapping documentation -- What options are available? Specifically, how to store a property but without indexing it?

Hello, The documentation at http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-put-mapping.html is a little sparse on details. Where can I find documentation for the options/parameters that put mapping takes? E.g. store, analyze, and just a list of what other

Re: Autocomplete for attachment field

Thanks for response. May this cause a problem while proceeding data for alternative field? Also the attachment field itself can't be copied, this action could be performed only for it's inner fields. When I am trying to set this mapping option it just disappears. So the initial question about

Re: Insert later feature

Also, if there are no other clients wanting a faster refresh, you can set index.refresh_interval to a higher value than the 1s default either in general for your index or just during the times when you're doing your bulk updates.

Re: Elasticsearch hadoop - java.lang.ClassCastException: org.apache.hadoop.io.IntWritable cannot be cast to org.apache.hadoop.io.Text

You're Hive mapping needs to match the Elasticsearch one - there's no type conversion applied between the two. The ClassCastException indicates that you are trying to write an INT (IntWritable) to a STRING (Text) - hence when you change your mapping to STRING, STRING things are working. I

Re: Insert later feature

Hello Michael - Thanks for the configuration. Hello Jörg - I was thinking more in lines of translog - http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-translog.html I believe the index operation is first written to translog ( Which i am not sure if is a part of

Re: Put mapping documentation -- What options are available? Specifically, how to store a property but without indexing it?

Are you looking for core types? http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html On Sunday, February 23, 2014 2:54:23 AM UTC-6, Daniel Winterstein wrote: Hello, The documentation at

Re: Problem with keeping in sync Elasticsearch across two data centers

I think with current ES version you have 3 options. - Use the great snapshot and restore feature to snapshot from a DC and restore in the other one - Index in both DC (so two distinct clusters) from a client level - Use Tribe node feature to search or index on multiple clusters Reference post

Re: Insert later feature

Yes, it is possible to disable the translog sync (the component where the operations are passed from ES to Lucene) with index.gateway.local.flush: -1 and use the flush action for manual commit instead. I have never done that practically, though. Jörg On Sun, Feb 23, 2014 at 5:42 PM, vineeth

Re: Insert later feature

Oops, the correct parameter is index.translog.disable_flush : true index.gateway.local.flush: -1 is controlling the gateway. Jörg On Sun, Feb 23, 2014 at 8:21 PM, joergpra...@gmail.com joergpra...@gmail.com wrote: Yes, it is possible to disable the translog sync (the component where the

Re: Insert later feature

Hello Joerg , So if i disable it , ES wont write the feeds to lucene until i make a manual flush... I believe translog is written to a file and its not resident in the memory. This also means that translogs are maintained between restarts and we will never loose data. If all the above are right

Re: Insert later feature

Hello Joerg , Your config doesnt seem to work. I gave the following parameter and while i was doing some inserts , there was no unusual behavior. The head showed the total number of documents i had inserted and it was searchable. index.translog.disable_flush : true ES version - 0.90.9 Is

Re: Insert later feature

Hi , I tried the below too without any luck - curl -XPUT 'localhost:9200/documents/_settings' -d '{ index : { translog : { disable_flush : true } } } ' Thanks Vineeth On Mon, Feb 24, 2014 at 1:42 AM, vineeth mohan vm.vineethmo...@gmail.comwrote: Hello Joerg , Your

Elasticsearch throws Could not reserve enough space for object heap

Hi guys, It seems that Elasticsearch stops working this morning. When i launch : sudo service elasticsearch start, it says : *Starting ElasticSearch Server Done* But when i check the status, it gives me : *elasticsearch is not running* I tried to launch it by the command :

Re: Elasticsearch throws Could not reserve enough space for object heap

What happen if you try 512m instead of 512 -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 23 févr. 2014 à 21:29, Mehdi medyo...@gmail.com a écrit : Hi guys, It seems that Elasticsearch stops working this morning. When i launch : sudo service elasticsearch start, it

Re: Insert later feature

It's not a dynamic setting, afaik. Sorry, I don't know for sure how a translog can grow forever. For my purposes, I decided to handle the challenge in front of ES, with better timing control, and archive files for replay I can use outside of ES too. Jörg On Sun, Feb 23, 2014 at 9:21 PM,

Re: Elasticsearch throws Could not reserve enough space for object heap

Same result, i tried also this command: *rcelasticsearch console* wrapper | Launching a JVM... wrapper | JVM exited while loading the application. jvm 1| Error occurred during initialization of VM jvm 1| Could not reserve enough space for object heap wrapper | Encountered an invalid

Indexing custom date format

All the out-of-the-box date formats are available here: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-date-format.html But other than preprocessing a custom date format before indexing the data, is there anything I can do on the mapping side to allow ES to process

Re: Indexing custom date format

My current mapping looks like: 'sale_date': { 'format': 'dateOptionalTime', 'type': 'date' } On Sunday, February 23, 2014 4:35:36 PM UTC-6, pulkitsinghal wrote: All the out-of-the-box date formats are available here:

Re: Elasticsearch throws Could not reserve enough space for object heap

Do you have already some indexed data? If so, may be 512m is not enough. It's a really low value. -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 23 févr. 2014 à 23:30, Mehdi medyo...@gmail.com a écrit : Same result, i tried also this command: rcelasticsearch console

Re: Elasticsearch throws Could not reserve enough space for object heap

Yes, Elasticsearch was deployed on the Vps 3 months ago, it worked perfectly, until today. VPS config : *512MB Ram, 20GB SSD Disk* Le dimanche 23 février 2014 22:45:05 UTC, David Pilato a écrit : Do you have already some indexed data? If so, may be 512m is not enough. It's a really low

Re: Elasticsearch throws Could not reserve enough space for object heap

Best practise is to use half of system ram for your heap, so ideally you should be setting it to 256mb. However you probably want to add more system RAM as you're hitting the limits with what you have. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: ma...@campaignmonitor.com

Re: Elasticsearch throws Could not reserve enough space for object heap

I tried low sizes : 256 and 128, it does not work. The vps is only used to host Ruby on rails Api for mobile apps (Ruby, Postgresql, Redis...) Le dimanche 23 février 2014 22:54:08 UTC, Mark Walkom a écrit : Best practise is to use half of system ram for your heap, so ideally you should be

Differences between an index and an alias which points to a single index

Hello, Say I have an index called duckling and an alias called duck which points to duckling and no other index. Except for creating an alias pointing to duck, all the other operations seem to route directly to duckling. Is that true? is there something besides creating an alias that I can do

Re: Optimizing configuration (Help me)

Sounds like you need more nodes, which isn't easy to work around. You can try increasing the RAM to 64GB and then assigning 32GB to ES, but above that and you start losing to GC. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: ma...@campaignmonitor.com web:

Re: Very high sys cpu usage with HTTP KeepAlive

All right. Thank you! -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Very-high-sys-cpu-usage-with-HTTP-KeepAlive-tp4049998p4050346.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- You received this message because you are

Search time field extraction

I am a newbie to ES/Kibana/logstash and still getting my feet wet. I could be missing something obvious but I haven't come across a way so far to extract a field at search time i.e., without setting up a grok{}/grep{}/similar filter in logstash. The grok{} filter is great for an event format

Re: Text Categorization in ES

Hi Hannes, Thanks for the info , also I came to know about lingo3G/Carrot Search. So whether that could also be a solution for that? -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Text-Categorization-in-ES-tp4050194p4050349.html Sent from the ElasticSearch

Re: Elasticsearch throws Could not reserve enough space for object heap

It can not work with less RAM. May be starting new nodes to have less shards per node could help but I'm guessing you don't want to do that. -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 24 févr. 2014 à 00:00, Mehdi medyo...@gmail.com a écrit : I tried low sizes : 256

Re: Count versus Search API

How does your count query look like? -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 24 févr. 2014 à 04:51, pulkitsinghal pulkitsing...@gmail.com a écrit : Hello, I have a bool query with a filter applied to it, which runs against the _search endpoint successfully

Re: Regex supported in index templates ?

Hi, Thanks for the reply. So incase if I am applying the simple matching pattern as * which will match all index, mapping will be created for indices which might not have that field in the future. Will there be any performance issue in those indices which have mapping but no data ? On

Re: Count versus Search API

I guess you are still on 0.90, where the count request is slightly different compared to a search request, as it contains the query without it being wrapped into the query object: { term : {field:value} } instead of { query : { term : {field:value} } } Beware that we

Re: Differences between an index and an alias which points to a single index

No limitations, as long as the alias points to a single index. If it pointed to multiple indices then you couldn't execute single index operations, like index etc. as it's not possible to identify which single index the operation is supposed to execute on. On Monday, February 24, 2014 12:03:08

Re: Alias across tribe node clusters?

You can read and write data using the tribe node, but you cannot execute master level write operations. Those are all the operations that modify the cluster state, something that's done only by the master node. As aliases are part of the cluster state, modifying them means modifying the cluster