HUE 4.7 "'ascii' codec can't decode byte" error

Is the issue already present in https://github.com/cloudera/hue/issues or discussed in the forum https://discourse.gethue.com? No, at least I couldn’t find it

Describe the bug: When running Hive or Impala query that contains special characters, for example çã the error is returned: 'ascii' codec can't decode byte 0xc3 in position 90: ordinal not in range(128)

Log file with more details attached. hue_47_ascii_codec_cant_decode_error.txt The same query works without errors when executed from Hue 4.6

Steps to reproduce it? Create table with data that contains symbols ç or ã in string fields and try to query it like this: select * from db.table where name='Don Pelição' The query works fine if it doesn’t contain special characters.

Hue version or source? (e.g. open source 4.5, CDH 5.16, CDP 1.0…). System info (e.g. OS, Browser…). Open source 4.7. System info - OS: Windows 10; Browsers: Firefox and Chrome.

[milletnis]

we are facing the same problem. With HUE 4.8.0 some LDAP users are not able to login anymore. Same users and same LDAP backend but Hue 4.4.0 works fine for us.

[18/Mar/2021 21:06:02 +0000] decorators   INFO     AXES: Calling decorated function: dt_login
[18/Mar/2021 21:06:02 +0000] backend      INFO     Augmenting users with class: <class 'desktop.auth.backend.DefaultUserAugmentor'>
[18/Mar/2021 21:06:03 +0000] forms        ERROR    LDAP auth error: 'ascii' codec can't decode byte 0xc3 in position 18: ordinal not in range(128)
[18/Mar/2021 21:06:03 +0000] access       WARNING  127.0.0.1 -anon- - "POST /hue/accounts/login HTTP/1.1" --- Failed login for user: dummy
[18/Mar/2021 21:06:03 +0000] access       WARNING  127.0.0.1 -anon- - "POST /hue/accounts/login HTTP/1.1" --- Failed login for user: dummy
[18/Mar/2021 21:06:03 +0000] decorators   INFO     AXES: New login failure by 127.0.0.1. Creating access record.

[romainr]

Indeed, this is has not been working for a while. There are a few tricky unicode places to handle correctly. I faced a few of those while porting to Python 3 (in the fetch result call) and will see if possible to fix at some point.