[JBoss JIRA] (TEIID-4340) add encoding as "UTF-8-BOM" in the file translator override property
by Tom Johnston (JIRA)
[ https://issues.jboss.org/browse/TEIID-4340?page=com.atlassian.jira.plugin... ]
Tom Johnston commented on TEIID-4340:
-------------------------------------
I can retrieve the file by negating the BOM characters by doing this:
select replace(convert(a.file,string),'','')
from (EXEC Model.getTextFiles('file.csv')) as a
as a workaround but I can't seem to leverage that along with the TEXTTABLE function to provide a usable query... any other thoughts?
> add encoding as "UTF-8-BOM" in the file translator override property
> --------------------------------------------------------------------
>
> Key: TEIID-4340
> URL: https://issues.jboss.org/browse/TEIID-4340
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.7.8.6_2
> Reporter: Debbie Steigner
> Priority: Trivial
> Fix For: Open To Community
>
>
> it will be good if teiid supports Encoding to "UTF-8-BOM" since other middleware technologies supports similar to this and also even editor such as Notepad++ supports to convert / save file as "UTF-8-BOM".
> Currently we have added Translator override for File to include "Encoding Property to UTF-8" so similarly we should be able to set it to "UTF-8-BOM" , instead of writing code manually to add BOM to generate a file.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIID-4340) add encoding as "UTF-8-BOM" in the file translator override property
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4340?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4340:
---------------------------------------
>From the link:
The Unicode Standard permits the BOM in UTF-8,[3] but does not require or recommend its use.[4] Byte order has no meaning in UTF-8,[5] so its only use in UTF-8 is to signal at the start that the text stream is encoded in UTF-8, or that it was converted to UTF-8 from a stream that contained an optional BOM.
You are looking for compatibility with some older windows or other tools that expect a BOM correct?
As for a workaround there aren't great options. A udf would be the best bet to take a file and prepend the BOM.
> add encoding as "UTF-8-BOM" in the file translator override property
> --------------------------------------------------------------------
>
> Key: TEIID-4340
> URL: https://issues.jboss.org/browse/TEIID-4340
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.7.8.6_2
> Reporter: Debbie Steigner
> Priority: Trivial
> Fix For: Open To Community
>
>
> it will be good if teiid supports Encoding to "UTF-8-BOM" since other middleware technologies supports similar to this and also even editor such as Notepad++ supports to convert / save file as "UTF-8-BOM".
> Currently we have added Translator override for File to include "Encoding Property to UTF-8" so similarly we should be able to set it to "UTF-8-BOM" , instead of writing code manually to add BOM to generate a file.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIID-5453) With TransactionSupport set to LOCAL the transaction is not propogated
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5453:
-------------------------------------
Summary: With TransactionSupport set to LOCAL the transaction is not propogated
Key: TEIID-5453
URL: https://issues.jboss.org/browse/TEIID-5453
Project: Teiid
Issue Type: Bug
Components: Connector API, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.1
Setting a translator override with TransactionSupport as LOCAL still allows the work to fork, but the transaction is not propagated / resumed at the connector work item.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIID-5452) Infinispan: Add support @Field annotation as Indexable property
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-5452:
-----------------------------------
Summary: Infinispan: Add support @Field annotation as Indexable property
Key: TEIID-5452
URL: https://issues.jboss.org/browse/TEIID-5452
Project: Teiid
Issue Type: Enhancement
Components: Infinispan
Affects Versions: 10.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 11.1
Add support for @Field annotation as the Indexable property in Infinispan translator. Currently, the code only recognises @Indexed annotation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIID-4340) add encoding as "UTF-8-BOM" in the file translator override property
by Tom Johnston (JIRA)
[ https://issues.jboss.org/browse/TEIID-4340?page=com.atlassian.jira.plugin... ]
Tom Johnston commented on TEIID-4340:
-------------------------------------
[~shawkins] Wondering why this is not needed?
I have csv files that are encoded as such but TO_CHARS(a.file, 'UTF-8-BOM') returns as TEIID30492 Encoding 'UTF-8-BOM' is not valid
Is there some other workaround?
> add encoding as "UTF-8-BOM" in the file translator override property
> --------------------------------------------------------------------
>
> Key: TEIID-4340
> URL: https://issues.jboss.org/browse/TEIID-4340
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.7.8.6_2
> Reporter: Debbie Steigner
> Priority: Trivial
> Fix For: Open To Community
>
>
> it will be good if teiid supports Encoding to "UTF-8-BOM" since other middleware technologies supports similar to this and also even editor such as Notepad++ supports to convert / save file as "UTF-8-BOM".
> Currently we have added Translator override for File to include "Encoding Property to UTF-8" so similarly we should be able to set it to "UTF-8-BOM" , instead of writing code manually to add BOM to generate a file.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months