mirror of https://github.com/apache/druid.git
16817e408d
* SQL + Expressions = Best friends forever. - Use expressions as a projection layer for anything that can't be expressed using traditional Druid extractionFns. Sometimes they're embedded directly (like "expression" filters, builtin aggregators, or "expression" post-aggregators). Sometimes they're referenced through virtual columns (like dimensionSpecs, which can't innately reference functions of more than one column without the virtual column layer). - Add many new functions and operators, taking advantage of the expression capability (see the querying/sql.md doc). - Improve consistency of constant reduction and of casting by using Druid expressions for this instead of Calcite's RexExecutor. * Fix casting bug, and other code review comments. * Fix docs. |
||
---|---|---|
.. | ||
aggregations.md | ||
caching.md | ||
datasource.md | ||
datasourcemetadataquery.md | ||
dimensionspecs.md | ||
filters.md | ||
granularities.md | ||
groupbyquery.md | ||
having.md | ||
joins.md | ||
limitspec.md | ||
lookups.md | ||
multi-value-dimensions.md | ||
multitenancy.md | ||
post-aggregations.md | ||
query-context.md | ||
querying.md | ||
searchquery.md | ||
searchqueryspec.md | ||
segmentmetadataquery.md | ||
select-query.md | ||
sorting-orders.md | ||
sql.md | ||
timeboundaryquery.md | ||
timeseriesquery.md | ||
topnmetricspec.md | ||
topnquery.md |