April 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3446) NumberFormatException By Oracle during metadata import

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3446: ----------------------------------- Summary: NumberFormatException By Oracle during metadata import Key: TEIID-3446 URL: https://issues.jboss.org/browse/TEIID-3446 Project: Teiid Issue Type: Bug Components: JDBC Connector Reporter: Ramesh Reddy Assignee: Steven Hawkins When dealing with very high cardinatlity in Oracle source table, during the metadata retrieval in JDBC translator the driver throws a NumberFormatException. The largest table has 6 Billion rows -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3445) StackOverflowError on TempTableStore.getTempTable()

by Mark Addleman (JIRA)

Mark Addleman created TEIID-3445: ------------------------------------ Summary: StackOverflowError on TempTableStore.getTempTable() Key: TEIID-3445 URL: https://issues.jboss.org/browse/TEIID-3445 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 8.10 Reporter: Mark Addleman Assignee: Steven Hawkins Below is a log snippet (working on getting the full plan) for a StackOverflowError on TempTableStore.getTempTable(): Exception processin contiuous query begin insert into #mom_collectors select * from (call mom.connected_collectors()) t; insert into #apm_collectors select * from (call apm_server.connected_collectors()) t; select 'add', hostname, port, id from #mom_collectors where (hostname, port) not in (select (hostname, port) from #apm_collectors) union select 'delete', hostname, port, id from #apm_collectors where (hostname, port) not in (select (hostname, port) from #mom_collectors) with return; end org.teiid.jdbc.TeiidSQLException: org.teiid.core.TeiidException at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135) at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71) at org.teiid.jdbc.ResultSetImpl.processBatch(ResultSetImpl.java:425) at org.teiid.jdbc.ResultSetImpl.access$000(ResultSetImpl.java:64) at org.teiid.jdbc.ResultSetImpl$1.onCompletion(ResultSetImpl.java:242) at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:135) at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:40) at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:79) at org.teiid.dqp.internal.process.RequestWorkItem.sendError(RequestWorkItem.java:1056) at org.teiid.dqp.internal.process.RequestWorkItem.close(RequestWorkItem.java:563) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:363) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:265) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.j ava:119) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.teiid.core.TeiidException at org.teiid.client.ResultsMessage.setException(ResultsMessage.java:196) at org.teiid.dqp.internal.process.RequestWorkItem.sendError(RequestWorkItem.java:1054) ... 10 more Caused by: java.lang.StackOverflowError at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) at org.teiid.query.tempdata.TempTableStore.getTempTable(TempTableStore.java:614) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3444) Add the model properties as extension metadata on the schema

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3444: ------------------------------------- Summary: Add the model properties as extension metadata on the schema Key: TEIID-3444 URL: https://issues.jboss.org/browse/TEIID-3444 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.11 To provide an ability to set extension metadata on the schema we would either need to introduce a new ddl construct or let the existing model property functionality be used. To promote a single mechanism it seems good to let the model properties be injected onto the schema object as extension metadata. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3434) Ability to enable/disable caching by table and/or source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3434?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3434: --------------------------------------- Materialization ttl (defined on the relevant view) affects just the refresh strategy of the materialization table. This is for result set cache entries and would be set on source tables. You could bridge the two by computing automatically computing a ttl for a materialized view, but it makes more sense to me to leave that explicit. > Ability to enable/disable caching by table and/or source > -------------------------------------------------------- > > Key: TEIID-3434 > URL: https://issues.jboss.org/browse/TEIID-3434 > Project: Teiid > Issue Type: Feature Request > Reporter: Burak Serdar > Assignee: Steven Hawkins > Fix For: 8.11 > > > We need to be able to enable/disable caching by table and/or source. Some of our tables have real-time data, and we do not want to cache those, and some other tables can use cached data. It is not sufficient to use SQL options to turn caching on or off, because we're using 3rd party tools, and we don't have control over the SQL they generate. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3434) Ability to enable/disable caching by table and/or source

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3434?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3434: ------------------------------------- How is this different from materialization TTL? Is this only scoped to the user query? > Ability to enable/disable caching by table and/or source > -------------------------------------------------------- > > Key: TEIID-3434 > URL: https://issues.jboss.org/browse/TEIID-3434 > Project: Teiid > Issue Type: Feature Request > Reporter: Burak Serdar > Assignee: Steven Hawkins > Fix For: 8.11 > > > We need to be able to enable/disable caching by table and/or source. Some of our tables have real-time data, and we do not want to cache those, and some other tables can use cached data. It is not sufficient to use SQL options to turn caching on or off, because we're using 3rd party tools, and we don't have control over the SQL they generate. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3434) Ability to enable/disable caching by table and/or source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3434?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3434: --------------------------------------- Added the extension property teiid_rel:data-ttl that will be examined for each table/source contributing to result set cache entry. The least non-zero entry will be used as the ttl (or the lesser or the cache hint ttl). A zero value indicates that entries accessing that table/source should not be cached. An issue with this approach is that we don't have in ddl a way to set a property on the schema (I'm not sure if designer will allow that either, but the current index metadata logic supports it). We also have model properties that fill the same role. So for this to work at a schema level may require a new ddl construct. > Ability to enable/disable caching by table and/or source > -------------------------------------------------------- > > Key: TEIID-3434 > URL: https://issues.jboss.org/browse/TEIID-3434 > Project: Teiid > Issue Type: Feature Request > Reporter: Burak Serdar > Assignee: Steven Hawkins > Fix For: 8.11 > > > We need to be able to enable/disable caching by table and/or source. Some of our tables have real-time data, and we do not want to cache those, and some other tables can use cached data. It is not sufficient to use SQL options to turn caching on or off, because we're using 3rd party tools, and we don't have control over the SQL they generate. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3412) Change MS Access to use jackcess, since ODBC-JDBC bridge is removed in JDK 1.8

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3412?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3412: --------------------------------------- Committed the pull request and removed the blob handling. If there is a need to copy blob values, there is an existing setting property called copyLobs (which can be defaulted to true if needed. Can you describe under what circumstances or why the blob values need to be copied, their potential size, etc.? > Change MS Access to use jackcess, since ODBC-JDBC bridge is removed in JDK 1.8 > ------------------------------------------------------------------------------ > > Key: TEIID-3412 > URL: https://issues.jboss.org/browse/TEIID-3412 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Kylin Soong > > In JDK 1.8, the ODBC-JDBC bridge is removed, so accessing MS Access using this method will not be available. An alternative, open source, driver that can be used is: http://jackcess.sourceforge.net > In nexus: > <dependency> > <groupId>com.healthmarketscience.jackcess</groupId> > <artifactId>jackcess</artifactId> > <version>2.0.9</version> > </dependency> > This may require a new translator, but won't be know until a deeper look is done. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3418) Allow positional group by for odbc

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3418?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3418: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1211342|https://bugzilla.redhat.com/show_bug.cgi?id=1211342] from NEW to MODIFIED > Allow positional group by for odbc > ---------------------------------- > > Key: TEIID-3418 > URL: https://issues.jboss.org/browse/TEIID-3418 > Project: Teiid > Issue Type: Quality Risk > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.2-8.7.2, 8.11 > > > A remaining item for TEIID-3073 was that since tableau assumes we are postgresql they will use the pg specific positional group by references. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3358) Issues with entity set names

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3358?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3358: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1208515|https://bugzilla.redhat.com/show_bug.cgi?id=1208515] from NEW to MODIFIED > Issues with entity set names > ---------------------------- > > Key: TEIID-3358 > URL: https://issues.jboss.org/browse/TEIID-3358 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 6.2-8.7.2, 8.11 > > > The entity set name used for sql generation should be the fully qualified name. If there is for example two table with the same names in schemas visible to odata, but one of the tables does not have a key, then an ambiguous name exception will be thrown if an odata url is used with only the base table name. > It also appears that the URI link in the results metadata uses the non-qualified table name, which will have issues in the scenario above. > We may also need to document or add an additional check for ambiguity as the OData4j findEdmEntitySet logic will return the first matching entity, which is generally against our approach to resolving. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3410) OData object URI does not resolve to a usable URL.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3410?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3410: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1208515|https://bugzilla.redhat.com/show_bug.cgi?id=1208515] from NEW to MODIFIED > OData object URI does not resolve to a usable URL. > -------------------------------------------------- > > Key: TEIID-3410 > URL: https://issues.jboss.org/browse/TEIID-3410 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > OData object URI does not resolve to a usable URL. When accessing a VDB via odata with a browser either via JSON or XML the uri listed in the metadata is not valid, it doesn't have the FQN of the table, only the type shows FQN: > "__metadata" : { > "uri" : "http://localhost:8080/odata/ODataRHQ/rhq_agent(10001)", > "type" : "RHQ32.rhq_agent" -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2015