March 2017 - teiid-issues - Jboss List Archives

[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)

7 years, 2 months

1
0
0 / 0

[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)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1700) Move odbc cursor logic to engine

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1700?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1700. ----------------------------------- Resolution: Deferred If/when we add explicit server side cursors, we will see if it makes sense to match the syntax of the pg client cursors. > Move odbc cursor logic to engine > -------------------------------- > > Key: TEIID-1700 > URL: https://issues.jboss.org/browse/TEIID-1700 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > ODBC added support for declared cursors, which would be a good general/procedure language feature. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[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)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-245) Update costing metadata at runtime

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-245?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-245: --------------------------------- Fix Version/s: 10.0 > Update costing metadata at runtime > ---------------------------------- > > Key: TEIID-245 > URL: https://issues.jboss.org/browse/TEIID-245 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > Attachments: OracleExecutionFactory.java.patch > > > Defect Tracker #24584: Cost analysis should be both a design-time activity and scheduled/feed during runtime. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2017