[GitHub] [superset] eschutho commented on pull request #19770: chore: remove druid datasource from the config

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

eschutho commented on PR #19770:
URL: https://github.com/apache/superset/pull/19770#issuecomment-1104562178

   > I thought for Superset 2.0 we were just going to mark this as deprecated and actually remove it in Superset 3.0? This change could be seen as too aggressive for some institutions and ideally we should strive not to unnecessarily churn users.
   
   I think the original plan was to remove native Druid support for SIP68, and in trying to get ahead of that work, to mark it as "no longer supported" in 2.0. I believe there is likely going to be something coming before 3.0 that will break this functionality. Do you think that we need to give people more time to switch over to Druid Sql? If absolutely necessary, we can  try not to break Druid as part of the SIP68 work, but I think it's going to be complicated. Or we just hold off on finishing the SIP68 work until 3.0.


-- 
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: notifications-unsubscribe@superset.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org