Fix boundary conditions in kronos

This also adds an `end_id` parameter which is analogous to `start_id`. 
Can this wait until after the sqlite branch is merged?

On Mon, Nov 17, 2014 at 5:01 PM, Usman Masood <notifications@github.com>
wrote:

> In kronos/kronos/storage/elasticsearch/client.py:
>
> > @@ -258,15 +257,23 @@ def _delete(self, namespace, stream, start_id, end_time, configuration):
> >                'should': [
> >                  {
> >                    'range': {TIMESTAMP_FIELD: {'gt': start_time,
>
> There are 3 separate filters. This one picks out events in (start_time,
> end_time). The other two pick out events where time=start_time AND id >=
> start_id(analogous toend_time`).
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Locu/chronology/pull/320/files#r20479071>.
>