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/09/02 22:53:19 UTC
[GitHub] [superset] kevinwen2k opened a new issue #16574: SqlLab page can't handle UTF-8 codec
kevinwen2k opened a new issue #16574:
URL: https://github.com/apache/superset/issues/16574
Hi all, I would like to report another bug here: The SqlLab can’t handle the UTF-8 codec. Steps to reproduce:
1. Run a query that can retrieve data from foreign country and I got the following error as the first 2 screenshots (either sync query or async query).
2. When I used other software tool (including browser) to run the same query, we can get the result displayed as the 3rd and 4th screenshots
Without the problem solved, we can’t create charts with data including character in UTF-8 or even other format. It would be great to get it fixed in current 1.2 branch before we can upgrade to 1.3. Thanks.
--
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] spdustin commented on issue #16574: SqlLab page can't handle UTF-8 codec
Posted by GitBox <gi...@apache.org>.
spdustin commented on issue #16574:
URL: https://github.com/apache/superset/issues/16574#issuecomment-912823874
`0xe9` is a bytestring; perhaps it should be cast `to_char(column, 'utf-8')` first? Or, more appropriately, correct the data stored in Snowflake…because it seems like some entries are storing data in that column as a binary rather than a UTF-8-encoded string.
--
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] rumbin commented on issue #16574: SqlLab page can't handle UTF-8 codec
Posted by GitBox <gi...@apache.org>.
rumbin commented on issue #16574:
URL: https://github.com/apache/superset/issues/16574#issuecomment-913106714
Could you please try to reproduce this issue with a minimal example which does not depend on any existing table? Something like:.
`select 'éèëē ñäâæ öøœ' as unicode_chars`
This way we can narrow down, if @spdustin's suspicion is true and anyone with a Snowflake DB can reproduce the bug, if it still exists.
--
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] kevinwen2k commented on issue #16574: SqlLab page can't handle UTF-8 codec
Posted by GitBox <gi...@apache.org>.
kevinwen2k commented on issue #16574:
URL: https://github.com/apache/superset/issues/16574#issuecomment-916272277
@rumbin Yes, when running the query you provided, I could get the result without any problem. However, the input from all of the editors in any software is compliant with UTF-8 and can't reproduce the scenario that happened on our end where data came from different sources or are collected from 3rd party. It's hard to enforce all of our sources to convert the non-UTF8 bytes to UTF8 bytes.
Also, as I mentioned in this ticket earlier, Snowflake (for some reasons) can convert these byte string back to UTF-8 characters and displayed well in the browser. DBVisualizer does similar thing that can convert byte into some non-human readable characters, but at least it won't cause the error when running the query.
The following query goes through in Chrome browser connecting Snowflake account (meaning that Snowflake implemented both frontend and backend for the endpoint service with our Snowflake account) and in DBvisualizer, but it throws an error in SqlLab.
```
select install_country, install_city
from my_table
where return_date between current_date - 10 and current_date - 1
and install_country = 'Venezuela' and endswith(install_city, 'rida')
limit 100;
```
I know the data are not perfect, but what I wanted was to have the query goes through, so we can create chart on dashboard. I'm ok if those non-human readable characters are displayed in the charts.
--
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] kevinwen2k commented on issue #16574: SqlLab page can't handle UTF-8 codec
Posted by GitBox <gi...@apache.org>.
kevinwen2k commented on issue #16574:
URL: https://github.com/apache/superset/issues/16574#issuecomment-912114032
--
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] etr2460 commented on issue #16574: SqlLab page can't handle UTF-8 codec
Posted by GitBox <gi...@apache.org>.
etr2460 commented on issue #16574:
URL: https://github.com/apache/superset/issues/16574#issuecomment-912686217
According to the error messages, this seems to be an issue with Snowflake, and not with sql lab. Was this a regression that used to work in superset, or did you only now notice the issue. I would be inclined to think that there's not an issue with superset here, given that i've used utf-8 characters with Presto fine, but let me know if you think differently before I close the issue
--
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