Github user arina-ielchiieva commented on the issue:
https://github.com/apache/drill/pull/936
@paul-rogers
agree with you that charsets used in saffron properties should be defaulted
in Drill to `UTF-8` since Drill can read UTF-8 data and it's strange that it
would fail by
Github user paul-rogers commented on the issue:
https://github.com/apache/drill/pull/936
@arina-ielchiieva, my comments boil down to two points:
1. What happens if UTF-8 support in Drill is disabled? Do we have
consistent handling of character data? Do we revert to ASCII? The
Github user paul-rogers commented on the issue:
https://github.com/apache/drill/pull/936
@arina-ielchiieva, thanks for the explanation. Drill's runtime framework
assumes that data is either:
1. ASCII (or, at least, single-byte character set based on ASCII), or
2. UTF-8
Github user arina-ielchiieva commented on the issue:
https://github.com/apache/drill/pull/936
@paul-rogers, the unit tests just show which influence saffron property has
on Drill (since people in the community where asking how to enable support
UTF-8 in Drill), a long with this PR
