April 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1407) Client code fails while inserting "lobs" in few situations

by Ramesh Reddy (JIRA)

Client code fails while inserting "lobs" in few situations ---------------------------------------------------------- Key: TEIID-1407 URL: https://issues.jboss.org/browse/TEIID-1407 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.2, 7.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Critical There were few different lob issues surfaced while inserting a blob into database using the Teiid. 1) Using "javax.sql.rowset.serial.SerialBlob" to construct a blob, and using stmt.setBlob(int, blob) on prepared statement ended up with "broken pipe" error and terminated the client connection when the blob size was bigger than a 1 MB. 2) Using "org.teiid.core.types.ClobImpl" with constructor " new ClobImpl(int, InputStreamFactory)" resulted in the java.io.NotSerializableException: exception. 3) Using simple stmt.setBlob(int, inputstream), also ended up with same java.io.NotSerializableException: exception. Currently only option is to use (1) and making sure that Objects are not bigger than 1 MB. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1372) Change the default Teiid user from "admin" to something else

by Ramesh Reddy (JIRA)

Change the default Teiid user from "admin" to something else ------------------------------------------------------------ Key: TEIID-1372 URL: https://jira.jboss.org/browse/TEIID-1372 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.2 Reporter: Ramesh Reddy Currently Teiid default user is "admin" with password "teiid", also the Admin Console's default user name is "admin" with password "admin". This is a confusion point with users in differentiating the Admin user from default Teiid user. Should consider changing the default user to something else. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

8
11
0 / 0

[JBoss JIRA] Commented: (TEIID-245) Update costing metadata at runtime

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-245?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-245: -------------------------------------- Added the sysadmin setTableStats and setColumnStats, and exposed the null/distinct counts on sys.columns. see the reference and the developers guide for more on runtime updates of metadata. > Update costing metadata at runtime > ---------------------------------- > > Key: TEIID-245 > URL: https://issues.jboss.org/browse/TEIID-245 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Attachments: OracleExecutionFactory.java.patch > > > Defect Tracker #24584: Cost analysis should be both a design-time activity and scheduled/feed during runtime. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1552) Error using EDS ODBC driver with Oracle OBEII tool to import metadata

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-1552?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-1552. --------------------------------- Assignee: Ramesh Reddy Resolution: Cannot Reproduce Bug This particular query issued by the ODBC driver to find out the primary key columns in table. The current code shows that this is correctly being handled. The log shown here is from the OBEII tool, not from the Teiid Server log. With out more information there is not much we can do on this issue. Open again with correct server log. Tested with 7.4 Beta3 > Error using EDS ODBC driver with Oracle OBEII tool to import metadata > ---------------------------------------------------------------------- > > Key: TEIID-1552 > URL: https://issues.jboss.org/browse/TEIID-1552 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.1.1 > Environment: Oracle OBIEE tool on windows, win 32 bit ODBC EDS driver > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Attachments: obiee_error.txt > > > When using the Oracle OBIEE tool to import metadata from EDS using the EDS ODBC windows 32 bit driver, there is an exception when trying to view the column metadata for a table. See attachment for the exception. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1568) Partial Pushdown of WHERE clause columns

by Mark Addleman (JIRA)

Partial Pushdown of WHERE clause columns ---------------------------------------- Key: TEIID-1568 URL: https://issues.jboss.org/browse/TEIID-1568 Project: Teiid Issue Type: Feature Request Reporter: Mark Addleman Assignee: Steven Hawkins We have some exotic data sources that can efficiently support WHERE clause filtering on particular columns + operators combinations but are no better than Teiid for other operation. In particular, suppose I have a data source that supplies columns A and B. The data source can efficiently support A='some value' but may not support A>'value' or A!='value' and does not support efficient processing of column B at all. We would like an enhance supports* protocol to describe the particulars of a data source's capabilities with finer detail. Even partially solving this problem without operator support would be helpful -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1565) Clustered Caching Not Working

by Mark Drilling (JIRA)

Clustered Caching Not Working ----------------------------- Key: TEIID-1565 URL: https://issues.jboss.org/browse/TEIID-1565 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.1.1, 7.2 Reporter: Mark Drilling Assignee: Ramesh Reddy Fix For: 7.4 I have configured two Teiid servers in a cluster and renamed the teiid-cache-manager-jboss-beans-rename-me.xml file to enable clustered caching. I submit a query to one node and see in the log that the internal materialized view is being cached on that node. When I submit the same query to the second node, i see the following error: 12:17:12,040 INFO [MATVIEWS] Loading materialized view table #MAT_CACHED.TEIID.EDS_TAB1_MV 12:17:12,041 WARN [PROCESSOR] Processing exception 'Temporary table "#MAT_CACHED.TEIID.EDS_TAB1_MV" does not exist.' for request BBcYbxuqEAHL.5. Exception type org.teiid.api.exception.query.QueryProcessingException thrown from org.teiid.query.tempdata.TempTableStore.getOrCreateTempTable(TempTableStore.java:220). Enable more detailed logging to see the entire stacktrace. 12:17:12,165 ERROR [MATVIEWS] Failed to load materialized view table #MAT_CACHED.TEIID.EDS_TAB1_MV. [BlockedException] at org.teiid.common.buffer.BlockedException.<clinit>(BlockedException.java:34) at org.teiid.common.buffer.TupleBuffer$1.finalRow(TupleBuffer.java:290) at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:69) at org.teiid.common.buffer.AbstractTupleSource.nextTuple(AbstractTupleSource.java:48) at org.teiid.query.tempdata.TempTable$UpdateProcessor.process(TempTable.java:205) at org.teiid.query.tempdata.TempTable.insert(TempTable.java:446) at org.teiid.query.tempdata.TempTableDataManager.loadGlobalTable(TempTableDataManager.java:516) at org.teiid.query.tempdata.TempTableDataManager.access$100(TempTableDataManager.java:105) at org.teiid.query.tempdata.TempTableDataManager$2.call(TempTableDataManager.java:443) at org.teiid.query.tempdata.TempTableDataManager$2.call(TempTableDataManager.java:440) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Case:00451425 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-245) Update costing metadata at runtime

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-245?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-245: --------------------------------- Attachment: OracleExecutionFactory.java.patch Possible stat gathering implemented for Oracle > Update costing metadata at runtime > ---------------------------------- > > Key: TEIID-245 > URL: https://issues.jboss.org/browse/TEIID-245 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Attachments: OracleExecutionFactory.java.patch > > > Defect Tracker #24584: Cost analysis should be both a design-time activity and scheduled/feed during runtime. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1558) Salesforce Connector gives NPE when the resultset is empty

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1558?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1558. ----------------------------------- Resolution: Done The sf connection retrieve method was not filtering null records from the results. > Salesforce Connector gives NPE when the resultset is empty > ---------------------------------------------------------- > > Key: TEIID-1558 > URL: https://issues.jboss.org/browse/TEIID-1558 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 7.4 > > Attachments: Salesforce_ModelProjectSet.zip > > > When querying a Relational Model created from the Salesforce importer and the criteria returns zero rows, instead of an empty resultset a Null Pointer Exception is given. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1558) Salesforce Connector gives NPE when the resultset is empty

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1558?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1558: ---------------------------------- Assignee: Steven Hawkins Fix Version/s: 7.4 > Salesforce Connector gives NPE when the resultset is empty > ---------------------------------------------------------- > > Key: TEIID-1558 > URL: https://issues.jboss.org/browse/TEIID-1558 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 7.4 > > Attachments: Salesforce_ModelProjectSet.zip > > > When querying a Relational Model created from the Salesforce importer and the criteria returns zero rows, instead of an empty resultset a Null Pointer Exception is given. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1558) Salesforce Connector gives NPE when the resultset is empty

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1558?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-3029 to TEIID-1558: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1558 (was: SOA-3029) Affects Version/s: 7.1.1 (was: 5.1.0 GA) Component/s: Salesforce Connector (was: EDS) Security: (was: Public) > Salesforce Connector gives NPE when the resultset is empty > ---------------------------------------------------------- > > Key: TEIID-1558 > URL: https://issues.jboss.org/browse/TEIID-1558 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Attachments: Salesforce_ModelProjectSet.zip > > > When querying a Relational Model created from the Salesforce importer and the criteria returns zero rows, instead of an empty resultset a Null Pointer Exception is given. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2011