[GitHub] [druid] samarthjain commented on issue #9421: Unknown complex types break Druid SQL

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

samarthjain commented on issue #9421: Unknown complex types break Druid SQL
URL: https://github.com/apache/druid/issues/9421#issuecomment-610040732
 
 
   I think you are right. I had backported #7331 to our internal fork based off of 0.12.2 and users started using it. Then when the cluster was updated to 0.16, things broke because 0.16 had #8100 which removed the aggregators that were added in #7331. 
   
   Having said that, I think this PR is still worth while. Aggregator modules, especially in the extensions-contrib module, can make some changes which may or may not be compatible with each other. I am actually not even sure if we have any such guidelines around backward and forward compatibility when it comes to extension modules. This change is making sure that an incompatibility like the one I inadvertently introduced doesn't end up breaking a major Druid functionality (Druid SQL in this case). 

----------------------------------------------------------------
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