[JBoss JIRA] (TEIID-2188) When using CONCAT2(x, y), can the source query be changed to not include the CASE statements and let Oracle do the NULL compare
by Van Halbert (JIRA)
Van Halbert created TEIID-2188:
----------------------------------
Summary: When using CONCAT2(x, y), can the source query be changed to not include the CASE statements and let Oracle do the NULL compare
Key: TEIID-2188
URL: https://issues.jboss.org/browse/TEIID-2188
Project: Teiid
Issue Type: Enhancement
Components: Embedded
Affects Versions: 7.4.4
Reporter: Van Halbert
Assignee: Steven Hawkins
When CONCAT2(x, y) is used, the rewritten query is very verbose in adding a CASE statement to check for nulls. Can the rewritten query not include the CASE statements and just let Oracle do the compare, because it can do it more efficiently within the CONCAT call?
Example:
select concat2(f1,f2) from table1
results in
SELECT c_0 FROM (SELECT CASE WHEN to_char(g_0.f1) IS NULL AND g_0.f2 IS NULL THEN NULL ELSE concat(nvl(to_char(g_0.f1), ''), nvl(g_0.f2, '')) END AS c_0 FROM table1 g_0)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (TEIID-2204) Teiid subsystem doesn't cleanly reload on AS7
by Heiko Braun (JIRA)
Heiko Braun created TEIID-2204:
----------------------------------
Summary: Teiid subsystem doesn't cleanly reload on AS7
Key: TEIID-2204
URL: https://issues.jboss.org/browse/TEIID-2204
Project: Teiid
Issue Type: Feature Request
Reporter: Heiko Braun
Assignee: Steven Hawkins
{noformat}
Laika:teiid-7.1.1.Final hbraun$ ./bin/jboss-cli.sh --connect
[standalone@localhost:9999 /] :reload
{noformat}
leads to
{noformat}
12:44:46,665 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 46) JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "teiid"),
("transport" => "embedded")
]): java.lang.IllegalArgumentException: JBAS011857: NamingStore is null
at org.jboss.as.naming.NamingContext.<init>(NamingContext.java:149)
at org.jboss.as.naming.NamingContext.<init>(NamingContext.java:122)
at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:85)
at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:44)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) [classes.jar:1.6.0_33]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) [classes.jar:1.6.0_33]
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:316) [classes.jar:1.6.0_33]
at javax.naming.InitialContext.lookup(InitialContext.java:392) [classes.jar:1.6.0_33]
at org.teiid.jboss.TransportAdd.isEmbeddedRegistered(TransportAdd.java:217)
at org.teiid.jboss.TransportAdd.performRuntime(TransportAdd.java:195)
at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:50) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (TEIID-1636) Programmatically configure internal materialized views
by Mark Addleman (JIRA)
Programmatically configure internal materialized views
------------------------------------------------------
Key: TEIID-1636
URL: https://issues.jboss.org/browse/TEIID-1636
Project: Teiid
Issue Type: Bug
Affects Versions: 7.3
Reporter: Mark Addleman
Assignee: Steven Hawkins
I am trying to programatically create a materialized view from the MetadataFactory object. I have created a table object using addTable() and then I call setMaterialized(true). I see there are a couple of other related method names in Table (setMaterializedStagedTable and setMaterializedTable). I assume those are when materializing to an external database. What I am doing is incorrect, however.
When I try to issue a refresh CALL SYSADMIN.refreshMatView(viewname=>'xyz_metadata.property', invalidate=>false), I get the following exception:
QueryMetadataException]QueryPlan could not be found for physical group chorus_metadata.property
at org.teiid.query.metadata.TransformationMetadata.getVirtualPlan(TransformationMetadata.java:453)
at org.teiid.query.metadata.TempMetadataAdapter.getVirtualPlan(TempMetadataAdapter.java:253)
at org.teiid.query.optimizer.relational.RelationalPlanner.getGlobalTempTableMetadataId(RelationalPlanner.java:1136)
at org.teiid.query.tempdata.TempTableDataManager.handleSystemProcedures(TempTableDataManager.java:320)
at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:188)
at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:170)
at org.teiid.query.processor.relational.AccessNode.registerRequest(AccessNode.java:197)
at org.teiid.query.processor.relational.AccessNode.open(AccessNode.java:118)
at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250)
at org.teiid.query.processor.relational.RelationalPlan.open(RelationalPlan.java:152)
at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:134)
at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:105)
at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:115)
at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:250)
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:184)
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49)
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)
13 Jun 2011 17:05:43,663 PDT INFO [MATVIEWS] Loading materialized view table #MAT_XYZ_METADATA.PROPERTY
Subsequent calls to the refresh stored procedure yield an NPE else in Teiid code.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (TEIID-2215) Allow embedded to be clusterable
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2215:
-------------------------------------
Summary: Allow embedded to be clusterable
Key: TEIID-2215
URL: https://issues.jboss.org/browse/TEIID-2215
Project: Teiid
Issue Type: Enhancement
Components: Embedded
Affects Versions: 8.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Now that we've pulled in infinispan/jgroup dependencies, there's nothing preventing us from allowing a fully clusertable embedded.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months