drill-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andries Engelbrecht <aengelbre...@maprtech.com>
Subject Re: UTF coding in JSON docs
Date Tue, 03 Mar 2015 15:56:00 GMT
I don’t think this is an option as this is for twitter data being fed in.

Any other options.


On Mar 2, 2015, at 10:40 PM, Ted Dunning <ted.dunning@gmail.com> wrote:

> The right solution is to go into the JSON format and somehow let character
> encoding be defined there.
> 
> 
> 
> On Tue, Mar 3, 2015 at 3:23 AM, Andries Engelbrecht <
> aengelbrecht@maprtech.com> wrote:
> 
>> How can I convert JSON data with various characters in a text field to a
>> more usable UTF8 encoding? (even if characters not in UTF8 is dropped)
>> Or if needs be filter out the records with characters not in UTF8?
>> 
>> CONVERT_TO is for binary and cast as varchar still passes these characters
>> through.
>> 
>> Results in sqlline works, but when using tools through ODBC various
>> failures occur (especially tools not capable of handling characters outside
>> of UTF8).
>> 
>> 
>> Thanks
>> —Andries


Mime
View raw message