Ingest metadata query implementation

Ingest metadata query - 
expose maxIngestedEventTime
Be careful with those intervals for maxtime style queries, they cause some
strange behavior with integration tests and applications using druid

On Wed, Dec 10, 2014 at 8:47 AM, Charles Allen <notifications@github.com>
wrote:

> In
> processing/src/main/java/io/druid/query/ingestmetadata/IngestMetadataQuery.java
> <https://github.com/metamx/druid/pull/952#discussion-diff-21616344>:
>
> > +import io.druid.query.Result;
> > +import io.druid.query.spec.MultipleIntervalSegmentSpec;
> > +import io.druid.query.spec.QuerySegmentSpec;
> > +import org.joda.time.DateTime;
> > +import org.joda.time.Interval;
> > +
> > +import java.util.Arrays;
> > +import java.util.List;
> > +import java.util.Map;
> > +
> > +/**
> > + */
> > +public class IngestMetadataQuery extends BaseQuery<Result<IngestMetadataResultValue>>
> > +{
> > +  public static final Interval MY_Y2K_INTERVAL = new Interval(
> > +      new DateTime("0000-01-01"),
>
> There is a min time and max time already defined. Can that be used here
> instead?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/metamx/druid/pull/952/files#r21616344>.
>