Skip to content
Fetching contributors…
Cannot retrieve contributors at this time
93 lines (46 sloc) 3.01 KB

Elastisch, a Clojure client for ElasticSearch

Elastisch is a minimalistic Clojure client for ElasticSearch, a modern distributed RESTful search engine.

Project Goals

  • Be reasonably feature complete
  • Be well documented
  • Be well tested
  • Closely follow ElasticSearch API structure, no new abstractions introduced
  • Follow recent ElasticSearch releases & developments
  • Target Clojure 1.3.0 and later from the ground up

Documentation & Examples

We are working on documentation guides & examples site for the 1.0 release. In the meantime, please refer to the test suite for code examples.


Elastisch has a mailing list. Feel free to join it and ask any questions you may have.

To subscribe for announcements of releases, important changes and so on, please follow @ClojureWerkz on Twitter.

Project Maturity

Elastisch is a young project, although it has been used in production since early days. Elastisch API is not fully stabilized, leep that in mind. 1.0 will be released when we are confident in the public API, reached feature completeness and documentation guides site is up and in good shape.


With Leiningen:

[clojurewerkz/elastisch "1.0.0-beta4"]

With Maven:


Supported Clojure versions

Elastisch is built from the ground up for Clojure 1.3 and up.

Elastisch Is a ClojureWerkz Project

Elastisch is part of the group of libraries known as ClojureWerkz, together with Monger, Welle, Langohr, Neocons, Quartzite and several others.

Continuous Integration

Continuous Integration status


Elastisch uses Leiningen 2. Make sure you have it installed and then run tests against all supported Clojure versions using

lein2 all test

Then create a branch and make your changes on it. Once you are done with your changes and all tests pass, submit a pull request on Github.


Copyright (C) 2011-2012 Alex Petrov, Michael S. Klishin

Distributed under the Eclipse Public License, the same as Clojure.


Why Not Just Wrap the Java Client?

Wrapping ES Java client may result in some performance gain but we don't see it to be great enough to be a significant factor for Elastisch. Following Java client conventions would likely make Elastisch less Clojuric.

Jump to Line
Something went wrong with that request. Please try again.