Ticket created: https://issues.apache.org/jira/browse/IGNITE-7092
-Val
On Thu, Nov 30, 2017 at 5:01 PM, Denis Magda wrote:
> Val,
>
> Sounds reasonable to me. The fewer useless and potentially harmful
> features or “switches” we have in Ignite the clear it will be for the user
> how to use us i
Val,
Sounds reasonable to me. The fewer useless and potentially harmful features or
“switches” we have in Ignite the clear it will be for the user how to use us in
a right way.
+1 for the deprecation and further removal.
—
Denis
> On Nov 30, 2017, at 3:07 PM, Valentin Kulichenko
> wrote:
>
So for what it's worth more and more of Spark's own services have also
moved to be in separate processes, and with the increased work around
scaling the executors are going to continue this trend.
On Thu, Nov 30, 2017 at 3:07 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Ignit
Igniters,
Currently we claim to support IgniteRDD in two modes: standalone and
embedded. Standalone means there is a separately running Ignite cluster,
and Spark start client node(s) to interact with it. In embedded node
everything runs within Spark, including Ignite server nodes that are
started
