So if you have an example of how you accomplished this, it would be appreciated. A column SELECTOR is not valid with fixed width parsing.

As for the test case, you add null to the end of the line, but in the sample file attached, the actual null column is in the middle.

and part of the problem with the sample is, each type has a different fixed width.

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.