June 2014 - teiid-issues - Jboss List Archives

[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: ------------------------------------- Connection properties seems to be more central place that can apply across all the transports > 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, > Fix For: 8.8 > > > 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)

10 years, 7 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: --------------------------------------- Or should we assume that vdb connection properties should be used for both odata and odbc? > 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, > Fix For: 8.8 > > > 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)

10 years, 7 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: --------------------------------------- Similar to odbc vdb properties, I propose adding connection. property handling to the servlet init. But the user will not be able to override proper values such as passthrough, transport name, etc. > 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, > Fix For: 8.8 > > > 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)

10 years, 7 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 updated TEIID-2981: ---------------------------------- Fix Version/s: 8.8 Will look at exposing more connection properties via the servlet config such that result set caching or even autocommit txn mode can be set for odata. > 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, > Fix For: 8.8 > > > 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)

10 years, 7 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: --------------------------------------- > We don't even bother paginating and simply set the batch size to 2048 To follow up on that, does that mean you don't expect results greater than 2048 rows? > a generic OData cache that by default caches all results sets smaller than some defined number would hit a greater number of ReST queries we're actually servicing. The initial logic will simply allow for result set caching to be enabled. If we add additional control logic it may be around the expected size of the result set, not just the row count, to account for varying data widths. > 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)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2977) class cast exception with odata json format function results

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2977?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2977: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1106511 > class cast exception with odata json format function results > ------------------------------------------------------------ > > Key: TEIID-2977 > URL: https://issues.jboss.org/browse/TEIID-2977 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > If the json format is requested for function/stored procedure results, the json formatting logic will through a class cast: > 14:56:38,642 ERROR [org.teiid.ODATA] (http-localhost/127.0.0.1:8080-1) TEIID16013 Error occured producing OData result.: java.lang.ClassCastException: org.odata4j.core.OComplexObjects$OComplexObjectImpl cannot be cast to org.odata4j.core.OCollection at org.odata4j.format.json.JsonFormatWriter.writeValue(JsonFormatWriter.java:145) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] at org.odata4j.format.json.JsonCollectionFormatWriter.writeContent(JsonCollectionFormatWriter.java:38) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] at org.odata4j.format.json.JsonCollectionFormatWriter.writeContent(JsonCollectionFormatWriter.java:14) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] at -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2993) Adding source table with quoted name results in wrong generated SQL statement

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2993?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2993. ----------------------------------- Resolution: Deferred There are two parts to this issue for the future. The first part is that we would look into altering the parser and the symbols to use the token or some other unmolested user input as the command output. The next part is to alter the resolver to make it aware of the proper usage of name parts - as it currently progressively resolves against partial names. The first change can be done without regard to backwards compatibility, but is inherently a design time concern and seemingly requires adding more state to the symbols. The resolving change could be breaking and would have to be approached more carefully - although from the perspective of Teiid as a database is more proper. > Adding source table with quoted name results in wrong generated SQL statement > ----------------------------------------------------------------------------- > > Key: TEIID-2993 > URL: https://issues.jboss.org/browse/TEIID-2993 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Paul Richardson > Assignee: Steven Hawkins > > Cloned from TEIIDDES-2152: > 1) Created source model with simple table named "My.Quoted.Table" (including quotes > 2) Created simple virtual table and pasted: SELECT * FROM "My.Quoted.Table" > 3) Parser returned a command resulting in the SQL: SELECT * FROM My.Quoted."Table" > Parser should be able to handle quoted names properly. In this case the SQL should have been valid as is. > Confirmed that this does go right back to the Teiid parser. To confirm, the following test was included in > src/test/java/org/teiid/query/parser/TestParser.java > {code} > @Test > public void testQuotedSQLString() { > String sql = "SELECT * FROM \"My.Quoted.Table\""; //$NON-NLS-1$ > String expected = "SELECT * FROM \"MY.QUOTED.TABLE\""; //$NON-NLS-1$ > helpTest(sql, expected, null); > } > {code} > Test fails with a comparison error with the parser returning the SQL in item 3 above. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[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: ------------------------------------ Hi, yes the servlet init parameter would be the best fit for my use cases. The virtual procs are more of a one off for us, but a generic OData cache that by default caches all results sets smaller than some defined number would hit a greater number of ReST queries we're actually servicing. Thanks, John > 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)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2993) Adding source table with quoted name results in wrong generated SQL statement

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-2993?page=com.atlassian.jira.plugin... ] Barry LaFond commented on TEIID-2993: ------------------------------------- I'd say reject it. I'll create a Designer JIRA to remove the validation check and reference this jira. Thx > Adding source table with quoted name results in wrong generated SQL statement > ----------------------------------------------------------------------------- > > Key: TEIID-2993 > URL: https://issues.jboss.org/browse/TEIID-2993 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Paul Richardson > Assignee: Steven Hawkins > > Cloned from TEIIDDES-2152: > 1) Created source model with simple table named "My.Quoted.Table" (including quotes > 2) Created simple virtual table and pasted: SELECT * FROM "My.Quoted.Table" > 3) Parser returned a command resulting in the SQL: SELECT * FROM My.Quoted."Table" > Parser should be able to handle quoted names properly. In this case the SQL should have been valid as is. > Confirmed that this does go right back to the Teiid parser. To confirm, the following test was included in > src/test/java/org/teiid/query/parser/TestParser.java > {code} > @Test > public void testQuotedSQLString() { > String sql = "SELECT * FROM \"My.Quoted.Table\""; //$NON-NLS-1$ > String expected = "SELECT * FROM \"MY.QUOTED.TABLE\""; //$NON-NLS-1$ > helpTest(sql, expected, null); > } > {code} > Test fails with a comparison error with the parser returning the SQL in item 3 above. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2993) Adding source table with quoted name results in wrong generated SQL statement

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2993?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2993: ------------------------------------- I seeing that time is to ripe to ditch, or gut the jdbc importer to use the Teiid translator importer underneath :) > Adding source table with quoted name results in wrong generated SQL statement > ----------------------------------------------------------------------------- > > Key: TEIID-2993 > URL: https://issues.jboss.org/browse/TEIID-2993 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Paul Richardson > Assignee: Steven Hawkins > > Cloned from TEIIDDES-2152: > 1) Created source model with simple table named "My.Quoted.Table" (including quotes > 2) Created simple virtual table and pasted: SELECT * FROM "My.Quoted.Table" > 3) Parser returned a command resulting in the SQL: SELECT * FROM My.Quoted."Table" > Parser should be able to handle quoted names properly. In this case the SQL should have been valid as is. > Confirmed that this does go right back to the Teiid parser. To confirm, the following test was included in > src/test/java/org/teiid/query/parser/TestParser.java > {code} > @Test > public void testQuotedSQLString() { > String sql = "SELECT * FROM \"My.Quoted.Table\""; //$NON-NLS-1$ > String expected = "SELECT * FROM \"MY.QUOTED.TABLE\""; //$NON-NLS-1$ > helpTest(sql, expected, null); > } > {code} > Test fails with a comparison error with the parser returning the SQL in item 3 above. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2014