[
https://issues.apache.org/jira/browse/IGNITE-7077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440351#comment-16440351
]
Valentin Kulichenko commented on IGNITE-7077:
---------------------------------------------
[~NIzhikov], several minor comments.
# I noticed that the new setting name has {{ignite.}} prefix. I generally like
this, but this is not consistent with others. Is it possible to change all
others in the same way? If yes, let's do this. Otherwise, let's remove the
prefix.
# Is {{IgniteOptimization}} a public class? If yes, is this required? If not
required, is it possible to avoid that?
# Out of curiosity, what is the purpose of the code below? Shouldn't we just do
nothing if optimization is disabled?
{code}
if (optimizationDisabled)
experimentalMethods.extraOptimizations.filter(_ != IgniteOptimization)
{code}
> 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.5
>
>
> 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)
