[ https://issues.apache.org/jira/browse/IGNITE-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333607#comment-16333607 ]
Vladimir Ozerov commented on IGNITE-5571: ----------------------------------------- [~al.psc], looks like final round of conflict resolution is needed (conflicts with recent error handling improvements). > Make sure that cache-less execution works as good as cache-based > ---------------------------------------------------------------- > > Key: IGNITE-5571 > URL: https://issues.apache.org/jira/browse/IGNITE-5571 > Project: Ignite > Issue Type: Task > Components: sql > Reporter: Vladimir Ozerov > Assignee: Alexander Paschenko > Priority: Critical > Fix For: 2.4 > > > Compare the following two methods: > 1) {{GridQueryProcessor.querySqlFields}} - old good entry point for query > execution; > 2) {{GridQueryProcessor.querySqlFieldsNoCache}} - new method for "cache-less" > execution. > Note how cache context is used in the first method: > 1) First, it helps determine whether query can be converted to "local" > 2) Second, it gets query parallelism of current cache, and if it differs from > {{1}}, then it turns on {{distributedJoins}}. > Neither of this happens in the second implementation. Moreover, I had to > throw an exception for local queries, as I didn't know how to handle them > properly. > We need to investigate and fix these two deficiencies somehow. Probably some > inputs from [~sergi.vladykin] would be required, to understand what is going > on. > Our ultimate goal is to make "cache-less" execution as good as the old one. -- This message was sent by Atlassian JIRA (v7.6.3#76005)