[JBoss JIRA] (TEIID-3093) SOLR: Translator ignores "Name In Source" attribute of table columns
by Filip Elias (JIRA)
Filip Elias created TEIID-3093:
----------------------------------
Summary: SOLR: Translator ignores "Name In Source" attribute of table columns
Key: TEIID-3093
URL: https://issues.jboss.org/browse/TEIID-3093
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Misc. Connectors
Affects Versions: 8.7
Reporter: Filip Elias
Assignee: Steven Hawkins
When I create a source model in teiid designer and I specify "Name In Source" attribute in one of the table columns, SOLR translator will ignore the "Name In Source" attribute and it will use a column name to create SOLR query.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 7 months
[JBoss JIRA] (TEIID-3074) NPE When using External Materialization management is use
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3074?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3074:
---------------------------------------
Yes a fix is needed there are non-deterministic non-serial subqueries should work, so leave this open for now.
> NPE When using External Materialization management is use
> ---------------------------------------------------------
>
> Key: TEIID-3074
> URL: https://issues.jboss.org/browse/TEIID-3074
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 8.5
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Attachments: debug_plan.txt, solr-integration-with-matview-vdb.xml
>
>
> When I was issuing query that has externalized materialization with management option to true, I am seeing NPE. Tried to see why NPE is occurring was not able to figure out (yet)
> {code}
> 14:37:50,269 ERROR [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue8477) 0z97J5OWq7x9 Connector worker process failed for atomic-request=0z97J5OWq7x9.7.1.4220: java.lang.NullPointerException
> at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:338)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:385) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:203) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:301) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}
--
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 Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3091?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3091.
---------------------------------
Resolution: Duplicate Issue
> 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.png, excel_row_number_issue.tiff, otherholdings.xls, portfolio-vdb.xml
>
>
> 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-3074) NPE When using External Materialization management is use
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3074?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3074:
-------------------------------------
command deteministic did the trick, now I get results without NPE. Is there anything needs to be done for the non deterministic case?
> NPE When using External Materialization management is use
> ---------------------------------------------------------
>
> Key: TEIID-3074
> URL: https://issues.jboss.org/browse/TEIID-3074
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 8.5
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Attachments: debug_plan.txt, solr-integration-with-matview-vdb.xml
>
>
> When I was issuing query that has externalized materialization with management option to true, I am seeing NPE. Tried to see why NPE is occurring was not able to figure out (yet)
> {code}
> 14:37:50,269 ERROR [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue8477) 0z97J5OWq7x9 Connector worker process failed for atomic-request=0z97J5OWq7x9.7.1.4220: java.lang.NullPointerException
> at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:338)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:385) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:203) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:301) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 7 months
[JBoss JIRA] (TEIID-2875) Metadata failed to load. No column found
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2875?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2875:
---------------------------------------
There hasn't been an update on this in a while. We may want to update VDBService logic in any case to log the full exception so that it's easier to determine where the problem is coming from.
> Metadata failed to load. No column found
> ----------------------------------------
>
> Key: TEIID-2875
> URL: https://issues.jboss.org/browse/TEIID-2875
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.6
> Environment: Windows server 2003, Windows 7.
> Reporter: SHI HONG CHIN
> Assignee: Steven Hawkins
> Attachments: JakkerData-vdb.xml
>
>
> Affected database: Oracle
> The following error displayed when Teiid loading a dynamic VDB:
> 10:21:41,458 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column found with name "RATE"."CHARGE_NAME"
> 10:23:29,994 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column found with name "RATE"."CHARGE_NAME"
> I am not the one who design the database. But, I cannot find any table with above mentioned column name in Oracle database. So, I am not sure whether the above mentioned column name is a hidden column or not.
> This bug does not exist in version 8.5.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 7 months