Elasticsearch 6.3.1 release, distributed search engine

Elasticsearch 6.3.1 has been released, ElasticSearch is a Lucene-based open source, distributed, RESTful search engine. Designed for cloud computing, to achieve real-time search, stable, reliable, fast, easy to install. Support for data indexing via HTTP using JSON.

Elasticsearch is a highly scalable open-source full-text search and analytics engine. It allows you to store, search, and analyze big volumes of data quickly and in near real time. It is generally used as the underlying engine/technology that powers applications that have complex search features and requirements.

Here are a few sample use-cases that Elasticsearch could be used for:

  • You run an online web store where you allow your customers to search for products that you sell. In this case, you can use Elasticsearch to store your entire product catalog and inventory and provide search and autocomplete suggestions for them.
  • You want to collect log or transaction data and you want to analyze and mine this data to look for trends, statistics, summarizations, or anomalies. In this case, you can use Logstash (part of the Elasticsearch/Logstash/Kibana stack) to collect, aggregate, and parse your data, and then have Logstash feed this data into Elasticsearch. Once the data is in Elasticsearch, you can run searches and aggregations to mine any information that is of interest to you.
  • You run a price alerting platform which allows price-savvy customers to specify a rule like “I am interested in buying a specific electronic gadget and I want to be notified if the price of gadget falls below $X from any vendor within the next month”. In this case you can scrape vendor prices, push them into Elasticsearch and use its reverse-search (Percolator) capability to match price movements against customer queries and eventually push the alerts out to the customer once matches are found.
  • You have analytics/business-intelligence needs and want to quickly investigate, analyze, visualize, and ask ad-hoc questions on a lot of data (think millions or billions of records). In this case, you can use Elasticsearch to store your data and then use Kibana (part of the Elasticsearch/Logstash/Kibana stack) to build custom dashboards that can visualize aspects of your data that are important to you. Additionally, you can use the Elasticsearch aggregations functionality to perform complex business intelligence queries against your data.

Changelog v6.3.1

    • Authentication
      • Security: fix joining cluster with production license #31341 (issue: #31332)
      • Security: fix token bwc with pre 6.0.0-beta2 #31254 (issues: #30743#31195)
      • Compliant SAML Response destination check #31175


      • Ingest Attachment: Upgrade Tika to 1.18 #31252

      Java High Level REST Client

      • Change bulk’s retry condition to be based on RestStatus #29329 (issues: #28885#29254)

      Java Low Level REST Client

      • Avoid setting connection request timeout #30384 (issue: #24069)

      Machine Learning

      • Fixes a bug introduced in 6.3.0 which may cause the a node to hang and drop out of the cluster if Machine Learning is enabled and has been actively used. The issue can be redressed in 6.3.0 by disabling Machine Learning on all nodes #31691 (issue: #31683)


      • Ensure we don’t use a remote profile if cluster name matches #31331 (issue: #29321)


      • Add package pre-install check for java binary #31343 (issue: #29665)


      • Fix missing historyUUID in peer recovery when rolling upgrade 5.x to 6.3 #31506 (issue: #31482)


      • [Rollup] Metric config parser must use builder so validation runs #31159


      • JDBC: Fix stackoverflow on getObject and timestamp conversion #31735 (issue: #31734)
      • SQL: Preserve scoring in bool queries #30730 (issue: #29685)


      • Painless: Fix bug for static method calls on interfaces #31348


      • Fix race in clear scroll #31259
      • Cross Cluster Search: preserve remote status code #30976 (issue: #27461)


      • Preserve thread context when connecting to remote cluster #31574 (issues: #31241#31462)


      • Watcher: Fix put watch action #31524


Leave a Reply

Your email address will not be published. Required fields are marked *