You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/04/21 06:49:57 UTC

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

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

   > 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.
   
   @john-bodley I understand the concern here, but at the same time the community has had ample time to prepare for this (link to the SIP #6032 ). Maybe we could float this via the dev list - if there's strong opposition maybe we can postpone until 3.0, but otherwise just rip the bandaid off in 2.0?
   
   My personal opinion: the native Druid connector is already missing some key functionality, so I'm actually surprised if it's even possible to use it in a production setting anymore. So I'd vote for removing it in 2.0 or at least making it abundantly clear that it's no longer maintained and may stop functioning all together at any given point after 2.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