You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "ziggekatten (via GitHub)" <gi...@apache.org> on 2023/04/06 08:56:06 UTC
[GitHub] [superset] ziggekatten opened a new issue, #23608: Upgrade from 2.0.1 to 2.1.0 - no database menu
ziggekatten opened a new issue, #23608:
URL: https://github.com/apache/superset/issues/23608
A running 2.0.1 installation (docker)
After deploy of new image:
superset db upgrade -> success
superset init ->success
Logging in as admin, and the menu option for adding/edit database is gone:
2.0.1:
2.1.0:
Have no clue on what to do, as the Admin role seems to have all menu accesses
--
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.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org.apache.org
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
Re: [I] Upgrade from 2.0.1 to 2.1.0 - no database menu [superset]
Posted by "vndroid (via GitHub)" <gi...@apache.org>.
vndroid commented on issue #23608:
URL: https://github.com/apache/superset/issues/23608#issuecomment-1767654685
> 与...一样@ralphkretzschmar
>
> /usr/local/lib/python3.8/site-packages/flask_appbuilder/models/sqla/interface.py:67：SAWarning：关系“SqlaTable.slices”会将列tables.id复制到列slices.datasource_id，这与关系：'Slice.table'（将tables.id复制到slice.datasource_id）。如果这不是目的，请考虑这些关系是否应与 back_populates 链接，或者如果它们是只读的，是否应将 viewonly=True 应用于一个或多个关系。对于不太常见的外键约束部分重叠的情况，可以使用 orm.foreign() 注释来隔离应写入的列。要消除此警告，请将参数“overlaps="table"”添加到“SqlaTable.slices”关系中。（此错误的背景位于：https://sqlalche.me/e/14/qzyx）
>
> @rusackas，你有什么线索吗？谢谢 ：）
I'm facing the same issue, No idea about it.
--
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.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
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] perugini commented on issue #23608: Upgrade from 2.0.1 to 2.1.0 - no database menu
Posted by "perugini (via GitHub)" <gi...@apache.org>.
perugini commented on issue #23608:
URL: https://github.com/apache/superset/issues/23608#issuecomment-1555929912
Same as @ralphkretzschmar
/usr/local/lib/python3.8/site-packages/flask_appbuilder/models/sqla/interface.py:67: SAWarning: relationship 'SqlaTable.slices' will copy column tables.id to column slices.datasource_id, which conflicts with relationship(s): 'Slice.table' (copies tables.id to slices.datasource_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="table"' to the 'SqlaTable.slices' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx)
@rusackas, do you have any clues about it?
--
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.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
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] ralphkretzschmar commented on issue #23608: Upgrade from 2.0.1 to 2.1.0 - no database menu
Posted by "ralphkretzschmar (via GitHub)" <gi...@apache.org>.
ralphkretzschmar commented on issue #23608:
URL: https://github.com/apache/superset/issues/23608#issuecomment-1542403716
just to mention it:
a clean installation of 2.1.0 is starting and working. but running the following command:
"sudo docker exec -it superset_app superset db upgrade"
i get the same notification:
/usr/local/lib/python3.9/site-packages/flask_appbuilder/models/sqla/interface.py:67: SAWarning: relationship 'SqlaTable.slices' will copy column tables.id to column slices.datasource_id, which conflicts with relationship(s): 'Slice.table' (copies tables.id to slices.datasource_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="table"' to the 'SqlaTable.slices' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx)
for prop in class_mapper(obj).iterate_properties:
--
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.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
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] rusackas commented on issue #23608: Upgrade from 2.0.1 to 2.1.0 - no database menu
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #23608:
URL: https://github.com/apache/superset/issues/23608#issuecomment-1507211988
Sounds like we're all good, but holler if this needs further attention!
--
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.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
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] rusackas closed issue #23608: Upgrade from 2.0.1 to 2.1.0 - no database menu
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #23608: Upgrade from 2.0.1 to 2.1.0 - no database menu
URL: https://github.com/apache/superset/issues/23608
--
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.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
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] ziggekatten commented on issue #23608: Upgrade from 2.0.1 to 2.1.0 - no database menu
Posted by "ziggekatten (via GitHub)" <gi...@apache.org>.
ziggekatten commented on issue #23608:
URL: https://github.com/apache/superset/issues/23608#issuecomment-1500917278
Uhhh....I thought I looked there and didn't see it. But yes, there it is!
--
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.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
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] ziggekatten commented on issue #23608: Upgrade from 2.0.1 to 2.1.0 - no database menu
Posted by "ziggekatten (via GitHub)" <gi...@apache.org>.
ziggekatten commented on issue #23608:
URL: https://github.com/apache/superset/issues/23608#issuecomment-1498733765
Update.
Running an superset init again, and it seems to try to create missing permissions every time, but starts with an warning:
`
/usr/local/lib/python3.8/site-packages/flask_appbuilder/models/sqla/interface.py:67:** SAWarning: relationship 'SqlaTable.slices' will copy column tables.id to column slices.datasource_id, which conflicts with relationship(s): 'Slice.table' (copies tables.id to slices.datasource_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="table"' to the 'SqlaTable.slices' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx)
for prop in class_mapper(obj).iterate_properties:
Syncing role definition
2023-04-06 11:04:57,253:INFO:superset.security.manager:Syncing role definition
Syncing Admin perms
2023-04-06 11:04:57,276:INFO:superset.security.manager:Syncing Admin perms
Syncing Alpha perms
2023-04-06 11:04:58,043:INFO:superset.security.manager:Syncing Alpha perms
Syncing Gamma perms
2023-04-06 11:04:58,847:INFO:superset.security.manager:Syncing Gamma perms
Syncing granter perms
2023-04-06 11:04:59,646:INFO:superset.security.manager:Syncing granter perms
Syncing sql_lab perms
2023-04-06 11:05:00,352:INFO:superset.security.manager:Syncing sql_lab perms
Fetching a set of all perms to lookup which ones are missing
2023-04-06 11:05:01,239:INFO:superset.security.manager:Fetching a set of all perms to lookup which ones are missing
Creating missing datasource permissions.
2023-04-06 11:05:02,073:INFO:superset.security.manager:Creating missing datasource permissions.
Creating missing database permissions.
2023-04-06 11:05:02,555:INFO:superset.security.manager:Creating missing database permissions.
Cleaning faulty perms
2023-04-06 11:05:02,583:INFO:superset.security.manager:Cleaning faulty perms
`
--
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.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
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] hienduyph commented on issue #23608: Upgrade from 2.0.1 to 2.1.0 - no database menu
Posted by "hienduyph (via GitHub)" <gi...@apache.org>.
hienduyph commented on issue #23608:
URL: https://github.com/apache/superset/issues/23608#issuecomment-1500779406
`Settings > Data > Database Connections` is where you're looking for.
<img width="188" alt="image" src="https://user-images.githubusercontent.com/94601620/230701753-7f9307e0-1b12-4a27-8ecb-67cbc8306852.png">
--
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.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
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