[JBoss JIRA] (TEIID-2252) Add a jdbc import option to disable all name qualification
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2252:
-------------------------------------
Summary: Add a jdbc import option to disable all name qualification
Key: TEIID-2252
URL: https://issues.jboss.org/browse/TEIID-2252
Project: Teiid
Issue Type: Enhancement
Components: JDBC Connector
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
If importing from a single schema, which is the default for the connection, no qualification is needed on teiid names nor name in source. No combination of import properties currently supports that option.
--
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
12 years, 10 months
[JBoss JIRA] (TEIID-2268) NullPointer Exception genetated while querying table built from WSDL query
by Paul Richardson (JIRA)
Paul Richardson created TEIID-2268:
--------------------------------------
Summary: NullPointer Exception genetated while querying table built from WSDL query
Key: TEIID-2268
URL: https://issues.jboss.org/browse/TEIID-2268
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.2
Reporter: Paul Richardson
Assignee: Steven Hawkins
Attachments: server.log
Using designer 8, I deploy the state service example models (found [here|https://github.com/phantomjinx/teiid-soap-example]) to an 8.2 beta1 teiid server. The models deploy successfully and the teiid connection in designer displays the catalog and stateService/stateServiceView schemas.
However, running the following query
{{exec stateServiceView.getAllStateInfo();}}
results in a generic TeiidException in designer's status view.
This exception comes from a NullPointerException that is displayed in the jboss server log.
The log of the jboss server is attached, detailing the following events:
# start of the server with the stateService data source and USStates vdb already deployed
# connection and execution of the query from designer
--
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
12 years, 10 months
[JBoss JIRA] (TEIID-2172) Load balancing configuration can result in extraneous "invalid session" messages
by Marc Shirley (JIRA)
Marc Shirley created TEIID-2172:
-----------------------------------
Summary: Load balancing configuration can result in extraneous "invalid session" messages
Key: TEIID-2172
URL: https://issues.jboss.org/browse/TEIID-2172
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 7.4.4
Environment: Clustered environment with load balancing enabled for the Teiid data source
Reporter: Marc Shirley
Assignee: Steven Hawkins
When set up in a load balancing configuration with "SET NEW INSTANCE" as the check valid connection SQL in the datasource definition, repeated messages indicating an invalid session are created, similar to:
2012-08-24 10:39:58,818 WARN [org.teiid.SECURITY] (New I/O server worker #1-3) Processing exception 'The specified session ID "5Wt/6zzmsLy2" is invalid. It cannot be found in the userbase.' for session R8ZxYqjZzf/S. Exception type org.teiid.client.security.InvalidSessionException thrown from org.teiid.services.SessionServiceImpl.getSessionInfo(SessionServiceImpl.java:315). Enable more detailed logging to see the entire stacktrace.
Not sure if this would be a defect in regards to the conditions that are resulting in the messages to be generated (ie, the old session id shouldn't be being reused), or an enhancement to clarify or adjust the log message or priority to indicate whether this will actually affect the query being submitted.
--
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
12 years, 10 months
[JBoss JIRA] (TEIID-2225) ResultSet.isLast() blocks in non-continuous query mode
by Mark Addleman (JIRA)
Mark Addleman created TEIID-2225:
------------------------------------
Summary: ResultSet.isLast() blocks in non-continuous query mode
Key: TEIID-2225
URL: https://issues.jboss.org/browse/TEIID-2225
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 8.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
I am executing a query using submitExecute(StatementCallback) under non-continuous mode. In the onRow() method of the callback, I execute ResultSet.isLast(). The query is against an execution whose next() method initially throws DataNotAvailable.NO_POLLING. Some time later, it calls ExecutionContext.dataAvailable(). After 255 rows reported through the callback's onRow(), ResultSet.isLast() hangs.
I know that the entire result set is ultimately returned from the execution's next() and it returns null at the last call.
See https://community.jboss.org/thread/205559?tstart=0 for more detail
--
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
12 years, 10 months
[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 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
12 years, 10 months
[JBoss JIRA] (TEIID-2259) Error executing CASE WHEN THEN ELSE END statement
by Ivan Chan (JIRA)
Ivan Chan created TEIID-2259:
--------------------------------
Summary: Error executing CASE WHEN THEN ELSE END statement
Key: TEIID-2259
URL: https://issues.jboss.org/browse/TEIID-2259
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 8.1, 8.2
Environment: Running Teiid 8.1 embedded version on Windows
Reporter: Ivan Chan
Assignee: Steven Hawkins
Attachments: stacktrace.txt
Error executing CASE WHEN THEN ELSE END statement with boolean expression in the WHEN clause
--
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
12 years, 10 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: 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
12 years, 10 months