hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Illecker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-699) Add commons module
Date Thu, 24 Oct 2013 14:18:04 GMT

    [ https://issues.apache.org/jira/browse/HAMA-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804235#comment-13804235

Martin Illecker commented on HAMA-699:

A lot of io classes currently located in o.a.h.bsp have a dependency to BSP, BSPJob, BSPPeer.
e.g., PartitioningRunner needs BSP, BSPPeer
If we would add PartitioningRunner and others to o.a.h.c.io (commons) we would need a dependency
from commons to core, which would lead to a cyclic one.

Therefore it's not possible to combine all io classes in commons without moving BSP, BSPJob,
BSPPeer from core to commons!

o.a.h.c.io.writable.* don't need a dependency to core therefore we can isolate them in commons.
So the dependency issue is not between o.a.h.c.io.* and o.a.h.c.io.writable.*, it's a cyclic
dependency between commons and core module.

> Add commons module
> ------------------
>                 Key: HAMA-699
>                 URL: https://issues.apache.org/jira/browse/HAMA-699
>             Project: Hama
>          Issue Type: Improvement
>            Reporter: Edward J. Yoon
>            Assignee: Martin Illecker
>             Fix For: 0.7.0
>         Attachments: commons-module.txt, HAMA-699.patch
> As we disscussed, I'd like to add commons module.

This message was sent by Atlassian JIRA

View raw message