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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
