Qbox to join forces with Instaclustr. Read about it on our blog post here.

In the previous article, we covered “Painless” and provided details about its syntax and usage. The article also covered some best practices, like why to use “params”, when to use “doc” values versus “_source” when accessing the document fields, and how to create fields on the fly etc.

We also covered topics like using Painless scripting in a query context, filter context and topics like using conditionals in scripting, deleting fields/nested fields, accessing nested objects and usage of scripting in scoring etc. In this final “Painless” post, we explore how to use Painless scripting in Kibana.

Keep reading

A common use case when working with Elasticsearch(ES) are the creation of dynamic fields, performing calculations on fields on the fly, modifying the scoring based upon a logic, etc. In order to perform these operations, Elasticsearch supports scripting.

Since the earlier versions of ES, it supported scripting, but the scripting language has evolved over the ES releases. Starting with MVEL prior version 1.4, Groovy (post version 1.4), and now the latest entry “Painless” starting ES 5.0, the scripting in ES has evolved. A key reason for this evolution is the need for faster, safer and simpler scripting language.

Keep reading