[JBoss JIRA] Closed: (TEIID-1427) Class not found in Teiid JON agent
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1427?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-1427.
---------------------------------
> Class not found in Teiid JON agent
> ----------------------------------
>
> Key: TEIID-1427
> URL: https://issues.jboss.org/browse/TEIID-1427
> Project: Teiid
> Issue Type: Bug
> Components: Jopr Plugin
> Affects Versions: 7.1.1
> Reporter: Paul Nittel
> Assignee: Ted Jones
> Priority: Blocker
> Fix For: 7.1.1, 7.3
>
> Attachments: agent.log.zip
>
>
> While trying to delete a VDB form my server, it was noticed the agent's log showed a missing class.
> 2011-01-07 10:26:54,366 WARN [MeasurementManager.collector-1] (rhq.core.pc.measurement.MeasurementCollectorRunner)- Failure to collect measurement data for Resource[id=10301, type=Data Services, key=RuntimeEngineDeployer, name=Data Services, parent=sllxqm27:1099 production, version=7.1.1] - cause: java.lang.Exception:java.lang.NoClassDefFoundError: Could not initialize class org.teiid.adminapi.impl.SessionMetadataMapper -> java.lang.NoClassDefFoundError:Could not initialize class org.teiid.adminapi.impl.SessionMetadataMapper
> Attaching the whole log file for further analysis.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] Created: (TEIID-1376) Add support for pushing joins through a union
by Steven Hawkins (JIRA)
Add support for pushing joins through a union
---------------------------------------------
Key: TEIID-1376
URL: https://jira.jboss.org/browse/TEIID-1376
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.3
Given a query structure such as:
inner join
union all
a
b
union all
c
d
where a,b,c,d are access nodes to a source that supports joins and there is a constant column projected by each union branch and that column is used in the join predicates, then we should be able examine
union all
inner join
a
b
inner join
a
c
...
to determine if any of the joins will no longer be necessary.
This is a possible pattern in a multi-source or partitioning scenario.
In some scenarios there may not be an actual projected literal, which could be accommodated if a foreign key could be marked as partitioned.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] Created: (TEIID-1388) Appears to be a limit of only one functional SalesForce connector in Teiid at a time.
by John Doyle (JIRA)
Appears to be a limit of only one functional SalesForce connector in Teiid at a time.
-------------------------------------------------------------------------------------
Key: TEIID-1388
URL: https://issues.jboss.org/browse/TEIID-1388
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Affects Versions: 7.1.1
Environment: Teiid 7.1.1 in EDS ER5, JBDS Beta2, RHEL 5.1
Reporter: John Doyle
Assignee: John Doyle
Priority: Blocker
It appears they only one SalesForce connector can be run at a time. If you preview a model from Designer and there are no SF connections in Teiid, it works. When you create a DS for the VDB and deploy, the VDB cannot get connections from SalesForce. If you delete the preview VDB and Datasource, then the deployed VDB begins working.
I originally suspected that the problem might be that we are running out of connections; SalesForce limits you to 5 simultaneous connections per username/password. But I deployed the two DataSources with different credentials, and the result did not change. Need to investigate more.
Think that we do need to default the SF DS to a pool of 1 and then doc that it should be bumped to 5 for production. The current default is 10, and that should never be. Even 5 will exhaust the limit with just a preview connection.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] Closed: (TEIID-1336) EDS adminshell - clearCache() having no effect
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1336?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-1336.
---------------------------------
> EDS adminshell - clearCache() having no effect
> ----------------------------------------------
>
> Key: TEIID-1336
> URL: https://issues.jboss.org/browse/TEIID-1336
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.1.1
> Environment: SOA-P 5.1 ER3 build
> Reporter: Len DiMaggio
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 7.1.1
>
>
> clearCache() doesn't look like it's doing anything - see below:
> groovy:000> connectAsAdmin("mms://localhost:31443", "admin", "admin", "conn-1")
> ===> null
> groovy:000> getCacheStats("QUERY_SERVICE_RESULT_SET_CACHE")
> ===> hitRatio=0.0; totalEntries=0; requestCount=3
> groovy:000> clearCache("QUERY_SERVICE_RESULT_SET_CACHE")
> ===> null
> groovy:000> getCacheStats("QUERY_SERVICE_RESULT_SET_CACHE")
> ===> hitRatio=0.0; totalEntries=0; requestCount=3
> ===================
> server.log:
> 2010-10-29 12:13:07,065 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) processing message:MessageHolder: contents=org.teiid.net.socket.ServiceInvocationStruct@18cf5ea
> 2010-10-29 12:13:07,065 DEBUG [org.teiid.SECURITY] (New I/O server worker #2-1) Ping MLwHWKFcHgcq
> 2010-10-29 12:13:07,065 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) message: MessageHolder: contents=null for request ID:38
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) processing message:MessageHolder: contents=org.teiid.net.socket.ServiceInvocationStruct@c171b7
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.ADMIN_API] (New I/O server worker #2-1) before clearCache:org.teiid.adminapi.jboss.Admin@1a42c71(QUERY_SERVICE_RESULT_SET_CACHE)
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.ADMIN_API] (New I/O server worker #2-1) after clearCache : null
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) message: MessageHolder: contents=null for request ID:39
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] Closed: (TEIID-1389) Add additional detection for conflicting criteria to help optimize query plan
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1389?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-1389.
---------------------------------
> Add additional detection for conflicting criteria to help optimize query plan
> -----------------------------------------------------------------------------
>
> Key: TEIID-1389
> URL: https://issues.jboss.org/browse/TEIID-1389
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 6.0.0
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
> Fix For: 7.3
>
>
> Add additional detection for conflicting criteria such as "(column1=1 OR column1=2) AND column1=3". The attempted use case was a case of a UNION that was using the column as a measure of selecting a specific datasource, with each query joined by the UNION having a specific set of column1 values (such as "column1=1 OR column1=2"). In the case of the end user application submitting criteria such as "column1=3", the query planner should prune any branches of the UNION with a conflicting set of values for column1. It would also be helpful if other operators such as <, >, <>, IN, etc. could be accounted for.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months