August 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5455) Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5455?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5455. ----------------------------------- Fix Version/s: 11.1 Resolution: Done Added code to allow the resultset cache property to elevate caching beyond session specific. > Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries > ----------------------------------------------------------------------- > > Key: TEIID-5455 > URL: https://issues.jboss.org/browse/TEIID-5455 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12.14.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 11.1 > > > The Result Set Cache Hit Ratio percentage metric appears to only use JDBC and ODBC connections in the calculation. Connected via JDBC with resultSetCacheMode=true Connection property and ran the same query a few times and it shows values in the Management Console for Hit Ratio %, Total Entries and Request Count. The same result when using vdb property "<property name="connection.resultSetCacheMode" value="true"/>" and ODBC connection. But after adding the init-param connection property[1] to the web.xml of the teiid-olingo-odata4.war and restarting the server. Then running the same odata4 query a few times only values show for Total Entries and Request Count, the Hit Ratio is still at 0.0. Is this intended behavior? Or should Odata and Odata4 queries be included in the Ratio? > [1] > <init-param> > <param-name>connection.resultSetCacheMode</param-name> > <param-value>true</param-value> > </init-param> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5455) Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5455?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-5455: ----------------------------------- > Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries > ----------------------------------------------------------------------- > > Key: TEIID-5455 > URL: https://issues.jboss.org/browse/TEIID-5455 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12.14.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > The Result Set Cache Hit Ratio percentage metric appears to only use JDBC and ODBC connections in the calculation. Connected via JDBC with resultSetCacheMode=true Connection property and ran the same query a few times and it shows values in the Management Console for Hit Ratio %, Total Entries and Request Count. The same result when using vdb property "<property name="connection.resultSetCacheMode" value="true"/>" and ODBC connection. But after adding the init-param connection property[1] to the web.xml of the teiid-olingo-odata4.war and restarting the server. Then running the same odata4 query a few times only values show for Total Entries and Request Count, the Hit Ratio is still at 0.0. Is this intended behavior? Or should Odata and Odata4 queries be included in the Ratio? > [1] > <init-param> > <param-name>connection.resultSetCacheMode</param-name> > <param-value>true</param-value> > </init-param> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5455) Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5455?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5455: --------------------------------------- I don't mean that it's an invalid request, just that odata had different caching behavior. I'll go ahead an implement this upstream. > Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries > ----------------------------------------------------------------------- > > Key: TEIID-5455 > URL: https://issues.jboss.org/browse/TEIID-5455 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12.14.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > The Result Set Cache Hit Ratio percentage metric appears to only use JDBC and ODBC connections in the calculation. Connected via JDBC with resultSetCacheMode=true Connection property and ran the same query a few times and it shows values in the Management Console for Hit Ratio %, Total Entries and Request Count. The same result when using vdb property "<property name="connection.resultSetCacheMode" value="true"/>" and ODBC connection. But after adding the init-param connection property[1] to the web.xml of the teiid-olingo-odata4.war and restarting the server. Then running the same odata4 query a few times only values show for Total Entries and Request Count, the Hit Ratio is still at 0.0. Is this intended behavior? Or should Odata and Odata4 queries be included in the Ratio? > [1] > <init-param> > <param-name>connection.resultSetCacheMode</param-name> > <param-value>true</param-value> > </init-param> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5455) Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-5455?page=com.atlassian.jira.plugin... ] Debbie Steigner closed TEIID-5455. ---------------------------------- Resolution: Won't Do > Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries > ----------------------------------------------------------------------- > > Key: TEIID-5455 > URL: https://issues.jboss.org/browse/TEIID-5455 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12.14.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > The Result Set Cache Hit Ratio percentage metric appears to only use JDBC and ODBC connections in the calculation. Connected via JDBC with resultSetCacheMode=true Connection property and ran the same query a few times and it shows values in the Management Console for Hit Ratio %, Total Entries and Request Count. The same result when using vdb property "<property name="connection.resultSetCacheMode" value="true"/>" and ODBC connection. But after adding the init-param connection property[1] to the web.xml of the teiid-olingo-odata4.war and restarting the server. Then running the same odata4 query a few times only values show for Total Entries and Request Count, the Hit Ratio is still at 0.0. Is this intended behavior? Or should Odata and Odata4 queries be included in the Ratio? > [1] > <init-param> > <param-name>connection.resultSetCacheMode</param-name> > <param-value>true</param-value> > </init-param> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5455) Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-5455?page=com.atlassian.jira.plugin... ] Debbie Steigner commented on TEIID-5455: ---------------------------------------- [~shawkins] Ok no problem I'll go ahead and close this jira. Thank you. > Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries > ----------------------------------------------------------------------- > > Key: TEIID-5455 > URL: https://issues.jboss.org/browse/TEIID-5455 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12.14.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > The Result Set Cache Hit Ratio percentage metric appears to only use JDBC and ODBC connections in the calculation. Connected via JDBC with resultSetCacheMode=true Connection property and ran the same query a few times and it shows values in the Management Console for Hit Ratio %, Total Entries and Request Count. The same result when using vdb property "<property name="connection.resultSetCacheMode" value="true"/>" and ODBC connection. But after adding the init-param connection property[1] to the web.xml of the teiid-olingo-odata4.war and restarting the server. Then running the same odata4 query a few times only values show for Total Entries and Request Count, the Hit Ratio is still at 0.0. Is this intended behavior? Or should Odata and Odata4 queries be included in the Ratio? > [1] > <init-param> > <param-name>connection.resultSetCacheMode</param-name> > <param-value>true</param-value> > </init-param> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5455) Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5455?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5455: ---------------------------------- Issue Type: Enhancement (was: Bug) Component/s: OData > Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries > ----------------------------------------------------------------------- > > Key: TEIID-5455 > URL: https://issues.jboss.org/browse/TEIID-5455 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12.14.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > The Result Set Cache Hit Ratio percentage metric appears to only use JDBC and ODBC connections in the calculation. Connected via JDBC with resultSetCacheMode=true Connection property and ran the same query a few times and it shows values in the Management Console for Hit Ratio %, Total Entries and Request Count. The same result when using vdb property "<property name="connection.resultSetCacheMode" value="true"/>" and ODBC connection. But after adding the init-param connection property[1] to the web.xml of the teiid-olingo-odata4.war and restarting the server. Then running the same odata4 query a few times only values show for Total Entries and Request Count, the Hit Ratio is still at 0.0. Is this intended behavior? Or should Odata and Odata4 queries be included in the Ratio? > [1] > <init-param> > <param-name>connection.resultSetCacheMode</param-name> > <param-value>true</param-value> > </init-param> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5455) Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5455?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5455: --------------------------------------- To support odata pagination the odata layer already adds its own cache hint which currently supersedes the result set cache mode as it makes the query results specific to a given skipToken. This would be a new feature to allow query results to be cached at a higher level via the connection property. > Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries > ----------------------------------------------------------------------- > > Key: TEIID-5455 > URL: https://issues.jboss.org/browse/TEIID-5455 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.14.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > The Result Set Cache Hit Ratio percentage metric appears to only use JDBC and ODBC connections in the calculation. Connected via JDBC with resultSetCacheMode=true Connection property and ran the same query a few times and it shows values in the Management Console for Hit Ratio %, Total Entries and Request Count. The same result when using vdb property "<property name="connection.resultSetCacheMode" value="true"/>" and ODBC connection. But after adding the init-param connection property[1] to the web.xml of the teiid-olingo-odata4.war and restarting the server. Then running the same odata4 query a few times only values show for Total Entries and Request Count, the Hit Ratio is still at 0.0. Is this intended behavior? Or should Odata and Odata4 queries be included in the Ratio? > [1] > <init-param> > <param-name>connection.resultSetCacheMode</param-name> > <param-value>true</param-value> > </init-param> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5455) Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries

by Debbie Steigner (JIRA)

Debbie Steigner created TEIID-5455: -------------------------------------- Summary: Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries Key: TEIID-5455 URL: https://issues.jboss.org/browse/TEIID-5455 Project: Teiid Issue Type: Bug Affects Versions: 8.12.14.6_4 Reporter: Debbie Steigner Assignee: Steven Hawkins The Result Set Cache Hit Ratio percentage metric appears to only use JDBC and ODBC connections in the calculation. Connected via JDBC with resultSetCacheMode=true Connection property and ran the same query a few times and it shows values in the Management Console for Hit Ratio %, Total Entries and Request Count. The same result when using vdb property "<property name="connection.resultSetCacheMode" value="true"/>" and ODBC connection. But after adding the init-param connection property[1] to the web.xml of the teiid-olingo-odata4.war and restarting the server. Then running the same odata4 query a few times only values show for Total Entries and Request Count, the Hit Ratio is still at 0.0. Is this intended behavior? Or should Odata and Odata4 queries be included in the Ratio? [1] <init-param> <param-name>connection.resultSetCacheMode</param-name> <param-value>true</param-value> </init-param> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4340) add encoding as "UTF-8-BOM" in the file translator override property

by Tom Johnston (JIRA)

[ https://issues.jboss.org/browse/TEIID-4340?page=com.atlassian.jira.plugin... ] Tom Johnston commented on TEIID-4340: ------------------------------------- Right now I can't get the output from the replace to work with texttable but yes I am concerned for files longer than 4000 chars. > add encoding as "UTF-8-BOM" in the file translator override property > -------------------------------------------------------------------- > > Key: TEIID-4340 > URL: https://issues.jboss.org/browse/TEIID-4340 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.7.8.6_2 > Reporter: Debbie Steigner > Priority: Trivial > Fix For: Open To Community > > > it will be good if teiid supports Encoding to "UTF-8-BOM" since other middleware technologies supports similar to this and also even editor such as Notepad++ supports to convert / save file as "UTF-8-BOM". > Currently we have added Translator override for File to include "Encoding Property to UTF-8" so similarly we should be able to set it to "UTF-8-BOM" , instead of writing code manually to add BOM to generate a file. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4340) add encoding as "UTF-8-BOM" in the file translator override property

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4340?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4340: --------------------------------------- > but I can't seem to leverage that along with the TEXTTABLE function to provide a usable query... any other thoughts? Yes that will strip the BOM. Locally that seems to work fine. Are you running into issues with files that are longer than 4000 characters? For this issue we could extend the behavior of the UTF8 charset to include BOM handling - which would make it consistent with java's UTF16 and 32 handling - https://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.... > add encoding as "UTF-8-BOM" in the file translator override property > -------------------------------------------------------------------- > > Key: TEIID-4340 > URL: https://issues.jboss.org/browse/TEIID-4340 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.7.8.6_2 > Reporter: Debbie Steigner > Priority: Trivial > Fix For: Open To Community > > > it will be good if teiid supports Encoding to "UTF-8-BOM" since other middleware technologies supports similar to this and also even editor such as Notepad++ supports to convert / save file as "UTF-8-BOM". > Currently we have added Translator override for File to include "Encoding Property to UTF-8" so similarly we should be able to set it to "UTF-8-BOM" , instead of writing code manually to add BOM to generate a file. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2018