Re: [DISCUSS] Move our official slack channel to the one in the-asf.slack.com

+1 good idea! On Mon, Jul 8, 2024 at 10:28 PM Clay B. wrote: > > (Nonbinding) +1! > Original message From: Wei-Chiu Chuang > Date: 7/8/24 11:44 AM (GMT-07:00) To: dev@hbase.apache.org Cc: hbase-user > Subject: Re: [DISCUSS] Move our official slack > channel to the one in t

Re: Make the AccessChecker configurable

yAgentCoprocessor. > > > > You're right that there are a couple direct calls to AccessChecker, but > we > > should wrap those with coprocessor instead. I thought we actually did > that > > recently > > > > On Fri, May 24, 2024 at 11:54 AM Lars Fran

Re: Make the AccessChecker configurable

s its own authorization by HBase coprocessor > > https://github.com/apache/ranger/tree/master/hbase-agent > > Lars Francke 于2024年5月24日周五 22:54写道： > > > > Hi, > > > > we'd like to implement a way to use authorization information from > > Open Policy Agent[1].

Make the AccessChecker configurable

Hi, we'd like to implement a way to use authorization information from Open Policy Agent[1]. We already do the same for HDFS, Trino and a few other tools. It's been a while since I dug into the internals on this one but it seems as if we're missing a piece that's needed and that is a plugin point

Re: HBASE-28242: Remove support for async-profiler v1

this to branch-2, but in that backport we add back > > whatever enum options are necessary to keep support for both v1 and v2. We > > can say that v1 is dropped in 3.x. If necessary, we can add a config in > > branch-2 to specify which version of async-profiler to use (like if we n

Re: HBASE-28242: Remove support for async-profiler v1

gt; options, when we could just directly send the user's input to > async-profiler. If they specify a bad option, maybe we can show them the > error message from async-profiler. This approach might allow for any > async-profiler version. > > [1] https://hbase.apache.org/book.h

HBASE-28242: Remove support for async-profiler v1

Hi, I just wanted to give a heads-up on an issue I created (thanks for everyone's help)[1] This would be a breaking change as it removes support for async-profiler v1 but in exchange it does add support for various v2 features and in general "unbreaks" things that were broken. I already have an

Re: Debugging slowness in Gets

7, 2023 at 9:11 AM Lars Francke wrote: > > Hi Nick, > > yes, thank you. We have it running in containers now but privileged > containers are not allowed. > I created this https://github.com/apache/hbase/pull/5566 to allow the > "itimer" thing and upgrade to async-p

Re: Debugging slowness in Gets

ttps://github.com/async-profiler/async-profiler#basic-usage > [1]: > https://github.com/async-profiler/async-profiler#profiling-java-in-a-container > > On Wed, Dec 6, 2023 at 10:03 AM Lars Francke wrote: > > > Thanks Nick, > > I'll take a look at that. > > > &

Re: Debugging slowness in Gets

oad it from the region server file system > (annoying to do from a container). There’s probably a closed Jira where I > scratch my head in public. > > On Wed, 6 Dec 2023 at 08:15, Lars Francke wrote: > > > > > Also, are you sure you couldn't use async-profile

[jira] [Created] (HBASE-28242) ProfileServlet does not allow selecting all events (e.g. itimer)

Lars Francke created HBASE-28242: Summary: ProfileServlet does not allow selecting all events (e.g. itimer) Key: HBASE-28242 URL: https://issues.apache.org/jira/browse/HBASE-28242 Project: HBase

Re: Debugging slowness in Gets

docs earlier) that it's hard to run async-profiler in a container. For us, this is all running on Kubernetes, so we'll test that today. Testing i tlocally it looked very promising. > > > > On Tue, Dec 5, 2023 at 3:46 PM Lars Francke wrote: > > > > > Hi,

Re: Debugging slowness in Gets

er used async-profiler. Shame on me. That is a fabulous hint and I'll read up on it immediately. Thank you again! > > On Tue, Dec 5, 2023 at 3:46 PM Lars Francke wrote: > > > Hi, > > > > I am debugging an issue where we see some Get requests taking 2-5s. > > We do

Re: Debugging slowness in Gets

s, > using byte buffers and hadoop IOUtils to read from hdfs. Excellent, thank you! I'm sometimes wondering if it would make sense to document the architecture somewhere but the audience is small and it would need to be kept in sync. That's kept me from doing that so far. > > Em ter

Debugging slowness in Gets

Hi, I am debugging an issue where we see some Get requests taking 2-5s. We do see "responseTooSlow" etc. and this is in an environment where I cannot run a Profiler but I _can_ run modified code. So what I did was I added a stupid "MethodTimer"[1] which records how long certain operations take a

[jira] [Created] (HBASE-28205) Remove mention of MasterRegistry being the default

Lars Francke created HBASE-28205: Summary: Remove mention of MasterRegistry being the default Key: HBASE-28205 URL: https://issues.apache.org/jira/browse/HBASE-28205 Project: HBase Issue

Re: Time for new releases?

plan is to release 2.6.0 first, and then do a final 2.4.18 release > for the 2.4.x release line, and then mark 2.4.x as EOL. > > I think Byran is still working on stabilizing current branch-2, but at > least for me I think it is time to cut branch-2.6 now. > > Thanks. >

Re: Time for new releases?

Hi, I know this thread is a bit older but due to https://issues.apache.org/jira/browse/HBASE-27860 I have an interest in a release of 2.4.18 and was wondering if you have a rough timeline already? Cheers, Lars On Thu, Aug 24, 2023 at 4:40 AM 张铎(Duo Zhang) wrote: > > Thanks Andrew. > > I think r

[jira] [Created] (HBASE-28160) Build fails with Hadoop 3.3.5 and higher

Lars Francke created HBASE-28160: Summary: Build fails with Hadoop 3.3.5 and higher Key: HBASE-28160 URL: https://issues.apache.org/jira/browse/HBASE-28160 Project: HBase Issue Type: Bug

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

Hi Nick, I do not mean to derail your mail so I'll keep mine short: Yes, I think testing & infrastructure on Kubernetes would be worthwhile and I thank you for the offer. We're happy to take a look and would try to review any incoming contributions depending on how large/digestable they are :) We

Region Normalizer improvements / contribution

Hi everyone, it's been a long time since I contributed and I'm sorry. I hope everyone is well and it's great to still see some familiar names on the mailing list. 1,5 years ago a customer asked me to write a "better" Region Normalizer and so I did. I have to admit that I can't remember all the d

Re: HBase 2.4.x + Spark 3.3

ingle -DskipTests -Dhadoop.profile=3.0 > -Dhadoop-three.version=XXX > > Then once the results are in your local maven cache or nexus instance, you > can compile Spark as indicated. > > > On Tue, Oct 18, 2022 at 11:39 PM Lars Francke > wrote: > > > Hi Andrew, > &g

Re: HBase 2.4.x + Spark 3.3

g > HBase using -Dhadoop.profile=3.0 as a first step as well. > > > On Mon, Oct 17, 2022 at 1:52 PM Lars Francke > wrote: > > > Hi everyone, > > > > we've just recently tried getting the HBase Spark connector running > against > > Spark 3.3 and HBas

Re: [DISCUSS] HBase 3 release plans

> The mandating of Java 11 or later runtimes is a much bigger investment > that this discussion seems to contemplate. Unless we don’t care about > adoption. > > > > If you want next generation low pause GC, Shenandoah has been ported > back to 8, is supported and available in R

Re: [DISCUSS] HBase 3 release plans

move up the bytecode compatibility line. Any thoughts there. I > >>> can’t think of a one. Eventually the value types work might be worth > it. > >>> There may be differences in runtime, like we’ve seen historically. So > far > >>> we have managed to na

Re: [DISCUSS] HBase 3 release plans

Amazon, and so > > on), at least a big part of java world will still be on JDK8, this means > we > > still need to run HBase 2 for a very long time? > > > > Lars Francke 于2020年2月17日周一 下午6:45写道： > > > >> Sean, > >> > >> you didn't have

Re: [DISCUSS] HBase 3 release plans

Sean, you didn't have any explicit questions or request for feedback in your mail so I'll just say that from my point all the points from your mail make sense to me and I'm +1 on all of them. - Timeline (GA December/January) - Start of shorter release cycle - Rolling upgrade - JDK11+ - Hadoop 3 o

Re: [ANNOUNCE] Please welcome Jan Hentschel to the Apache HBase PMC

Congratulations Jan and especially thank you for your work on the deprecations On Wed, May 8, 2019 at 11:37 PM Sean Busbey wrote: > On behalf of the Apache HBase PMC I am pleased to announce that Jan > Hentschel has accepted our invitation to become a PMC member on the > HBase project. We apprec

Re: [DISCUSS] Handling removal of deprecated methods and classes

On Tue, Apr 23, 2019 at 9:04 PM Zach York wrote: > Always good to see the history of the discussion :) It looks like nothing > really was decided last time (use caution if removing before a full major > version), hopefully we can come up with something more descriptive this > time. > Yeah, I fol

Re: [DISCUSS] Handling removal of deprecated methods and classes

We had this exact same discussion four years ago (I thought it was last year :O ): < https://lists.apache.org/thread.html/bbdbf135abe7d8a0a4e7e9563f0bdc3dd6b555a0d3cdc1b1fdd688c2@1427759561@%3Cdev.hbase.apache.org%3E > On Tue, Apr 23, 2019 at 6:32 PM Sean Busbey wrote: > I have the same interpre

Re: HBase Jira Issues via Rest Api

Hi, yes you can. And it's just as it says in the documentation you provided so I'm not sure what you're looking for exactly. One example: You need to be logged in. If you plan on scraping please be considerate and implement rate-l

Re: Expose an API to get all ACLs

On Wed, Nov 28, 2018 at 7:22 AM Stack wrote: > On Tue, Nov 27, 2018 at 11:04 AM Lars Francke > wrote: > > > Hi, > > > > I have a use-case for a customer who's looking to build an audit tool. > This > > audit tool should build a report of all authorizati

Re: Expose an API to get all ACLs

today, it just requires more work. Agreed on the permissions! [1] <https://issues.apache.org/jira/browse/HBASE-12470> > > -- > > Best regards, > R.C > > > > > From: Lars Francke > Sent: 28 Novemb

Expose an API to get all ACLs

Hi, I have a use-case for a customer who's looking to build an audit tool. This audit tool should build a report of all authorizations across various products. HBase is one of them. Unfortunately in HBase it's not currently possible to list all ACLs without going directly to the _hbase:acl_ table

Re: Updating team in pom.xml

don't want to run the check locally, a jira with a patch will > cause the QABot to render the site for you. > On Mon, Aug 27, 2018 at 1:09 PM Lars Francke > wrote: > > > > It looks like I never added myself to the team listing in pom.xml. > > Looking at past c

Updating team in pom.xml

It looks like I never added myself to the team listing in pom.xml. Looking at past commits it looks like I can just do that myself without opening a Jira? And everyone's using numerical timezones but Maven also allows text identifiers[1] like "Europe/Berlin". Any objections in me using that? It's

Re: Debugging HBase

If you stumble onto anything that would be good for other devs, I think > that would be a nice addition to the HBase book. > > > On 8/19/18 2:43 PM, Lars Francke wrote: > >> Thanks Josh, are you using IntelliJ or Eclipse? >> >> This is one of those things that ha

Re: Debugging HBase

t; Most of the time I have to do this, it's either in an RPC handler thread > or in a daemon thread we spawned off for some specific purpose. These would > naturally not preclude the RS from continuing to talk to ZK or the Master. > > > On 8/15/18 11:46 PM, Lars Francke wrot

Debugging HBase

Hi everyone, this might sound like a stupid question but how do you go about debugging HBase? (With the Java debugger I mean) I use IntelliJ to attach to the running Master or RegionServer as needed, set breakpoints etc. But every time I do so the connection to ZK times out and Master or RS are

Re: [DISCUSS] Kafka Connection, HBASE-15320

I'd love to have the Kafka Connector included. @Mike thanks so much for the contribution (and your planned ones) I'm +1 on adding it to the core but I'm also +1 on having a separate repository under Apache governance On Tue, Jul 24, 2018 at 6:01 PM, Josh Elser wrote: > +1 to the great point by

[jira] [Created] (HBASE-20797) hbase-spark

Lars Francke created HBASE-20797: Summary: hbase-spark Key: HBASE-20797 URL: https://issues.apache.org/jira/browse/HBASE-20797 Project: HBase Issue Type: Bug Components: spark

Re: [DISCUSS] Effective HBase in the Cloud

Josh, thanks to you (and all the others working on this). I did read it once and I think it sounds very sane. It answers questions that I face more and more from customers. I have not looked at Ratis in detail so I can't comment on the challenge of adopting it but I agree with the comments on avoi

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

I did run this on my local MacBook with embedded ZooKeeper and had two issues: - Master starts up and uses a random port, seems to be related to https://issues.apache.org/jira/browse/HBASE-20027 & https://issues.apache.org/jira/browse/HBASE-20224 - I did run LTT (for the first time ever so I might

Re: [DISCUSS] Branching for HBase 1.5 and Hadoop minimum version update (to 2.7)

I'm in favour of 2.7.1+ as well. A special call-out about Hadoop also seems fine. Thanks Andrew! On Thu, Apr 26, 2018 at 8:42 AM Andrew Purtell wrote: > I think yes > > On Wed, Apr 25, 2018 at 7:13 AM, Sean Busbey wrote: > > > How would we rephrase our compatibility guidelines? Special call-out

Re: [VOTE] The third release candidate for HBASE 2.0.0 (RC2) is available

Thanks Stack. In that case I'm -0 on this RC. I'd really like to either revert that patch or at least document the deprecation so we can remove it in 3.0. The way it is now we can't remove getTypeByte() in 3.0 because we'll need it for getType() which we can't change because it's not documented as

Re: [VOTE] The third release candidate for HBASE 2.0.0 (RC2) is available

Hi all, I'm sorry, I didn't mean to send this mail as an answer to this thread but separate. It does not belong in this discussion. Cheers, Lars On Tue, Apr 24, 2018 at 4:25 PM, Lars Francke wrote: > Stack, > > I'm sure you'll want to slap me for bringing this

Re: [VOTE] The third release candidate for HBASE 2.0.0 (RC2) is available

Stack, I'm sure you'll want to slap me for bringing this up so late (I only found it recently) but could you take a look at the recent discussions in < https://issues.apache.org/jira/browse/HBASE-19746>? Is there any need for me to work on this or would it be too late to merge this change anyway?

Re: Introduce a new annotation to say there is no BC guarantee in the inheritance

Sorry to dig up this old thread. I've also just commented on < https://issues.apache.org/jira/browse/HBASE-19746> The book says: > MAJOR version when you make incompatible API changes, So do we really need to keep BC between major versions? How else would we ever add new methods to interfaces wit

Re: Tools for balancing a poorly distributed table

Thanks Tim! I've seen both problems myself (independent of Tim I should add, even though he helps us here) and continue to see them at customers almost every month. 1) Hard to determine proper pre-split points: Everyone I meet either just guesses or writes their own little program that basically

Re: [DISCUSS] changing our project mission statement

I like the new version: +1 Thanks Sean! On Sun, Apr 8, 2018 at 4:58 AM, Yu Li wrote: > +1 on changing to use the summarization in release announcement for both > board report and landing page > > Best Regards, > Yu > > On 7 April 2018 at 03:54, Josh Elser wrote: > > > > > > > On 4/3/18 10:38 A

Re: [ANNOUNCE] New HBase committer Lars Francke

On Wed, Oct 25, 2017 at 12:56 PM, Lars George > > wrote: > > > > > On behalf of the Apache HBase PMC, I am pleased to announce that Lars > > > Francke has accepted the PMC's invitation to become a committer on the > > > project. > > > &g

[jira] [Created] (HBASE-18599) Add missing @Deprecated annotations

Lars Francke created HBASE-18599: Summary: Add missing @Deprecated annotations Key: HBASE-18599 URL: https://issues.apache.org/jira/browse/HBASE-18599 Project: HBase Issue Type: Bug

[jira] [Created] (HBASE-17184) Code cleanup of LruBlockCache

Lars Francke created HBASE-17184: Summary: Code cleanup of LruBlockCache Key: HBASE-17184 URL: https://issues.apache.org/jira/browse/HBASE-17184 Project: HBase Issue Type: Improvement

[jira] [Resolved] (HBASE-16273) Display ServerLoad sizes in appropriate units

[ https://issues.apache.org/jira/browse/HBASE-16273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Francke resolved HBASE-16273. -- Resolution: Duplicate > Display ServerLoad sizes in appropriate un

[jira] [Created] (HBASE-16273) Display ServerLoad sizes in appropriate units

Lars Francke created HBASE-16273: Summary: Display ServerLoad sizes in appropriate units Key: HBASE-16273 URL: https://issues.apache.org/jira/browse/HBASE-16273 Project: HBase Issue Type

Re: [DISCUSS] issue trackers and recent stability of issues.apache/jira

JIRA is not always stable and that sucks but the cost of moving to a different tool would be fairly high because lots of workflows we know about (and probably more we don't) rely on JIRA (including my own). I'd be -0 on changing especially if the issues can and will be resolved at some point in the

Re: Changing resolution in JIRA

2243 issues have been closed. I added a comment to each (e.g. https://issues.apache.org/jira/browse/HBASE-4708 ) On Fri, Nov 20, 2015 at 9:43 AM, Lars Francke wrote: > Thank you St.Ack. Seems to work now. I'll bulk close issues without > sending notification mails. > > On Thu

Re: Changing resolution in JIRA

Thank you St.Ack. Seems to work now. I'll bulk close issues without sending notification mails. On Thu, Nov 19, 2015 at 5:25 PM, Stack wrote: > Try now. Made you an administrator Lars. > St.Ack > > On Thu, Nov 19, 2015 at 5:07 AM, Lars Francke > wrote: > > > That

Re: Changing resolution in JIRA

That was quick: I'm not allowed to close issues. Would you consider giving me more permissions for JIRA also as per my other previous mail? On Thu, Nov 19, 2015 at 2:04 PM, Lars Francke wrote: > As a first step I'm going to try and change all issues to closed that > match

Re: Changing resolution in JIRA

possibility of changing issues that have been applied to any unreleased version. Currently this filter matches 2243 issues. On Mon, Nov 9, 2015 at 9:32 PM, Lars Francke wrote: > Sounds sensible. There's a whole bunch of them (~3600 in total but haven't > checked yet whether

[jira] [Resolved] (HBASE-3933) Hmaster throw NullPointerException

[ https://issues.apache.org/jira/browse/HBASE-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Francke resolved HBASE-3933. - Resolution: Won't Fix > Hmaster throw NullPointerE

[jira] [Reopened] (HBASE-3933) Hmaster throw NullPointerException

[ https://issues.apache.org/jira/browse/HBASE-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Francke reopened HBASE-3933: - > Hmaster throw NullPointerException > -- > >

[jira] [Resolved] (HBASE-3879) Add way to control the split position of region

[ https://issues.apache.org/jira/browse/HBASE-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Francke resolved HBASE-3879. - Resolution: Duplicate > Add way to control the split position of reg

[jira] [Reopened] (HBASE-3879) Add way to control the split position of region

[ https://issues.apache.org/jira/browse/HBASE-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Francke reopened HBASE-3879: - > Add way to control the split position of reg

[jira] [Resolved] (HBASE-3779) Allow split regions to be placed on different region servers

[ https://issues.apache.org/jira/browse/HBASE-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Francke resolved HBASE-3779. - Resolution: Won't Fix > Allow split regions to be placed on different region

[jira] [Reopened] (HBASE-3779) Allow split regions to be placed on different region servers

[ https://issues.apache.org/jira/browse/HBASE-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Francke reopened HBASE-3779: - > Allow split regions to be placed on different region serv

[jira] [Resolved] (HBASE-3544) list all current active settings

[ https://issues.apache.org/jira/browse/HBASE-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Francke resolved HBASE-3544. - Resolution: Invalid > list all current active setti

[jira] [Reopened] (HBASE-3544) list all current active settings

[ https://issues.apache.org/jira/browse/HBASE-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Francke reopened HBASE-3544: - > list all current active settings > > >

Re: Changing resolution in JIRA

re if you can (or want to) only give those out for committers. On Mon, Nov 9, 2015 at 7:56 PM, Ted Yu wrote: > Lars: > Resolved issues for released versions should be closed. > > Cheers > > On Mon, Nov 9, 2015 at 11:52 AM, Lars Francke > wrote: > > > Thanks guys! &

Re: Changing resolution in JIRA

elieve that's correct. Anyway, I don't think we object to this practice. > Please feel free to help us with JIRA hygiene. > > On Mon, Nov 9, 2015 at 8:37 AM, Nick Dimiduk wrote: > > > I think reopen and reclose is "how it is done." > > > > On Monday, No

Re: Changing resolution in JIRA

it on the jira. > But may be a jira guru can do something about this... > > On Mon, Nov 9, 2015 at 10:17 AM, Lars Francke > wrote: > > > Hi, > > > > LarsG and I have been looking at a couple of JIRA issues (861 to be > > precise) that are listed as Resolved &am

Changing resolution in JIRA

Hi, LarsG and I have been looking at a couple of JIRA issues (861 to be precise) that are listed as Resolved & Fixed but without a Fix version. Some of them should have been closed as Invalid instead of Fixed and various other problems. We weren't able to change the Resolution though. We worked a

[jira] [Resolved] (HBASE-10937) How to run CsvBulkLoadTool of Phoenix 4.0

[ https://issues.apache.org/jira/browse/HBASE-10937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Francke resolved HBASE-10937. -- Resolution: Invalid > How to run CsvBulkLoadTool of Phoenix

[jira] [Reopened] (HBASE-10937) How to run CsvBulkLoadTool of Phoenix 4.0

[ https://issues.apache.org/jira/browse/HBASE-10937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Francke reopened HBASE-10937: -- > How to run CsvBulkLoadTool of Phoenix

[jira] [Created] (HBASE-14524) Short-circuit comparison of rows in CellComparator

Lars Francke created HBASE-14524: Summary: Short-circuit comparison of rows in CellComparator Key: HBASE-14524 URL: https://issues.apache.org/jira/browse/HBASE-14524 Project: HBase Issue

[jira] [Created] (HBASE-14461) Cleanup IncreasingToUpperBoundRegionSplitPolicy

Lars Francke created HBASE-14461: Summary: Cleanup IncreasingToUpperBoundRegionSplitPolicy Key: HBASE-14461 URL: https://issues.apache.org/jira/browse/HBASE-14461 Project: HBase Issue Type

[jira] [Created] (HBASE-14194) Undeprecate methods in ThriftServerRunner.HBaseHandler

Lars Francke created HBASE-14194: Summary: Undeprecate methods in ThriftServerRunner.HBaseHandler Key: HBASE-14194 URL: https://issues.apache.org/jira/browse/HBASE-14194 Project: HBase Issue

Re: Support for upgrades from 0.94

Just FYI. Tracking this in < https://issues.apache.org/jira/browse/HBASE-14193> On Sat, Aug 1, 2015 at 2:05 AM, Lars Francke wrote: > Great, thanks Lars. I'll go ahead and will try to clean this up then. > > On Fri, Jul 31, 2015 at 4:33 PM, lars hofhansl wrote: > >>

[jira] [Created] (HBASE-14193) Remove support for direct upgrade from pre-0.96 versions

Lars Francke created HBASE-14193: Summary: Remove support for direct upgrade from pre-0.96 versions Key: HBASE-14193 URL: https://issues.apache.org/jira/browse/HBASE-14193 Project: HBase

Re: Support for upgrades from 0.94

.98 is a major version step over > 0.94 we could in theory remove such from 1.x, but we only established > semantic versioning with 1.0.0. > So, yes, it seems we can (and I would argue, should) remove the upgrade > code in question from 2.x. > -- Lars > > From: Lars F

Support for upgrades from 0.94

Hi, this is referring to these two issues: I'm still looking for deprecated stuff that can be cleaned up. We have a file in the code (FSTableDescriptorMigrationToSubdir) that is used to migrate

[jira] [Resolved] (HBASE-13655) Deprecate duplicate getCompression methods in HColumnDescriptor

[ https://issues.apache.org/jira/browse/HBASE-13655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Francke resolved HBASE-13655. -- Resolution: Fixed > Deprecate duplicate getCompression methods in HColumnDescrip

Re: Ruby shell versions for HBase 2.0

I'm also in favor of a rewrite in another language (but it doesn't have to be now). This is very subjective but I never got the hang of the Ruby stuff, it's always annoying to use and I end up googling Ruby stuff almost every time I want to do something that's not covered in the help command. Scala

[jira] [Created] (HBASE-13656) Rename getDeadServers to getDeadServersSize in Admin

Lars Francke created HBASE-13656: Summary: Rename getDeadServers to getDeadServersSize in Admin Key: HBASE-13656 URL: https://issues.apache.org/jira/browse/HBASE-13656 Project: HBase Issue

[jira] [Created] (HBASE-13655) Deprecate duplicate getCompression methods in HColumnDescriptor

Lars Francke created HBASE-13655: Summary: Deprecate duplicate getCompression methods in HColumnDescriptor Key: HBASE-13655 URL: https://issues.apache.org/jira/browse/HBASE-13655 Project: HBase

[jira] [Created] (HBASE-13645) Rename *column methods in MasterObserver to *columnFamily

Lars Francke created HBASE-13645: Summary: Rename *column methods in MasterObserver to *columnFamily Key: HBASE-13645 URL: https://issues.apache.org/jira/browse/HBASE-13645 Project: HBase

[jira] [Created] (HBASE-13636) Remove deprecation for HBASE-4072 (Reading of zoo.cfg)

Lars Francke created HBASE-13636: Summary: Remove deprecation for HBASE-4072 (Reading of zoo.cfg) Key: HBASE-13636 URL: https://issues.apache.org/jira/browse/HBASE-13636 Project: HBase Issue

[jira] [Reopened] (HBASE-1989) Admin (et al.) not accurate with Column vs. Column-Family usage

[ https://issues.apache.org/jira/browse/HBASE-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Francke reopened HBASE-1989: - Assignee: Lars Francke > Admin (et al.) not accurate with Column vs. Column-Family us

Re: Spinning up for 1.1 Release

I'd love to have in if no one objects. On Wed, Apr 22, 2015 at 7:51 PM, Nick Dimiduk wrote: > My mistake Jerry, you're correct. My pre-coffee brain was thinking that by > upgrading Hadoop we'd promote the version of Jackson under us. This is no

Re: Removal of deprecated features

I've created umbrella issues for 1.x and 2.0.0 2.0.0: https://issues.apache.org/jira/browse/HBASE-13462 1.x: https://issues.apache.org/jira/browse/HBASE-13465 On Tue, Apr 14, 2015 at 12:42 PM, Lars Francke wrote: > Okay I'll go with another option. As I don't have as muc

[jira] [Created] (HBASE-13466) Document deprecations in 1.x - Part 1

Lars Francke created HBASE-13466: Summary: Document deprecations in 1.x - Part 1 Key: HBASE-13466 URL: https://issues.apache.org/jira/browse/HBASE-13466 Project: HBase Issue Type: Task

[jira] [Created] (HBASE-13465) Document deprecations in 1.x

Lars Francke created HBASE-13465: Summary: Document deprecations in 1.x Key: HBASE-13465 URL: https://issues.apache.org/jira/browse/HBASE-13465 Project: HBase Issue Type: Umbrella

[jira] [Created] (HBASE-13464) Remove deprecations for 2.0.0 - Part 1

Lars Francke created HBASE-13464: Summary: Remove deprecations for 2.0.0 - Part 1 Key: HBASE-13464 URL: https://issues.apache.org/jira/browse/HBASE-13464 Project: HBase Issue Type: Sub-task

[jira] [Created] (HBASE-13462) Handle deprecations for 2.0.0

Lars Francke created HBASE-13462: Summary: Handle deprecations for 2.0.0 Key: HBASE-13462 URL: https://issues.apache.org/jira/browse/HBASE-13462 Project: HBase Issue Type: Umbrella

Re: Removal of deprecated features

#x27;ll create the first JIRAs and post patches now. On Tue, Apr 7, 2015 at 10:29 PM, Lars Francke wrote: > Hmm...that'd work too but is a bit more arbitrary as some patches were > cross-cutting...I don't really have an opinion though :) > > On Tue, Apr 7, 2015 at 3:31 PM, Se

Re: Removal of deprecated features

; Sean > On Apr 7, 2015 7:21 AM, "Lars Francke" wrote: > > > Great, thanks everyone for your input. > > > > I started to go through the issues. > > > > I see two options: 1) One issue per "source" issue or 2) one issue per > > version. &

Re: Removal of deprecated features

filing. Cheers, Lars On Mon, Apr 6, 2015 at 8:42 PM, Stack wrote: > On Mon, Apr 6, 2015 at 8:20 AM, Sean Busbey wrote: > > > On Mon, Apr 6, 2015 at 6:54 AM, Lars Francke > > wrote: > > > > > Thanks Lars. Any other opinions, any more input? > > > >

Re: Removal of deprecated features

That should give plenty of time. > > No? > > Lars > > On Tue, Mar 31, 2015 at 8:36 AM, Lars Francke > wrote: > > > Sean, thanks for your comments. > > > > On Tue, Mar 31, 2015 at 2:09 AM, Sean Busbey > wrote: > > > > > I thought &q

Re: Removal of deprecated features

to SemVer this should be the next major version (e.g. "This feature is scheduled to be removed in HBase 3.0.0"[2]) > -- > Sean > On Mar 30, 2015 6:53 PM, "Lars Francke" wrote: > > > I know this was discussed briefly last year[1] but I'd like to bring it >

Removal of deprecated features

I know this was discussed briefly last year[1] but I'd like to bring it up again. I'd like to remove a bunch of deprecated features. Now with Semantic Versioning this should be a bit simpler. I propose the following: * In the master branch (which will be released as 2.0.0 if I'm not mistaken) re

  1   2   >