August 2014 - teiid-issues - Jboss List Archives

[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 commented on TEIID-3091: ------------------------------------- 1 = Header Row 2 = Data Row It does, that is how you got results from above image. If you are using squirrel take the LIMIT clause off and try to see the results. > 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)

10 years, 4 months

1
0
0 / 0

[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: ------------------------------------ Looking at the attached screen shot, the 1st row results contain the column headings (first name, last name, age) from the xls file. But the FIRST_DATA_ROW_NUMBER is set to 2. So I would have thought the results would have excluded the 1st row column names in the results. > 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)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3092) error with xml project minimization

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3092?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3092. ----------------------------------- Resolution: Done Corrected to not change the state of the parent member. > 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)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3081) Correct test errors with Java 8

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3081?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3081. ----------------------------------- Resolution: Done Updated mostly map usage logic to ensure expected behavior. > Correct test errors with Java 8 > ------------------------------- > > Key: TEIID-3081 > URL: https://issues.jboss.org/browse/TEIID-3081 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Common > Affects Versions: 8.8 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > When running with a Java 8 vm there are test errors. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3061) MongoDB: Support VARBINARY type

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3061?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3061. --------------------------------- Labels: Alpha2 (was: ) Fix Version/s: 8.7.1 Resolution: Done Added support for mapping BINARY data type of MongoDB to VARBINARY type in Teiid. Previously it was read as object. If dynamic VDB with schema import was used it was mapped to Blob. Now this will map to varbinary. Caution needs to be taken by the user of this type to make sure the size does not exceed 8K per document, if it does then converting this data type to a Blob will resolve any memory issues. That can be done by overriding the schema retrieved at deployment time and defining the schema directly using DDL or using Teiid Designer. However, if blob is used, if you write data though this translator then they will be stored to GridFS. If needed, a enhancement can be added to store the Blob data as Binary data. See https://docs.jboss.org/author/display/TEIID/Supported+Types > MongoDB: Support VARBINARY type > ------------------------------- > > Key: TEIID-3061 > URL: https://issues.jboss.org/browse/TEIID-3061 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.7.1, 8.9 > > > Map BinData structure of MongoDB to Teiid's VarBinary type, and MAP VARBINARY to byte[]. Correct the import time byte[] to VARBINARY instead of blob. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3089) TEIID10078 Invalid double format in String: Age

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3089?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3089: ------------------------------------- The issue was when limit clause is present without the offset, it was overwriting the first data row property that has been set, thus ending up in error. Also the offset processing in the testcase was wrong, it should be relative to the resultset not to the rows number of excel sheet. Also adjusted code such that if any row with all nulls are encountered, then it will be considered as terminal row, and no rows after that row will be read. > TEIID10078 Invalid double format in String: Age > ----------------------------------------------- > > Key: TEIID-3089 > URL: https://issues.jboss.org/browse/TEIID-3089 > 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 > Labels: Alpha2 > Fix For: 8.7.1, 8.9 > > Attachments: otherholdings.xls > > > Seeing the following error when querying attached excel file: > TEIID10078 Invalid double format in String: Age -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3089) TEIID10078 Invalid double format in String: Age

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3089?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3089. --------------------------------- Labels: Alpha2 (was: ) Fix Version/s: 8.7.1 8.9 Resolution: Done > TEIID10078 Invalid double format in String: Age > ----------------------------------------------- > > Key: TEIID-3089 > URL: https://issues.jboss.org/browse/TEIID-3089 > 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 > Labels: Alpha2 > Fix For: 8.7.1, 8.9 > > Attachments: otherholdings.xls > > > Seeing the following error when querying attached excel file: > TEIID10078 Invalid double format in String: Age -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[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 commented on TEIID-3091: ------------------------------------- The additional nulls I have addressed in TEIID-3089, but I do not understand the premise of this JIRA. You say option is not working and the attachment shows all the results. Can you explain why you think the FIRST_DATA_ROW_NUMBER option is not working? > 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)

10 years, 4 months

1
0
0 / 0

[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 reassigned TEIID-3091: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > 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: > <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)

10 years, 4 months

1
0
0 / 0

[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)

10 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2014