[
https://issues.redhat.com/browse/TEIID-5986?page=com.atlassian.jira.plugi...
]
Steven Hawkins commented on TEIID-5986:
---------------------------------------
To clarify the s3 translator supports an encoding property that can utilize any of the JRE
built-in charsets, including utf-8 and utf-16. There are several common ones missing that
the engine has support for such as utf-8-bom, HEX, and BASE64. A workaround is to use
getFile instead of getTextFile and use the engine function to_chars
http://teiid.github.io/teiid-documents/master/content/reference/r_string-... to
convert the blob to a clob with the engine supported encodings.
S3 translator flat file parser can not support unicode
------------------------------------------------------
Key: TEIID-5986
URL:
https://issues.redhat.com/browse/TEIID-5986
Project: Teiid
Issue Type: Feature Request
Reporter: Rui Wang
Assignee: Steven Hawkins
Priority: Major
I saw there is one ticket on Unicode support for flat file. Seems I can not config it
in V14 if I am using java api to create my VDB xml. Steven mentioned it is migrated to
S3 translater. Could you pls enhance it in latest Teiid version
[
https://issues.redhat.com/browse/TEIID-4340?page=com.atlassian.jira.plugi...]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)