version selection: Elasticsearch Latest Version 2.20
Elasticsearch update is too fast, February 2, 16 updated to version 2.2, first look at the version of the new features added. The first is based on Lucene 5.4.1, which fixes many bugs that exist in Elasticsearch 2.1.2 and Elasticsearch 1.7.5, while Elasticsearch 2.2.0 adds two great new features: Query Analyzer and enhanced geolocation field. This version adds more stringent security and fixes a significant bug in 2.1, which is very slow when the Shard is restored. As well as many other bug fixes and improvements. The official encourages all users to upgrade to this version.
Profiler (Profile API)
The parser provides detailed analysis of the query, which allows you to understand and debug query performance. Each part of the query records statistical time independently, such as how long it takes to rewrite the query, find the matching documents, and their score. When the query is slow, you don't need to guess why it's so slow: as long as you set the profile to True, you can get the most direct in-depth query analysis.
Enhanced Geolocation field
The Geo-location field has been almost written from 2.20, and it uses a new compact data structure stored in the Lucene index, which can add 50% of inbound efficiency, 20-50% query efficiency, half of the storage space and memory footprint, and simpler mapping parameters.
Stricter security checks on plugins and scripts
As part of the security enhancements, groovy and Lucene's expression scripting languages have moved out of the core layer and now use them as plugins for the default distributed modules. Such adjustments can control the permissions of these modules, have reduced hacker attacks, elasticsearch core modules in the future will be more modular processing. scripting language, now predefined provides a whitelist list, which cannot read and write files, and cannot open remote connections. By default, plug-ins are not permitted to have special permissions, or they must be declared beforehand. At the same time when the plug-in installation will be warned of special permissions requirements, this time you can confirm if necessary to remove the plug-ins.
This article by Saikesaisi Pharmaceutical Lande (Secisland) original, reprint please indicate the author and source.
Installation
Elasticsearch installation requires Java 7 support at a minimum. The latest version recommends using Oracle's JDK version 1.8.0_72. To learn about Java, you can find the relevant information on Oracle's website. Before you install Elasticsearch, please check your Java version to run:
Java-version
When we set up Java, we can download the latest version. : https://www.elastic.co/downloads/past-releases/elasticsearch-2-2-0.
After the download is complete, unzip directly. Then go to the CD Elasticsearch-2.2.0/bin directory.
Execute elasticsearch.bat under Windows, run under Linux./elasticsearch.
If all goes well, you should see a bunch of information like this:
[2016-02-03 16:53:31,122] [INFO ] [node ] [rintrah] version[2.2.0], pid[6840], build[8ff36d1/2016-01-27t13 :32:39z][2016-02-03 16:53:31,122][info ][node ] [rintrah] initializing &NBSP, ..... [2016-02-03 16:53:31,668] [INFO ] [plugins ] [rintrah] modules [lang-groovy, lang-expression], plugins [], sites [][2016-02-03 16:53:31,684][INFO ][env ] [rintrah] using [1] data paths, mounts [[work (D:)]], NET USABLE_SPACE [67.2GB], NET TOTAL_SPACE [99.9GB], spins? [unknown], types [NTFS][2016-02-03 16:53:31,684][INFO ][env ] [rintrah] heap size [910.5mb], compressed ordinary object pointers [true][2016-02-03 16:53:33,637][INFO ][node ] [rintrah] initialized[2016-02-03 16:53:33,637][INFO ][node ] [Rintrah] STARTING&NBSP, ..... [2016-02-03 16:53:33,918] [INFO ] [transport ] [rintrah] publish_address {127.0.0.1:9300}, bound_addresses {[::1]:9300}, {127.0.0.1:9300}[2016-02-03 16:53:33,934][INFO ][discovery ] [Rintrah] elasticsearch/1oo5dtelt8ax-3lmntrs8g[2016-02-03 16:53:37,982][info ][cluster.service ] [rintrah] new_master {rintrah}{ 1oo5dtelt8ax-3lmntrs8g}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-join (elected_as_master, [ 0] joins received) [2016-02-03 16:53:40,363][info ][gateway ] [rintrah] recovered [0] indices into cluster_state[2016-02-03 16:53:40,567][INFO ][http &nbSp; ] [rintrah] publish_address {127.0.0.1:9200}, bound_addresses {[::1]:9200}, {127.0.0.1:9200}[2016-02-03 16:53:40,567][info ][node ] [rintrah] started
So we've started the Elasticsearch, and of course we can change the name of the cluster and the name of the node at startup. For example:
./elasticsearch--cluster.name My_cluster_name--node.name my_node_name
By default, Elasticsearch uses the rest API provided by Port 9200. The port is configurable.
On the native access http://127.0.0.1:9200/
Will get a little bit of content:
{"Name": "Rintrah", "cluster_name": "Elasticsearch", "version": {"number": "2.2.0", "Build_hash": "8ff36d1 39e16f8720f2947ef62c8167a888992fe "," Build_timestamp ":" 2016-01-27t13:32:39z "," Build_snapshot ": false," Lucene _version ":" 5.4.1 "}," tagline ":" You Know, for Search "}
Now that we have our nodes (and clusters) will fight for the run, the next step is to understand how to use it. Elasticsearch provides a very comprehensive and powerful rest API through which we can understand the information of the cluster. These APIs can do the following things:
1. Check cluster, node and index conditions, status and statistics
2. Managing cluster, node, and index data and document data
3, perform crud (Create, read, update and delete) operations, can operate on the index
4. Perform advanced search operations such as paging, sorting, filtering, scripting, aggregation, and other actions.
Lande (Secisland) will gradually analyze the features of the latest version of Elasticsearch, and look forward to it.
Elasticsearch Latest Version 2.20 features and how to install