hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18640) Move mapreduce out of hbase-server into separate hbase-mapreduce moduel
Date Mon, 28 Aug 2017 19:40:00 GMT

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

Sean Busbey commented on HBASE-18640:
-------------------------------------

sorry boss on the lack of clarity. the contents is the opposite of what you say above. Previously
it had all the MR classes and now it has just the load tool.

I don't think we've ever gotten a ref guide entry for the shaded artifacts put together. 
there was some talk of pushing folks towards them more for 2.0, but I dont' think we ever
got boots on the ground for either a docs update nor an artifact refactoring (I'd favor the
former, personally).

> Move mapreduce out of hbase-server into separate hbase-mapreduce moduel
> -----------------------------------------------------------------------
>
>                 Key: HBASE-18640
>                 URL: https://issues.apache.org/jira/browse/HBASE-18640
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Appy
>            Assignee: Appy
>             Fix For: 2.0.0-alpha-3
>
>         Attachments: HBASE-18640.branch-2.001.patch, HBASE-18640.master.001.patch, HBASE-18640.master.002.patch,
HBASE-18640.master.003.patch, HBASE-18640.master.003.patch, HBASE-18640.master.004.patch,
HBASE-18640.master.004.patch, HBASE-18640.master.005.patch, HBASE-18640.master.006.patch,
HBASE-18640.master.007.patch, HBASE-18640.master.008.patch
>
>
> (Couldn't find another dedicated jira, so creating new one).
> Uploaded patch which is moving ~60 files to the new module. Few notes:
> - The classes remaining in hbase-server are the ones which are intensively coupled with
visibility labels/wal/filesystem/hfile. These can not be migrated to new module until corresponding
subcomponents are untangled out of hbase-server into their own separate modules.
> - Almost all mapreduce tests uses HBaseTestingUtil, so they can't be moved to hbase-mapreduce
module. Given these dependency constraints, one way would be having a separate module for
tests:
> hbase-mapreduce <---- hbase-server <------- hbase-mapreduce-tests 
> Imo, this makes sense and looks fine.
> The only issue is - yetus' pre-commit. It won't run tests in hbase-mapreduce-tests module
if something changed in just hbase-mapreduce. However, yetus' limitation shouldn't warrant
against the idea.
> So i'd say that we should go that way, unless there are better suggestions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message