[
https://issues.jboss.org/browse/TEIIDDES-2091?page=com.atlassian.jira.plu...
]
Steven Hawkins updated TEIIDDES-2091:
-------------------------------------
Issue Type: Enhancement (was: Feature Request)
Description:
From TEIID-2898: To allow for fixed width files containing multiple
record types, the selector functionality should apply to fixed width as well. At least
initially this will be restricted to only the overall selector as positional selector
column references won't be possible. See the reference for more:
https://docs.jboss.org/author/display/TEIID/FROM+Clause#FROMClause-TEXTTABLE
Also from TEIID-2896 fixed width parsing will now make an effort to parse lines that are
too short, rather than immediately throwing an exception. If there is designer logic with
that limitation, it should be lifted.
was:To allow for fixed width files containing multiple record types, the selector
functionality should apply to fixed width as well. At least initially this will be
restricted to only the overall selector as positional selector column references won't
be possible.
Assignee: (was: Steven Hawkins)
Component/s: Modeling
Allow selector to be used with fixed width
------------------------------------------
Key: TEIIDDES-2091
URL:
https://issues.jboss.org/browse/TEIIDDES-2091
Project: Teiid Designer
Issue Type: Enhancement
Components: Modeling
Reporter: Van Halbert
From TEIID-2898: To allow for fixed width files containing multiple record types, the
selector functionality should apply to fixed width as well. At least initially this will
be restricted to only the overall selector as positional selector column references
won't be possible. See the reference for more:
https://docs.jboss.org/author/display/TEIID/FROM+Clause#FROMClause-TEXTTABLE
Also from TEIID-2896 fixed width parsing will now make an effort to parse lines that are
too short, rather than immediately throwing an exception. If there is designer logic with
that limitation, it should be lifted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira