6. Improving the Search Experience | ElasticSearch Blueprints

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

ElasticSearch Blueprints

By : Mohan

3 (2)

ElasticSearch Blueprints

3 (2)

By: Mohan

Overview of this book

If you are a data enthusiast and would like to explore and specialize on search technologies based on Elasticsearch, this is the right book for you. A compelling case-to-case mapping of features and implementation of Elasticsearch to solve many real-world use cases makes this book the right choice to start and specialize on Elasticsearch.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Google-like Web Search

1. Google-like Web Search

Deploying Elasticsearch

Communicating with the Elasticsearch server

Setting the analyzer

Using phrase query to search

Using the highlighting feature

Pagination

Summary

2. Building Your Own E-Commerce Solution

2. Building Your Own E-Commerce Solution

Data modeling in Elasticsearch

Choosing between a query and a filter

Searching your documents

Aggregating your results

Filter your results based on a date range

Implementing a prize range filter

Implementing a category filter

Implementation of filters in Elasticsearch

Searching with multiple conditions

Sorting results

Using the scroll API for consistent pagination

Autocomplete in Elasticsearch

Hotel suggester using autocomplete

Summary

3. Relevancy and Scoring

3. Relevancy and Scoring

How scoring works

The Ebola outbreak

Summary

4. Managing Relational Content

4. Managing Relational Content

The product-with-tags search problem

Nested types to the rescue

Limitations on a query on nested fields

Using a parent-child approach

Schema design to store questions and answers

Searching questions based on a criteria of answers

Searching answers based on a criteria of questions

The score of questions based on the score of each answer

Filtering questions with more than four answers

Summary

5. Analytics Using Elasticsearch

5. Analytics Using Elasticsearch

A flight ticket analytics scenario

Summary

6. Improving the Search Experience

6. Improving the Search Experience

News search

A case-insensitive search

Effective e-mail or URL link search inside text

Prioritizing a title match over content match

Terms aggregation giving weird results

Using a lowercased analyzer

Improving the search experience using stemming

A synonym-aware search

The holy box of search

Boolean operations

Words with similar sounds

Substring matching

Summary

7. Spicing Up a Search Using Geo

7. Spicing Up a Search Using Geo

Restaurant search

Data modeling for restaurants

The nearest hotel problem

The maximum distance covered

Inside the city limits

Distance values between the current point and each restaurant

Restaurant categorization based on distance

Aggregating restaurants based on their nearness

Summary

8. Handling Time-based Data

8. Handling Time-based Data

Overriding default mapping and settings in Elasticsearch

Index template creation

Searching for time-based data

Archiving time-based data

Closing older indices

Snapshot creation

Restoring a snapshot

Restoring multiple indices

The curator

Shard allocation using curator

Optimization

Summary

Index

Index

Customer Reviews

3 (2)

5 star

50%

4 star

0%

3 star

0%

2 star

0%

1 star

50%

Effective e-mail or URL link search inside text

Let's search in the content field of the documents that we have for the e-mail address <[email protected]>:

{
  "query" : {
    "match" : {
      "content" : "[email protected]"
      }
    }
}

Incidentally, Document 1 and Document 2 matched our query rather than just Document 1.

Let's see why this happened and how:

By default, the standard analyzer is taken as the default analyzer
The standard analyzer breaks <[email protected]> into malhotra and gmail.com
The standard analyzer also breaks the e-mail ID <[email protected]> into buygroceries and gmail.com
This means that when we search for the e-mail ID <[email protected]>, either malhotra or gmail.com needs to match for the document to be qualified as a result

Hence, both Document 1 and Document 2 matched our query rather than just Document 1.

The solution for this problem is to use the UAX Email URL tokenizer rather than the default tokenizer. This tokenizer preserves...

Visually different images

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

ElasticSearch Blueprints

Search

Your notes and bookmarks