[GitHub] [druid] Fryuni commented on issue #95: Small Feature Request: Add a flag to prevent aggs and postAggs from being sent back.

[GitBox <gi...@apache.org>]

Fryuni commented on issue #95:
URL: https://github.com/apache/druid/issues/95#issuecomment-1004305566


   We're having the same problem.
   For now most of our queries are wrapped on secondary queries just to hide the intermediary fields, but not all query types can be wrapped in other queries (e.g. the `movingAverage` query).
   
   Some of our queries are timeseries with about 240 entries and each entry contains a 50KB thetaSketch that is generate by an intersection postAgg that we need. That is 12MB of useless data for each chart on our dashboards while the actual data is less than 2KB.
   
   DruidSQL is not a solution since it does not support many of the agg and postAgg that we use (some from extensions that may not even try to support DruidSQL)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org