TL;DR
Elastisch is a battle tested, small but feature rich and well documented Clojure client for ElasticSearch. It supports virtually every Elastic Search feature and has solid documentation.
2.0.0-beta4 is a preview release of Elastisch 2.0, which focuses on the new features in ElasticSearch 1.0 and 1.1 as well as some API refinements.
Changes between Elastisch 2.0.0-beta3 and 2.0.0-beta4
Options As Maps
Elastisch has tranditionally accepted options as (pseudo) keywrod arguments, e.g.
1
|
|
Starting with 2.0.0-beta4
, passing a single map of arguments
is now also supported by nearly all document, index, admin and percolation
functions:
1
|
|
As a new design rule, all new API elements (e.g. aggregations) will accept a single map of options.
GH issue: #59.
Percolation of Existing Documents (REST API)
REST API client now supports percolation of existing documents:
1 2 3 |
|
Changes between Elastisch 2.0.0-beta2 and 2.0.0-beta3
ElasticSearch Client Update
ElasticSearch client has been upgraded to 1.1.0
.
Clojure 1.6
Elastisch now depends on org.clojure/clojure
version 1.6.0
. It is
still compatible with Clojure 1.4 and if your project.clj
depends on
a different version, it will be used, but 1.6 is the default now.
Type Exists Operation
types-exists support in both rest and native clients:
1 2 3 |
|
Contributed by Halit Olali.
Full Change Log
Elastisch change log is available on GitHub.
Thank You, Contributors
Kudos to Halit Olali, shmish111, and Richie Vos for contributing to this release.
Elastisch is a ClojureWerkz Project
Elastisch is part of the group of libraries known as ClojureWerkz, together with
- Langohr, a Clojure client for RabbitMQ that embraces the AMQP 0.9.1 model
- Monger, a Clojure MongoDB client for a more civilized age
- Cassaforte, a Clojure Cassandra client
- Titanium, a Clojure graph library
- Neocons, a client for the Neo4J REST API
- Welle, a Riak client with batteries included
- Quartzite, a powerful scheduling library
and several others. If you like Elastisch, you may also like our other projects.
Let us know what you think on Twitter or on the Clojure mailing list.
About the Author
Michael on behalf of the ClojureWerkz Team