[JBoss JIRA] (TEIID-3358) Issues with entity set names
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3358?page=com.atlassian.jira.plugin... ]
Van Halbert reopened TEIID-3358:
--------------------------------
> Issues with entity set names
> ----------------------------
>
> Key: TEIID-3358
> URL: https://issues.jboss.org/browse/TEIID-3358
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Labels: Alpha1
> Fix For: 8.7.1.6_2, 8.11, 8.7.3
>
>
> The entity set name used for sql generation should be the fully qualified name. If there is for example two table with the same names in schemas visible to odata, but one of the tables does not have a key, then an ambiguous name exception will be thrown if an odata url is used with only the base table name.
> It also appears that the URI link in the results metadata uses the non-qualified table name, which will have issues in the scenario above.
> We may also need to document or add an additional check for ambiguity as the OData4j findEdmEntitySet logic will return the first matching entity, which is generally against our approach to resolving.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3553) Odata - if table name is ambiguous, teiid returns result from first table
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3553?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3553:
----------------------------------
Issue Type: Quality Risk (was: Bug)
This was identified with the other odata resolving issues. However it is the way OData4J works by default. We can change it now that we are forked, but we'll have to see if that was a conscious choice / part of the spec.
> Odata - if table name is ambiguous, teiid returns result from first table
> -------------------------------------------------------------------------
>
> Key: TEIID-3553
> URL: https://issues.jboss.org/browse/TEIID-3553
> Project: Teiid
> Issue Type: Quality Risk
> Components: OData
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> If table name is ambiguous, teiid returns data from first matching table. I expect, that it should return error message similar to exception which is thrown via JDBC.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3451) OData does not inject schema into queries
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3451?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3451:
------------------------------------------------
Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1215675|https://bugzilla.redhat.com/show_bug.cgi?id=1215675] from ON_QA to VERIFIED
> OData does not inject schema into queries
> -----------------------------------------
>
> Key: TEIID-3451
> URL: https://issues.jboss.org/browse/TEIID-3451
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.7
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 8.7.1.6_2, 8.11, 8.7.3
>
>
> OData service does not inject a fully qualified object names for tables for POSTS, PUTs, and DELETEs:
> 12:50:34,367 DEBUG [org.teiid.COMMAND_LOG] (http-localhost/127.0.0.1:8080-1) START USER COMMAND: startTime=2015-04-22 12:50:34.367 requestID=XxHTbednhDq7.0 txID=null sessionID=XxHTbednhDq7 applicationName=JDBC principal=teiidUser@teiid-security vdbName=ImsOne vdbVersion=2 sql=INSERT INTO Subscription (SUBSCRIPTION_ID, CLIENT_NAME, DEST_CONNECTION_URI, DEST_SCHEMA_NAME, DEST_TABLE_NAME, PROVIDER_URL, TOPIC_NAME) VALUES (?, ?, ?, ?, ?, ?, ?)
> 12:50:34,380 DEBUG [org.teiid.COMMAND_LOG] (http-localhost/127.0.0.1:8080-1) ERROR USER COMMAND: endTime=2015-04-22 12:50:34.379 requestID=XxHTbednhDq7.0 txID=null sessionID=XxHTbednhDq7 principal=teiidUser@teiid-security vdbName=ImsOne vdbVersion=2 finalRowCount=null
> 12:50:34,380 WARN [org.teiid.PROCESSOR] (http-localhost/127.0.0.1:8080-1) TEIID30020 Processing exception for request XxHTbednhDq7.0 'Group specified is ambiguous, resubmit the query by fully qualifying the group name: Subscription'. Originally QueryResolverException ResolverUtil.java:814. Enable more detailed logging to see the entire stacktrace.
> 12:50:34,383 WARN [org.teiid.ODATA] (http-localhost/127.0.0.1:8080-1) TEIID16012 Could not produce a successful OData response. Returning status ServerErrorException with message Group specified is ambiguous, resubmit the query by fully qualifying the group name: Subscription.
> Same insert works fine over JDBC. Offending line from 8.7.0 public github:
> https://github.com/teiid/teiid/blob/8.7.x/odata/src/main/java/org/teiid/o...
> Note that private Table findTable() on line 925 depends upon org.odata4j.core.EdmEntitySet#getName to return the name, but this is not fully qualified
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3553) Odata - if table name is ambiguous, teiid returns result from first table
by Juraj Duráni (JIRA)
[ https://issues.jboss.org/browse/TEIID-3553?page=com.atlassian.jira.plugin... ]
Juraj Duráni updated TEIID-3553:
--------------------------------
Description: If table name is ambiguous, teiid returns data from first matching table. I expect, that it should return error message similar to exception which is thrown via JDBC. (was: If table name is ambiguous [1], teiid returns data from first matching table. I expect, that it should return error message similar to exception which is thrown via JDBC.)
> Odata - if table name is ambiguous, teiid returns result from first table
> -------------------------------------------------------------------------
>
> Key: TEIID-3553
> URL: https://issues.jboss.org/browse/TEIID-3553
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> If table name is ambiguous, teiid returns data from first matching table. I expect, that it should return error message similar to exception which is thrown via JDBC.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3358) Issues with entity set names
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3358?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3358:
------------------------------------------------
Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1208515|https://bugzilla.redhat.com/show_bug.cgi?id=1208515] from ON_QA to ASSIGNED
> Issues with entity set names
> ----------------------------
>
> Key: TEIID-3358
> URL: https://issues.jboss.org/browse/TEIID-3358
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Labels: Alpha1
> Fix For: 8.7.1.6_2, 8.11, 8.7.3
>
>
> The entity set name used for sql generation should be the fully qualified name. If there is for example two table with the same names in schemas visible to odata, but one of the tables does not have a key, then an ambiguous name exception will be thrown if an odata url is used with only the base table name.
> It also appears that the URI link in the results metadata uses the non-qualified table name, which will have issues in the scenario above.
> We may also need to document or add an additional check for ambiguity as the OData4j findEdmEntitySet logic will return the first matching entity, which is generally against our approach to resolving.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3552) NPE on calling the native query procedure with null variable parameter
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3552?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3552.
-----------------------------------
Resolution: Done
Made the null handling more consistent. For pushdown purposes we'll treat a null value the same as an empty array.
> NPE on calling the native query procedure with null variable parameter
> ----------------------------------------------------------------------
>
> Key: TEIID-3552
> URL: https://issues.jboss.org/browse/TEIID-3552
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Salvatore R
> Assignee: Steven Hawkins
> Fix For: 8.12
>
>
> Calling the native query procedure and passing null as "variable" parameter like in the following example:
> {code:sql}
> exec my.native("request" => 'Select 1', "variable" => null)
> {code}
> the following exception is thrown:
> {code:sql}
> 19:41:00,707 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue10) zC4UryNl1/3R TEIID30019 Unexpected exception for request zC4UryNl1/3R.5: java.lang.NullPointerException
> at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:958) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:183) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.<init>(ConnectorWorkItem.java:165) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.dqp.internal.datamgr.ConnectorManager.registerRequest(ConnectorManager.java:203) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.dqp.internal.process.DataTierManagerImpl.registerRequest(DataTierManagerImpl.java:966) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:179) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.query.processor.relational.AccessNode.registerRequest(AccessNode.java:475) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.query.processor.relational.AccessNode.open(AccessNode.java:248) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.query.processor.relational.RelationalPlan.open(RelationalPlan.java:136) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:231) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:457) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:339) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:267) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.11.0.Final.jar:8.11.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67]
> {code}
> As a workaround, the query is successfully executed if the "variable" parameter is omitted:
> {code:sql}
> exec my.native("request" => 'Select 1')
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3524) Database Logging not working
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3524?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3524:
------------------------------------
The issue is in how its deployed. For standalone, need to deploy using the "path" setting. Example:
/deployment=database-service.jar:add(runtime-name=database-service.jar,content=[{path=bin/scripts/database-service-1.1.0.jar/,archive=false,relative-to=jboss.home.dir}],enabled=true)
But note, this type of deployment doesn't work for domain, it wouldn't work. Use the existing deployment method.
> Database Logging not working
> ----------------------------
>
> Key: TEIID-3524
> URL: https://issues.jboss.org/browse/TEIID-3524
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Jan Stastny
> Assignee: Van Halbert
> Fix For: 8.7.1.6_2
>
>
> When using db logging in Teiid, nothing gets inserted into the db. Logs appear at server.log, but not in the db.
> I set up the logging as follows:
> Created java:/teiid-log-ds datasource.
> Added these to logging subsystem:
> {code:xml}
> <async-handler name="TEIID_COMMAND_LOG">
> <level name="DEBUG"/>
> <queue-length value="50"/>
> <overflow-action value="block"/>
> <subhandlers>
> <handler name="TEIID_JPA_LOG"/>
> </subhandlers>
> </async-handler>
> <async-handler name="TEIID_AUDIT_LOG">
> <level name="DEBUG"/>
> <queue-length value="50"/>
> <overflow-action value="block"/>
> <subhandlers>
> <handler name="TEIID_JPA_LOG"/>
> </subhandlers>
> </async-handler>
> <custom-handler name="TEIID_JPA_LOG" class="org.teiid.logger.DatabaseAppender" module="org.jboss.teiid.extensions">
> <level name="DEBUG"/>
> </custom-handler>
> <logger category="org.teiid.COMMAND_LOG">
> <level name="DEBUG"/>
> <handlers>
> <handler name="TEIID_COMMAND_LOG"/>
> </handlers>
> </logger>
> <logger category="org.teiid.AUDIT_LOG">
> <level name="DEBUG"/>
> <handlers>
> <handler name="TEIID_AUDIT_LOG"/>
> </handlers>
> </logger>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3524) Database Logging not working
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3524?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-3524:
-------------------------------
Fix Version/s: 8.7.1.6_2
> Database Logging not working
> ----------------------------
>
> Key: TEIID-3524
> URL: https://issues.jboss.org/browse/TEIID-3524
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Jan Stastny
> Assignee: Van Halbert
> Fix For: 8.7.1.6_2
>
>
> When using db logging in Teiid, nothing gets inserted into the db. Logs appear at server.log, but not in the db.
> I set up the logging as follows:
> Created java:/teiid-log-ds datasource.
> Added these to logging subsystem:
> {code:xml}
> <async-handler name="TEIID_COMMAND_LOG">
> <level name="DEBUG"/>
> <queue-length value="50"/>
> <overflow-action value="block"/>
> <subhandlers>
> <handler name="TEIID_JPA_LOG"/>
> </subhandlers>
> </async-handler>
> <async-handler name="TEIID_AUDIT_LOG">
> <level name="DEBUG"/>
> <queue-length value="50"/>
> <overflow-action value="block"/>
> <subhandlers>
> <handler name="TEIID_JPA_LOG"/>
> </subhandlers>
> </async-handler>
> <custom-handler name="TEIID_JPA_LOG" class="org.teiid.logger.DatabaseAppender" module="org.jboss.teiid.extensions">
> <level name="DEBUG"/>
> </custom-handler>
> <logger category="org.teiid.COMMAND_LOG">
> <level name="DEBUG"/>
> <handlers>
> <handler name="TEIID_COMMAND_LOG"/>
> </handlers>
> </logger>
> <logger category="org.teiid.AUDIT_LOG">
> <level name="DEBUG"/>
> <handlers>
> <handler name="TEIID_AUDIT_LOG"/>
> </handlers>
> </logger>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months