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 2021/02/10 19:35:59 UTC
[GitHub] [superset] prb219 opened a new issue #13064: Unable to use oracle db for storing superset metadata
prb219 opened a new issue #13064:
URL: https://github.com/apache/superset/issues/13064
Hi,
I am trying to bring up a superset instance and in the process I am using oracle db to store the metadata for superset. However, superset fails to start with the below error. Works fine when I switch to sqlLite instead however that is not a viable option in my case.
### Expected results
Expected superset to start storing metadata in oracle db
### Actual results
I see the below error instead
`"/logs/superset/superset.log" [readonly] 559L, 53803C 1,1 Top
return self.impl.get(instance_state(instance), dict_)
File "/appvenv/lib/python3.6/site-packages/sqlalchemy/orm/attributes.py", line 723, in get
value = self.callable_(state, passive)
File "/appvenv/lib/python3.6/site-packages/sqlalchemy/orm/strategies.py", line 760, in _load_for_state
session, state, primary_key_identity, passive
File "<string>", line 1, in <lambda>
File "/appvenv/lib/python3.6/site-packages/sqlalchemy/orm/strategies.py", line 902, in _emit_lazyload
.with_post_criteria(set_default_params)
File "/appvenv/lib/python3.6/site-packages/sqlalchemy/ext/baked.py", line 544, in all
return list(self)
File "/appvenv/lib/python3.6/site-packages/sqlalchemy/ext/baked.py", line 444, in __iter__
return q._execute_and_instances(context)
File "/appvenv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3560, in _execute_and_instances
result = conn.execute(querycontext.statement, self._params)
File "/appvenv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1011, in execute
return meth(self, multiparams, params)
File "/appvenv/lib/python3.6/site-packages/sqlalchemy/sql/elements.py", line 298, in _execute_on_connection
return connection._execute_clauseelement(self, multiparams, params)
File "/appvenv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1130, in _execute_clauseelement
distilled_params,
File "/appvenv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1317, in _execute_context
e, statement, parameters, cursor, context
File "/appvenv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1511, in _handle_dbapi_exception
sqlalchemy_exception, with_traceback=exc_info[2], from_=e
File "/appvenv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 182, in raise_
raise exception
File "/appvenv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1277, in _execute_context
cursor, statement, parameters, context
File "/appvenv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 593, in do_execute
cursor.execute(statement, parameters)
sqlalchemy.exc.DatabaseError: (cx_Oracle.DatabaseError) ORA-00942: table or view does not exist
[SQL: SELECT ab_permission_view.id AS ab_permission_view_id, ab_permission_view.permission_id AS ab_permission_view_permi_1, ab_permission_view.view_menu_id AS ab_permission_view_view__2
FROM ab_permission_view, ab_permission_view_role
WHERE :param_1 = ab_permission_view_role.role_id AND ab_permission_view.id = ab_permission_view_role.permission_view_id]
[parameters: {'param_1': 6}]
(Background on this error at: http://sqlalche.me/e/13/4xp6)`
#### How to reproduce the bug
1. In the superset config file simply use oracle db for metadata as follows
`SQLALCHEMY_DATABASE_URI ='oracle://<username>:<password>@service_name:1521`
2. try starting the superset server
### Environment
(please complete the following information):
- superset version: 0.37.0
### Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [Y ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
- [ Y] I have reproduced the issue with at least the latest released version of superset.
- [ Y] I have checked the issue tracker for the same issue and I haven't found one similar.
----------------------------------------------------------------
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.
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
[GitHub] [superset] willbarrett commented on issue #13064: Unable to use oracle db for storing superset metadata
Posted by GitBox <gi...@apache.org>.
willbarrett commented on issue #13064:
URL: https://github.com/apache/superset/issues/13064#issuecomment-777699217
Hi @prb219 - thanks for the question. Currently Superset supports two production-appropriate database types for the metadata database: MySQL and Postgres. May I recommend one of those two for your setup?
----------------------------------------------------------------
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.
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
[GitHub] [superset] prb219 commented on issue #13064: Unable to use oracle db for storing superset metadata
Posted by GitBox <gi...@apache.org>.
prb219 commented on issue #13064:
URL: https://github.com/apache/superset/issues/13064#issuecomment-783648526
I switched to MySql and it worked as expected. However, can we have an action item to include Oracle db to store metadata for future?
----------------------------------------------------------------
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.
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
[GitHub] [superset] amitmiran137 closed issue #13064: Unable to use oracle db for storing superset metadata
Posted by GitBox <gi...@apache.org>.
amitmiran137 closed issue #13064:
URL: https://github.com/apache/superset/issues/13064
--
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.
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