Hi Maxime,

We have been digging into superset for our organisation to make 
enterprise-ready business intelligence web applications. We have been going 
through our use cases and trying to evaluate the same with superset.
We tried few sql alchemy data sources and it worked fine for us and at the same 
time we want to connect via Elastic search use ES capabilities in one of our 
use case. But we see there is no out of the box support in superset yet.
We have been reading about all the PR’s over GitHub where people have already 
asked about the same and there is one 
PR<https://github.com/apache/incubator-superset/pull/2953> where you guys have 
actually started to do something about ES connector but left due to to some 
priority crunch.
So we request you to please help us with the need, why you guys left it? were 
there some problems or conceptually did you guys thought of something which 
doesn’t fit with superset tool?
As we believe that this new connector would surely unlock a wealth of valuable 
contributions from other businesses which happen to not use Druid or a plain 
RDBMS.


Also, if you could provide us some guidance if we plan to start writing the 
same by forking the existing repository over GitHub.
Please respond to that email as we are already aligned to this tool to take up 
for the organisation to serve various use cases but this might be a deal 
breaker for us if we can support ES with the same.


Regards,
Bipin Soni

Reply via email to