It did not identify the correct character ยต. The encoding in UTF would be 0xc2b5. 0xb5 by itself is not valid in UTF-8.
We would need to implement an ISO-8859-1 convert function. Shouldn't too much work. On Sat, Sep 20, 2014 at 6:25 AM, Jim Scott <[email protected]> wrote: > Perhaps you can download the file and self assess that question? > > My original question: > It properly identifies the character 0xb5 while decoding as a UTF8 string. > > Is there a way I can tell Drill to read it with a different encoding if > that is the issue? I cannot find a way to tell it that is should think the > files is ISO-8859-1 or CP1252, if that is the actual problem. > -- Steven Phillips Software Engineer mapr.com
