[
https://issues.apache.org/jira/browse/IGNITE-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14974861#comment-14974861
]
Konstantin Boudnik commented on IGNITE-1701:
--------------------------------------------
I haven't committed it yet. And yes, I am aware about this thread and the
issue. It has nothing to do with the patch in question. The problem user is
facing comes from running ignite and spark services under different user
accounts. Which leads to the permission conflicts in {{/tmp/ignite}} work
directory. I worked with Rich directly and the issue was solved (see
[here|http://apache-ignite-users.70518.x6.nabble.com/Question-about-getting-started-with-spark-shell-tp1663p1676.html]
Ideally, it needs to be documented as the requirement. Also, is it possible to
start an Ignite node and specify the location of the work directory via command
line or sys.prop?
The patch has been tested and as it stance shouldn't pose any threat to the
release, unless there some sudden incompatibilities between new spark and
latest ignite, which I don't think is the case. Will be committing this today.
Thanks!
> Bump Spark dependenency to 1.5.1 (the latest stable)
> ----------------------------------------------------
>
> Key: IGNITE-1701
> URL: https://issues.apache.org/jira/browse/IGNITE-1701
> Project: Ignite
> Issue Type: Improvement
> Components: build
> Affects Versions: ignite-1.4
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Fix For: 1.5
>
> Attachments: IGNITE-1701.patch
>
>
> At the moment, {{ignite-spark}} module is built against spark 1.3.1 which is
> like 3 versions old already. Let's bump the version to 1.5.1, which is the
> latest stable.
> In the process, I'd like to add an ability to specify the version of Spark
> during the build time, like it is done for Hadoop now.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
