[JBoss JIRA] (TEIID-2123) Per model getMetadata() timeout
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2123?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2123:
----------------------------------
Component/s: Misc. Connectors
> Per model getMetadata() timeout
> -------------------------------
>
> Key: TEIID-2123
> URL: https://issues.jboss.org/browse/TEIID-2123
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.0
> Reporter: Mark Addleman
> Priority: Minor
> Fix For: Open To Community
>
>
> A way of specifying, per model, a timeout for the getMetadata() call. The timeout should be processed in such a way that delegating translators have an opportunity to intercept the interruption and, potentially, supply default metadata. I think the normal Thread.interrupt() approach should work.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-2123) Per model getMetadata() timeout
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2123?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2123:
----------------------------------
Fix Version/s: Open To Community
> Per model getMetadata() timeout
> -------------------------------
>
> Key: TEIID-2123
> URL: https://issues.jboss.org/browse/TEIID-2123
> Project: Teiid
> Issue Type: Feature Request
> Affects Versions: 8.0
> Reporter: Mark Addleman
> Priority: Minor
> Fix For: Open To Community
>
>
> A way of specifying, per model, a timeout for the getMetadata() call. The timeout should be processed in such a way that delegating translators have an opportunity to intercept the interruption and, potentially, supply default metadata. I think the normal Thread.interrupt() approach should work.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-2052) Add Problem/Resolution to query problem using the query plan
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2052?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2052:
----------------------------------
Fix Version/s: 10.0
Let's evaluate if there is anything more you want to do here Van.
> 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
> Fix For: 10.0
>
> 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
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-1131) Document/expand sequence support
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-1131:
----------------------------------
Fix Version/s: 10.0
> Document/expand sequence support
> --------------------------------
>
> Key: TEIID-1131
> URL: https://issues.jboss.org/browse/TEIID-1131
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector, Query Engine
> Affects Versions: 7.0
> Reporter: Steven Hawkins
> Fix For: 10.0
>
>
> Currently sequence workaround logic only exists for oracle and is undocumented. We should look at expanding sequence support - even for dynamic vdbs, see SQuriel's handling of system queries for retrieving sequence metadata.
> At least allowing the workaround logic to work for all sources that support sequences (Postgres, DB2, etc.) would be good.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years