-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[metric]Rename column name with non-english string #16108
Comments
we will consider this issue in metric refactor project. cc: @junlincc |
@heartcored98 we will start the metrics redesign/refactoring in later Q3 to include more column customization. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue |
Are there any updates on the issue? This issue is very annoying when using Superset with BigQuery. |
Same issue: #3136 |
Closing in favor of #21658 - please take the discussion there. |
Is your feature request related to a problem? Please describe.
Hi, I am really enjoying superset, but I am frustrated when I have to rename column with non-english string.
Because if I try to change the column name in Korean (for example metrics column), then generated sql query contains Korean with
AS
statement. Therefore, BigQuery engine is broken.Describe the solution you'd like
I would like to manually assign column names of group by and metrics with any-language string, through the chart explore ui.
Since bigquery column name rule does not allows non-english character, I think a field name variable should be prepared separately from the column name in SQL query.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Following images is error message when I assign '날짜' string to one of the metrics column.
The text was updated successfully, but these errors were encountered: