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 2022/02/25 10:54:16 UTC
[GitHub] [superset] srinisubramanian opened a new issue #18942: If the same table name exists in multiple databases, hard to distinguish dataset when adding charts
srinisubramanian opened a new issue #18942:
URL: https://github.com/apache/superset/issues/18942
A clear and concise description of what the bug is.
Lets assume that the same table USERS exists in DB1 and DB2. Both datasets can be added and since Database is also shown its easy to add. However when adding a chart (for e.g.) only dataset name is shown and USERS appears twice. Hard to distinguish if its from DB1 or DB2. If the Database or datasource name is displayed in addition to dataset name it will be easy to distinguish
#### How to reproduce the bug
1. Go to Database and add two databases that have a common table like USERS. Also add the USERS table (for .e.g) from both databases to the datasets
2. Click on Charts and search for USERS. Its displayed twice and cannot be distinguished
### Expected results
Should be possible to distinguish between the two entries
what you expected to happen.
### Actual results
what actually happens.
#### Screenshots
If applicable, add screenshots to help explain your problem.
### Environment
(please complete the following information):
- browser type and version:
- superset version: `superset version`
- python version: `python --version`
- node.js version: `node -v`
- any feature flags active:
### Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
- [ ] I have reproduced the issue with at least the latest released version of superset.
- [ ] I have checked the issue tracker for the same issue and I haven't found one similar.
### Additional context
Add any other context about the problem here.
--
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] srinify commented on issue #18942: If the same table name exists in multiple databases, hard to distinguish dataset when adding charts
Posted by GitBox <gi...@apache.org>.
srinify commented on issue #18942:
URL: https://github.com/apache/superset/issues/18942#issuecomment-1050872497
Agree with this @srinisubramanian ! Check out the new designs, which should help address the issue by providing a better UX for finding & filtering datasets, contextualized to the database / schema they originate from:
https://github.com/apache/superset/discussions/18803
--
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] srinify edited a comment on issue #18942: If the same table name exists in multiple databases, hard to distinguish dataset when adding charts
Posted by GitBox <gi...@apache.org>.
srinify edited a comment on issue #18942:
URL: https://github.com/apache/superset/issues/18942#issuecomment-1050872497
Agree with this @srinisubramanian ! Check out the new designs, which should help address the issue by providing a better UX for finding & filtering datasets, contextualized to the database / schema they originate from:
https://github.com/apache/superset/discussions/18803
And please feedback as well! ^
--
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