[JBoss JIRA] (TEIID-2656) Teiid OData Servlet throws java.lang.NullPointerException on every GET
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2656?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2656:
---------------------------------------
> There will be any fixes for this for 8.3?
Not by the core team. You should be able to patch 8.3 based upon the commit and build from source. Also this only affects Designer based VDBs so a workaround would be to use a dynamic vdb.
> We cannot pass to EAP
Keep in mind that EAP 6 Alpha is the same as AS 7.2.
> Teiid OData Servlet throws java.lang.NullPointerException on every GET
> ----------------------------------------------------------------------
>
> Key: TEIID-2656
> URL: https://issues.jboss.org/browse/TEIID-2656
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.3, 8.4
> Environment: Windows 7 64 bit
> Oracle JDK 1.7.0 update 17
> JBoss AS 7.1.1 + Teiid 8.3 (both resteasy-jaxrs 2.3.5 and 2.3.7)
> JBoss EAP 6.1 + Teiid 8.4 (resteasy-jaxrs 2.3.6)
> Reporter: John Muller
> Assignee: Steven Hawkins
> Labels: final
> Fix For: 8.4.1, 8.5
>
> Attachments: server.log, Teiid_8.4_on_JBoss_EAP_6.1Alpha_RHEL6.log
>
>
> A simple GET on any Teiid 8.3 or 8.4 OData ReST resource results in a Null Pointer:
> 11:43:20,166 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/odata].[Resteasy]] (http-localhost-127.0.0.1-8080-2) Servlet.service() for servlet Resteasy threw exception: java.lang.NullPointerException
> at com.ctc.wstx.sw.BaseStreamWriter.writeCharacters(BaseStreamWriter.java:447)
> at org.codehaus.stax2.ri.Stax2EventWriterImpl.add(Stax2EventWriterImpl.java:124)
> at org.odata4j.stax2.staximpl.StaxXMLWriter2.writeText(StaxXMLWriter2.java:108) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.odata4j.format.xml.AtomErrorFormatWriter.writeError(AtomErrorFormatWriter.java:31) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.odata4j.format.xml.AtomErrorFormatWriter.write(AtomErrorFormatWriter.java:20) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.odata4j.format.xml.AtomErrorFormatWriter.write(AtomErrorFormatWriter.java:15) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.teiid.odata.ODataExceptionMappingProvider.toResponse(ODataExceptionMappingProvider.java:55) [classes:]
> at org.teiid.odata.ODataExceptionMappingProvider.toResponse(ODataExceptionMappingProvider.java:42) [classes:]
> at org.jboss.resteasy.core.SynchronousDispatcher.executeExceptionMapper(SynchronousDispatcher.java:344) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.unwrapException(SynchronousDispatcher.java:373) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:362) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:233) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:209) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:557) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97) [classes:]
> at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.7.Final.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:489) [jbossweb-7.0.13.Final.jar:]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_17]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIID-2656) Teiid OData Servlet throws java.lang.NullPointerException on every GET
by luca gioppo (JIRA)
[ https://issues.jboss.org/browse/TEIID-2656?page=com.atlassian.jira.plugin... ]
luca gioppo commented on TEIID-2656:
------------------------------------
There will be any fixes for this for 8.3?
We cannot pass to EAP and are at the time stuck with 7.1.1 and 8.3
Thanks
Luca
> Teiid OData Servlet throws java.lang.NullPointerException on every GET
> ----------------------------------------------------------------------
>
> Key: TEIID-2656
> URL: https://issues.jboss.org/browse/TEIID-2656
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.3, 8.4
> Environment: Windows 7 64 bit
> Oracle JDK 1.7.0 update 17
> JBoss AS 7.1.1 + Teiid 8.3 (both resteasy-jaxrs 2.3.5 and 2.3.7)
> JBoss EAP 6.1 + Teiid 8.4 (resteasy-jaxrs 2.3.6)
> Reporter: John Muller
> Assignee: Steven Hawkins
> Labels: final
> Fix For: 8.4.1, 8.5
>
> Attachments: server.log, Teiid_8.4_on_JBoss_EAP_6.1Alpha_RHEL6.log
>
>
> A simple GET on any Teiid 8.3 or 8.4 OData ReST resource results in a Null Pointer:
> 11:43:20,166 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/odata].[Resteasy]] (http-localhost-127.0.0.1-8080-2) Servlet.service() for servlet Resteasy threw exception: java.lang.NullPointerException
> at com.ctc.wstx.sw.BaseStreamWriter.writeCharacters(BaseStreamWriter.java:447)
> at org.codehaus.stax2.ri.Stax2EventWriterImpl.add(Stax2EventWriterImpl.java:124)
> at org.odata4j.stax2.staximpl.StaxXMLWriter2.writeText(StaxXMLWriter2.java:108) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.odata4j.format.xml.AtomErrorFormatWriter.writeError(AtomErrorFormatWriter.java:31) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.odata4j.format.xml.AtomErrorFormatWriter.write(AtomErrorFormatWriter.java:20) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.odata4j.format.xml.AtomErrorFormatWriter.write(AtomErrorFormatWriter.java:15) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.teiid.odata.ODataExceptionMappingProvider.toResponse(ODataExceptionMappingProvider.java:55) [classes:]
> at org.teiid.odata.ODataExceptionMappingProvider.toResponse(ODataExceptionMappingProvider.java:42) [classes:]
> at org.jboss.resteasy.core.SynchronousDispatcher.executeExceptionMapper(SynchronousDispatcher.java:344) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.unwrapException(SynchronousDispatcher.java:373) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:362) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:233) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:209) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:557) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97) [classes:]
> at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.7.Final.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:489) [jbossweb-7.0.13.Final.jar:]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_17]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIID-2706) Cache hint for resultset cache in user query doesn't work
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2706?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2706.
-----------------------------------
Resolution: Cannot Reproduce Bug
I don't see this behavior on latest under a controlled scenario (directly using jdbc), so marking as non-reproducible.
> Cache hint for resultset cache in user query doesn't work
> ---------------------------------------------------------
>
> Key: TEIID-2706
> URL: https://issues.jboss.org/browse/TEIID-2706
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7.7
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> I enabled TRACE logging and Command Logging to see if the Resultset Cache was being used on my queries. If I use the ResultSetCacheMode=true on connection string you can see Teiid using the cache instead of pulling from source again:
> This is displayed the first time the query is run, it's loading the Cache:
> 2013-10-18 07:17:52,951 TRACE [org.teiid.PROCESSOR] Adding to global/distributed cache Cache Entry<tR+M2n5wIwzI=bqt2@teiid-security> params:null sql:select * from SmallA
> This displays the subsequent times the same query is run and you will not see source queries:
> 2013-10-18 07:19:21,115 TRACE [org.teiid.PROCESSOR] Cache hit for Cache Entry<tR+M2n5wIwzI=bqt2@teiid-security> params:null sql:select * from SmallA
> But if I remove the connection string and just try using the Cache Hint /*+ cache*/ you see nothing in the logs in regards to the Cache loading or being used on the second query, you still see Teiid pulling the results from the source.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIID-2706) Cache hint for resultset cache in user query doesn't work
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIID-2706?page=com.atlassian.jira.plugin... ]
Debbie Steigner commented on TEIID-2706:
----------------------------------------
Strange, I restarted JBDS and picked a different table and now it is working. So I guess we can close this JIRA
> Cache hint for resultset cache in user query doesn't work
> ---------------------------------------------------------
>
> Key: TEIID-2706
> URL: https://issues.jboss.org/browse/TEIID-2706
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7.7
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> I enabled TRACE logging and Command Logging to see if the Resultset Cache was being used on my queries. If I use the ResultSetCacheMode=true on connection string you can see Teiid using the cache instead of pulling from source again:
> This is displayed the first time the query is run, it's loading the Cache:
> 2013-10-18 07:17:52,951 TRACE [org.teiid.PROCESSOR] Adding to global/distributed cache Cache Entry<tR+M2n5wIwzI=bqt2@teiid-security> params:null sql:select * from SmallA
> This displays the subsequent times the same query is run and you will not see source queries:
> 2013-10-18 07:19:21,115 TRACE [org.teiid.PROCESSOR] Cache hit for Cache Entry<tR+M2n5wIwzI=bqt2@teiid-security> params:null sql:select * from SmallA
> But if I remove the connection string and just try using the Cache Hint /*+ cache*/ you see nothing in the logs in regards to the Cache loading or being used on the second query, you still see Teiid pulling the results from the source.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIID-2706) Cache hint for resultset cache in user query doesn't work
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIID-2706?page=com.atlassian.jira.plugin... ]
Debbie Steigner commented on TEIID-2706:
----------------------------------------
Not unless it's on by default in the Designer
> Cache hint for resultset cache in user query doesn't work
> ---------------------------------------------------------
>
> Key: TEIID-2706
> URL: https://issues.jboss.org/browse/TEIID-2706
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7.7
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> I enabled TRACE logging and Command Logging to see if the Resultset Cache was being used on my queries. If I use the ResultSetCacheMode=true on connection string you can see Teiid using the cache instead of pulling from source again:
> This is displayed the first time the query is run, it's loading the Cache:
> 2013-10-18 07:17:52,951 TRACE [org.teiid.PROCESSOR] Adding to global/distributed cache Cache Entry<tR+M2n5wIwzI=bqt2@teiid-security> params:null sql:select * from SmallA
> This displays the subsequent times the same query is run and you will not see source queries:
> 2013-10-18 07:19:21,115 TRACE [org.teiid.PROCESSOR] Cache hit for Cache Entry<tR+M2n5wIwzI=bqt2@teiid-security> params:null sql:select * from SmallA
> But if I remove the connection string and just try using the Cache Hint /*+ cache*/ you see nothing in the logs in regards to the Cache loading or being used on the second query, you still see Teiid pulling the results from the source.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIID-2706) Cache hint for resultset cache in user query doesn't work
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2706?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2706:
---------------------------------------
Are you running with noexec turned on?
> Cache hint for resultset cache in user query doesn't work
> ---------------------------------------------------------
>
> Key: TEIID-2706
> URL: https://issues.jboss.org/browse/TEIID-2706
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7.7
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> I enabled TRACE logging and Command Logging to see if the Resultset Cache was being used on my queries. If I use the ResultSetCacheMode=true on connection string you can see Teiid using the cache instead of pulling from source again:
> This is displayed the first time the query is run, it's loading the Cache:
> 2013-10-18 07:17:52,951 TRACE [org.teiid.PROCESSOR] Adding to global/distributed cache Cache Entry<tR+M2n5wIwzI=bqt2@teiid-security> params:null sql:select * from SmallA
> This displays the subsequent times the same query is run and you will not see source queries:
> 2013-10-18 07:19:21,115 TRACE [org.teiid.PROCESSOR] Cache hit for Cache Entry<tR+M2n5wIwzI=bqt2@teiid-security> params:null sql:select * from SmallA
> But if I remove the connection string and just try using the Cache Hint /*+ cache*/ you see nothing in the logs in regards to the Cache loading or being used on the second query, you still see Teiid pulling the results from the source.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIID-2706) Cache hint for resultset cache in user query doesn't work
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIID-2706?page=com.atlassian.jira.plugin... ]
Debbie Steigner commented on TEIID-2706:
----------------------------------------
Using VDB Execute in the Designer, you can see the hint coming thru, so
/*+ cache */ select * from bqt.SmallA
Shows it using the cache hint:
2013-10-21 07:22:29,923 DEBUG [org.teiid.PROCESSOR] CCeIPNy1zUVF.0 Using cache hint /*+ cache */
2013-10-21 07:22:29,923 TRACE [org.teiid.PROCESSOR] Adding to global/distributed cache Cache Entry<CCeIPNy1zUVF=user@teiid-security> params:null sql:/*+ cache */ select * from bqt.SmallA
2013-10-21 07:22:29,924 TRACE [org.teiid.BUFFER_MGR] Add batch to BufferManager 3 with size estimate 83866
2013-10-21 07:22:29,924 DEBUG [org.teiid.PROCESSOR] [RequestWorkItem.sendResultsIfNeeded] requestID: CCeIPNy1zUVF.0 resultsID: 16 done: true
2013-10-21 07:22:29,925 DEBUG [org.teiid.TRANSPORT] send message: MessageHolder: key=35 contents=ResultsMessage rowCount=50 finalRow=50
But then when I rerun the same query: /*+ cache */ select * from bqt.SmallA
It shows it hitting the cache, but it returns 0 rows.
2013-10-21 07:22:43,356 TRACE [org.teiid.PROCESSOR] Cache hit for Cache Entry<QJa3VEi6VZAC=user@teiid-security> params:null sql:/*+ cache */ select * from bqt.SmallA
2013-10-21 07:22:43,356 TRACE [org.teiid.PLANNER.RESOLVER] Resolving command /*+ cache */ SELECT * FROM bqt.SmallA
2013-10-21 07:22:43,356 DEBUG [org.teiid.PROCESSOR] [RequestWorkItem.sendResultsIfNeeded] requestID: QJa3VEi6VZAC.0 resultsID: 16 done: true
2013-10-21 07:22:43,356 DEBUG [org.teiid.TRANSPORT] send message: MessageHolder: key=41 contents=ResultsMessage rowCount=0 finalRow=0
> Cache hint for resultset cache in user query doesn't work
> ---------------------------------------------------------
>
> Key: TEIID-2706
> URL: https://issues.jboss.org/browse/TEIID-2706
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7.7
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> I enabled TRACE logging and Command Logging to see if the Resultset Cache was being used on my queries. If I use the ResultSetCacheMode=true on connection string you can see Teiid using the cache instead of pulling from source again:
> This is displayed the first time the query is run, it's loading the Cache:
> 2013-10-18 07:17:52,951 TRACE [org.teiid.PROCESSOR] Adding to global/distributed cache Cache Entry<tR+M2n5wIwzI=bqt2@teiid-security> params:null sql:select * from SmallA
> This displays the subsequent times the same query is run and you will not see source queries:
> 2013-10-18 07:19:21,115 TRACE [org.teiid.PROCESSOR] Cache hit for Cache Entry<tR+M2n5wIwzI=bqt2@teiid-security> params:null sql:select * from SmallA
> But if I remove the connection string and just try using the Cache Hint /*+ cache*/ you see nothing in the logs in regards to the Cache loading or being used on the second query, you still see Teiid pulling the results from the source.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months