I have no more time to maintain (and finish) this plugin. Any help will be welcome!

When dealing with DataTables and ElasticSearch, one can quickly think about two things:

• By its ability to return almost instantaneously a set of result and the total amount of matching results, ElasticSearch is a perfect fit for server-side processing
• But ElasticSearch is a search engine, not a server in which we can code as we want.

So we can't simply give an ElasticSearch request to DataTables ajax config and hope for the pagination/filter/sort to be handled automagically. We can't modify the server code so we need to fake the system. We need to develop the server-side magic on client-side.

DataTables allow us to override the fnServerData function to have access to the internal state of our datatable before sending a request, which allows us to add the pagination/filter/sort information to the ElasticSearch request. See here for more informations.

The fact is that in every case, the same code will be used for that. The DataTable parameters (i.e. aoData.length: the number of row to display) will always be used the same way to construct the ElasticSearch request (i.e. { size: aoData.length }). This is a door for automation, and this plug-in is made for it.

Focus on your ElasticSearch request. Let this plug-in handle the pagination, filters and sorting of your DataTables.

Download the production version or the development version.

In your web page:

<script src="jquery.js"></script>
<script src="jquery.dataTables.min.js"></script>
<script src="elasticsearch.js"></script>
<script src="dist/jquery.elastic-datatables.min.js"></script>
<script>
var client = elasticsearch.Client({
  host: 'localhost:9200'
});

$('#example').dataTable( {
    'columns': [
        { 'sTitle': 'First name', 'sName': 'firstname' },
        { 'sTitle': 'Last name', 'sName': 'lastname' }
    ],
    'bProcessing': true,
    'bServerSide': true,
    'fnServerData': $.fn.dataTable.elastic_datatables( {
      index: 'test',
      type: 'test',
      client: client,
      body: {
        query: {
          match: {
            title: 'test'
          }
        }
      }
    } )
} );
</script>

(Coming soon)

(Nothing yet)