Fixes #243 Tuples should no longer be squashed in the event store

Yes in the GlobalIndexExpirationFilter.
It looks like you handle the parseTimestamp method differently in three different places.
GloablIndexExpirationFilter = k.getTimestamp();
MetadataExpirationFilter = 0;
EventExpirationFilter = extracts it from the key

At a minimum I find it strange the the GlobalIndex and Metadata extraction filters are using to different values for the timestamp.