Re: Aiming for 2.5.0RC1 this Friday

ovements we > can make there will be helpful to new RMs. > > Great to see the progress here. > (Hello from Nassau!) > > > On Aug 22, 2022, at 6:07 AM, Nick Dimiduk wrote: > > > > On Mon, Aug 22, 2022 at 3:57 AM 张铎(Duo Zhang) > wrote: > > >

[VOTE] Release candidate for HBase 2.5.0 (RC1) is available

Please vote on this Apache hbase release candidate, hbase-2.5.0RC1 The VOTE will remain open for at least 72 hours. [ ] +1 Release this package as Apache hbase 2.5.0 [ ] -1 Do not release this package because ... The tag to be voted on is 2.5.0RC1: https://github.com/apache/hbase/tree/2.5.0RC

Re: [VOTE] HBase 2.4.14 release candidate (RC1) is available

+1 * Compatibility Report: ok * Jenkins CI history: ok * Signature: ok * Checksum : ok * Rat check (1.8.0_292): ok - mvn clean apache-rat:check -D skipTests * Rat check (11.0.11): ok - mvn clean apache-rat:check -D skipTests -D hado

Re: [VOTE] Release candidate for HBase 2.5.0 (RC1) is available

t; > Issues: > The region visualizer is interesting, it could show the total region > size, but the region server info just shows as 'undefined'. > When quiting the hbase shell, the command will hang several tens of > seconds before shutting down. Not a blocker as it could fina

Re: How to store keystore/truststore password securely?

Is the Hadoop Credentials API protected by their compatibility guidelines? If not, can we convince them to support it formally? On Thu, Aug 25, 2022 at 17:15 Andrew Purtell wrote: > We can import the code from our sister Apache project if long term > dependency and compatibility are concerns. Th

Re: [DISCUSS] HBase 2.5 / Hadoop 3 artifacts

oenix side is required but that’s it. > >>>> > >>>> The additional build time complexity for generating two releases can > be > >>> incorporated into create-release. Nobody does manual releases any more > as > >>> far as I know. Likewis

[DISCUSS] Should we exclude shaded artifacts from the API compatibility report?

Heya, Browsing through the report on 2.5.0RC1, I find I'm scrolling past the changes reported in the shaded artifacts because they are a repeat of what's observed in the core jars. Because they are generated from the core libraries, should we exclude these shaded artifacts from the report? Asked a

Re: [DISCUSS] Should we exclude shaded artifacts from the API compatibility report?

Or perhaps we shouldn't skip over these shaded results. I don't actually see these issues reported twice. Please disregard. On Mon, Aug 29, 2022 at 2:19 PM Nick Dimiduk wrote: > Heya, > > Browsing through the report on 2.5.0RC1, I find I'm scrolling past the > cha

Re: [VOTE] Release candidate for HBase 2.5.0 (RC1) is available

t; and not something like "Critical". Perhaps we can have some further discussion on that ticket. Thanks, Nick On Wed, Aug 24, 2022 at 11:52 AM Nick Dimiduk wrote: > Please vote on this Apache hbase release candidate, > hbase-2.5.0RC1 > > The VOTE will remain open for at lea

Re: [DISCUSS] HBase 2.5 / Hadoop 3 artifacts

as Hadoop 2 > hasn't gone EOL. > > On Mon, Aug 29, 2022 at 5:30 AM Nick Dimiduk wrote: > > > Should we also make hadoop3 the default active profile for branch-2 going > > forward? > > > > On Fri, Aug 26, 2022 at 5:25 PM Andrew Purtell > > > wrot

[RESULT][VOTE] Release candidate for HBase 2.5.0 (RC1) is available

With 8 binding votes in the affirmative, 1 non-binding vote in the affirmative, and no dissenting votes cast, this motion passes. Congratulations team, we have Apache HBase 2.5.0 ! Thank you for all your hard work. Thanks, Nick On Wed, Aug 24, 2022 at 11:52 AM Nick Dimiduk wrote: > Ple

[ANNOUNCE] Apache HBase 2.5.0 is now available for download

The HBase team is happy to announce the immediate availability of HBase 2.5.0. Apache HBase™ is an open-source, distributed, versioned, non-relational database. Apache HBase gives you low latency random access to billions of rows with millions of columns atop non-specialized hardware. To learn mor

Re: About time for 2.5.1

I am also concerned about the feature that squashes out the profiles from our poms. To me, specifying the maven profile at build time is a part of the API contract that we should not break in a patch release. I’d like to see that feature integrated into the do-release tooling such that two sets of

Re: About time for 2.5.1

SE-27340 in branch-2.5... So in the 2.5.1 > release we will flatten the pom file, if we do not revert this > commit... > > Nick Dimiduk 于2022年9月27日周二 16:46写道： > > > > I am also concerned about the feature that squashes out the profiles from > > our poms. To me, specifying

Re: [VOTE] First release candidate for hbase-thirdparty 4.1.2 is available for download

+1 (binding) * Signature: ok * Checksum : ok * Rat check (1.8.0_292): ok - mvn clean apache-rat:check * Built from source (1.8.0_292): ok - mvn clean install -DskipTests * Unit tests pass (1.8.0_292): ok - mvn clean package -Dsu

Re: [VOTE] The first release candidate for HBase 2.4.15 (RC0) is available

+1 (binding) * Signature: ok * Checksum : ok * Rat check (1.8.0_292): ok - mvn clean apache-rat:check -D skipTests * Rat check (11.0.11): ok - mvn clean apache-rat:check -D skipTests -D hadoop.profile=3.0 * Built from source (1.8.0_292): ok

Re: [VOTE] The second release candidate for HBase 2.5.1 (RC1) is available

> Checked logs and web page, the region visualizer showed two pictures, which > was a bit strange but not a blocker I believe(or maybe it is by design?) Yes, this is by design. The lower bar is selectable -- the user can reduce the range of hosts displayed by click-and-drag horizontally on that b

Re: [VOTE] The second release candidate for HBase 2.5.1 (RC1) is available

+1 (binding) * Signature: ok * Checksum : ok * Rat check (1.8.0_292): ok - mvn clean apache-rat:check -D skipTests * Built from source (1.8.0_292): ok - mvn clean install -D skipTests -DskipTests * Built from source (11.0.11): ok -

Re: [VOTE] First release candidate for hbase-thirdparty 4.1.3 is available for download

+1 * Signature: ok * Checksum : ok * Rat check (1.8.0_292): ok - mvn clean apache-rat:check * Built from source (1.8.0_292): ok - mvn clean install -DskipTests * Unit tests pass (1.8.0_292): ok - mvn clean package -Dsurefire.rer

Re: [DISCUSS] How to deal with the disabling of public sign ups for jira.a.o(enable github issues?)

This new situation around JIRA seems very similar to the existing situation around Slack. A new community member currently must acquire a Slack invite somehow, usually by emailing one of the lists. Mailing lists themselves involve a signup process, though it may be possible to email user/-zh/dev wi

Fwd: Infra 2022 Survey

ASF Infra is soliciting feedback. Committers, make your voices heard. Thanks, Nick -- Forwarded message - From: Chris Thistlethwaite Date: Thu, Dec 1, 2022 at 22:49 Subject: Infra 2022 Survey To: We're going to start using regular surveys to get to understand the heart of the

Re: [DISCUSS] Time to release 2.5.3 and 2.4.16?

On Mon, Jan 16, 2023 at 15:02 张铎(Duo Zhang) wrote: > If the release managers do not have enough time, do we have any volunteers? I’m happy to help out as needed. Thanks, Nick >

Re: Jira assignments

Hi Jarryd, I've added you as a Contributor to the HBase Jira. You may need to log out and log back in again, but you should now be able to assign yourself tickets. Thanks, Nick On Fri, Jan 20, 2023 at 7:15 PM Jarryd Lee wrote: > > My username is jlee > > On Fri, Jan 20, 2023 at 10:12 AM Jarryd

Re: [VOTE] Second release candidate for hbase-operator-tools 1.2.0 is available for download

I observe the same omission. Any objections if I promote the existing RC tag? Thanks, Nick On 2022/01/06 19:47:30 Zach York wrote: > Hey Guangxu, > > I noticed recently that there is no rel/1.2.0 tag on github for > hbase-operator tools. Was that step missed while releasing? > > Thanks, > Zach

Re: [Discuss] Mapreduce based major compactions to minimise compactions overhead in HBase cluster

Hi Rajeshbabu, I think that compaction management and execution are important areas for experimentation and growth of HBase. I’m more interested in the harness and APIs that make an implementation possible than in any specific implementation. I’d also like to see consideration for a cluster-wide c

Re: Working on HBase CVEs

Hi Wes, Thanks a lot for your interest. I think that you'll find this community is interested in squashing CVEs. As you can see in the description on HBASE-27436, doing so in a way that meets our strict compatibility guidelines can be technically challenging. Flagging the attention of specific iss

[DISCUSS] Kubernetes Orchestration for ZK, HDFS, and HBase

Heya team, Over here at $dayjob, we have an increasing reliance on Kubernetes for both development and production workloads. Our tools are maturing and we're hoping that they might be of interest to the wider community. I'd like to see if there's community interest in receiving some/any of them as

[DISCUSS] Flatten plugin and project metadata

Heya, At the bottom of [0], we're having a small discussion about the impact of the flatten-maven-plugin on the poms we publish. For background, since we've started using Maven's "CI Friendly Versions" feature, we have also started using the flatten plugin on install/deploy [1]. I notice that usin

Re: [DISCUSS] How to align hbase-default.xml and hbase-default.adoc

I agree that this is an important detail to keep consistent. It's further complicated because things change between release versions, and the book usually only speaks to the current master version. I don't know how the tools work, but I believe that we generate portions of the book from the site-d

Re: [DISCUSS] Kubernetes Orchestration for ZK, HDFS, and HBase

s exploring what are the possibilities such as kustomize or helm or > > operator. I found it can get pretty complex in terms of writing > extensible > > deployment manifest (for different kinds of deployments) with tools like > > kustomize or helm. Here is our attempt to contera

Re: [DISCUSS] Kubernetes Orchestration for ZK, HDFS, and HBase

t; > Network topology (hostname/IP problem) or performance issue? > > > > That's a bit detail and we can take above question offline if we have a > > JIRA or other share documentation as well. > > > > Thanks, > > Stephen > > > > > >

Re: Working on HBase CVEs

gt; especially > > that all the CPEPs for branch-2.x still depend on it, doing this will > break > > Phoenix and other projects which are based on HBase... > > > > Thanks. > > > > Nick Dimiduk 于2023年3月7日周二 20:08写道： > > > > > Hi Wes, > > > &

Re: [DISCUSS] Time for new releases?

On Fri, Mar 24, 2023 at 7:16 AM 张铎(Duo Zhang) wrote: > Checked the jira release pages, there are 34 issues for 2.4.17[1], and 49 > issues for 2.5.4[2]. The previous releases for 2.5.x and 2.4.x were > releases around ~2.10, so I think it is time to roll new releases now. > +1 And for 3.0.0-alph

Fwd: TAC supporting Berlin Buzzwords

FYI -- Forwarded message - From: Gavin McDonald Date: Fri, Mar 24, 2023 at 10:57 Subject: TAC supporting Berlin Buzzwords To: PMCs, Please forward to your dev and user lists. Hi All, The ASF Travel Assistance Committee is supporting taking up to six (6) people to attend Berl

Re: [VOTE] First release candidate for HBase 2.4.17 is available

+1 (binding) * Signature: ok * Checksum : ok * Rat check (11.0.18): ok - mvn clean apache-rat:check -D hadoop.profile=3.0 -D skipTests * Built from source (11.0.18): ok - mvn clean install -D hadoop.profile=3.0 -D skipTests -DskipTests * Re

Re: [DISCUSS] Flatten plugin and project metadata

; > https://www.mojohaus.org/flatten-maven-plugin/apidocs/org/codehaus/mojo/flatten/FlattenMode.html > >> > >> Maybe we should try to use oss or ossrh mode? So we can keep the mailing > >> list and other things in pom. > >> > >> I will try these two op

Re: Scanning HBase for CVEs

Hi Wes, Thanks a lot for doing this work. Let's start burning down your list! On Tue, Apr 11, 2023 at 11:37 AM Wes Schuitema wrote: > We've scanned the HBase repositories (both hbase and hbase-thirdparty) for > CVEs using a Maven dependency-check plugin ( > https://jeremylong.github.io/Dependen

Re: Slack invitation request

Sent and sent. On Fri, Apr 21, 2023 at 10:10 asma zgolli wrote: > I wish to have an invite as well. > > Le ven. 21 avr. 2023 à 09:35, Wes Schuitema a écrit : > > > Can I also get an invite? > > > > On Fri, Apr 21, 2023 at 9:29 AM 张铎(Duo Zhang) > > wrote: > > > > > Invitation sent. > > > > > >

Re: Access to Slack channel please

Invitation sent, dropping the “invalid.” On Thu, Apr 20, 2023 at 23:23 Mitchell Thomas wrote: > Please provide access to the hbase Slack channel. I participated in the > last meetup and would like to review the recording and I see that the > password for the recording has been placed there. >

Re: [DISCUSS] Do not send jira notification emails to dev list?

I prefer the system as it is. It’s simple enough to filter for messages not sent by Jira in my mail client. Maybe it’s a bad UX if you’re on lists.a.o? That comment from the board didn’t include enough context for me to understand their issue. On Fri, Apr 21, 2023 at 11:17 张铎(Duo Zhang) wrote: >

FYI: CNCF Storage Committee meetings

Heya, For folks interested in HBase on Kubernetes, and storage in CNCF more broadly, the CNCF has a technical advisory group ("TAG") focused on storage [0]. They meet twice each month, the next call being tomorrow, 26 April. I don't yet know the nature of the calls. I had some discussions about t

Re: Scanning HBase for CVEs

ctionable Jira > > issues later this week. > > > > Regards, > > > > Wes > > > > > > > > On Mon, Apr 17, 2023 at 1:06 PM Nick Dimiduk > wrote: > > > >> Hi Wes, > >> > >> Thanks a lot for doing this work. Let's st

[ANNOUNCE] New HBase committer Nihal Jain

Hello! On behalf of the Apache HBase PMC, I am pleased to announce that Nihal Jain has accepted the PMC's invitation to become a committer on the project. We appreciate all of Nihal's generous contributions thus far and look forward to his continued involvement. Congratulations and welcome, Nihal

Re: [DISCUSS] Kubernetes Orchestration for ZK, HDFS, and HBase

perator-tools/tree/HBASE-27827-kubernetes-deployment [3]: https://github.com/apache/hbase-operator-tools/compare/HBASE-27827-kubernetes-deployment...ndimiduk:hbase-operator-tools:HBASE-27827-kubernetes-deployment On Mon, Mar 13, 2023 at 11:28 AM Nick Dimiduk wrote: > Heya team, > > Over

Re: [DISCUSS] Move stable pointer to 2.5.x

+1 On Fri, 5 May 2023 at 09:13, 张铎(Duo Zhang) wrote: > As discussed in the online meeting, and also other places, before EOL > 2.4.x, we should first move our stable pointer to 2.5.x. > > And there are also som2.5.x usages around the community on large clusters > which proves that the release c

Re: [DISCUSS] Kubernetes Orchestration for ZK, HDFS, and HBase

d at maven integration via exec-maven-plugin. I'm also investigating how to pull the container image build up into maven as well. Thanks, Nic, On Thu, May 4, 2023 at 2:42 PM Nick Dimiduk wrote: > Heya team, > > I've created a feature ticket [0] from which this contributio

Re: [DISCUSS] Kubernetes Orchestration for ZK, HDFS, and HBase

https://github.com/apache/hbase-operator-tools/pull/118 On Fri, May 12, 2023 at 4:19 PM Nick Dimiduk wrote: > Heya team, > > I have created individual pull-requests for each of the major functional > pieces outlined in the initial branch. These await review. > > I've now sta

Re: [DISCUSS] Kubernetes Orchestration for ZK, HDFS, and HBase

en I come back I will review them) > > -Stephen > > On Mon, May 22, 2023 at 6:08 PM Nick Dimiduk wrote: > > > Heya team, > > > > I have rebuilt one of the early PRs so that the docker image build pieces > > are integrated with the maven build. If this is accep

Re: [DISCUSS] Disable HDFS readahead for PREAD reads

Hi Bryan, Based on your observations, I'm in favor of changing the default for new minor releases going forward, and maybe some comments about this in the online book. I'm also in favor of exposing configurable readahead for STREAM reads, enabling easier experimentation for those keen to do so. T

[DISCUSS] Introduce new git repository for kustomize definitions (was: Kubernetes Orchestration for ZK, HDFS, and HBase)

nvironment that are not otherwise needed by operator-tools. What do you think? SHould we request a new repository for the kustomize files? I propose hbase-kustomize.git. Thanks, Nick On Mon, May 22, 2023 at 4:33 PM Nick Dimiduk wrote: > I went ahead and rebuilt the Hadoop image module in the

Re: [DISCUSS] Introduce new git repository for kustomize definitions (was: Kubernetes Orchestration for ZK, HDFS, and HBase)

2023 at 5:33 PM Viraj Jasani wrote: > > > +1 for hbase-kustomize > > > > On Mon, Jun 5, 2023 at 4:44 AM Nick Dimiduk wrote: > > > > > Hello, > > > > > > As I work through the integration of these kustomize definitions into > the >

Re: [DISCUSS] Introduce new git repository for kustomize definitions (was: Kubernetes Orchestration for ZK, HDFS, and HBase)

I’ve created this repository. Unless there is an objection, I’ll push an initial commit with a LICENSE file so that there’s a baseline to make PRs against. Thanks, Nick On Fri, 9 Jun 2023 at 18:30, Nick Dimiduk wrote: > Thanks everyone who has replied. > > If there are no further

[DISCUSS] Release versioning scheme for new hbase-kustomize repo (was: Introduce new git repository for kustomize definitions)

efix across our repositories, by using "hbase-thirdparty-" as that repo's version prefix going forward.) What do you think? Thanks, Nick On Mon, Jun 12, 2023 at 7:18 PM Nick Dimiduk wrote: > I’ve created this repository. > > Unless there is an objection, I’ll push an initia

Artifact signing via CI

Heya, It has come to my attention that Infra is now willing to manage signing keys. This is a big step toward moving our release builds to CI, which would take a major burden off of our release managers. I thought that y’all might also be interested. Thanks, Nick https://infra.apache.org/releas

Re: Artifact signing via CI

Signing releases with Jenkins implies to me that we’re building releases with Jenkins, but perhaps that’s presumptuous. On Wed, 19 Jul 2023 at 16:18, 张铎(Duo Zhang) wrote: > +1 for releasing with jenkins job! > > Nick Dimiduk 于2023年7月19日周三 16:09写道： > > > > Heya, >

Re: Access to Hbase Slack channel

Invitation sent. Thanks, Nick On Mon, 24 Jul 2023 at 12:02, Anwesha Banerjee wrote: > Hi Team, > I wish to begin my contribution to HBase as a developer. Request you to > kindly send me an invite to the Slack Channel > . > > Best Regards, > Anwesha Banerjee >

Re: [ANNOUNCE] New HBase committer Hui Ruan(阮辉)

Congratulations Hui Ruan and thanks a lot for all your contributions ! On Fri, Sep 15, 2023 at 11:08 AM 张铎(Duo Zhang) wrote: > On behalf of the Apache HBase PMC, I am pleased to announce that Hui > Ruan(frostruan) > has accepted the PMC's invitation to become a committer on the > project. We app

Re: [VOTE] First release candidate for hbase-thirdparty 4.1.5 is available for download

+1 * Signature: ok * Checksum : ok * Rat check (1.8.0_382): ok - mvn clean apache-rat:check * Built from source (1.8.0_382): ok - mvn clean install -DskipTests * Unit tests pass (1.8.0_382): ok - mvn clean package hbase#5411 l

Re: Please welcome our newest committer, Jeffrey Zhong

Well done Jeffrey! On Tue, Jun 4, 2013 at 10:33 AM, Jeffrey Zhong wrote: > > Thanks so much for all the warm welcomes. I'm very excited to be onboard! > Looking forward to working more with you all. > > On 6/4/13 10:25 AM, "Jimmy Xiang" wrote: > > >Congrats and welcome, Jeffrey! > > > > > >On Tu

Re: large heaps

It looks like there's some interest from RedHat in solving these problems using OpenJDK. http://rkennke.wordpress.com/2013/06/10/shenandoah-a-pauseless-gc-for-openjdk/ On Wed, Jun 12, 2013 at 11:55 PM, Nicolas Liochon wrote: > Thanks a lot Todd, your conclusion does confirm the feeling I had ar

Re: HBase svn-github synchronization is broken

This happens from time to time. After this bit me the second time, I switched my git origin to git.apache.org/hbase.git. It seems slower for initial clone, but subsequent updates are fast enough. -n On Wed, Jun 19, 2013 at 6:50 PM, Sergey Shelukhin wrote: > FYI: > > https://issues.apache.org/jir

Re: 0.95 and 0.96 remaining issues

I want to see initial data type APIs ship out with 0.95.2. A patch for ordered byte serialization is up (HBASE-8201) and is nearing steady-state. However, sershe is the only person who's left feedback. I just posted an early patch for the data type API itself (HBASE-8693). It should get some eyes f

Re: Opinions on the 'watcher' script that surrounds launched hbase daemons

The template approach is cleaner. It sounds like it's encroaching on BigTop territory. On Mon, Jun 24, 2013 at 1:49 PM, Stack wrote: > New in 0.95, when you do a process listing, there are two 'hbase' > processes. There is the old java process itself and then there is the > launcher script that

Re: HBASE-8803: region_mover.rb should move multiple regions at a time

Hi JM, I'll take this for a spin and post my findings. Can you post your 0.94 patch as well so I can compare apples-to-apples? Thanks, Nick On Thu, Jun 27, 2013 at 11:25 AM, Jean-Marc Spaggiari < jean-m...@spaggiari.org> wrote: > Hi mates, > > I have done some changes in the region_mover to all

Re: Adding a new region server or splitting an old region in a Hash-partitioned HBase Data Store

Hi Joarder, I think you're slightly confused about the impact of using a hashed (or sometimes called "salted") prefix for your rowkeys. This strategy for rowkey design has an impact on the logical ordering of your data, not necessarily the physical distribution of your data. In HBase, these are or

Data types stage 1 is ready for reivew

Heya devs, I have two 90k patches I'd like to get some more eyes on. The first is the OrderedBytes patch, HBASE-8201 [0]. It is lightly analogous to the existing Bytes.toXXX methods, but implements order-preserving serialization strategies. Its encoding format can be inspected to determine the enc

Re: Data types stage 1 is ready for reivew

New patch posted. What do you think about the new isSkippable() and the associated limitation in Struct? I also posted some "dogfeed" per Enis's suggestion. -n On Fri, Jul 12, 2013 at 1:38 PM, Stack wrote: > On Fri, Jul 12, 2013 at 1:10 PM, Enis Söztutar wrote: > > > Did some chatting with Ni

Re: Data types stage 1 is ready for reivew

n > the same order as you've used for write. > (but maybe is just an immutable/fixed list of fields, and I'm ok with just > adding that info to the comment on top of the class) > > > Matteo > > > > On Wed, Jul 17, 2013 at 12:39 AM, Nick Dimiduk wrote: > >

Re: Connection reference counting

On Wed, Jul 17, 2013 at 1:03 AM, Lars George wrote: > Is that wanted? Just curious, since obviously this is not a biggie in real > life. > I dunno, it sounds like an issue to me. -n

Apache mailing list archives?

Apache's mail archives appear to be down, both http://hbase.apache.org/mail/issues/ and http://hbase.apache.org/mail/dev/return 404. What's the appropriate mechanism for reporting these back to infra? Thanks, Nick

Re: Apache mailing list archives?

om/ which indexes most Hadoop TLP's. > > Cheers > > On Tue, Jul 23, 2013 at 9:37 AM, Nick Dimiduk wrote: > > > Apache's mail archives appear to be down, both > > http://hbase.apache.org/mail/issues/ and > > http://hbase.apache.org/mail/dev/return 404. What'

Re: Apache mailing list archives?

http://hbase.apache.org/mail-lists.html Other links column. On Wed, Jul 24, 2013 at 11:00 AM, Stack wrote: > On Tue, Jul 23, 2013 at 9:53 AM, Nick Dimiduk wrote: > > > I wanted to page through the issues list. mail-archives.a.o works just as > > well; reporting the 404 to

Re: Data types stage 1 is ready for reivew

If you've already left me a review, thank you; please have another look at these patches. If you have an opinion here and haven't voiced it, we're approaching the "forever hold your peace" part of the ceremony. Thanks, Nick On Wed, Jul 17, 2013 at 9:33 AM, Nick Dimiduk w

Re: Resend: NIST Big Data Working Group, Open Source, and Standards

dev to bcc, +devaraj Hi Bob, I think you meant to address Devaraj Das, not the HBase Developer list. Thanks, Nick On Tue, Jul 23, 2013 at 9:26 PM, Bob Marcus wrote: > Alan, Arun, Devaraj: > > I am the industry and standards Co-Chair of NIST's Big Data Working Group > Initiative. Participant

Re: ycsb and hbase 0.95.1 hadoop2

Hi Paul, I think Nicolas Liochon maintains a personal set of branches for this. Maybe he can point you in the right direction. Thanks, Nick On Mon, Jul 29, 2013 at 12:48 AM, Paul Baclace wrote: > [This might look like a user list question, or a question for another > project, but people on the

Re: 60000 millis timeout while waiting for channel to be ready for read

Hi Shapoor, Moving the conversation to the users list. Have you solved your issue? Sorry you haven't gotten a response sooner -- I think everyone is working overtime to get 0.96 released. I'm assuming each put is independent of the others. You're not putting 100mm times to the same row, are you?

Re: [UPDATE] Finishing up 0.96 --> WAS Re: 0.95 and 0.96 remaining issues

On Tue, Jul 30, 2013 at 3:28 PM, Enis Söztutar wrote: > Let me elaborate. There are at least new RPC PB, PB structures in HFiles / > hlogs, and zk, table locks, bucket cache, online merge, stochastic LB, > hbase on windows, *new data types*, AM changes, favorite node assignment, > dist log replay

Re: [UPDATE] Finishing up 0.96 --> WAS Re: 0.95 and 0.96 remaining issues

27;re open to such a patch. The OrderedBytes stuff will require applications to have a plan for data migration when they decide to transition over to it, but they can get a head-start on the boiler-plate code. On Tue, Jul 30, 2013 at 5:39 PM, Nick Dimiduk wrote: > > > On Tue, Jul 30, 2013

Re: [UPDATE] Finishing up 0.96 --> WAS Re: 0.95 and 0.96 remaining issues

t not negatives; &c. HBase would not ship out-of-the-box with general purpose order-preserving types, but you'd have the API and be able to implement your own. On Tue, Jul 30, 2013 at 9:11 PM, Nick Dimiduk wrote: > > > On Tue, Jul 30, 2013 at 8:20 PM, James Taylor > >wr

Re: [UPDATE] Finishing up 0.96 --> WAS Re: 0.95 and 0.96 remaining issues

On Wed, Jul 31, 2013 at 10:31 AM, Stack wrote: > So what would be the incentive using the new API be? > Hopefully the new API is nicer than managing byte[]'s on manually. The only incentive for users would be keeping up with progress, giving users the chance to start migrating their applications

Re: [UPDATE] Finishing up 0.96 --> WAS Re: 0.95 and 0.96 remaining issues

dent concessions considering the timelines. On Wed, Jul 31, 2013 at 12:04 PM, Nick Dimiduk wrote: > > > On Wed, Jul 31, 2013 at 10:31 AM, Stack wrote: > > > > > So what would be the incentive using the new API be? > > > > > > > Hopefully the new API is

Re: unit test help

This one has fallen by the way-side. Stack, are you still seeing this behavior? Maybe Jeffrey's Jenkins history utility can get you the information you need? On Sat, Jul 20, 2013 at 7:42 PM, Stack wrote: > Any ideas on how to debug failures where all tests 'pass' but build still > reported as fa

Re: Data types stage 1 is ready for reivew

Finally-for-real-this-time patches posted. I'll take your +1's any time now ;) Thanks, Nick On Wed, Jul 24, 2013 at 11:27 AM, Nick Dimiduk wrote: > Hi everyone, > > As of yesterday, I've posted "final" patched on both > HBASE-8201<https://issues.apach

Re: Data types stage 1 is ready for reivew

to me. Without the strict dependencies on hadoop or hbase > > it'll be easy to pull into its own standalone module or new project if > > there's demand. > > > > > > On Thu, Aug 1, 2013 at 6:30 PM, Nick Dimiduk wrote: > > > >> Finally

Re: Heads up, HTablePool will be deprecated in 0.94, 0.95/0.96, and removed in 0.98

On Fri, Aug 2, 2013 at 9:29 PM, lars hofhansl wrote: > * HConnection: > public HTableInterface getTable(byte[] tableName) throws IOException > public HTableInterface getTable(byte[] tableName, ExecutorService > pool) throws IOException > public HTableInterface getTable(String tableNam

Re: Heads up, HTablePool will be deprecated in 0.94, 0.95/0.96, and removed in 0.98

On Sat, Aug 3, 2013 at 8:52 PM, Ted Yu wrote: > Does this mean that user code wouldn't be able to depend > on HConnectionManager for connection sharing ? > My read of the above is that the HConnection instance is shared across consumers, is the shared connection. Am I reading that correctly? On

Re: 0.94.11 this week

It'd be nice to see HBASE-8803 make the cut, but it's not critical. On Mon, Aug 5, 2013 at 1:21 PM, lars hofhansl wrote: > Any last wishes (for 0.94.11)? > > -- Lars >

Re: Data types stage 1 is ready for reivew

we should not enforce clients to use it. > > JM > > 2013/8/3 Nick Dimiduk > > > On Sat, Aug 3, 2013 at 10:33 AM, Michael Segel < > msegel_had...@hotmail.com > > >wrote: > > > > > How do you plan on enforcing data types within the engine? > >

Re: Chocolatey package for Windows

Hi Andrew, I don't think the homebrew recipes are managed by an HBase developer. Rather, someone in the community has taken it upon themselves to provide the project through brew. Likewise, the Apache HBase project does not provide RPM or DEB packages, but you're likely to find them if you look ar

Re: [UPDATE] Finishing up 0.96 --> WAS Re: 0.95 and 0.96 remaining issues

Mr Taylor has asked for a small cleanup in the Struct type's handling of trailing NULLs: HBASE-9283. On Thu, Aug 22, 2013 at 1:56 PM, Stack wrote: > I'm thinking of cutting a 0.96.0RC0 on Monday. You lot good w/ that? > > The only real blocker is HBASE-8348, the migration script, but that is >

Re: [UPDATE] Finishing up 0.96 --> WAS Re: 0.95 and 0.96 remaining issues

On Mon, Aug 26, 2013 at 2:17 PM, Jonathan Hsieh wrote: > I'd really like to get the api clean up (get KeyValue out of the > InterfaceAudience.public API). > I'm +1 for this if it's at all reasonably possible. Let me know if I can help with more than reviews, @jon. On Mon, Aug 26, 2013 at 12:21

Is DynamicClassLoader necessary for client applications?

Hi all, It appears that as of HBASE-1936, we now require that client applications have write access to hbase.local.dir. This is because ProtobufUtil instantiates a DyanamicClassLoader as part of static initialization. This classloader is used for instantiating Comparators, Filters, and Exceptions.

Re: [UPDATE] Finishing up 0.96 --> WAS Re: 0.95 and 0.96 remaining issues

at 5:47 PM, Nick Dimiduk wrote: > > > Mr Taylor has asked for a small cleanup in the Struct type's handling of > > trailing NULLs: HBASE-9283. > > > > > Long as it is done by Monday! > St.Ack >

Re: Is DynamicClassLoader necessary for client applications?

On Tue, Aug 27, 2013 at 11:09 PM, Stack wrote: > what do we gain if we go to the trouble distinguishing > true clients from clients used by hbase servers internally (even for > clients used internally by servers, why would we want these fellas doing > dynamic loading out of an hbase.local.dir)? >

Re: Is DynamicClassLoader necessary for client applications?

Thanks. I opened HBASE-9374. On Wed, Aug 28, 2013 at 4:49 PM, Nick Dimiduk wrote: > On Tue, Aug 27, 2013 at 11:09 PM, Stack wrote: > >> what do we gain if we go to the trouble distinguishing >> true clients from clients used by hbase servers internally (even for >> cl

Re: [VOTE] The 1st hbase-0.96.0 release candidate is available for download

I will second Mr. Hsieh's concern for minimizing the impact of unnecessary API and ABI changes via more intentional evaluation of said changes (expressed on a different thread). He's done a great effort with that doc of his, but it needs more eyes. I think we also need consensus on how much code we

Re: Corrupted log file

Detecting the condition, printing the warning, and breaking the loop sounds like an urgent bandaid solution to me. -n On Tue, Apr 30, 2013 at 11:51 AM, Jean-Marc Spaggiari < jean-m...@spaggiari.org> wrote: > When a log file (into /hbase/.logs) is corrupted, HBase is not able to > start because i

Re: running test suite for patches using 0.94 branch on Jenkins

There's quite a bit of activity on 0.94: +1 On Wed, Mar 13, 2013 at 6:23 PM, Ted Yu wrote: > Hi, > I noticed the number of backports to 0.94 is ticking up. > If the contributor clicks 'Submit Patch' button for the backport, he / she > would get: > > -1 patch. The patch command could not apply th

Re: HBase type support

with more thorough type awareness, but they are not addressed here. This is intended only as a client-side improvement for the sake of users of HBase. How can the motivation document be improved to make these intentions more clear? Thanks, Nick On Wed, Mar 13, 2013 at 4:42 PM, Nick Dimiduk wr

Re: The Jenkins VMs are increasingly slow / overloaded

What, like travis-ci.org ? On Tue, Mar 19, 2013 at 8:49 AM, Andrew Purtell wrote: > Would the HBase dev community be open to alternate hosted Jenkins test > infrastructure? > > -- > Best regards, > >- Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via To

<    5   6   7   8   9   10   11   12   13   14   >