[JBoss JIRA] (TEIID-3357) Add the final processor plan to the command log
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3357?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3357.
-----------------------------------
Resolution: Done
At a trace level we'll now output the initial plan with the plan event, and include the final plan with the close/cancel - which should include relevant node stats, bytes sent, etc.
Also add a plan property for the time spent in planning and more information to the enhanced sort to see what style of processing is ultimately done.
> Add the final processor plan to the command log
> -----------------------------------------------
>
> Key: TEIID-3357
> URL: https://issues.jboss.org/browse/TEIID-3357
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.11
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.11
>
>
> We should add the plan output not just once planning has completed, but when processing has completed as well so that the node statistics have been populated.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIID-3358) Issues with entity set names
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3358?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3358:
---------------------------------------
Updated the sql generation logic to use fully qualified names. I'm not sure what to do about the link formation. For example:
<link rel="self" title="Customers" href="Customers"/><entry><id>http://localhost:8081/odata/northwind/Customers('12')</id>
But we'd like to see the qualified Customer:
http://localhost:8081/odata/northwind/nw.Customers('12')
> 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: Steven Hawkins
> Fix For: 8.11
>
>
> 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.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIID-3366) postgresql extract used for date functions returns double, not integer
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3366?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3366.
-----------------------------------
Resolution: Done
Added a cast to integer for the relevant functions.
> postgresql extract used for date functions returns double, not integer
> ----------------------------------------------------------------------
>
> Key: TEIID-3366
> URL: https://issues.jboss.org/browse/TEIID-3366
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.11
>
>
> Postgresql extract returns a double precision (which is documented as the expectation), but we expect integer values from the respective Teiid functions. This typically won't lead to an issue in a simple projection scenario, but is problematic for combined expressions, such as using mod which will result in an exception.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIID-3367) Developing/documenting karaf deployment and/or another container
by Kylin Soong (JIRA)
Kylin Soong created TEIID-3367:
----------------------------------
Summary: Developing/documenting karaf deployment and/or another container
Key: TEIID-3367
URL: https://issues.jboss.org/browse/TEIID-3367
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 8.11
Reporter: Kylin Soong
Assignee: Kylin Soong
Current Teiid only can deployed on JBoss container, It would probably be worth some effort at developing/documenting karaf deployment and/or another container as well.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIID-3364) Teiid Embedded generic-soap run failed
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3364?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-3364:
------------------------------------
I will use vdb.xml file replace the code, also add more data sources base on this issue,
> It would probably be worth some effort at developing/documenting karaf deployment and/or another container as well.
I think we can create a new JIRA for this.
> Teiid Embedded generic-soap run failed
> --------------------------------------
>
> Key: TEIID-3364
> URL: https://issues.jboss.org/browse/TEIID-3364
> Project: Teiid
> Issue Type: Enhancement
> Components: Embedded
> Reporter: Kylin Soong
>
> I test the 8.10 embedded-dist zip download, the generic-soap run failed with Connection reset exception.
> On the other sides, can we add more samples for teiid embedded mode?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIID-2052) Add Problem/Resolution to query problem using the query plan
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-2052?page=com.atlassian.jira.plugin... ]
Work on TEIID-2052 stopped by Van Halbert.
------------------------------------------
> Add Problem/Resolution to query problem using the query plan
> ------------------------------------------------------------
>
> Key: TEIID-2052
> URL: https://issues.jboss.org/browse/TEIID-2052
> Project: Teiid
> Issue Type: Enhancement
> Components: Documentation
> Affects Versions: 7.7.1
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Optional
> Attachments: INClauseNotPushedDown.odt
>
>
> Adding content that could be used for query problem resolution. The initial attachment does the following:
> - states the query problem (i.e., not pushing down the "IN" clause)
> - provides the query plan (and debug log) for the query being submitted
> - provides recommendations for resolving the problem
> - then indicates how this problem was resolved and what the resulting query plan / debug log
> The idea here is to continue to add other problem scenarios so that this information is really useful for resolving issues.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month