mirror of https://github.com/apache/druid.git synced 2025-02-10 12:05:00 +00:00

rajk-tetration 362b9266f8 Adding filters for TimeBoundary on backend (#3168 )

* Adding filters for TimeBoundary on backend

Signed-off-by: Balachandar Kesavan <raj.ksvn@gmail.com>

* updating TimeBoundaryQuery constructor in QueryHostFinderTest

* add filter helpers

* update filterSegments + test

* Conditional filterSegment depending on whether a filter exists

* Style changes

* Trigger rebuild

* Adding documentation for timeboundaryquery filtering

* added filter serialization to timeboundaryquery cache

* code style changes

2016-08-15 10:25:24 -07:00

1.3 KiB

Raw Blame History

layout
doc_page

Time Boundary Queries

Time boundary queries return the earliest and latest data points of a data set. The grammar is:

{
    "queryType" : "timeBoundary",
    "dataSource": "sample_datasource",
    "bound"     : < "maxTime" | "minTime" > # optional, defaults to returning both timestamps if not set 
    "filter"    : { "type": "and", "fields": [<filter>, <filter>, ...] } # optional
}

There are 3 main parts to a time boundary query:

property	description	required?
queryType	This String should always be "timeBoundary"; this is the first thing Druid looks at to figure out how to interpret the query	yes
dataSource	A String or Object defining the data source to query, very similar to a table in a relational database. See DataSource for more information.	yes
bound	Optional, set to `maxTime` or `minTime` to return only the latest or earliest timestamp. Default to returning both if not set	no
filter	See Filters	no
context	See Context	no

The format of the result is:

[ {
  "timestamp" : "2013-05-09T18:24:00.000Z",
  "result" : {
    "minTime" : "2013-05-09T18:24:00.000Z",
    "maxTime" : "2013-05-09T18:37:00.000Z"
  }
} ]

1.3 KiB Raw Blame History

Time Boundary Queries

1.3 KiB

Raw Blame History