mirror of
https://github.com/apache/druid.git
synced 2025-02-09 03:24:55 +00:00
d007477742
* Docusaurus build framework + ingestion doc refresh. * stick to npm instead of yarn * fix typos * restore some _bin * Adjustments. * detect and fix redirect anchors * update anchor lint * Web-console: remove specific column filters (#8343) * add clear filter * update tool kit * remove usless check * auto run * add % * Fix resource leak (#8337) * Fix resource leak * Patch comments * Enable Spotbugs NP_NONNULL_RETURN_VIOLATION (#8234) * Fixes from PR review. * Fix more anchors. * Preamble nix. * Fix more anchors, headers * clean up placeholder page * add to website lint to travis config * better broken link checking * travis fix * Fixed more broken links * better redirects * unfancy catch * fix LGTM error * link fixes * fix md issues * Addl fixes
2.0 KiB
2.0 KiB
| id | title | sidebar_label |
|---|---|---|
| datasourcemetadataquery | DatasourceMetadata queries | DatasourceMetadata |
Data Source Metadata queries return metadata information for a dataSource. These queries return information about:
- The timestamp of latest ingested event for the dataSource. This is the ingested event without any consideration of rollup.
The grammar for these queries is:
{
"queryType" : "dataSourceMetadata",
"dataSource": "sample_datasource"
}
There are 2 main parts to a Data Source Metadata query:
| property | description | required? |
|---|---|---|
| queryType | This String should always be "dataSourceMetadata"; this is the first thing Apache Druid (incubating) 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 |
| context | See Context | no |
The format of the result is:
[ {
"timestamp" : "2013-05-09T18:24:00.000Z",
"result" : {
"maxIngestedEventTime" : "2013-05-09T18:24:09.007Z"
}
} ]