[
https://issues.apache.org/jira/browse/IGNITE-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948189#comment-14948189
]
Vladimir Ozerov commented on IGNITE-1555:
-----------------------------------------
Honestly, I have no other ideas how to express both Hadoop and Spark
integration modules in a single word or so. Another problem is that the list of
modules included into "accelerator" might evolve over time as we add
integrations with other products.
Provided that Ignite Hadoop and Ignite Spark users are usually disjoint (am I
right here?), may be it is better to leave "ignite-hadoop" build as is, and
make "ignite-accelerator" separate assembly which will be primarily used for
projects like BigTop?
If this suggestion doesn't make sense, let's stick with "ignite-accelerator" as
there are no other ideas.
> Combine ignite-hadoop and ignite-spark into signle ignite-accelerator
> assembly.
> -------------------------------------------------------------------------------
>
> Key: IGNITE-1555
> URL: https://issues.apache.org/jira/browse/IGNITE-1555
> Project: Ignite
> Issue Type: New Feature
> Components: hadoop
> Affects Versions: ignite-1.4
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Fix For: ignite-1.5
>
> Attachments: IGNITE-1555.patch, IGNITE-1555.patch
>
>
> Let's combine all nice things that Ignite provides for Hadoop and Spark into
> single assembly called ignite-accelerator. This will be advantageous for
> downstream integrators like Bigtop, where all bits can be packaged together,
> tested, and deployed with proper configurations and permissions to avoid
> interoperability issues. A typical is when spark-shell starts an Ignite node
> which crashes because user 'spark' isn't allowed to write into Ignite's
> work-dir, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
