elasticsearch date reader issues

[jsnoble]

There is an issue that the date reader does not properly handle multiple repeated sequences of data that have many slices of zero then big massive spikes that cannot be broken down.

IE size: 100 but sequence is [0, 1000, 0, 1000, 0, 1000, 0, 0, 1000, 0]

There was a slice record that encapsulated three of the spikes instead of one.

We should consider a threshold of just failing the slice if the data is to large compared to size. How this would work for the slicer needs to be thought out