error on Timeseries with Grafana 4.1.2 about druidplugin

[abhisant]

Let me have a look into it.

[tutunci]

Thanks!
I've manually updated the plugin and now it's working fine.

Thanks a lot!
M.

[abhisant]

Released:
https://grafana.net/plugins/abhisant-druid-datasource?version=0.0.4

[emitskevich]

I have the same issue. Looks like only topN charts are affected.

[abhisant]

I am working out with Grafana team to understand what exactly changed. According to them there is no breaking change in the plugin except the Lodash version upgrade. They have asked for further details, please follow the link below.

grafana/grafana#7581

[knoguchi]

EDIT: it wasn't working actually. It was still using lodash v3. Please disregard this comment.

It works fine for me. I'm using the HEAD of Grafana v4.1.x branch (commit: v4.1.1+2-g46c1f7), compiled myself, and the HEAD of master branch of the druidplugin compiled myself (Thanks for the build script!).

git diff dist has lots of differences. Maybe the checked-in dist files are outdated?

I tested timeseries, topN, groupBy queries. All works.

[abhisant]

@knoguchi : It's surprising because even I am seeing the issues in topN and groupBy.

[abhisant]

git diff dist has lots of differences - Yes, I have just checked in build related files..

[knoguchi]

Created PR #9 to fix the topN. I noticed my compilation had a problem that I reported earlier.

[abhisant]

@knoguchi : Thank you for all the pull's and identifying the issue. Instead of a branch I was thinking to put a git tag, because anyways when I release the grafana version, they take the commitId and all commits before the particular commitId are taken into the consideration. Please let me know if you are ok with creating a tag instead of branch.

[knoguchi]

tag is fine.

[abhisant]

Issued a pull request to the Grafana team to release 0.0.3 and 0.0.4. (Release notes at: grafana/grafana-plugin-repository#99)

The fix is available in the dist folder. Till the version is released the dist files can be copied to fix the issues. Thanks to @knoguchi for identifying it and issuing a pull.