[JBoss JIRA] (TEIID-1992) Create Connector/Translator to support Infinispan as a data source
by Van Halbert (JIRA)
Van Halbert created TEIID-1992:
----------------------------------
Summary: Create Connector/Translator to support Infinispan as a data source
Key: TEIID-1992
URL: https://issues.jboss.org/browse/TEIID-1992
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Create a Connector/Translator in order for Teiid to support …
[View More]Infinispan as a read-only data source on its initial release. Read Only because if someone is building an object cache, the primary means for updating the cache would not be thru relational means. However, if someone is wanting to add an object cache as a disparate data source for data integration for exposing the content, then this connector/translator will enable that.
A goal here is to build an object translator framework that can easily plug in other object cache sources. Example, add support for Coherence. There was a Coherence connector/translator already created in the sandbox, for which, it will provide direction for the object translator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
12 years, 4 months
[JBoss JIRA] (TEIID-2219) NullPointer Exception when doing count aggregations on two individual columns from separate databases
by Ivan Chan (JIRA)
Ivan Chan created TEIID-2219:
--------------------------------
Summary: NullPointer Exception when doing count aggregations on two individual columns from separate databases
Key: TEIID-2219
URL: https://issues.jboss.org/browse/TEIID-2219
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.1
Environment: Running embedded mode
Reporter: Ivan Chan
Assignee: …
[View More]Steven Hawkins
I have issues doing Count aggregations in 2 different databases. 2 out of 3 following cases fail... (But distinct count seems ok)
<----------- CASE 1 ----------> SUM first, then COUNT => OK
SUM(DB_2.field_1), COUNT(DB_1.field_1)
select sum("FoodmartDataSourceJNDI_public_expense_fact"."amount") as "FoodmartDataSourceJNDI_public_expense_fact_amount_Sum",
count("FoodmartDataSource_public_employee"."full_name") as "FoodmartDataSource_public_employee_full_name_Count"
from "FoodmartDataSource_public"."employee" "FoodmartDataSource_public_employee"
inner join "FoodmartDataSourceJNDI_public"."expense_fact" "FoodmartDataSourceJNDI_public_expense_fact" on ("FoodmartDataSource_public_employee"."store_id" = "FoodmartDataSourceJNDI_public_expense_fact"."store_id")
SELECT g_0."store_id" AS c_0, g_0."full_name" AS c_1 FROM "public"."employee" AS g_0 ORDER BY c_0
SELECT g_0."store_id" AS c_0, SUM(g_0."amount") AS c_1 FROM "public"."expense_fact" AS g_0 GROUP BY g_0."store_id" ORDER BY c_0
<-----------CASE 2 ---------------> COUNT first, then SUM => ERROR
COUNT(DB_1.field_1), SUM(DB_2.field_1)
select count("FoodmartDataSourceJNDI_public_expense_fact"."category_id") as "FoodmartDataSourceJNDI_public_expense_fact_category_id_Count",
sum("FoodmartDataSource_public_employee"."salary") as "FoodmartDataSource_public_employee_salary_Sum"
from "FoodmartDataSource_public"."employee" "FoodmartDataSource_public_employee"
inner join "FoodmartDataSourceJNDI_public"."expense_fact" "FoodmartDataSourceJNDI_public_expense_fact" on ("FoodmartDataSource_public_employee"."store_id" = "FoodmartDataSourceJNDI_public_expense_fact"."store_id")
Caused by: java.lang.NullPointerException
at org.teiid.query.processor.relational.GroupingNode.initialize(GroupingNode.java:184)
at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:108)
at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:113)
at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:103)
at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:194)
at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:130)
at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:109)
at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153)
at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:382)
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:291)
... 123 more
<-----------CASE 3 ---------------> COUNT on DB1.COL1 and COUNT on DB2.COL2 => ERROR
COUNT(DB_1.field_1), COUNT(DB_2.field_1)
select count("FoodmartDataSourceJNDI_public_expense_fact"."category_id") as "FoodmartDataSourceJNDI_public_expense_fact_category_id_Count",
count("FoodmartDataSource_public_employee"."first_name") as "FoodmartDataSource_public_employee_first_name_Count"
from "FoodmartDataSource_public"."employee" "FoodmartDataSource_public_employee"
inner join "FoodmartDataSourceJNDI_public"."expense_fact" "FoodmartDataSourceJNDI_public_expense_fact" on ("FoodmartDataSource_public_employee"."store_id" = "FoodmartDataSourceJNDI_public_expense_fact"."store_id")
Caused by: java.lang.NullPointerException
at org.teiid.query.processor.relational.GroupingNode.initialize(GroupingNode.java:184)
at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:108)
at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:113)
at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:103)
at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:194)
at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:130)
at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:109)
at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153)
at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:382)
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:291)
... 123 more
--
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
[View Less]
12 years, 4 months
[JBoss JIRA] (TEIID-2267) Verify Custom Appenders (command, audit) work in AS7
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2267:
-----------------------------------
Summary: Verify Custom Appenders (command, audit) work in AS7
Key: TEIID-2267
URL: https://issues.jboss.org/browse/TEIID-2267
Project: Teiid
Issue Type: Task
Components: Common
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.2
AS7 has different logging configuration than the …
[View More]AS 5.1. The appenders do work as is, and configuration may be different. However based on this AS7-4925 it looks like Log4J appender can be supported in AS 7.2. This information needs to be verified and update Teiid documentation at
https://docs.jboss.org/author/display/teiid/Custom+Logging
https://docs.jboss.org/author/display/teiid/Logging
Since 7.2, is not available yet if we want to fix this change the document to use java.util.logging.Handler interface to extend and add configuration like below in the logging subsystem in standalone-teiid.xml file
{code}
<custom-handler name="COMMAND" module="" class="org.something.CustomAppender">
</custom-handler>
<logger category="org.teiid.COMMAND_LOG">
<level name="INFO"/>
<handler name="COMMAND"/>
</logger>
{code}
--
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
[View Less]
12 years, 4 months
[JBoss JIRA] (TEIID-2266) When using JNDI to obtain cache, need to support EmbeddedCacheManager
by Van Halbert (JIRA)
Van Halbert created TEIID-2266:
----------------------------------
Summary: When using JNDI to obtain cache, need to support EmbeddedCacheManager
Key: TEIID-2266
URL: https://issues.jboss.org/browse/TEIID-2266
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.2
Reporter: Van Halbert
Assignee: Van Halbert
When building the quick start for infinispan, the …
[View More]test application is using the following injection:
<code>
@Produces
@Resource(lookup = "java:jboss/infinispan/container/teiid-infinispan-quickstart")
private CacheContainer container;
</code>
But when the Infinispan connector tries to get the container from JNDI, getting a ClassCastException: org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager cannot be cast to org.infinispan.api.BasicCacheContainer
So the injection must be handling getting the container, for which wasn't taken into consideration. So the connector-infinispan needs to be changed accordingly.
--
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
[View Less]
12 years, 4 months
[JBoss JIRA] (TEIID-2193) System Catalog queries producing IllegalArgumentException: Invalid Type
by Warren Gibson (JIRA)
Warren Gibson created TEIID-2193:
------------------------------------
Summary: System Catalog queries producing IllegalArgumentException: Invalid Type
Key: TEIID-2193
URL: https://issues.jboss.org/browse/TEIID-2193
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.1
Environment: Teiid 8.1 with AS 7.1.1
Reporter: Warren Gibson
Assignee: Steven Hawkins
All …
[View More]System Catalog queries producing IllegalArgumentException: Invalid Type
Example queries:
select * from SYS.VirtualDatabases
select VDBName, SchemaName, Name, Type, NameInSource, IsPhysical, SupportsUpdates, UID, Cardinality, Description, IsSystem, IsMaterialized from SYS.Tables
09:50:55,300 DEBUG [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue12) Request Thread FwKHlqK21Snf.6 - error occurred: java.lang.IllegalArgumentException: Invalid type: org.teiid.metadata.Schema.
at org.teiid.query.metadata.TransformationMetadata.createInvalidRecordTypeException(TransformationMetadata.java:619) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.query.metadata.TransformationMetadata.getModelID(TransformationMetadata.java:253) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.query.metadata.TempMetadataAdapter.getModelID(TempMetadataAdapter.java:175) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.query.metadata.TempMetadataAdapter.getModelID(TempMetadataAdapter.java:175) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.query.optimizer.relational.plantree.PlanNode.recordDebugAnnotation(PlanNode.java:423) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.query.optimizer.relational.rules.RulePushLimit.raiseAccessOverLimit(RulePushLimit.java:235) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.query.optimizer.relational.rules.RuleRaiseAccess.raiseAccessNode(RuleRaiseAccess.java:293) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.query.optimizer.relational.rules.RuleRaiseAccess.execute(RuleRaiseAccess.java:76) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:457) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:199) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:188) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:433) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.dqp.internal.process.Request.processRequest(Request.java:453) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:532) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:280) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:219) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:249) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.1.0.Final.jar:8.1.0.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.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
[View Less]
12 years, 4 months
[JBoss JIRA] (TEIID-2310) VDB import issues
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2310:
-----------------------------------
Summary: VDB import issues
Key: TEIID-2310
URL: https://issues.jboss.org/browse/TEIID-2310
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.1
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.2
During the vdb-import testing found couple issues
1) VDB-Import information is not …
[View More]available, when a vdb that has vdb-import defined, and queried through CLI or Teiid Console, Admin Shell.
2) VDB is not properly re-loading, when dependent VDB has been re-deployed. For example, if we have 3 vdbs
PartsTop_VDB.vdb -> imports -> PartsCommon_View.vdb -> imports -> PartsCommon_Root.vdb
then if we do deploy of all the vdbs in any order, we will have all the 3 VDBS available in server. Then if you, undeploy
undeploy PartsCommon_View.vdb
then it will remove "PartsCommon_View.vdb" and also "PartsTop_VDB.vdb" as it depends on it.
However, upon re-deployment of "PartsCommon_View.vdb" the "PartsTop_VDB.vdb" should come up with out any issues, but it does not.
--
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
[View Less]
12 years, 4 months
[JBoss JIRA] (TEIID-2191) Detect recursive view definitions
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2191:
-------------------------------------
Summary: Detect recursive view definitions
Key: TEIID-2191
URL: https://issues.jboss.org/browse/TEIID-2191
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
A feature from designer that was never added to the runtime is …
[View More]detection of recursive view definitions. Currently if a recursive view is supplied via ddl or translator it will cause a stackoverflow in the relational planner when it is accessed.
--
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
[View Less]
12 years, 4 months