Win Elasticsearch Server second editon ebook

Send to Kindle

essb_secondWe would like to announce that Packt Publishing gave us the opportunity to give away two electronic copies of our newest book – the Elasticsearch Server second edition.

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.

Good luck 🙂

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 🙂

6 thoughts on “Win Elasticsearch Server second editon ebook

  1. Eyal Golan says:

    I created two cluster in different data-centers.
    The clusters are cloned (same data, indexes and shards).
    I created a wrapping (facade) client that can be initialized with as many clusters as one would want.

    We have full text search and some N:V pairs queries against our cluster.

    The clients can call any data-center and always have the same data for searching.

  2. I’m Research and Development Engineer Intern working on an E-commerce search engine. I’ve decided to adopt Elasticsearch instead of the usual relational database help optimize my product search engine.

    I have a small products database (around 20 million products). So I’m using Elasticsearch Scoring Functions to rank a products according to a query in the full text search feature using the BM25 similarity.

    I’m also using facets as for now to group my results according to brands, categories, etc.

    I’ll also be using the Aggregation features from Elasticsearch on top of a local machine learning module for better classification (categorization) of my database products.

  3. Coming over from Solr world and talking about missing functionality.

    I am pretty sure ElasticSearch does not have equivalents of UpdateRequestProcessors and custom chains.

  4. Evgeny says:

    In terms of unusual usage of Solr I think the most peculiar thing we’ve done at my company is putting XML files converted into JSON into a Solr field. The reason for that was that we were struggling with having Solr accept those XMLs properly so ended up adding an extra step of identifying each XML element and encoding it as JSON.
    I guess people here would mostly be sharing the smartest things they made Solr do for them, but hey – the content rules say “unusual”. 🙂

    Anyway, it’d be cool to learn what elastic search is all about and how it compares to Solr.

  5. We use elastic search to search our code base.

  6. Jorge Luis says:

    Building a custom web analytics platform, so no much of unusual usage of Elasticsearch. We are combining the power of aggregations, and more recently significant terms to deliver analytics about click streams in any website.

    Well, we’re doing even a little more about this because we are using elasticsearch also for monitoring, logstash to deliver logs and metrics and kibana for the UI (for now). With this we’re doing a couple of interesting things like correlating slow queries with network traffic and CPU/RAM usage. So we always know when the things are going slowly and why.

Leave a Reply