Re: [DISCUSS] changes in shell behavior wrt returning values

Elser <els...@apache.org> wrote: > > +1 ditto -- this one is better to revert and ask forgiveness on from > users, > > IMO. > > > > > > On 4/3/18 3:27 PM, Apekshit Sharma wrote: > >> > >> +1 on going back to old behavior, i.e. returning valu

Re: [DISCUSS] changes in shell behavior wrt returning values

+1 on going back to old behavior, i.e. returning values, in branch-1 and 2.0 release. bq. Open question: should we also revert this change in branch-1.4, even though it means the shell will behave very differently between maintenance releases? Earlier, i was inclining towards reverting the

Re: Flush requires global ADMIN permission on 2.0

https://issues.apache.org/jira/browse/HBASE-20185 On Tue, Mar 13, 2018 at 4:35 PM, Apekshit Sharma <a...@cloudera.com> wrote: > exactly what Duo said. > > Trying something > > On Tue, Mar 13, 2018 at 7:44 AM, 张铎(Duo Zhang) <palomino...@gmail.com> > w

Re: Flush requires global ADMIN permission on 2.0

exactly what Duo said. Trying something On Tue, Mar 13, 2018 at 7:44 AM, 张铎(Duo Zhang) wrote: > I think the problem is that, in MasterRpcService.execProcedure, we do not > know the type of the Procedure so it is not possible for us to require > different permissions

Re: [VOTE] Merge branch HBASE-19397 back to master and branch-2.

modification >>>>>>>> >>>>>>> on >>>>>>> >>>>>>>> zk and the actual loading of the modification on RS. And we have >>>>>>>> also >>>>>>>> >>>>>>&

Re: [VOTE] Merge branch HBASE-19397 back to master and branch-2.

lot > >> > > > > when we start to stabilize our build. > >> > > > > > >> > > > > Thanks. > >> > > > > > >> > > > > > >> > > > You see it as a big bug fix Duo? > >&g

Re: DISCUSSION: "branch RM" roles for non-released branches branch-1, branch-2, and master

one is welcome to RM those > branch-x.y. As long as someone is actively RMing branch-x.y it stays alive. > That's how we'd come to a consensus on what is long term stable. > > > On Wed, Mar 7, 2018 at 5:55 PM, Apekshit Sharma <a...@cloudera.com> wrote: > > >

Re: DISCUSSION: "branch RM" roles for non-released branches branch-1, branch-2, and master

I like the thought, continuing to brainstorm In this method, the following holds true, right? - Care taking "branch-X.Y" will require least effort and will by default fall onto the shoulders of RM for X.Y version. For eg. Andrew will caretake branch-1.4, Stack will caretake branch-2.0, and so

Re: [ANNOUNCE] Please welcome Ashish Singhi to the HBase PMC

Congrats Ashish! On Wed, Feb 28, 2018 at 11:55 AM, Umesh Agashe wrote: > Congratulations Ashish! > > On Wed, Feb 28, 2018 at 11:21 AM, Amit Virmani > wrote: > > > Congrats Ashish! > > > > > > Regards > > Amit > > > > On Wed, Feb 28, 2018 at 10:57

Re: [ANNOUNCE] Please welcome Guanghao Zhang to the HBase PMC

Congrats Guanghao! On Wed, Feb 28, 2018 at 11:54 AM, Umesh Agashe wrote: > Congratulations Guanghao! > > On Wed, Feb 28, 2018 at 11:21 AM, Amit Virmani > wrote: > > > Congrats! > > > > > > Regards > > Amit > > > > On Wed, Feb 28, 2018 at 10:56 AM,

Re: [ANNOUNCE] Please welcome Mike Drob to the HBase PMC

Congrats Mike. On Wed, Feb 28, 2018 at 11:54 AM, Umesh Agashe wrote: > Congratulations Mike! > > On Wed, Feb 28, 2018 at 10:56 AM, Zach York > wrote: > > > Nice work, Congratulations Mike! > > > > On Wed, Feb 28, 2018 at 10:52 AM, Peter

Re: Temporarily disabled the timeout setting for flakey tests jenkins job

Looks nice again. On Tue, Feb 27, 2018 at 9:49 PM, Stack wrote: > Duo: > > A bad nightly build ruined our dashboard. A bad run produced many tests for > the flakies list. The flakies list then timed out because too many tests to > run. Appy cleaned it up, mostly. It will take

Critical security related notice for releases containing HBASE-19483 (1.4.1, 1.5.0, 2.0.0)

Default value for hbase.security.authorization has been changed from true to false. Secured clusters should make sure to explicitly set it to true in XML configuration file before upgrading to one of these versions. ( https://issues.apache.org/jira/browse/HBASE-19483) True as default value of

Re: Is HBaseTestingUtility part of public API?

bq. Anything in test/ can't be public API by definition. Move it into src/ if that is desired. If that has always been our stance, we should probably clarify it in our documentation. Or maybe it's already there and i missed it. Didn't find anything searching for 'test' in

Re: Flaky dashboard is flaky

Someone, jenkins process on GCP instance (that IP) died. Removed it from flaky list for now (to unblock building fresh dashboards). I have restarted the jenkins process, and will add it back later once dash-building job goes green again. Thanks for bringing it up Balazs. -- Appy On Fri, Feb 2,

Re: Two master branches?

Done. Lemme know here if there are more issues related to this. On Mon, Jan 22, 2018 at 11:48 AM, Apekshit Sharma <a...@cloudera.com> wrote: > Both branches are same. > appy appy-MBP-3 ~/apache/hbase (master) → git log > apache/master..apache/Master > appy appy-MBP-3 ~/ap

Re: Two master branches?

"HBASE-19827 Addendum for Flakey > > > TestAssignmentManager" Premature commit. (3 days ago) > > > * 298dc0c626 - (apache/master) HBASE-19822 Override cancel(boolean) in > > > LogCleaner (Addendum) (3 days ago) > > > > > > > > > O

Temporary jenkins job to run tests for 2.0 against hadoop3

Here's the job: https://builds.apache.org/job/HBase-2.0-hadoop3-tests (Still trying to make it work). Why do we need separate temporary job? - Jenkins pipeline doesn't yet support running step B if step A fails, and our hadoop2 tests (which run before hadoop3 tests) always fail. - Parallelizing

Two master branches?

I see following three branches: remotes/apache/HEAD -> apache/master remotes/apache/Master remotes/apache/master Was "Master" always there? -- -- Appy

Re: Flaky dashboard for current branch-2

> bq. we can actually update the script to send a mail to dev@ > > > > A post to the JIRA which caused the 100% failing test would be better. > > The committer would notice the post and take corresponding action. > > > > Cheers > > > > On Fri, Jan 12, 2018

Re: Flaky dashboard for current branch-2

etrics > > Thanks, > Zach > > On Fri, Jan 12, 2018 at 8:19 AM, Stack <st...@duboce.net> wrote: > > > Dashboard doesn't capture timed out tests, right Appy? > > Thanks, > > S > > > > On Thu, Jan 11, 2018 at 6:10 PM, Apekshit Sharma <a...@clou

Flaky dashboard for current branch-2

https://builds.apache.org/job/HBase-Find-Flaky-Tests-branch2.0/lastSuccessfulBuild/artifact/dashboard.html @stack: when you branch out branch-2.0, let me know, i'll update the jobs to point to that branch so that it's helpful in release. Once release is done, i'll move them back to "branch-2".

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

37373 > > > > > > > 2018-01-10 05:28:08,228 INFO [regionserver/node8.com/192. > > > > > 168.23.2:16020 > > > > > > ] > > > > > > > util.FSHDFSUtils: Failed to recover l

Re: [VOTE] Merge branch HBASE-19397 back to master and branch-2.

> > looksee sir. > > > > > Thanks sir. All the concerns here about whether we should merge this into > > 2.0 are reasonable, I know. Although I really want this in 2.0 because I > > believe it will help a lot for stabilizing, I'm OK with merge it to 2.1 > &g

Re: [VOTE] Merge branch HBASE-19397 back to master and branch-2.

Same questions as Josh's. 1) We have RCs for beta1 now, which means only commits that can go in are bug fixes only. This change - although important, needed from long time and well done (testing, summary, etc) - seems rather very large to get into 2.0 now. Needs good justification why it has to be

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

>> > >> >> Thanks, JMS! > >> >> > >> >> On Sat, Jan 6, 2018 at 6:42 AM, Jean-Marc Spaggiari < > >> >> jean-m...@spaggiari.org > >> >> > wrote: > >> >> > >> >> > How you guys are

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

bq. Care needs to be exercised backporting. Bug fixes only please. If in doubt, ping me, the RM, please. Thanks. In that case, shouldn't we branch out branch-2.0? We can then do normal backports to branch-2 and only bug fixes to branch-2.0. On Fri, Jan 5, 2018 at 9:48 AM, Andrew Purtell

Re: Assignment Manager and clock advance.

ve seen cases where > subsequent calls to currentTimeMillis() are non-incrementing on specific > Linux distributions. Taken in aggregate, the system clock makes progress, > but those aggregations are on the multi-second scale. > > On Tue, Jan 2, 2018 at 4:37 PM Apekshit Sharma <a...

Re: Assignment Manager and clock advance.

Hi Sergey, Interesting test and find. Makes total sense too. However, in real world case, any put in meta table itself will take more than a ms, and then we have lot of Procedure framework and other logic in between meta accesses which would make this scenarios impossible. Specifically, there a

Re: Accessing region state via web UI

json api when we already have a whole well designed way to do it - REST apis. It should rather be an addition to Table endpoints (table 14 here: http://hbase.apache.org/book.html#_using_rest_endpoints). -- Appy On Sun, Dec 24, 2017 at 5:16 PM, Apekshit Sharma <a...@cloudera.com> wrote:

Re: Accessing region state via web UI

More details: Proposed interface is json. Pros: - more info exposed to operators, can be used for scripting Cons: - We don't have functions in Admin to expose region states - We don't expose much programatic info through our web ui. -- Appy On Fri, Dec 22, 2017 at 6:01 PM, Ted Yu

Re: Moving To SLF4J and Log4J2

, but we need clear picture now. 4) Followup jira for hbase-backup/http or a reason why they can't be done. Reverting this patch would be hell, wouldn't want to do it because we missed basic checks. -- Appy On Mon, Dec 18, 2017 at 3:53 PM, Apekshit Sharma <a...@cloudera.com> wrote: > Oh

Re: Moving To SLF4J and Log4J2

Oh, just 60 pages of review :D -- Appy On Mon, Dec 18, 2017 at 3:48 PM, Stack <st...@duboce.net> wrote: > On Wed, Dec 13, 2017 at 10:09 AM, Stack <st...@duboce.net> wrote: > > > On Mon, Dec 11, 2017 at 12:49 PM, Apekshit Sharma <a...@cloudera.com> > >

Can we always add new regions as CLOSED?

Hi folks, Was debugging TestTruncateTableProcedure when starting thinking about this. (That's one mean test! What nice fault tolerant tests!) So the specific case: If we fail after adding new regions to meta ( TRUNCATE_TABLE_ADD_TO_META

Re: Suggestion to speed up precommit - Reduce versions in Hadoop check

https://issues.apache.org/jira/browse/HBASE-19489 On Mon, Dec 11, 2017 at 4:30 PM, Josh Elser <els...@apache.org> wrote: > +1 > > > On 12/11/17 7:11 PM, Apekshit Sharma wrote: > >> Oh, btw, here's the little piece of code if anyone want's to analyze more. >> &g

Suggestion to speed up precommit - Reduce versions in Hadoop check

Hi +1 hadoopcheck 52m 1s Patch does not cause any errors with Hadoop 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 2.7.4 or 3.0.0-alpha4. Almost 1 hr to check against 10 versions. And it's only going to increase as more 2.6.x, 2.7.x and 3.0.x releases come out. Suggestion here is simple,

Re: Suggestion to speed up precommit - Reduce versions in Hadoop check

"| -1 |hadoopcheck" `ls 1*` | awk '{x[$1] = 1} END{for (i in x) print i;}' | wc -l Number of passed runs: grep "| +1 |hadoopcheck" `ls 1*` | awk '{x[$1] = 1} END{for (i in x) print i;}' | wc -l -- Appy On Mon, Dec 11, 2017 at 4:07 PM, Apekshit Sharma <a...@clo

Re: Moving To SLF4J and Log4J2

Seems like good idea: - remove long dead dependency - a bit cleaner code - hadoop also moved to slf4j Quickly looking at codebase to get idea of amount of work required, here are some numbers: - LOG.debug : ~1800 - LOG.trace : ~500 - LOG.info: ~3000 Looking at this patch (

Re: Moving To SLF4J and Log4J2

+1 for dropping dependency which has been EOL for long now. What does the work here looks like? Change dependency, update properties file, changed log messages, what else? Given upcoming beta1 release, what's the minimum work required to change just the dependency? Is it possible to make code

Re: [DISCUSS] Any committers willing to do maintenance releases over the holidays?

compatibility > report. > >> > >> Who will carry this banner? Apekshit, Jan: shall we draw straws? One of > >> you > >> have a bit of extra free time over the next 4 weeks? > >> > >> Thanks, > >> Nick > >> > >> On Wed, N

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

was planned and was decided not to be done. It's new. And new things can be important! On Wed, Nov 1, 2017 at 4:34 PM, Apekshit Sharma <a...@cloudera.com> wrote: > Came here just to track anything related to Distributed Log Replay which I > am trying to purge. But looks like it's anothe

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

Came here just to track anything related to Distributed Log Replay which I am trying to purge. But looks like it's another discussion thread about hbase-backup. Am coming here with limited knowledge about the feature (did a review initially once, lost track after). But then, looks like discussion

Re: [DISCUSS] Any committers willing to do maintenance releases over the holidays?

Loads of helping hands...woohoo! -Appy On Oct 31, 2017 4:01 PM, "Nick Dimiduk" wrote: > As 1.1 is rounding down, I will be able to apply that time to helping out > on another release line, if that's useful to the community. > > Thanks, > Nick > > On Mon, Oct 30, 2017 at

Re: [DISCUSS] Any committers willing to do maintenance releases over the holidays?

I can do it. -- Appy On Mon, Oct 30, 2017 at 9:35 PM, Sean Busbey wrote: > Hi folks! > > I'm in the process of getting us a 1.2.7-RC, hopefully soon[1]. This > release is badly behind schedule. I'd very much like to get us back on > a regular cadence for our stable release

Re: [DISCUSS] Merge hbase-metrics:oahh.metrics.impl into hbase-metrics-api

; Additionally, $business1 may have a hard requirement to not deploy > > metrics-library2 (and vice versa). One final concern, bundling our > > "default" DropwizardMetrics 3-based implementation could cause headaches > > for users who want to build their own metrics-api

Re: Is our maven build order correct? Do we have required jars in binary/source tar.gz?

Any reason why we don't build both together? On Wed, Oct 25, 2017 at 3:17 PM, Apekshit Sharma <a...@cloudera.com> wrote: > Thanks for the quick reply Busbey. Let me work on fixing the includes list > (HBASE-19089 <https://issues.apache.org/jira/browse/HBASE-19089>). Will > c

Re: Is our maven build order correct? Do we have required jars in binary/source tar.gz?

arball does a manual > invocation of the maven assembly plug-in and points at the source > descriptor directly. > > On Oct 25, 2017 4:57 PM, "Apekshit Sharma" <a...@cloudera.com> wrote: > > Hi folks, > > Found some discrepancies in moduleSet list in src.xml and

Is our maven build order correct? Do we have required jars in binary/source tar.gz?

Hi folks, Found some discrepancies in moduleSet list in src.xml and hadoop-two-compat.xml. Got a crash course on hbase-assembly today by stack. Throwing some larger questions here; 1. Do we want h-archetypes in binary tar? 2. Shouldn't we be building h-shaded, h-examples and h-archetypes before

Re: [DISCUSS] Merge hbase-metrics:oahh.metrics.impl into hbase-metrics-api

gt; functionality with less headache, but I, admittedly, don't have a concrete > use-case behind it. > > - Josh > > [1] https://github.com/apache/calcite-avatica > > On 10/24/17 6:09 PM, Apekshit Sharma wrote: > >> Hi >> >> Am confused why do we have this weird circular

Re: [DISCUSS] Merge hbase-metrics:oahh.metrics.impl into hbase-metrics-api

came from needing to extend inner > hadoop classes on multiple different versions. This was back when HBase had > to support hadoop < 1, hadoop 1.x, and hadoop 2.x. When we dropped older > hadoop versions then things got easier. > > On Tue, Oct 24, 2017 at 3:09 PM, Apekshit Sharma

Re: [DISCUSS] Fate of CoordinatedStateManager and hbase.coordinated.state.manager.class config

2017 at 1:15 PM, Andrew Purtell <apurt...@apache.org> > wrote: > > > Sounds good to me. > > > > > > On Mon, Oct 23, 2017 at 1:00 PM, Apekshit Sharma <a...@cloudera.com> > > wrote: > > > > > Thanks Andrew! > > > > >

Re: [DISCUSS] Fate of CoordinatedStateManager and hbase.coordinated.state.manager.class config

o need necessarily to abandon > the idea of abstraction between our coordination needs and the > implementation. > > > On Mon, Oct 23, 2017 at 12:16 PM, Apekshit Sharma <a...@cloudera.com> > wrote: > > > Hi everyone, > > > > Am coming from limited kno

[DISCUSS] Fate of CoordinatedStateManager and hbase.coordinated.state.manager.class config

Hi everyone, Am coming from limited knowledge here, so pardon me if it seems outrageous. I guess this effort (HBASE-10909 ) was to separate out state into an interface which was then made pluggable via the config

Re: [DISCUSS] Punt the Coprocessor TableWrapper and CoprocessorHConnection?

+1 I remember Andrew saying same thing about CoprocessorEnvironment#getTable functions during the review of HBASE-17732, that we should get rid of them and let CP do their own table resource management like all other things. On Wed, Oct 18, 2017 at 2:45 PM, Stack wrote: >

Re: Please congratulate our new PMC Chair Misty Stanley-Jones

Congrats Misty! Wohooo! -- Appy On Thu, Sep 21, 2017 at 2:17 PM, Mike Drob wrote: > Rock on, Misty! > > On Thu, Sep 21, 2017 at 2:35 PM, Sean Busbey wrote: > > > congrats Misty! > > > > On Thu, Sep 21, 2017 at 2:08 PM, Andrew Purtell

Re: [DISCUSS] Coprocessor major design changes HBASE-17732

Just realized that earlier linked doc might not be accessible publicly. Here's the new link : https://docs.google.com/document/d/1mPkM1CRRvBMZL4dBQzrus8obyvNnHhR5it2yyhiFXTg/edit?usp=sharing -- Appy On Wed, Sep 6, 2017 at 5:07 PM, Apekshit Sharma <a...@cloudera.com> wrote: > Hi > &g

[DISCUSS] Coprocessor major design changes HBASE-17732

Hi Links: HBASE-17732 , Code Review With 2.0 beta 1 approaching, this seems to be the ripe time to make much needed coprocessor design changes. Here's a summary of what's changing (from jira description):

Re: [DISCUSS] Merging Hybrid Logical Clocks with Master

demonstrate that perf is > not affected by HLC. > > Enis > > On Fri, Aug 25, 2017 at 2:00 PM, Apekshit Sharma <a...@cloudera.com> > wrote: > > > It's true that hlc clock is very slower than system, but is it really a > > bottleneck? I mean 7mil ops/sec with 16 threa

Re: [DISCUSS] Merging Hybrid Logical Clocks with Master

It's true that hlc clock is very slower than system, but is it really a bottleneck? I mean 7mil ops/sec with 16 threads doesn't sound bottleneck because: - It's like 70 times of any RS' throughput (assuming 100k write throughput) - It's certainly enough for meta operations. What say? But i

Re: [DISCUSS] hbase-2.0.0 compatibility expectations

Ref: deleting/deprecating some methods in HBaseAdmin https://github.com/apache/hbase/commit/de696cf6b653749c6bf105ef3d62d7a6c6923c57 >From first message: *" An hbase1 client can run against an hbase2 cluster but it will only be able to do DML (Get/Put/Scan, etc.). We do not allow being able to do

Re: Slack access

Samir Ahmic <ahmic.sa...@gmail.com> > wrote: > > > Hi Dima, > > > > Mind sending me invite to channel to? > > Thanks chief. > > > > Best Regards > > Samir > > > > On Mon, Jul 24, 2017 at 8:28 AM, Apekshit Sharma <a...@cloudera.com> >

Re: Ycsb and Hbase - read+write simulation.

not clear on what's the ask here. Going by just two sentences, am confused how it can be 97% in last 2 hours but only 90% in 24 hours? Shouldn't second number be larger? -- Appy On Wed, Aug 9, 2017 at 1:01 AM, Meirav Malka wrote: > -- Forwarded message --

Re: Slack access

There are 2 other ways: - whitelist domain names. For eg. @apache.com. - Signup link which anyone can use to join the group. Sadly, that remains alive only for a day or two. On Sun, Jul 23, 2017 at 9:47 AM, Sachin Jain wrote: > As long as you are fine with sending

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

Fixed 'trends' in flaky dashboard. Since i changed the test names in last fix, the dots in the name were messing up with CSS selectors. :) On Mon, Jul 10, 2017 at 11:34 AM, Apekshit Sharma <a...@cloudera.com> wrote: > Quick update on flaky dashboard: > Flaky dashboard wasn't wor

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

Quick update on flaky dashboard: Flaky dashboard wasn't working earlier because our trunk build was broken. After trunk was fixed, the format of log lines in consoleText was not the same, so findHangingTests.py was not able to parse it correctly for broken/hanging/timeout tests. That's been fixed

Re: Flaky Test Dashboard Empty

Looks like the latest build which you kicked off passed. It was on H22 too, so maybe no need to exclude? On Fri, Jul 7, 2017 at 3:49 PM, Mike Drob wrote: > Hi Folks, > > I was looking at the flaky test dashboard and noticed that the aggregation > job failed[1] > > It's been

Re: flaky test report

Retention policy for that job is max 7 day, max 20 builds. https://builds.apache.org/job/HBASE-Flaky-Tests/configure Tuned it up to 100 builds. On Fri, May 5, 2017 at 3:13 PM, Ted Yu wrote: > Hi, > I was looking at > https://builds.apache.org/job/HBASE-Find-Flaky-Tests/ >

Re: org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot broken in branch-1?

So the issue here is, somehow Test*ExportSnapshot (4 tests classes) tests are stepping on each other. When we run locally, tests are run sequentially, hence they always pass. But in precommit/flaky-tests-job, there are multiple forks and multiple tests can run in parallel. That's when they fail.

Re: ANNOUNCE: Good news!!!! Two new PMC and a new Committer!

Congrats Josh, Jing and Eshcar! On Sun, Mar 19, 2017 at 6:08 PM, 宾莉金 or binlijin wrote: > Congratulations and welcome! > > 2017-03-18 8:42 GMT+08:00 Yi Liang : > > > Congratulations, Jerry and Josh Elser > > > > Best, > > Yi > > > > On Fri, Mar 17,

Re: Reminder: Please use git am when committing patches

ionally, as a PMC member it is much easier to try > to build an idea of contributions to the repo over time if I can scan > through git author and sign-off tags than if I have to try to pick out > bespoke commit message details. > > > > On Thu, Jan 26, 2017 at 8:45 PM, Apekshit Shar

Re: Reminder: Please use git am when committing patches

. One more thing is that, do > not > > > forget to add --signoff :) > > > > > > Mind opening a issue to modify the above section in hbase book, Appy? > > > > > > Thanks. > > > > > > 2017-01-27 4:12 GMT+08:00 Che

Re: Git Pull Request to HBase

Thu, Jan 26, 2017 at 11:47 AM, Apekshit Sharma <a...@cloudera.com> > wrote: > > > Hi Chetan, Ted > > > > It's the right question to ask. One who does the work should get the > > credits, and that means commit authorship too. > > That's where the script subm

Reminder: Please use git am when committing patches

Hi devs, A recent question by new contributor (thread: Git Pull Request to HBase) and looking at history of commits, i think it is worth re-iterating that committer should use *git am* while committing patches so that whoever did the actual work gets appropriate credit in git history. In case the

Re: Git Pull Request to HBase

Hi Chetan, Ted It's the right question to ask. One who does the work should get the credits, and that means commit authorship too. That's where the script submit_patch.py which i wrote a while back helps too. If contributors use the script to submit formatted patch (instead of just git diff and

Re: Merge and HMerge

>>>> > > >>>> We should not have any tool which will work in offline mode by going > > >> over > > >>>> the HDFS data. Seems very brittle to be broken when things get > > changed. > > >>>> Only use ca

Re: [ANNOUNCE] New HBase committer Phil Yang

Congratulations Phil! On Tue, Nov 29, 2016 at 10:36 AM, Jerry He wrote: > Congratulations and welcome, Phil. > > On Tue, Nov 29, 2016 at 9:35 AM, Huaxiang Sun wrote: > > > Congratulations, Phil! > > > > > On Nov 29, 2016, at 5:29 AM, Yu Li

Re: [ANNOUNCE] New HBase committer Lijin Bin

Congratulations Lijin. On Tue, Nov 29, 2016 at 10:35 AM, Jerry He wrote: > *Congratulations, *宾莉金! > > On Tue, Nov 29, 2016 at 9:34 AM, Huaxiang Sun wrote: > > > > > Congratulations, Lijin! > > > > > On Nov 29, 2016, at 5:15 AM, 宾莉金 or binlijin

Re: Merge and HMerge

bq. HMerge can merge multiple regions by going over the list of regions and checking their sizes. bq. But both of these tools (Merge and HMerge) are very dangerous I came across HMerge and it looks like dead code. Isn't referenced from anywhere except one test. (This is what lars also pointed out

Re: Update apache cli version from 1.2 to 1.3.1?

It's for 2.0. The work am planning to do, using apache cli in our tools, will be in master only to avoid compatibility issues. On Mon, Oct 31, 2016 at 8:37 PM, Sean Busbey <bus...@apache.org> wrote: > update for which version(s) of HBase? > > On Mon, Oct 31, 2016 at 6:31 PM,

Re: Hangout on Slack?

ther thread, do > you > > > have to have an apache.org id to join up? > > > > > > The Slack channel should be published on the website? Is it there (I > > don't > > > see it on a quick search on site and in refguide but I could be blind). > > >

Re: Hangout on Slack?

hread, do > you > > > have to have an apache.org id to join up? > > > > > > The Slack channel should be published on the website? Is it there (I > > don't > > > see it on a quick search on site and in refguide but I could be blind). > > > >

Update apache cli version from 1.2 to 1.3.1?

1.3 came out in 2015, 6 years after 1.2. It was few bug fixes and new features. These are few good/important ones: - HelpFormatter now prints command-line options in the same order as they have been added. Fixes CLI-212. - Standard help text now shows mandatory arguments also for the first

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

the other jobs. I don't see > > a downside. Anyone else have concerns? > > > > > > On Fri, Sep 16, 2016 at 6:15 PM, Apekshit Sharma <a...@cloudera.com> > > wrote: > > > So this all started with spaces-in-path issue, right? I think it has > > &g

Re: [DISCUSSION] Merge Backup / Restore - Branch HBASE-7912

t;>> >>> > apache/hadoop/hbase/io/encoding/rowindexV1/RowIndexCodecV1.j > > >>>> ava:[45,8] > > >>>> >>> > org.apache.hadoop.hbase.io.encoding.rowindexV1. > RowIndexCodecV1 > > is > > >>>> not > > >>&g

Re: [DISCUSSION] Merge Backup / Restore - Branch HBASE-7912

@stack, it compiled for me. Also tried few commands, and have to say, it's well designed from user commands perspective. On Tue, Oct 11, 2016 at 5:08 PM, Stack wrote: > On Tue, Oct 11, 2016 at 1:50 PM, Vladimir Rodionov > > wrote: > > > Michael, > >

Should we remove Mob Sweeper MR job

>From what i understand, it was part of initial implementation of MOB but was later replaced by DefaultMobStoreCompactor and ExpiredMobFileCleaner. Let's remove this 1500+ lines tool if it's redundant, because it's unnecessary maintainence. I stumbled across it when i was trying to replace zk

Use hemcrest in hbase

Hey guys, Hemcrest seems like a wonderful library of matchers for unit testing. Am sure our tests can use that improvement. Any good reason it's not widely used in hbase? I'll start using it more often unless there's a good reason not to. It's BSD licence, that's compatible with Apache? -- Appy

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

w, right? Also, it looks like the hbase-spark > > integration-test phase is what's tripping up the build. Why not just > > temporarily disable that to unblock testing? > > > > On Friday, September 16, 2016, Apekshit Sharma <a...@cloudera.com> > wrote: > > > >

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

jdk8 or > needs to be updated to a jdk8 compatible version. > > > -- > *With Regards:-* > *Aman Poonia* > > On Fri, Sep 16, 2016 at 2:40 AM, Apekshit Sharma <a...@cloudera.com> > wrote: > > > Andeverything is back to red. > > Because something is plagu

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

Emm, can it be because scalatest tries to use a different java then that specified by JAVA_HOME (which is used to compile) On Thu, Sep 15, 2016 at 2:10 PM, Apekshit Sharma <a...@cloudera.com> wrote: > Andeverything is back to red. > Because something is plaguing our

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

eased or otherwise > supposedly stable branches. > > -Mikhail > > On Mon, Sep 12, 2016 at 4:53 PM, Sean Busbey <bus...@cloudera.com> wrote: > > > awesome work Appy! > > > > That's certainly good news to hear. > > > > On Mon, Sep 12, 2016 at 2:14 PM,

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

://builds.apache.org/view/H-L/view/HBase/job/HBASE-Flaky-Tests/) which was disabled for almost a month due to trunk being on fire. I will keep an eye on how things are going. On Mon, Sep 12, 2016 at 2:02 PM, Apekshit Sharma <a...@cloudera.com> wrote: > @Sean, Mikhail: I found the alternate soluti

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

@Sean, Mikhail: I found the alternate solution. Using user defined axis, tool environment and env variable injection. See latest diff to https://builds.apache.org/job/HBase-Trunk_matrix/ job for reference. On Tue, Aug 30, 2016 at 7:39 PM, Mikhail Antonov wrote: > FYI, I

Re: [ANNOUNCE] Misty Stanley-Jones joins the Apache HBase PMC

Congrats Misty! On Wed, Sep 7, 2016 at 11:56 AM, Andrew Purtell wrote: > Congratulations, Misty! > > On Wed, Sep 7, 2016 at 11:40 AM, Sean Busbey wrote: > > > On behalf of the Apache HBase PMC I am pleased to announce that Misty has > > accepted our

Re: Flaky tests

t; Ram > > On Fri, Jun 24, 2016 at 9:09 AM, Apekshit Sharma <a...@cloudera.com> > wrote: > > > Oh, this missed my view. > > Yeah, these flaky tests are big pain. At the very least, we should file > the > > jiras for them. I don't think everyone tracks the builds or

Re: Flaky tests

Oh, this missed my view. Yeah, these flaky tests are big pain. At the very least, we should file the jiras for them. I don't think everyone tracks the builds or the dashboard (yet), but many do track the jiras. Instead of RMs cracking down on them on every minor/major release, maybe everyone in

Re: Hangout on Slack?

Anyone can join anytime with @apache.org email id using following link. https://apache-hbase.slack.com/x-37639653748-52658243986/signup Sorry, but slack doesn't allow doing same for @gmail.com email ids. On Mon, Jun 20, 2016 at 11:36 AM, Apekshit Sharma <a...@cloudera.com> wrote: > H

Re: Hangout on Slack?

py, could you make another link? if there's a "no-expiration" option > that would be best. > > On Fri, Jun 17, 2016 at 7:23 PM, Apekshit Sharma <a...@cloudera.com> > wrote: > > Or you can join the team using this link: > &g

Re: Task #57953b5d

Hi Rohit Welcome to HBase community. We can certainly help you get started/learn more about HBase depending on your current familiarity. HBase book [1] is going to be immensely helpful resource. I suggest you start with 'Data Model' and 'Building and

Re: Hangout on Slack?

Or you can join the team using this link: https://apache-hbase.slack.com/shared_invite/NTIxMTE4NTQwMzYtMTQ2NjIwOTMwMi1kMzc2YzkwYTJm It expires on Sunday. On Fri, Jun 17, 2016 at 4:43 PM, Apekshit Sharma <a...@cloudera.com> wrote: > Created slack team apache-hbase.slack.com. > It has

  1   2   >