[
https://issues.apache.org/jira/browse/IGNITE-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953555#comment-14953555
]
Konstantin Boudnik commented on IGNITE-1555:
--------------------------------------------
Honestly, for last 3 weeks I was trying to see the importance of the name and I
failed. I personally don't envision anyone using a raw assembly being used to
install on a cluster for filesystem caching or else. The assembly is going to
be consumed by downstream projects in an automated fashion. And in such case
name is a negligent matter. At any rate, here's the latest version of the
patch which preserve the name and includes spark integration module into the
binary assembly. I will commit this by the morrow unless I hear any objections
on the approach. Thanks!
> Combine ignite-hadoop and ignite-spark into signle assembly for downstream
> consumption.
> ---------------------------------------------------------------------------------------
>
> 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: 1.5
>
> Attachments: IGNITE-1555.patch, IGNITE-1555.patch, 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)
