- Elasticsearch 5.x Cookbook Third Edition
- Credits
- About the Author
- About the Reviewer
- www.PacktPub.com
- Customer Feedback
- Dedication
- Preface
- 1. Getting Started
- 2. Downloading and Setup
- Introduction
- Downloading and installing Elasticsearch
- Setting up networking
- Setting up a node
- Setting up for Linux systems
- Setting up different node types
- Setting up a client node
- Setting up an ingestion node
- Installing plugins in Elasticsearch
- Installing plugins manually
- Removing a plugin
- Changing logging settings
- Setting up a node via Docker
- 3. Managing Mappings
- Introduction
- Using explicit mapping creation
- Mapping base types
- Mapping arrays
- Mapping an object
- Mapping a document
- Using dynamic templates in document mapping
- Managing nested objects
- Managing child document
- Adding a field with multiple mapping
- Mapping a GeoPoint field
- Mapping a GeoShape field
- Mapping an IP field
- Mapping an attachment field
- Adding metadata to a mapping
- Specifying a different analyzer
- Mapping a completion field
- 4. Basic Operations
- Introduction
- Creating an index
- Deleting an index
- Opening/closing an index
- Putting a mapping in an index
- Getting a mapping
- Reindexing an index
- See also
- Refreshing an index
- Flushing an index
- ForceMerge an index
- Shrinking an index
- Checking if an index or type exists
- Managing index settings
- Using index aliases
- Rollover an index
- Indexing a document
- Getting a document
- Deleting a document
- Updating a document
- Speeding up atomic operations (bulk operations)
- Speeding up GET operations (multi GET)
- 5. Search
- Introduction
- Executing a search
- Sorting results
- Highlighting results
- Executing a scrolling query
- Using the search_after functionality
- Returning inner hits in results
- Suggesting a correct query
- Counting matched results
- Explaining a query
- Query profiling
- Deleting by query
- Updating by query
- Matching all the documents
- Using a boolean query
- 6. Text and Numeric Queries
- Introduction
- Using a term query
- Using a terms query
- Using a prefix query
- Using a wildcard query
- Using a regexp query
- Using span queries
- Using a match query
- Using a query string query
- Using a simple query string query
- Using the range query
- The common terms query
- Using IDs query
- Using the function score query
- Using the exists query
- Using the template query
- 7. Relationships and Geo Queries
- 8. Aggregations
- Introduction
- Executing an aggregation
- Executing stats aggregations
- Executing terms aggregation
- Executing significant terms aggregation
- Executing range aggregations
- Executing histogram aggregations
- Executing date histogram aggregations
- Executing filter aggregations
- Executing filters aggregations
- Executing global aggregations
- Executing geo distance aggregations
- Executing children aggregations
- Executing nested aggregations
- Executing top hit aggregations
- Executing a matrix stats aggregation
- Executing geo bounds aggregations
- Executing geo centroid aggregations
- 9. Scripting
- 10. Managing Clusters and Nodes
- 11. Backup and Restore
- 12. User Interfaces
- 13. Ingest
- 14. Java Integration
- Introduction
- Creating a standard Java HTTP client
- Creating an HTTP Elasticsearch client
- Creating a native client
- Managing indices with the native client
- Managing mappings
- Managing documents
- Managing bulk actions
- Building a query
- Executing a standard search
- Executing a search with aggregations
- Executing a scroll search
- 15. Scala Integration
- 16. Python Integration
- 17. Plugin Development
- 18. Big Data Integration
In Elasticsearch 5.x, there are only two ways to communicate with the server using HTTP protocol or the native one. In this recipe, we will take a look at these main protocols.
The standard installation of Elasticsearch provides access via its web services on port 9200 for HTTP and 9300 for native Elasticsearch protocol. Simply starting an Elasticsearch server, you can communicate on these ports with it.
Elasticsearch is designed to be used as a RESTful server, so the main protocol is the HTTP usually on port 9200 and above. This is the only protocol that can be used by programming languages that don't run on a Java Virtual Machine (JVM).
Every protocol has advantages and disadvantages. It's important to choose the correct one depending on the kind of applications you are developing. If you are in doubt, choose the HTTP protocol layer that is the most standard and easy to use.
Choosing the right protocol depends on several factors, mainly architectural and performance related. This schema factorizes the advantages and disadvantages related to them:
|
Protocol |
Advantages |
Disadvantages |
Type |
|
HTTP |
This is more frequently used. It is API safe and has general compatibility for different ES versions. Suggested. JSON. It is easy to proxy and to balance with HTTP balancers. |
This is an HTTP overhead. HTTP clients don't know the cluster topology, so they require more hops to access data. |
Text |
|
Native |
This is a fast network layer. It is programmatic. It is best for massive index operations. |
The API changes and breaks applications. It depends on the same version of ES Server. Only on JVM. It is more compact due to its binary nature. It is faster because the clients know the cluster topology. The native serializer/deserializer are more efficient than the JSON ones. |
Binary |
-
No Comment