[JBoss JIRA] Created: (TEIID-1351) Replace translate criteria
by Steven Hawkins (JIRA)
Replace translate criteria
--------------------------
Key: TEIID-1351
URL: https://jira.jboss.org/browse/TEIID-1351
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.3
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 7.3
While we hardened the usage in 7.2, translate criteria has too many implied restrictions to reliably perform the update/delete the user query is specifying.
It would be better to rely on better default handling (especially pass-through) TEIID-1349 and to remove the current restrictions on virtual update, such as requiring scalar set clause values and no subquery evaluation TEIID-1276.
This change should not remove the possibility of using TRANSLATE CRITERIA/CREATE PROCEDURE, as it will not be removed until Teiid 8 or later.
Beyond the default handling, one possible construct is to provide the user with an cursor that contains the update (or delete) set with the corresponding updated values. Then leave it up to the user to iterate over the change set and process the changes. One drawback with this approach is that it may be hard to decipher from the view output rows how to apply the updates to constituent tables when the view transformation is a set or join and branch descriminators or additional primary keys are not projected. Of course those situations were already difficult to handle with translate criteria.
This will require coordinated designer changes.
--
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
13 years, 3 months
[JBoss JIRA] Created: (TEIID-1349) Better default update procedure handling
by Steven Hawkins (JIRA)
Better default update procedure handling
----------------------------------------
Key: TEIID-1349
URL: https://jira.jboss.org/browse/TEIID-1349
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.0
We are currently very restrictive in what we can automatically handle in terms of updates procedures. Anything other than a simple non-joined select cannot have a default update procedure. We should look at expanding our default handling to simple joins and union all - along with designer warnings for derived columns or other situations that would not be automatically updatable.
--
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
13 years, 3 months
[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
13 years, 3 months
[JBoss JIRA] Created: (TEIID-1399) Adding ORDER BY to SELECT COUNT(*) FROM ... returns org.teiid.core.TeiidProcessingException: null to client - Needs clearer message
by Paul Nittel (JIRA)
Adding ORDER BY to SELECT COUNT(*) FROM ... returns org.teiid.core.TeiidProcessingException: null to client - Needs clearer message
-----------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1399
URL: https://issues.jboss.org/browse/TEIID-1399
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.1.1
Reporter: Paul Nittel
Assignee: Steven Hawkins
I had quickly queried SELECT COUNT(*) FROM sometable ORDER BY ColA, ColB and received org.teiid.core.TeiidProcessingException: null as a result. Checking the server, I found the stack trace below. Neither actually points out the ORDER BY is incorrect since it does not reference projected columns.
A clearer message will help the users.
2010-12-14 12:54:05,010 ERROR [org.teiid.CONNECTOR] (Worker28_QueryProcessorQueue2669) Connector worker process failed for atomic-request=J76UbF11tQAM.0.1.753
java.lang.AssertionError
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:504)
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:432)
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:207)
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:130)
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:213)
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:281)
at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:71)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:123)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:120)
at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:108)
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)
2010-12-14 12:54:05,042 WARN [org.teiid.PROCESSOR] (Worker27_QueryProcessorQueue2670) Processing exception 'null' for request J76UbF11tQAM.0. Exception type org.teiid.core.TeiidProcessingException thrown from org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:504). Enable more detailed logging to see the entire stacktrace.
2010-12-14 12:54:20,404 ERROR [org.teiid.CONNECTOR] (Worker28_QueryProcessorQueue2673) Connector worker process failed for atomic-request=Tfqv5NFZIOX4.0.1.754
java.lang.AssertionError
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:504)
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:432)
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:207)
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:130)
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:213)
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:281)
at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:71)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:123)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:120)
at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:108)
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)
2010-12-14 12:54:20,405 WARN [org.teiid.PROCESSOR] (Worker27_QueryProcessorQueue2674) Processing exception 'null' for request Tfqv5NFZIOX4.0. Exception type org.teiid.core.TeiidProcessingException thrown from org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:504). Enable more detailed logging to see the entire stacktrace.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[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
13 years, 3 months