[
https://issues.jboss.org/browse/TEIID-2896?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2896:
----------------------------------
Attachment: TEIID-2896.patch
Here's a patch that uses a system property (org.teiid.bestEffortFixed) to control
whether we make a best effort to return data from a fixed row that is too short or whether
we throw an exception (the default).
I don't think that we need this upstream based upon TEIID-2898.
Add TEXTTABLE function capabilities to interpret fixed width data
file content that is shorter than the defined line length
---------------------------------------------------------------------------------------------------------------------------
Key: TEIID-2896
URL:
https://issues.jboss.org/browse/TEIID-2896
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Van Halbert
Attachments: TEIID-2896.patch
Current behavior is that data lines too short to fit a fixed width data interpretation
produces an error such as "Error: Text parse error: Fixed width line width 35 is
smaller than the expected 60 on text line 1 in file:/tmp/file.csv.". The
customer's use case is interpreting data files from another application which bundles
multiple types of data along with additional descriptive info/metadata about the data
contained within the file. As the error is thrown if any lines after the first interpreted
line are shorter than the summed value of the fixed width columns, they are unable to
query the file. The customer wishes for the ERROR to be suppressed and the query to return
the data independent of whether it fits the fixed width criteria and potentially to be
able to filter the data being retrieved.
--
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