Bug 1180641 - Flat file import does not set File Encoding translator override on source model
Summary: Flat file import does not set File Encoding translator override on source model
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Tooling
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Barry LaFond
QA Contact: Andrej Smigala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-09 15:47 UTC by Andrej Smigala
Modified: 2016-02-05 08:07 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-02-05 08:07:03 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIIDDES-2421 0 Minor Open Flat file import does not set File Encoding translator override on source model 2018-01-30 20:51:05 UTC

Description Andrej Smigala 2015-01-09 15:47:43 UTC 
When importing from flat file with connection profile that has a file encoding specified, that file encoding is not set as a Translator Override on the source model. A workaround is to set it manually.

1. Create a new flat file connection profile, set the flatfile charset to windows-1250
2. Import any file using the new connection profile
3. Edit translator overrides on the newly created source model, notice File Encoding is UTF-8 (or whatever the OS's default is)
Comment 2 Barry LaFond 2015-03-25 11:36:53 UTC 
There is a workaround. Recommend pushing to DV 6.3
Comment 3 Matus Makovy 2016-02-05 08:07:03 UTC 
Closing this since we are tracking issues for tooling only in JIRA from now on.
Note You need to log in before you can comment on or make changes to this bug.