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

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

GitHub user tledkov-gridgain opened a pull request:

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

    IGNITE-3167 Hadoop: restore external execution.

    

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

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

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

    https://github.com/apache/ignite/pull/987.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 #987
    
----
commit 4e9e7b8ee1c990bacdc2d081b706ca315927fdce
Author: vozerov-gridgain <[email protected]>
Date:   2016-08-24T09:12:00Z

    IGNITE-3716: ODBC: Added SQL escape sequence parsing.

commit 118db2fcffe3534aa1e5f4b97b8fbe23891752c4
Author: vozerov-gridgain <[email protected]>
Date:   2016-08-24T09:12:24Z

    Merge remote-tracking branch 'upstream/ignite-1.6.6' into ignite-1.6.6

commit c02ad87f863bd730e60fb7052547fa0848e7eb77
Author: isapego <[email protected]>
Date:   2016-08-24T14:21:48Z

    IGNITE-3736: ODBC: Added support for string scalar functions. This closes 
#979.

commit 13dfcbe03aca137ee70698f6083df27c10ecdaf9
Author: vozerov-gridgain <[email protected]>
Date:   2016-08-24T14:31:38Z

    IGNITE-3736: ODBC: Reverted back removed "supported" futures.

commit d6449ffbc65acda6a2cf4484608188367837dd17
Author: sboikov <[email protected]>
Date:   2016-08-24T15:34:02Z

    Fixed issues on node stop:
    - in service processor need guard depExe access with busyLock
    - do not error log IO errors in ClientImpl on stop

commit 12fd4976f482ebc43831754645e34042c9073b2d
Author: sboikov <[email protected]>
Date:   2016-08-25T09:29:04Z

    Fixed GridQueryParsingTest.

commit 6eefceb98deed5d65f17cb327517dd1599bfe068
Author: tledkov-gridgain <[email protected]>
Date:   2016-08-25T15:34:01Z

    IGNITE-3167 Hadoop: restore external execution.

----


> Hadoop: restore external execution.
> -----------------------------------
>
>                 Key: IGNITE-3167
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3167
>             Project: Ignite
>          Issue Type: Task
>          Components: hadoop
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ozerov
>            Assignee: Taras Ledkov
>            Priority: Critical
>              Labels: roadmap
>
> Some time ago we decided to get rid external execution mode. It appears to be 
> a wrong decision.
> Hadoop users rely on its process-per-job nature in lot's places. One of such 
> case could be observed in HiBench Bayes benchmark:
> 1) Job creates something in the local file system through Hadoop FileSystem 
> API.
> 2) Then it tries to get this data using regular java.io.FileReader and 
> relative paths. 
> This doesn't work in embedded mode because our LocalFileSystem wrapper 
> assigns different work dirs for jobs, but process-wide working directory is 
> always the same. As a result, aforementioned benchmark doesn't work in 
> Ignite, but work with standard Hadoop job tracker.
> It seems that we must return external execution back.



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

Reply via email to