[ https://issues.apache.org/jira/browse/IGNITE-7077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328944#comment-16328944 ]
ASF GitHub Bot commented on IGNITE-7077: ---------------------------------------- GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/3397 IGNITE-7077: Implementation of Spark query optimization. You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite IGNITE-7077 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3397.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3397 ---- ---- > Spark Data Frame Support. Strategy to convert complete query to Ignite SQL > -------------------------------------------------------------------------- > > Key: IGNITE-7077 > URL: https://issues.apache.org/jira/browse/IGNITE-7077 > Project: Ignite > Issue Type: New Feature > Components: spark > Affects Versions: 2.3 > Reporter: Nikolay Izhikov > Assignee: Nikolay Izhikov > Priority: Major > Labels: bigdata > Fix For: 2.4 > > > Basic support of Spark Data Frame for Ignite implemented in IGNITE-3084. > We need to implement custom spark strategy that can convert whole Spark SQL > query to Ignite SQL Query if query consists of only Ignite tables. > The strategy does nothing if spark query includes not only Ignite tables. > Memsql implementation can be taken as an example - > https://github.com/memsql/memsql-spark-connector -- This message was sent by Atlassian JIRA (v7.6.3#76005)