the name of the column in the Druid resultset
the Druid Dimension this is mapped to
in Druid Spark DateTime Expressions handled as TimeFormatExtractionFunctionSpec; this specifies the format to apply on the Druid Dimension.
see above
this controls the expression evlaution that happens on return from Druid. So for expression like
to_date(cast(dateCol as DateType))
to_date(cast(DruidValue, DatetYpe))
on the resultset of Druid. This is required because Dates are Ints and Timestamps are Longs in Spark, whereas the value coming out of Druid is an ISO DateTime String.
format to use to parse input value.
the Druid Dimension this is mapped to
in Druid Spark DateTime Expressions handled as TimeFormatExtractionFunctionSpec; this specifies the format to apply on the Druid Dimension.
format to use to parse input value.
the name of the column in the Druid resultset
this controls the expression evlaution that happens on return from Druid.
this controls the expression evlaution that happens on return from Druid. So for expression like
to_date(cast(dateCol as DateType))
to_date(cast(DruidValue, DatetYpe))
on the resultset of Druid. This is required because Dates are Ints and Timestamps are Longs in Spark, whereas the value coming out of Druid is an ISO DateTime String.
see above
the name of the column in the Druid resultset
the Druid Dimension this is mapped to
in Druid Spark DateTime Expressions handled as TimeFormatExtractionFunctionSpec; this specifies the format to apply on the Druid Dimension.
see above
this controls the expression evlaution that happens on return from Druid. So for expression like
on the resultset of Druid. This is required because Dates are Ints and Timestamps are Longs in Spark, whereas the value coming out of Druid is an ISO DateTime String.
format to use to parse input value.