[JBoss JIRA] (TEIID-3091) Excel translator issue: FIRST_DATA_ROW_NUMBER option not working
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3091?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-3091:
--------------------------------
Description:
The FIRST_DATA_ROW_NUMBER option not working, seeing the first row in the results, when using the following dynamic VDB definition:
{code}
<model name="OtherHoldings">
<property name="importer.headerRowNumber" value="1"/>
<property name="importer.ExcelFileName" value="otherholdings.xls"/>
<source name="excelconnector" translator-name="excel" connection-jndi-name="java:/excel-file"/>
<metadata type="DDL"><![CDATA[
SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel;
CREATE FOREIGN TABLE Sheet1 (
ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'),
FirstName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'),
LastName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'),
Age string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'),
CONSTRAINT PK0 PRIMARY KEY(ROW_ID)
) OPTIONS ("teiid_excel:FILE" 'otherholdings.xls', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2');
]]> </metadata>
</model>
{code}
was:
The FIRST_DATA_ROW_NUMBER option not working, seeing the first row in the results, when using the following dynamic VDB definition:
<model name="OtherHoldings">
<property name="importer.headerRowNumber" value="1"/>
<property name="importer.ExcelFileName" value="otherholdings.xls"/>
<source name="excelconnector" translator-name="excel" connection-jndi-name="java:/excel-file"/>
<metadata type="DDL"><![CDATA[
SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel;
CREATE FOREIGN TABLE Sheet1 (
ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'),
FirstName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'),
LastName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'),
Age string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'),
CONSTRAINT PK0 PRIMARY KEY(ROW_ID)
) OPTIONS ("teiid_excel:FILE" 'otherholdings.xls', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2');
]]> </metadata>
</model>
> Excel translator issue: FIRST_DATA_ROW_NUMBER option not working
> -----------------------------------------------------------------
>
> Key: TEIID-3091
> URL: https://issues.jboss.org/browse/TEIID-3091
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Attachments: excel_row_number_issue.tiff
>
>
> The FIRST_DATA_ROW_NUMBER option not working, seeing the first row in the results, when using the following dynamic VDB definition:
> {code}
> <model name="OtherHoldings">
> <property name="importer.headerRowNumber" value="1"/>
> <property name="importer.ExcelFileName" value="otherholdings.xls"/>
> <source name="excelconnector" translator-name="excel" connection-jndi-name="java:/excel-file"/>
> <metadata type="DDL"><![CDATA[
> SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel;
> CREATE FOREIGN TABLE Sheet1 (
> ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'),
> FirstName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'),
> LastName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'),
> Age string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'),
> CONSTRAINT PK0 PRIMARY KEY(ROW_ID)
> ) OPTIONS ("teiid_excel:FILE" 'otherholdings.xls', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2');
> ]]> </metadata>
> </model>
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 7 months
[JBoss JIRA] (TEIID-3092) error with xml project minimization
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3092:
-------------------------------------
Summary: error with xml project minimization
Key: TEIID-3092
URL: https://issues.jboss.org/browse/TEIID-3092
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Query Engine
Affects Versions: 8.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7.1, 8.9
The project minimization logic will not look at the appropriate parent chain for each binding and can result in dropping columns that are used from the query which would be seen at runtime as a value not available from context exception. This became apparent with TEIID-3081 where the map order changed in different vms.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 7 months
[JBoss JIRA] (TEIID-3091) Excel translator issue: FIRST_DATA_ROW_NUMBER option not working
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3091?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-3091:
-------------------------------
Attachment: excel_row_number_issue.tiff
> Excel translator issue: FIRST_DATA_ROW_NUMBER option not working
> -----------------------------------------------------------------
>
> Key: TEIID-3091
> URL: https://issues.jboss.org/browse/TEIID-3091
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Attachments: excel_row_number_issue.tiff
>
>
> The FIRST_DATA_ROW_NUMBER option not working, seeing the first row in the results, when using the following dynamic VDB definition:
> <model name="OtherHoldings">
> <property name="importer.headerRowNumber" value="1"/>
> <property name="importer.ExcelFileName" value="otherholdings.xls"/>
> <source name="excelconnector" translator-name="excel" connection-jndi-name="java:/excel-file"/>
> <metadata type="DDL"><![CDATA[
> SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel;
> CREATE FOREIGN TABLE Sheet1 (
> ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'),
> FirstName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'),
> LastName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'),
> Age string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'),
> CONSTRAINT PK0 PRIMARY KEY(ROW_ID)
> ) OPTIONS ("teiid_excel:FILE" 'otherholdings.xls', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2');
>
> ]]> </metadata>
> </model>
>
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 7 months
[JBoss JIRA] (TEIID-3091) Excel translator issue: FIRST_DATA_ROW_NUMBER option not working
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3091?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3091:
------------------------------------
Also note in the attached image, that the results are also include additional NULL rows.
> Excel translator issue: FIRST_DATA_ROW_NUMBER option not working
> -----------------------------------------------------------------
>
> Key: TEIID-3091
> URL: https://issues.jboss.org/browse/TEIID-3091
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Attachments: excel_row_number_issue.tiff
>
>
> The FIRST_DATA_ROW_NUMBER option not working, seeing the first row in the results, when using the following dynamic VDB definition:
> <model name="OtherHoldings">
> <property name="importer.headerRowNumber" value="1"/>
> <property name="importer.ExcelFileName" value="otherholdings.xls"/>
> <source name="excelconnector" translator-name="excel" connection-jndi-name="java:/excel-file"/>
> <metadata type="DDL"><![CDATA[
> SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel;
> CREATE FOREIGN TABLE Sheet1 (
> ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'),
> FirstName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'),
> LastName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'),
> Age string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'),
> CONSTRAINT PK0 PRIMARY KEY(ROW_ID)
> ) OPTIONS ("teiid_excel:FILE" 'otherholdings.xls', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2');
>
> ]]> </metadata>
> </model>
>
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 7 months
[JBoss JIRA] (TEIID-3091) Excel translator issue: FIRST_DATA_ROW_NUMBER option not working
by Van Halbert (JIRA)
Van Halbert created TEIID-3091:
----------------------------------
Summary: Excel translator issue: FIRST_DATA_ROW_NUMBER option not working
Key: TEIID-3091
URL: https://issues.jboss.org/browse/TEIID-3091
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Misc. Connectors
Affects Versions: 8.7.1
Reporter: Van Halbert
Assignee: Steven Hawkins
The FIRST_DATA_ROW_NUMBER option not working, seeing the first row in the results, when using the following dynamic VDB definition:
<model name="OtherHoldings">
<property name="importer.headerRowNumber" value="1"/>
<property name="importer.ExcelFileName" value="otherholdings.xls"/>
<source name="excelconnector" translator-name="excel" connection-jndi-name="java:/excel-file"/>
<metadata type="DDL"><![CDATA[
SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel;
CREATE FOREIGN TABLE Sheet1 (
ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'),
FirstName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'),
LastName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'),
Age string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'),
CONSTRAINT PK0 PRIMARY KEY(ROW_ID)
) OPTIONS ("teiid_excel:FILE" 'otherholdings.xls', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2');
]]> </metadata>
</model>
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 7 months
[JBoss JIRA] (TEIID-3090) Unexpected exception for correct SQL query
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3090?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3090:
-------------------------------------
Also try with MySQL JDBC driver instead of MariaDB driver.
> Unexpected exception for correct SQL query
> ------------------------------------------
>
> Key: TEIID-3090
> URL: https://issues.jboss.org/browse/TEIID-3090
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7
> Environment: OS: Fedora 20
> hardware: x86_64
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Attachments: exception-stack-trace, full-server.log, server.log
>
>
> Description of problem:
> Query ends with exception. Same query for MariaDB database returns correct result but Teiid throws an exception.
> Actual results:
> Query ends with exception - TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 Source: Unexpected exception while translating results: Error
> Expected results:
> No exception
> Additional info:
> excption stack trace and server log in attachment
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 7 months
[JBoss JIRA] (TEIID-3090) Unexpected exception for correct SQL query
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3090?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3090:
---------------------------------------
It looks like an issue with the mariadb support for getTimestamp - more than likely https://mariadb.atlassian.net/browse/CONJ-88
As 1.1.8 hasn't been released yet, we'd have to offer a workaround. The simplest is to must model the source column as a string value instead.
> Unexpected exception for correct SQL query
> ------------------------------------------
>
> Key: TEIID-3090
> URL: https://issues.jboss.org/browse/TEIID-3090
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7
> Environment: OS: Fedora 20
> hardware: x86_64
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Attachments: exception-stack-trace, full-server.log, server.log
>
>
> Description of problem:
> Query ends with exception. Same query for MariaDB database returns correct result but Teiid throws an exception.
> Actual results:
> Query ends with exception - TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 Source: Unexpected exception while translating results: Error
> Expected results:
> No exception
> Additional info:
> excption stack trace and server log in attachment
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 7 months
[JBoss JIRA] (TEIID-3090) Unexpected exception for correct SQL query
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3090?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3090:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1131091
> Unexpected exception for correct SQL query
> ------------------------------------------
>
> Key: TEIID-3090
> URL: https://issues.jboss.org/browse/TEIID-3090
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7
> Environment: OS: Fedora 20
> hardware: x86_64
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Attachments: exception-stack-trace, full-server.log, server.log
>
>
> Description of problem:
> Query ends with exception. Same query for MariaDB database returns correct result but Teiid throws an exception.
> Actual results:
> Query ends with exception - TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 Source: Unexpected exception while translating results: Error
> Expected results:
> No exception
> Additional info:
> excption stack trace and server log in attachment
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 7 months