You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2019/08/06 14:08:28 UTC

[GitHub] [incubator-druid] himanshug commented on issue #8242: should we deprecate extractionFn field in various Aggregators and Filters

himanshug commented on issue #8242: should we deprecate extractionFn field in various Aggregators and Filters
URL: https://github.com/apache/incubator-druid/issues/8242#issuecomment-518685289
 
 
   @gianm I think we could do something on the line of rewriting the query in early stage of processing pipeline at broker to... for each aggregator/filter/whatever, auto generate the virtual columns spec and set extractionFn field to null in it.
   
   that said, doing and testing it is overhead if we decide to "deprecate and remove" it. OTOH if you mean that we should not deprecate extractionFn field and will always keep the compatibility layer, then it may make sense to write it.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

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