[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144553#comment-16144553
]
stack commented on HBASE-18640:
---
@appy I am on the doc and basic CLASSPATH issues. I presume you'll work on
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144548#comment-16144548
]
Appy commented on HBASE-18640:
--
I'll work on these followup tasks. Thanks a lot [~busbey] for listing them
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144322#comment-16144322
]
Hudson commented on HBASE-18640:
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3614 (See
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144247#comment-16144247
]
stack commented on HBASE-18640:
---
Thanks for clarification. Makes more sense now.
> Move mapreduce out of
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144244#comment-16144244
]
Sean Busbey commented on HBASE-18640:
-
the {{git reset}} line in my examples is going back to the
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144242#comment-16144242
]
Sean Busbey commented on HBASE-18640:
-
sorry boss on the lack of clarity. the contents is the
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144230#comment-16144230
]
Hudson commented on HBASE-18640:
FAILURE: Integrated in Jenkins build HBase-2.0 #413 (See
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144099#comment-16144099
]
stack commented on HBASE-18640:
---
[~busbey] I started in making a hbase-shaded-mapreduce... easy enough but
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143873#comment-16143873
]
Chia-Ping Tsai commented on HBASE-18640:
I push a
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143493#comment-16143493
]
Chia-Ping Tsai commented on HBASE-18640:
bq. Create a sub task in HBASE-18696 please.
The changes
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143392#comment-16143392
]
Duo Zhang commented on HBASE-18640:
---
[~chia7712] Create a sub task in HBASE-18696 please.
> Move
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143384#comment-16143384
]
stack commented on HBASE-18640:
---
We can do that for endpoints.
Yeah, lets address the teething issues in
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143357#comment-16143357
]
Chia-Ping Tsai commented on HBASE-18640:
HBASE15806 introduce a tool which exports table data by
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143319#comment-16143319
]
Duo Zhang commented on HBASE-18640:
---
And [~appy], seems {{LoadIncrementalHFiles}} does not depend on
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143317#comment-16143317
]
Duo Zhang commented on HBASE-18640:
---
So we need a hbase-shaded-mapreduce module?
> Move mapreduce out
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142702#comment-16142702
]
Appy commented on HBASE-18640:
--
Fixed tabs.
Spark test failure looks related to netty shading. [~stack] Do
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142691#comment-16142691
]
Hudson commented on HBASE-18640:
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3599 (See
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142684#comment-16142684
]
Hadoop QA commented on HBASE-18640:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142658#comment-16142658
]
Hadoop QA commented on HBASE-18640:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142541#comment-16142541
]
Appy commented on HBASE-18640:
--
Uploaded patch for branch-2. Waiting for precommit run.
> Move mapreduce
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142529#comment-16142529
]
Appy commented on HBASE-18640:
--
Pushed to master. Preparing patch for branch-2.
> Move mapreduce out of
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142498#comment-16142498
]
Hadoop QA commented on HBASE-18640:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142451#comment-16142451
]
Appy commented on HBASE-18640:
--
- Addressed all the comments on the RB. [~stack] said to write a release
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142437#comment-16142437
]
Appy commented on HBASE-18640:
--
Nvm, figured out. Had to move test resources to the new module too.
> Move
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142414#comment-16142414
]
Appy commented on HBASE-18640:
--
The last piece remaining is TestImportExport#testImport94Table failure.
For
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142349#comment-16142349
]
Appy commented on HBASE-18640:
--
btw, the only file left in hbase-server is LoadIncrementalHFiles.java which
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141614#comment-16141614
]
Hadoop QA commented on HBASE-18640:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141299#comment-16141299
]
Appy commented on HBASE-18640:
--
Update patch. Ptal at RB. Thanks.
> Move mapreduce out of hbase-server into
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140905#comment-16140905
]
Appy commented on HBASE-18640:
--
Sounds good.
> Move mapreduce out of hbase-server into separate
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140903#comment-16140903
]
stack commented on HBASE-18640:
---
[~appy] Could we have a single hbase-mapreduce module? We are having
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140882#comment-16140882
]
Appy commented on HBASE-18640:
--
I had split then out based solely on whether something needed hbase-server
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137845#comment-16137845
]
stack commented on HBASE-18640:
---
Yeah, I ask same up on rb review about hbase-mapreduce-util
Whats in
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137788#comment-16137788
]
Appy commented on HBASE-18640:
--
[~Apache9] Always up for better names :). Suggest please.
> Move mapreduce
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137746#comment-16137746
]
Duo Zhang commented on HBASE-18640:
---
So here, hbase-server will only depend on hbase-client, so we can
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136966#comment-16136966
]
Hadoop QA commented on HBASE-18640:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136545#comment-16136545
]
Appy commented on HBASE-18640:
--
v005
Rebased to master.
What do you think guys?
> Move mapreduce out of
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136498#comment-16136498
]
Hadoop QA commented on HBASE-18640:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136238#comment-16136238
]
Hadoop QA commented on HBASE-18640:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136007#comment-16136007
]
Hadoop QA commented on HBASE-18640:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16135856#comment-16135856
]
Appy commented on HBASE-18640:
--
bq. And I think it is worth to introduce a hbase-mapreduce module that does
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16135822#comment-16135822
]
stack commented on HBASE-18640:
---
I like the [~Apache9] comment (most folks only need input/output formats).
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16135402#comment-16135402
]
Appy commented on HBASE-18640:
--
003.patch
Second cut based on earlier discussions. Aim was to have two
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134998#comment-16134998
]
Hadoop QA commented on HBASE-18640:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134812#comment-16134812
]
Duo Zhang commented on HBASE-18640:
---
{{HBaseTestingUtility}} will start a mini cluster which means it
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134755#comment-16134755
]
Appy commented on HBASE-18640:
--
i have strong gut feeling of having two module: hbase-mapreduce-util
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134633#comment-16134633
]
Sean Busbey commented on HBASE-18640:
-
or! what if we break the mapreduce stuff into two modules, one
[
https://issues.apache.org/jira/browse/HBASE-18640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134631#comment-16134631
]
Sean Busbey commented on HBASE-18640:
-
HBaseTestingUtility should probably move into its own module
47 matches
Mail list logo