After setting up a connection between superset and a druid cluster. (scan new datasources works fine), datasources are created, but when i want to explore them, or make a chart on them. I get an 500 - Internal Server Error.
AttributeError: 'NoneType' object has no attribute 'data'
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 2292, in wsgi_app
response = self.full_dispatch_request()
File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1815, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1718, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/usr/local/lib/python3.6/site-packages/flask/_compat.py", line 35, in reraise
raise value
File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1813, in full_dispatch_request
rv = self.dispatch_request()
File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1799, in dispatch_request
return self.view_functions[rule.endpoint](**req.view_args)
File "/home/superset/superset/models/core.py", line 1149, in wrapper
value = f(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/flask_appbuilder/security/decorators.py", line 123, in wraps
return f(self, *args, **kwargs)
File "/home/superset/superset/views/core.py", line 1383, in explore
'datasource': datasource.data,
File "/home/superset/superset/connectors/base/models.py", line 192, in data
'database': self.database.data, # pylint: disable=no-member
AttributeError: 'NoneType' object has no attribute 'data'
Being able to use a druid datasource like the normal SQL ones
HTTP 500 Error
provide correct name and port. press 'Save'
Go to 'Sources'
Get the error
Python 3.6.8
v10.15.3
6.4.1
apache-druid-0.14.2-incubating
Make sure these boxes are checked before submitting your issue - thank you!
Issue-Label Bot is automatically applying the label #bug
to this issue, with a confidence of 0.80. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
The problem was that the cluster_name was not set in the DBtable clusters and DBTable datasources.
Tried to reproduce the cluster creation steps, and got some strange results while trying to add or edit clusters.
cluster name is an input, but is not mandatory. After saving the provided name is not used. After deletion, and creating a new cluster, the old clustername is used.
I seem to be having the same issue using the docker image
Just to reiterate what @deity-bram is saying, you must enter something in the verbose
field and the cluster
Most helpful comment
I seem to be having the same issue using the docker image
Just to reiterate what @deity-bram is saying, you must enter something in the
verbose
field and thecluster