July 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3023) records lost when query by hiernate

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3023?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3023: --------------------------------------- Without knowing the hibernate query issued to Teiid and the corresponding query plan, it's not really possible to say what is occurring here. We can leave this open for a while, but will resolve as incomplete without additional information. > records lost when query by hiernate > ----------------------------------- > > Key: TEIID-3023 > URL: https://issues.jboss.org/browse/TEIID-3023 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 7.3 > Environment: window7,eclipse Helios Service Release 2, Teiid v7.3.0 > Reporter: Lai Chao > Priority: Minor > > Recently, I get an issue when retrieve data from vdb that some records lost in the list. Fox example, from source table we can get 12100 records, but from vdb query(projects with hibernate) can only get 10800+ records. > Meanwhile, there's a set on maxSetSize = 1000, is there any affects? > Please advise. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3024) QueryTimeout not working for synchronous local queries against Teiid

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3024?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3024: ---------------------------------- Summary: QueryTimeout not working for synchronous local queries against Teiid (was: QueryTimeout not working for synchronous queries against Teiid) > QueryTimeout not working for synchronous local queries against Teiid > -------------------------------------------------------------------- > > Key: TEIID-3024 > URL: https://issues.jboss.org/browse/TEIID-3024 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JDBC Driver > Affects Versions: 8.1, 8.7 > Reporter: gaurav singhal > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > Attachments: query timeout bug.zip > > > If i run a query with synchronous query with a timeout set using PreparedStatementImpl.setQueryTimeout() method, that timeout is not honored. But if i run the same query with all the same setup and execute the query asynchronously then a timeout happens and warning message like below is printed: > > Jul 02, 2014 10:19:21 AM org.teiid.jdbc.StatementImpl timeoutOccurred > WARNING: Timeout occurred in Statement. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3023) records lost when query by hiernate

by Lai Chao (JIRA)

[ https://issues.jboss.org/browse/TEIID-3023?page=com.atlassian.jira.plugin... ] Lai Chao commented on TEIID-3023: --------------------------------- Thanks for reply. I know the Teiid version is out of date, I'll suggest to upgrade it. However, this only happened in production enviroment with large amount data, and I can't get the hibernate query plan. > records lost when query by hiernate > ----------------------------------- > > Key: TEIID-3023 > URL: https://issues.jboss.org/browse/TEIID-3023 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 7.3 > Environment: window7,eclipse Helios Service Release 2, Teiid v7.3.0 > Reporter: Lai Chao > Priority: Minor > > Recently, I get an issue when retrieve data from vdb that some records lost in the list. Fox example, from source table we can get 12100 records, but from vdb query(projects with hibernate) can only get 10800+ records. > Meanwhile, there's a set on maxSetSize = 1000, is there any affects? > Please advise. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3026) NPE using Excel translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3026?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3026. --------------------------------- Fix Version/s: 8.7.1 8.8 Resolution: Done There couple issues I found - When there is empty sheet next to correct sheet, the translator tries to read metadata at header row defined, however that always returns a null, thus NPE. Added validation to check for null. - Also, when header is not found the translator scans the rows to find the header row, and there is no max how many row this will scan. So, the code was scanning rows well after 1M+ giving impression the thread is locked. Limited the header row scan to 10K. If the header is not found in first 10K rows the scan is aborted - The header and data row numbers in POI is zero indexed, in excel sheet they are 1 based. Added code such that if user incorrectly used 0 based, translator does not compute negative values > NPE using Excel translator > -------------------------- > > Key: TEIID-3026 > URL: https://issues.jboss.org/browse/TEIID-3026 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.8 > > > {code} > 10:48:26,620 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:java.lang.NullPointerException: java.lang.NullPointerException > at org.teiid.translator.excel.ExcelMetadataProcessor.addTable(ExcelMetadataProcessor.java:106) > at org.teiid.translator.excel.ExcelMetadataProcessor.process(ExcelMetadataP > rocessor.java:87) > at org.teiid.translator.excel.ExcelMetadataProcessor.process(ExcelMetadataProcessor.java:45) > at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:915) [teiid-api-8.7.0.Final.jar:8.7.0.Final] > at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:73) [teiid-engine-8.7.0.Final.jar:8.7.0.Final] > at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.7.0.Final.jar:8.7.0.Final] > at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.7.0.Final.jar:8.7.0.Final] > at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.7.0.Final.jar:8.7.0.Final] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3026) NPE using Excel translator

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3026: ----------------------------------- Summary: NPE using Excel translator Key: TEIID-3026 URL: https://issues.jboss.org/browse/TEIID-3026 Project: Teiid Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ramesh Reddy Assignee: Ramesh Reddy {code} 10:48:26,620 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:java.lang.NullPointerException: java.lang.NullPointerException at org.teiid.translator.excel.ExcelMetadataProcessor.addTable(ExcelMetadataProcessor.java:106) at org.teiid.translator.excel.ExcelMetadataProcessor.process(ExcelMetadataP rocessor.java:87) at org.teiid.translator.excel.ExcelMetadataProcessor.process(ExcelMetadataProcessor.java:45) at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:915) [teiid-api-8.7.0.Final.jar:8.7.0.Final] at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:73) [teiid-engine-8.7.0.Final.jar:8.7.0.Final] at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.7.0.Final.jar:8.7.0.Final] at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.7.0.Final.jar:8.7.0.Final] at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.7.0.Final.jar:8.7.0.Final] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] at org.jboss.threads.JBossThread.run(JBossThread.java:122) {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3025) Issues with sorting by a subquery

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3025?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3025. ----------------------------------- Resolution: Done Kept the rewrite clone logic, but updated other code paths to generally plan subqueries in the order by clause. > Issues with sorting by a subquery > --------------------------------- > > Key: TEIID-3025 > URL: https://issues.jboss.org/browse/TEIID-3025 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > We have issues with processing subqueries in the order by clause (either directly through an unrelated column, or indirectly through the select clause). The pushdown processing can fail with an AssertionError during with the languagebridgefactory, while the engine processing can fail with a NPE during the evaluation rewrite. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3025) Issues with sorting by a subquery

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3025: ------------------------------------- Summary: Issues with sorting by a subquery Key: TEIID-3025 URL: https://issues.jboss.org/browse/TEIID-3025 Project: Teiid Issue Type: Bug Security Level: Public (Everyone can see) Components: Query Engine Affects Versions: 8.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7.1, 8.8 We have issues with processing subqueries in the order by clause (either directly through an unrelated column, or indirectly through the select clause). The pushdown processing can fail with an AssertionError during with the languagebridgefactory, while the engine processing can fail with a NPE during the evaluation rewrite. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3020) Materialized View timeout on loading

by Mark Addleman (JIRA)

[ https://issues.jboss.org/browse/TEIID-3020?page=com.atlassian.jira.plugin... ] Mark Addleman closed TEIID-3020. -------------------------------- Resolution: Won't Fix Current behavior is correct > Materialized View timeout on loading > ------------------------------------ > > Key: TEIID-3020 > URL: https://issues.jboss.org/browse/TEIID-3020 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Addleman > Assignee: Steven Hawkins > > Materialized view should timeout on loading if the translator/data source takes too long to respond. > Perhaps time out when the initiating JDBC statement times out or is cancelled? > See https://community.jboss.org/thread/242372 for more info -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3020) Materialized View timeout on loading

by Mark Addleman (JIRA)

[ https://issues.jboss.org/browse/TEIID-3020?page=com.atlassian.jira.plugin... ] Mark Addleman commented on TEIID-3020: -------------------------------------- No. Closing the issue > Materialized View timeout on loading > ------------------------------------ > > Key: TEIID-3020 > URL: https://issues.jboss.org/browse/TEIID-3020 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Addleman > Assignee: Steven Hawkins > > Materialized view should timeout on loading if the translator/data source takes too long to respond. > Perhaps time out when the initiating JDBC statement times out or is cancelled? > See https://community.jboss.org/thread/242372 for more info -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3024) QueryTimeout not working for synchronous queries against Teiid

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3024?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3024. ----------------------------------- Fix Version/s: 8.7.1 8.8 Resolution: Done Updated the client timeout to be processed for local synch queries. Also refined the handling of the server side exception produced in the event of a cancel. > could the local connections be made to work the same way as socked based connections? There is a server side timeout that can be set for all queries. See the query-timeout vdb property - https://docs.jboss.org/author/display/TEIID/VDB+Definition Otherwise, no this code fix is needed. > Also does teiid use a localconnection to materialize a view thats marked to be materialized? I think you are relating this to https://issues.jboss.org/browse/TEIID-3020 Anything specific to materialization should go on that issue. > QueryTimeout not working for synchronous queries against Teiid > --------------------------------------------------------------- > > Key: TEIID-3024 > URL: https://issues.jboss.org/browse/TEIID-3024 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JDBC Driver > Affects Versions: 8.1, 8.7 > Reporter: gaurav singhal > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > Attachments: query timeout bug.zip > > > If i run a query with synchronous query with a timeout set using PreparedStatementImpl.setQueryTimeout() method, that timeout is not honored. But if i run the same query with all the same setup and execute the query asynchronously then a timeout happens and warning message like below is printed: > > Jul 02, 2014 10:19:21 AM org.teiid.jdbc.StatementImpl timeoutOccurred > WARNING: Timeout occurred in Statement. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2014