As we already informed, for various security reasons, the dynamic scripting was disabled with the release of Elasticsearch 1.2.0. This means that you couldn’t modify scripts on-the-fly. That changed with the recent release of Elasticsearch 1.3.0.
The enter the competition, please write a comment or mail (blog(at)elasticsearchserverbook(dot)com) describing unusual usage of one of Elasticsearch features or just describe how you are using Elasticsearch or how you will use it.
The contents will be active from today (8th of June 2014) till (22th of June 2014). The winners (two persons) will be chosen randomly from the mails and comments that we will receive during the two weeks period.
Update: Please note that the winners will be contacted by mail, so please include an e-mail address under you can be reached.
Note: The contest is now over and the winners – Eyal and Jorge will be contacted by mail – congratulations
We wanted to share the information, that our first Elasticsearch book – the ElasticSearch Server was translated to Japanese and should be now available. Information about the book can be found at ASCII Index and the book can be purchased on Japanese Amazon site.
We would like to thank all the people who were involved in the translation process. Especially we would like to thank Jun Ohtani (@johtani, blog.johtani.info) who were in touch with us, submitted many corrections to the book (please see errata) and had to work with us Once again, thank you all!
The Mastering ElasticSearch book that was published in December 2013 included a chapter dedicated to improving user search experience. However, one of the topics didn’t made it into the book. Because of that we wanted to share this section of the book on the blog. We hope that you’ll find it useful.
Our publisher Packt Publishing is offering its ebooks and videos just for $5 till 3rd of January 2014 as the eBook Bonanza promotion. If you wanted to buy something published by Packt, like our ElasticSearch Server, Mastering ElasticSearch, Apache 4 Cookbook or Solr 3.1 Cookbook please go https://www.packtpub.com/ebookbonanza.
Its a nice promotion if you hesitated to buy any of the books from Packt Publishing, but remember that it end on 3rd of January, so not much time left.
Packt Publishing is giving everyone the chance to explore its entire catalog of eBooks and videos at 50% off in its biggest ever sale. During the event, anyone will be able to use the discount code COL50 at checkout for any eBooks or videos of their choice – as many times as they like until Thursday, 17th-Oct-2013. This is a great opportunity to buy both ElasticSearch Server and Mastering ElasticSearch books.
If you are interested please head to Packt Publishing home page, at https://www.packtpub.com/.
The Mastering ElasticSearch book that is going to be published in December 2013 (probable date, but may be available earlier) will include a chapter that is dedicated to extending ElasticSearch. However, one of the topics – the simplest one didn’t made it into the book. Because of that we wanted to share this section of the book on the blog. We hope that you’ll find it useful.
Till now, we didn’t talk about shard allocation process or ability to move shards around the cluster. If you recall what shard allocation is – the process of allocating shards to nodes which can happen during initial cluster start, during replicas allocation or when nodes are being removed or added to the cluster. However apart from the allocation mechanism control, sometimes it is crucial to be able to cancel shard allocation or move shards around inside the cluster. In order to do that ElasticSearch exposes the reroute API, which allows us to move shards, cancel their allocation and finally force the allocation. You can imagine a situation when you would like to take off a single node from your cluster for maintenance, but you have data on it and first you want to somehow move the data to some other node. This is where the reroute API can come in handy. So now, let’s discuss all the possibilities that give us.
ElasticSearch is designed to work with indices that are built of multiple shards and replicas and you probably have such indices in your cluster. Sometimes it may be handy to see which shard will the query be exectued at. Before ElasticSearch 0.90 you could run a query and check the stats to see that, but now we can use the Search Shards API. Let’s look on how we can use this API by using a simple example and queries that does and doesn’t use routing.