[
https://issues.jboss.org/browse/TEIID-2896?page=com.atlassian.jira.plugin...
]
Barry LaFond commented on TEIID-2896:
-------------------------------------
So what was not clear to me was what these data files actually look like so the UI
(TEIIDDES-2091) could help users create these *views*
My understanding is that there are standard CSV files and *complex* CSV files
* CSV files contain multiple rows of data containing the same #columns and column data
* complex CSV will contain different *types* of rows, with each type representing a
mini-CSV file format
It appears that you cannot create a TEXTTABLE() statement that crosses *types*, so
Designer would need to help users choose the *type* to create a single *view* as Van just
stated?
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: Enhancement
Components: Query Engine
Reporter: Van Halbert
Assignee: Steven Hawkins
Fix For: 8.7
Attachments: sample, 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 was sent by Atlassian JIRA
(v6.2.3#6260)