Re: [DISCUSS] hbase-spark module in branch-1 and branch-2

Hi, Andrew Stack was talking to me about this area when I met him in the HBase Meetup last December. Let me take a shot at HBASE-14375. Thanks, Jerry On Sat, Jan 14, 2017 at 9:22 PM, Andrew Purtell wrote: > > > > On Jan 14, 2017, at 9:07 PM, Jerry He

Re: Merge and HMerge

I think that makes sense. The tool with its custom code dates back to where we had no built in version. I am all for removing all of the tools and leave the API call only. That is the same for an admin then compared to calling flush or split. No? Lars Sent from my iPhone On 15 Jan 2017, at

Re: [DISCUSS] hbase-spark module in branch-1 and branch-2

> On Jan 14, 2017, at 9:07 PM, Jerry He wrote: > > I think it will be a big disappointment for the community if the > hbase-spark module is not going into 2.0. > I understand there are still a few blockers, including HBASE-16179. Patches welcome. :-) > We have it in our

Re: [DISCUSS] hbase-spark module in branch-1 and branch-2

I think it will be a big disappointment for the community if the hbase-spark module is not going into 2.0. I understand there are still a few blockers, including HBASE-16179. We have it in our distribution, probably in other vendors' as well. It is little easier for us because we can be flexible

Re: Merge and HMerge

>If you remove the util.Merge tool, how then does an operator ask for a merge in its absence? We have a shell command to merge region. In the past, it calls the same RS side code. I don't think there is a need to have util.Merge (even if we really want, we can ask this utility to call

[jira] [Created] (HBASE-17470) Remove merge region code from region server

Stephen Yuan Jiang created HBASE-17470: -- Summary: Remove merge region code from region server Key: HBASE-17470 URL: https://issues.apache.org/jira/browse/HBASE-17470 Project: HBase

Re: [DISCUSS] hbase-spark module in branch-1 and branch-2

I agree with Devaraj's assessment w.r.t. hbase-spark module in master (which is becoming branch-2). Cheers On Mon, Nov 21, 2016 at 11:46 AM, Devaraj Das wrote: > Hi Sean, I did a quick check with someone from the Spark team here and his > opinion was that the

Re: Moving 2.0 forward

Hey Eric! See this thread where it is suggested we remove the module for want of a sponsor [1]. The hbase-spark story is also muddled by there being different options available neither of which is complete instead of just 'the one' (Do a google search). St.Ack 1.

Re: Moving 2.0 forward

On Sat, Jan 14, 2017 at 11:10 AM, Andrew Purtell wrote: > Thanks for putting that document together Stack, that was really helpful. > > > 1.1 New Assignment Manager, AMv2 > > ​Can we get a virtual show of hands who is working on this and plans to > finish it? It was Stephen

Re: Moving 2.0 forward

After HBASE-16179 gets in, we can get wider feedback from interested users in using hbase-spark module. We would then be able to find missing pieces. > On Jan 14, 2017, at 12:30 PM, Eric Charles wrote: > > I read "3.3 hbase-spark STATUS: Needs work. No one on it at mo. Doc.

Re: Moving 2.0 forward

I read "3.3 hbase-spark STATUS: Needs work. No one on it at mo. Doc. is just wrong. What is there is dodgy. Could get punted." Unit tests are working and base functionality is there. Besides the doc and compilation against spark-2 (and scala-2.11), what else do you want to see? On 14/01/17

Re: Proposal: Create "branch RM" roles for non releasing branches branch-1, branch-2 (when it exists), and master

Thanks everyone for the discussion. I'll informally watch branch-1. Planning on monthly passes for cherry picks and release testing as I did for 0.98, but in this case the output will be nonrelease snapshots. Release RMs will not see pick backs from me. The changes you can expect is reverts if

Re: [VOTE] The 1st HBase 1.3.0 release candidate (RC0) is available

+1 - Downloaded the src tarball. - Checked the md5 and signature. All good. - Built from source. OpenJDk 1.8.0_101-b13 - Unit test suite. Passed. - mvn apache-rat:check Passed - Download the bin tarball. - Checked the md5 and signature. All good. - Untar it. Layout and files

Re: Moving 2.0 forward

Thanks for putting that document together Stack, that was really helpful. > 1.1 New Assignment Manager, AMv2 ​Can we get a virtual show of hands who is working on this and plans to finish it? It was Stephen and Matteo originally, right? Matteo seems temporarily sidelined, is that correct? > 1.3

Successful: HBase Generate Website

Build status: Successful If successful, the website and docs have been generated. To update the live site, follow the instructions below. If failed, skip to the bottom of this email. Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If

Re: Moving 2.0 forward

For 3.3, hbase-spark module, there is HBASE-16179 which enables support for Spark 2.0 It needs some review. Cheers > On Jan 13, 2017, at 11:25 PM, Stack wrote: > > On Sat, Dec 31, 2016 at 12:16 PM, Stephen Jiang > wrote: > >> Hello, Andrew, I

Re: [VOTE] The 1st HBase 1.3.0 release candidate (RC0) is available

+1 Checked sigs. Downloaded everything looks good. License and Notice files look good. On Mon, Jan 9, 2017 at 7:11 PM, Andrew Purtell wrote: > +1 > > Checked sums and signatures: ok > Spot check LICENSE and NOTICE files: ok > Built from source (7u80): ok > RAT audit (7u80):