ElasticSearch Cookbook

Book Image

ElasticSearch Cookbook

By : Alberto Paro

Book Image

ElasticSearch Cookbook

By: Alberto Paro

Overview of this book

ElasticSearch is one of the most promising NoSQL technologies available and is built to provide a scalable search solution with built-in support for near real-time search and multi-tenancy. This practical guide is a complete reference for using ElasticSearch and covers 360 degrees of the ElasticSearch ecosystem. We will get started by showing you how to choose the correct transport layer, communicate with the server, and create custom internal actions for boosting tailored needs. Starting with the basics of the ElasticSearch architecture and how to efficiently index, search, and execute analytics on it, you will learn how to extend ElasticSearch by scripting and monitoring its behaviour. Step-by-step, this book will help you to improve your ability to manage data in indexing with more tailored mappings, along with searching and executing analytics with facets. The topics explored in the book also cover how to integrate ElasticSearch with Python and Java applications. This comprehensive guide will allow you to master storing, searching, and analyzing data with ElasticSearch.

ElasticSearch Cookbook

ElasticSearch Cookbook

Credits

About the Author

About the Author

About the Reviewers

About the Reviewers

www.PacktPub.com

www.PacktPub.com

Preface

Free Chapter

Getting Started

Getting Started

Understanding node and cluster

Understanding node services

Managing your data

Understanding cluster, replication, and sharding

Communicating with ElasticSearch

Using the HTTP protocol

Using the Native protocol

Using the Thrift protocol

Downloading and Setting Up ElasticSearch

Downloading and Setting Up ElasticSearch

Downloading and installing ElasticSearch

Networking setup

Setting up a node

Setting up ElasticSearch for Linux systems (advanced)

Setting up different node types (advanced)

Installing a plugin

Installing a plugin manually

Removing a plugin

Changing logging settings (advanced)

Managing Mapping

Managing Mapping

Using explicit mapping creation

Mapping base types

Mapping an object

Mapping a document

Using dynamic templates in document mapping

Managing nested objects

Managing a child document

Mapping a multifield

Mapping a GeoPoint field

Mapping a GeoShape field

Mapping an IP field

Mapping an attachment field

Adding generic data to mapping

Mapping different analyzers

Standard Operations

Standard Operations

Creating an index

Deleting an index

Opening/closing an index

Putting a mapping in an index

Getting a mapping

Deleting a mapping

Refreshing an index

Flushing an index

Optimizing an index

Checking if an index or type exists

Managing index settings

Using index aliases

Indexing a document

Getting a document

Deleting a document

Updating a document

Speeding up atomic operations (bulk)

Speeding up GET

Search, Queries, and Filters

Search, Queries, and Filters

Executing a search

Sorting a search

Highlighting results

Executing a scan query

Suggesting a correct query

Deleting by query

Matching all the documents

Querying/filtering for term

Querying/filtering for terms

Using a prefix query/filter

Using a Boolean query/filter

Using a range query/filter

Using span queries

Using the match query

Using the IDS query/filter

Using the has_child query/filter

Using the top_children query

Using the has_parent query/filter

Using a regexp query/filter

Using exists and missing filters

Using and/or/not filters

Using the geo_bounding_box filter

Using the geo_polygon filter

Using the geo_distance filter

Facets

Executing facets

Executing terms facets

Executing range facets

Executing histogram facets

Executing date histogram facets

Executing filter/query facets

Executing statistical facets

Executing term statistical facets

Executing geo distance facets

Scripting

Installing additional script plugins

Sorting using script

Computing return fields with scripting

Filtering a search via scripting

Updating with scripting

Rivers

Managing a river

Using the CouchDB river

Using the MongoDB river

Using the RabbitMQ river

Using the JDBC river

Using the Twitter river

Cluster and Nodes Monitoring

Cluster and Nodes Monitoring

Controlling cluster health via API

Controlling cluster state via API

Getting nodes information via API

Getting node statistic via API

Installing and using BigDesk

Installing and using ElasticSerach-head

Installing and using SemaText SPM

Java Integration

Java Integration

Creating an HTTP client

Creating a native client

Managing indices with the native client

Managing mappings

Managing documents

Managing bulk action

Creating a query

Executing a standard search

Executing a facet search

Executing a scroll/scan search

Python Integration

Python Integration

Creating a client

Managing indices

Managing mappings

Managing documents

Executing a standard search

Executing a facet search

Plugin Development

Plugin Development

Creating a site plugin

Creating a simple plugin

Creating a REST plugin

Creating a cluster action

Creating an analyzer plugin

Creating a river plugin

Index

Customer Reviews

5 star

0

4 star

0

3 star

0

2 star

0

1 star

0

Deleting by query

In the previous chapter we saw how to delete a document. Deleting a document is very fast but we need to know the document ID.

ElasticSearch provides a call to delete all the documents that match a query.

Getting ready

You need a working ElasticSearch cluster and an index populated with the script available in online code.

How to do it...

For executing a delete by query, we need to perform the following steps:

From command line, we need to execute the following query:

curl -XDELETE 'http://127.0.0.1:9200/test-index/test-type/_query' -d '{"match_all":{}}'

The result returned by ElasticSearch, if everything is all right, should be as follows:

{
  "ok" : true,
  "_indices" : {
    "test-index" : {
      "_shards" : {
        "total" : 5,
        "successful" : 5,
        "failed" : 0
      }
    }
  }
}

The result is composed by the ok result (a Boolean type) and the shards status at the time of the delete by query.

How it works...

The query is interpreted as it is done for searching...