June 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2981) Add an OData query parameter that caches the resultset

by John Muller (JIRA)

[ https://issues.jboss.org/browse/TEIID-2981?page=com.atlassian.jira.plugin... ] John Muller commented on TEIID-2981: ------------------------------------ [~rareddy] Yes, I figured on both your points, but I don't see a way around extending the OData spec that still provides a result set cache over OData. [~shawkins] I figured there must be caching for skipToken / skip based pagination, thanks for confirming. Our use case is a lengthy SQLServer stored procedure call that comes back with a medium-sized result set (1k to 2k rows). We simply wrapped the physical SPROC in a virtual procedure and then wrapped that in a virtual table. We don't even bother paginating and simply set the batch size to 2048. The issue we're encountering is the length of time the SqlServer SPROC takes is too long and consuming apps tend to hit it repeatedly with the same query. The SPROC has an IN parameter that is basically a user identifier and the underlying tables are much too big for internal materialization. External materialization is an expensive option, but really we only need to cache the user-filtered end result of the SPROC call. OData based caching would help greatly here, but the more generalized use case is for really small ReST queries that are executed repeatedly. > Add an OData query parameter that caches the resultset > ------------------------------------------------------ > > Key: TEIID-2981 > URL: https://issues.jboss.org/browse/TEIID-2981 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.7 > Reporter: John Muller > Assignee: Steven Hawkins > Priority: Minor > Labels: Caching, OData, > > The Teiid caching guide indicates that the /*+ cache */ SQL hint is neccessary in order to cache results [1] . We would like two features added to the OData support: (1) to have a query parameter that basically injects the hint into the SQL statement run against the VDB and (2) a configuration setting that turns on OData resultset caching for all result sets smaller than some size (perhaps 256 as the default) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2981) Add an OData query parameter that caches the resultset

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2981?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2981: --------------------------------------- There are the other considerations that when paginated results are requested, we'll automatically use result set caching and you may want consider using materialized views to consolidate some of the caching logic to the server side rather than making clients too aware. > Add an OData query parameter that caches the resultset > ------------------------------------------------------ > > Key: TEIID-2981 > URL: https://issues.jboss.org/browse/TEIID-2981 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.7 > Reporter: John Muller > Assignee: Steven Hawkins > Priority: Minor > Labels: Caching, OData, > > The Teiid caching guide indicates that the /*+ cache */ SQL hint is neccessary in order to cache results [1] . We would like two features added to the OData support: (1) to have a query parameter that basically injects the hint into the SQL statement run against the VDB and (2) a configuration setting that turns on OData resultset caching for all result sets smaller than some size (perhaps 256 as the default) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2981) Add an OData query parameter that caches the resultset

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2981?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2981: ------------------------------------- URL semantics would not allow to use exactly like /*+ cache..*/, it would need to be such as &cache=true&ttl=.. etc. However then we will be extending the odata spec adding customization on top, not that it is bad, just want to make sure you know it. > Add an OData query parameter that caches the resultset > ------------------------------------------------------ > > Key: TEIID-2981 > URL: https://issues.jboss.org/browse/TEIID-2981 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.7 > Reporter: John Muller > Assignee: Steven Hawkins > Priority: Minor > Labels: Caching, OData, > > The Teiid caching guide indicates that the /*+ cache */ SQL hint is neccessary in order to cache results [1] . We would like two features added to the OData support: (1) to have a query parameter that basically injects the hint into the SQL statement run against the VDB and (2) a configuration setting that turns on OData resultset caching for all result sets smaller than some size (perhaps 256 as the default) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2981) Add an OData query parameter that caches the resultset

by John Muller (JIRA)

John Muller created TEIID-2981: ---------------------------------- Summary: Add an OData query parameter that caches the resultset Key: TEIID-2981 URL: https://issues.jboss.org/browse/TEIID-2981 Project: Teiid Issue Type: Feature Request Components: OData Affects Versions: 8.7 Reporter: John Muller Assignee: Steven Hawkins Priority: Minor The Teiid caching guide indicates that the /*+ cache */ SQL hint is neccessary in order to cache results [1] . We would like two features added to the OData support: (1) to have a query parameter that basically injects the hint into the SQL statement run against the VDB and (2) a configuration setting that turns on OData resultset caching for all result sets smaller than some size (perhaps 256 as the default) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2980) Expose sequences as arrays in XMLTABLE construct

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2980: ----------------------------------- Summary: Expose sequences as arrays in XMLTABLE construct Key: TEIID-2980 URL: https://issues.jboss.org/browse/TEIID-2980 Project: Teiid Issue Type: Feature Request Reporter: Ramesh Reddy Assignee: Steven Hawkins we should allow xmltable to select sequences as array values. The array then could be manipulated in any way needed -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2979) google-spreadsheet translator not included standalone-teiid.xml

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2979?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2979. ----------------------------------- Resolution: Done There must have been a merge issue as the commit after the initial adding of the translator removed it from the config. It's back now. > google-spreadsheet translator not included standalone-teiid.xml > --------------------------------------------------------------- > > Key: TEIID-2979 > URL: https://issues.jboss.org/browse/TEIID-2979 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > The google-spreadsheet translator is not included in the standalone-teiid.xml. Need to make sure this gets into the 8.7 product release branch also -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2979) google-spreadsheet translator not included standalone-teiid.xml

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2979?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2979: ---------------------------------- Issue Type: Bug (was: Enhancement) Fix Version/s: 8.7.1 8.8 Affects Version/s: 8.4 (was: 8.8) > google-spreadsheet translator not included standalone-teiid.xml > --------------------------------------------------------------- > > Key: TEIID-2979 > URL: https://issues.jboss.org/browse/TEIID-2979 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > The google-spreadsheet translator is not included in the standalone-teiid.xml. Need to make sure this gets into the 8.7 product release branch also -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2979) google-spreadsheet translator not included standalone-teiid.xml

by Mark Drilling (JIRA)

Mark Drilling created TEIID-2979: ------------------------------------ Summary: google-spreadsheet translator not included standalone-teiid.xml Key: TEIID-2979 URL: https://issues.jboss.org/browse/TEIID-2979 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.8 Reporter: Mark Drilling Assignee: Steven Hawkins The google-spreadsheet translator is not included in the standalone-teiid.xml. Need to make sure this gets into the 8.7 product release branch also -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2978) using LIKE on columns causes no results though they indeed exist

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2978?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2978: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) I can't say for sure if this is our issue, although we can disable like pushdown against Modeshape as a workaround. Can you attach a vdb to ensure we're reproducing correctly? > using LIKE on columns causes no results though they indeed exist > ---------------------------------------------------------------- > > Key: TEIID-2978 > URL: https://issues.jboss.org/browse/TEIID-2978 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Tom Johnston > Assignee: Van Halbert > Labels: modeshape, teiid > > Use of LIKE doesn't appear to work when querying modeshape through JDBC. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2978) using LIKE on columns causes no results though they indeed exist

by Tom Johnston (JIRA)

Tom Johnston created TEIID-2978: ----------------------------------- Summary: using LIKE on columns causes no results though they indeed exist Key: TEIID-2978 URL: https://issues.jboss.org/browse/TEIID-2978 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.4.1 Reporter: Tom Johnston Assignee: Steven Hawkins Use of LIKE doesn't appear to work when querying modeshape through JDBC. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2014