Yes. It would mean updating our README and adding something to the Release Notes.
In addition to the "we don't recommend it" text, a warning that we plan to remove it in the next version would also be good. -Sean On Fri, Apr 4, 2014 at 7:25 PM, Josh Elser <[email protected]> wrote: > Everyone else correct me if I'm mistaken, but I assume "deprecate Hadoop 1 > for 1.6.0" would primarily be an advertising/documentation change. Let > people know that it works, but it's not recommended that you use it". > > > On 4/4/14, 8:23 PM, Christopher wrote: > >> I'm not sure what it means to "deprecate" support in 1.6.0. Changing a >> minimum dependency isn't something you can really "deprecate" in the >> traditional sense of code deprecation. Perhaps this would mean just >> annotating in the 1.6.x release notes that this will be the last >> version supporting Hadoop 1, and that we encourage users to consider >> upgrading? >> >> However, I am in favor of dropping hadoop1 support (making hadoop >> 2.0.0, even 2.2.0 the minimum supported dependency) in the next >> version after the 1.6.x series (presently named 1.7.0), so long as we >> continue to support Hadoop 1 in 1.6.x releases. >> >> -- >> Christopher L Tubbs II >> http://gravatar.com/ctubbsii >> >> >> On Fri, Apr 4, 2014 at 3:11 PM, Joey Echeverria <[email protected]> >> wrote: >> >>> +1 to deprecating hadoop1 support in 1.6.0 >>> +1 to dropping hadoop1 support in 1.7.0 (or similar release) >>> >>> -- >>> Joey Echeverria >>> Chief Architect >>> Cloudera Government Solutions >>> >>> >>> On Fri, Apr 4, 2014 at 11:28 AM, Josh Elser <[email protected]> >>> wrote: >>> >>>> +1 ditto on what's been said >>>> >>>> Not sure on how "aggressive" it would be to call hadoop1 deprecated for >>>> 1.6.0, but I wouldn't mind seeing that happen. Can certainly poll the >>>> user >>>> list for input. We've already "encouraged" hadoop2 by switching the >>>> build >>>> profiles for 1.6, perhaps it's not unreasonable to call it deprecated >>>> too. >>>> >>>> >>>> On 4/4/14, 2:20 PM, Ravi Mutyala wrote: >>>> >>>>> >>>>> +1 for dropping support for hadoop1 in future versions. +1 to call it >>>>> deprecated for Hadoop 1. It might be to good option to get info from >>>>> user >>>>> list if anyone is going to use 1.6 on Hadoop1. >>>>> >>>>> Thanks >>>>> >>>>> >>>>> On Fri, Apr 4, 2014 at 1:07 PM, Mike Drob <[email protected]> wrote: >>>>> >>>>> https://issues.apache.org/jira/browse/HBASE-10690 >>>>>> >>>>>> Deprecated in 0.98, dropped in 1.0 >>>>>> >>>>>> >>>>>> On Fri, Apr 4, 2014 at 11:02 AM, Sean Busbey <[email protected]> >>>>>> wrote: >>>>>> >>>>>> Mike, as of which version is HBase dropping? >>>>>>> >>>>>>> I wouldn't want to do this in 1.6.x. Presumably that would mean if we >>>>>>> >>>>>> >>>>>> drop >>>>>> >>>>>>> >>>>>>> it in the next version, we'd still be supporting Hadoop 1 until both >>>>>>> 1.5 >>>>>>> and 1.6 have been EOLd? >>>>>>> >>>>>>> -Sean >>>>>>> >>>>>>> >>>>>>> On Fri, Apr 4, 2014 at 12:56 PM, Mike Drob <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>> HBase has started to drop hadoop 1 support already. >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Apr 4, 2014 at 10:54 AM, John Vines <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>> This is something that crossed my mind recently. Hadoop 2 is >>>>>>>>> solidly >>>>>>>>> >>>>>>>> >>>>>>>> moving >>>>>>>> >>>>>>>>> >>>>>>>>> forward and, as someone who does not actively follow the hadoop >>>>>>>>> >>>>>>>> >>>>>>>> community, >>>>>>>> >>>>>>>>> >>>>>>>>> hadoop 1 is slowing down. Adoption for hadoop2 is on the rise and >>>>>>>>> >>>>>>>> >>>>>> with >>>>>> >>>>>>> >>>>>>>> that >>>>>>>> >>>>>>>>> >>>>>>>>> I'm starting to wonder whether it's worth the code complexity to >>>>>>>>> >>>>>>>> >>>>>>> support >>>>>>> >>>>>>>> >>>>>>>>> both versions, particularly attempting to harness new features. >>>>>>>>> >>>>>>>>> What is the communities thought on this, maybe for 1.7 or maybe for >>>>>>>>> >>>>>>>> >>>>>>>> future >>>>>>>> >>>>>>>>> >>>>>>>>> releases? >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Sean >>>>>>> >>>>>>> >>>>>> >>>>> >>>> -- Sean
