[ 
https://issues.apache.org/jira/browse/IGNITE-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496112#comment-15496112
 ] 

ASF GitHub Bot commented on IGNITE-3916:
----------------------------------------

GitHub user devozerov opened a pull request:

    https://github.com/apache/ignite/pull/1072

    IGNITE-3916: Initial impl.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-3916

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/1072.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1072
    
----
commit b74894579b05fae59e5ec9c9de93be6c6de830c2
Author: vozerov-gridgain <voze...@gridgain.com>
Date:   2016-09-16T11:20:11Z

    IGNITE-3916: Initial impl.

----


> Hadoop: Create additional module.
> ---------------------------------
>
>                 Key: IGNITE-3916
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3916
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: hadoop
>    Affects Versions: 1.7
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>             Fix For: 1.8
>
>
> The plan is as follows:
> 1) {{ignite-hadoop}} will have helpers and interfaces, but *will not* have 
> direct Hadoop dependency. This module will be loaded in runtime by the core.
> 2) {{ignite-hadoop-impl}} will have Hadoop-dependent implementations and have 
> direct dependency on Hadoop libraries. It will be accessed only through 
> {{HadoopClassLoader}} interface and should not be located in normal classpath 
> of the {{core}} module.
> In this ticket we should only create additional module, move all current 
> Hadoop classes there, and ensure correct dependencies 
> {{core <- hadoop <- hadoop-impl}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to