[JBoss JIRA] Created: (TEIID-1332) After updating ManagedComponent value via ProfileService, Teiid JOPR components get Availability down
by Cristiano Nicolai (JIRA)
After updating ManagedComponent value via ProfileService, Teiid JOPR components get Availability down
------------------------------------------------------------------------------------------------------
Key: TEIID-1332
URL: https://jira.jboss.org/browse/TEIID-1332
Project: Teiid
Issue Type: Bug
Components: Jopr Plugin
Affects Versions: 7.2
Environment: JbossAS 5.1
Reporter: Cristiano Nicolai
Assignee: Steven Hawkins
Attachments: SimpleUpdate.java
After updating some Teiid ManagementComponent value via ProfileService their availability status in Admin Console are showed as down but after refreshing the page causes the status to be up again.
The main problem is that the ManagementView isn't refreshed after the ManagementComponent is updated.
To fix it, all Teiid JOPR components (DataRoleComponent, PlatformComponent, TranslatorComponent, VDBComponent) must call managementView.load() after updating the ManagementComponent in updateResourceConfiguration method.
This problem cause the JON Agent Plugin to report the JON server that the services are DOWN.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (TEIID-1379) ClearCache is too corse grained
by Ramesh Reddy (JIRA)
ClearCache is too corse grained
-------------------------------
Key: TEIID-1379
URL: https://jira.jboss.org/browse/TEIID-1379
Project: Teiid
Issue Type: Feature Request
Components: AdminApi
Affects Versions: 7.2
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 7.1.1
The Admin API and Porfile Service currently expose too coarse grained clear cache operation that will throw away all the cache entries system wide (prepared plan, resultset). The proposal is to provide way to clear cache for given VDB.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (TEIID-1362) salesforce push down queries won't get resolved correctly
by Wanja Pernath (JIRA)
salesforce push down queries won't get resolved correctly
---------------------------------------------------------
Key: TEIID-1362
URL: https://jira.jboss.org/browse/TEIID-1362
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Affects Versions: 7.2
Environment: Teiid 7.2 final on JBoss EAP 5.1 with sun java 1.6.0_20
Reporter: Wanja Pernath
Assignee: Steven Hawkins
GIVEN:
select a.name, b.sumary
from Opp a OUTER JOIN OLI b ON a.id = b.foreignId
JoinQueryVisitor of SFDC translator correctly creates:
select a.name, (select b.summary from OLI b) from Opp a
As of SFDC docs:
http://www.salesforce.com/us/developer/docs/api/index_Left.htm#StartTopic...
you get a result set of for example:
"opp #1", [b] QueryResult for row #1
"opp #2", [b] QueryResult for row #2
Which must be transformed into something like this (EXPECTED)
"opp #1", 100
"opp #1", 150
"opp #1", 43000
"opp #2", 10000
"opp #2", 100
etc.
Right now, it gets transformed into something like (CURRENT)
"opp #1", null
"opp #2", null
"opp #3", null
etc.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (TEIID-586) Like pushdown handling
by Steven Hawkins (JIRA)
Like pushdown handling
----------------------
Key: TEIID-586
URL: https://jira.jboss.org/jira/browse/TEIID-586
Project: Teiid
Issue Type: Bug
Components: LDAP Connector, Query Engine, Salesforce Connector
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.2.0
Both salesforce and ldap like semantics are not the same as SQL. We could capture this with more capabilities supportsLikeCaseSensitive and supportsLikeWildcardSingleCharacter repectively, or another approach would be to allow the connector to generically indicate partial support and have the query engine both push down the conjunct and leave a copy to be applied after the query. With either explicit supports or generic partial support it would only applicable to top level where clause conjuncts.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months