Hello! I installed version 3.0.1 of Superset to display charts! I have a MongoDB database so that the superset can work with it, I installed Apache Drill 1.21.1
Everything works, but there is a problem with the Drill to Details functionality. When I click the "Drill To Detail" button I get this error: "Unexpected error: Error: The number that was passed in is not a number." If I look at Apache Drill's logs, a request comes:
SELECT COUNT() AS COUNT(*)
FROM mongo.events_base.events
LIMIT 50000
and indeed, if I check this request in the SQL Lab tab, it returns null
But! if I change to SELECT COUNT() AS COUNT it works well, it retunrs 919176
If I clicl the "View as table" it works well. And the request normal :
SELECT vendor AS vendor,
COUNT(*) AS count
FROM mongo.events_base.events
GROUP BY vendor
LIMIT 100
I would be very grateful for any help in this matter, we have not been able to get around this for 2-3 weeks
Comment From: rusackas
I'm tempted to close this as stale, but curious to hear if you're still facing this, or found an acceptable workaround. I'm also curious if @cgivre sees a way forward here.
Comment From: cgivre
@NomadBYlife Do you have to alias your columns as COUNT(*)? It seems like something post-Drill is not liking that alias and therefore the obvious workaround would be to use a different alias.
Comment From: rusackas
This has gone quiet for nearly a year, but I'm wondering if the above advice worked for you, @NomadBYlife ? Would love to close this out.
I'll also ping @dosu-bot for extra input :D
Comment From: hariprasaath-bot
@NomadBYlife Do you have to alias your columns as
COUNT(*)? It seems like something post-Drill is not liking that alias and therefore the obvious workaround would be to use a different alias.
I am facing the same issue: superset Version: 4.1.2 apache drill : 1.21.2
How to can I resolve this or Do the workaround since count(*) is auto generated by Superset. I am facing this issue when I drill to detail.
Sorry I am not able upload any screenshots. but I am getting the same exception as shown as issue original reported.
Comment From: hariprasaath-bot
@NomadBYlife I saw your comments on the issue: https://github.com/apache/drill/issues/2858. Is this issue fixed ? Am I in the wrong ? Actually I downgraded my sqlalchemy_drill version 1.1.7 to sqlalchemy_drill-1.1.5 due to another issue "https://github.com/JohnOmernik/sqlalchemy-drill/issues/96".
I have upgraded to sqlalchemy_drill version 1.1.7 and verified the scenario once again. Issue still there.
Comment From: rusackas
Maybe @cgivre has some idea here... I sure don't :)
That said, this issue hasn't been touched for 90 days... can anyone verify if it's still an issue on 5.0.0 (just released) or on latest master where SQLGlot has replaced SQLParse?