[jira] [Updated] (IGNITE-1555) Combine ignite-hadoop and ignite-spark into signle assembly for downstream consumption.
[ https://issues.apache.org/jira/browse/IGNITE-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated IGNITE-1555: --- Attachment: IGNITE-1555.patch > 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)
[jira] [Updated] (IGNITE-1555) Combine ignite-hadoop and ignite-spark into signle assembly for downstream consumption.
[ https://issues.apache.org/jira/browse/IGNITE-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated IGNITE-1555: --- Summary: Combine ignite-hadoop and ignite-spark into signle assembly for downstream consumption. (was: Combine ignite-hadoop and ignite-spark into signle ignite-accelerator assembly.) > 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 > > > 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)
[jira] [Updated] (IGNITE-1555) Combine ignite-hadoop and ignite-spark into signle assembly for downstream consumption.
[ https://issues.apache.org/jira/browse/IGNITE-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated IGNITE-1555: --- Attachment: IGNITE-1555.patch > 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 > > > 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)
[jira] [Updated] (IGNITE-1555) Combine ignite-hadoop and ignite-spark into signle assembly for downstream consumption.
[
https://issues.apache.org/jira/browse/IGNITE-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated IGNITE-1555:
---
Attachment: IGNITE-1555.patch
Latest patch for the {{integration}} edition
> 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
>
>
> 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)
[jira] [Updated] (IGNITE-1555) Combine ignite-hadoop and ignite-spark into signle assembly for downstream consumption.
[ https://issues.apache.org/jira/browse/IGNITE-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated IGNITE-1555: --- Attachment: (was: IGNITE-1555.patch) > 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 > > > 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)
