Re: HADOOP-14163 proposal for new hadoop.apache.org
+1 looks good On Mon, 7 Aug 2017 at 16:23, Akira Ajisaka wrote: > Hi folks, > > I'd like to create a separate git repository for the web site (now managed > in svn). > For more details, please see the discussion in > https://issues.apache.org/jira/browse/HADOOP-14163. > > I'll ask INFRA to create a git repository if there are no objections. > > Thanks Marton Elek for the continuous work. > > Regards, > Akira > > On 2017/03/25 3:35, Andrew Wang wrote: > > Thanks again for working on this Marton! > > > > Based on my read of the blog post you linked, we should have the git > branch > > ready before asking infra to switch it over. > > > > I can do a more detailed review on the JIRA once you rev, and can help > with > > the INFRA ticket once it's ready. We'll also have to update BUILDING.txt > > and the wiki instructions as part of this. > > > > Best, > > Andrew > > > > On Fri, Mar 24, 2017 at 3:06 AM, Marton Elek > wrote: > > > >> > >> > >> Thank you all of the feedbacks, I fixed all of them (except one, see the > >> comment below) and updated the http://hadoop.anzix.net preview site. > >> > >> So the next steps: > >> > >> 0. Let me know if you have any comment about the latest version > >> > >> 1. I wait for the 2.8.0 announcement, and migrate the new announcement > as > >> well. (wouldn't like to complicate the 2.8.0 with the site change) > >> > >> 2. I like the suggestion of Owen to move the site to a specific git > >> branch. I wouldn't like to pending on it if it's too much time, but if > any > >> of the commiters could pick it up, I would wait for it. > >> > >> I tested it, and seems to be easy: > >> > >> git svn clone https://svn.apache.org/repos/asf/hadoop/common/site/main > >> cd main > >> git remote add elek g...@github.com:elek/hadoop.git > >> git push elek master:asf-site > >> > >> According to the blog entry, an INFRA issue should be opened (I guess > by a > >> commiter or maybe a pmc member): > >> > >> https://blogs.apache.org/infra/entry/git_based_websites_available > >> > >> 3. After that I can submit the new site as a regular patch against the > >> asf-site branch. > >> > >> 4. If it's merged, I can update the release wiki pages > >> > >> Marton > >> > >> ps: > >> > >> The only suggested item which is not implemented is the short version > >> names in the documentation menu (2.7 instead of 2.7.3). > >> > >> I think there are two forces: usability of the site and the simplicity > of > >> the site generation. Ideally a new release could be added to the site as > >> easy as possible (that was one of the motivation of the migration). > >> > >> While a new tag could be added to the header of the markdown files (eg: > >> versionLine: 3.0), it requires multiple files update during a new > release. > >> And if something would be missed, there could be displayed multiple > "2.7" > >> menu item (one for 2.7.3 and for 2.7.4). So the current method is not so > >> nice, but much more bug-safe. > >> > >> I prefer to keep the current/content in this step (if possible) and if > the > >> site is migrated we can submit new patches (hopefully against a git > branch) > >> in the normal way and further improve the site. > >> > >> > >> > >> From: Owen O'Malley > >> Sent: Monday, March 13, 2017 6:15 PM > >> To: Marton Elek > >> Cc: common-dev@hadoop.apache.org > >> Subject: Re: HADOOP-14163 proposal for new hadoop.apache.org > >> > >> Thanks for addressing this. Getting rid of Hadoop's use of forrest is a > >> good thing. > >> > >> In terms of content, the documentation links should be sorted by number > >> with only the latest from each minor release line (eg. 3.0, 2.7, 2.6). > >> > >> The download page points to the mirrors for checksums and signatures. It > >> should use the direct links, such as > >> > >> https://dist.apache.org/repos/dist/release/hadoop/common/ > >> hadoop-2.7.3/hadoop-2.7.3-src.tar.gz.asc > >> https://dist.apache.org/repos/dist/release/hadoop/common/ > >> hadoop-2.7.3/hadoop-2.7.3-src.tar.gz.mds > >> > >> Speaking of which, Hadoop's dist directory is huge and should be heavily > >> pruned. We should probably take it down to just hadoop-2.6.5, > hadoop-2.7.3, > >> and hadoop-3.0.0-alpha2. > >> > >> You might also want to move us to git-pubsub so that we can use a > branch in > >> our source code git repository to publish the html. Typically this uses > the > >> asf-site branch. > >> > >> .. Owen > >> > >> On Mon, Mar 13, 2017 at 7:28 AM, Marton Elek > >> wrote: > >> > >>> > >>> Hi, > >>> > >>> In the previous thread the current forrest based hadoop site is > >> identified > >>> as one of the pain points of the release process. > >>> > >>> I created a new version of the site with exactly the same content. > >>> > >>> As it uses newer site generator (hugo), now: > >>> > >>> 1. It’s enough to create one new markdown file per release, and all the > >>> documentation/download links will be automatically added. > >>> 2. It requires only one single
Re: HADOOP-14163 proposal for new hadoop.apache.org
+1. Looks really good. - Sunil On Mon, Sep 3, 2018 at 10:51 AM Vinayakumar B wrote: > +1, New site looks great. > > Just one nit in README > '--refresh' flag for hugo server no longer available. > > -Vinay > > On Mon, 3 Sep 2018, 10:21 am Shashikant Banerjee, < > sbaner...@hortonworks.com> > wrote: > > > +1 > > > > Thanks > > Shashi > > > > On 9/3/18, 9:23 AM, "Mukul Kumar Singh" wrote: > > > > +1, Thanks for working on this Marton. > > > > -Mukul > > > > On 03/09/18, 9:02 AM, "John Zhuge" wrote: > > > > +1 Like the new site. > > > > On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang > > wrote: > > > > > That's really nice, +1. > > > > > > -- > > > Weiwei > > > > > > On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan > > > wrote: > > > > > > > +1, thanks for working on this, Marton! > > > > > > > > Best, > > > > Wangda > > > > > > > > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal < > > aagar...@hortonworks.com > > > > > > > > wrote: > > > > > > > > > +1 > > > > > > > > > > Thanks for initiating this Marton. > > > > > > > > > > > > > > > On 8/31/18, 1:07 AM, "Elek, Marton" > wrote: > > > > > > > > > > Bumping this thread at last time. > > > > > > > > > > I have the following proposal: > > > > > > > > > > 1. I will request a new git repository hadoop-site.git > > and import > > > the > > > > > new site to there (which has exactly the same content > as > > the > > > existing > > > > > site). > > > > > > > > > > 2. I will ask infra to use the new repository as the > > source of > > > > > hadoop.apache.org > > > > > > > > > > 3. I will sync manually all of the changes in the next > > two months > > > > back > > > > > to the svn site from the git (release announcements, > new > > > committers) > > > > > > > > > > IN CASE OF ANY PROBLEM we can switch back to the svn > > without any > > > > > problem. > > > > > > > > > > If no-one objects within three days, I'll assume lazy > > consensus and > > > > > start with this plan. Please comment if you have > > objections. > > > > > > > > > > Again: it allows immediate fallback at any time as svn > > repo will be > > > > > kept > > > > > as is (+ I will keep it up-to-date in the next 2 > months) > > > > > > > > > > Thanks, > > > > > Marton > > > > > > > > > > > > > > > On 06/21/2018 09:00 PM, Elek, Marton wrote: > > > > > > > > > > > > Thank you very much to bump up this thread. > > > > > > > > > > > > > > > > > > About [2]: (Just for the clarification) the content > of > > the > > > proposed > > > > > > website is exactly the same as the old one. > > > > > > > > > > > > About [1]. I believe that the "mvn site" is perfect > > for the > > > > > > documentation but for website creation there are more > > simple and > > > > > > powerful tools. > > > > > > > > > > > > Hugo has more simple compared to jekyll. Just one > > binary, without > > > > > > dependencies, works everywhere (mac, linux, windows) > > > > > > > > > > > > Hugo has much more powerful compared to "mvn site". > > Easier to > > > > > create/use > > > > > > more modern layout/theme, and easier to handle the > > content (for > > > > > example > > > > > > new release announcements could be generated as part > > of the > > > release > > > > > > process) > > > > > > > > > > > > I think it's very low risk to try out a new approach > > for the site > > > > > (and > > > > > > easy to rollback in case of problems) > > > > > > > > > > > > Marton > > > > > > > > > > > > ps: I just updated the patch/preview site with the > > recent > > > releases: > > > > > > > > > > > > *** > > > > > > * http://hadoop.anzix.net * > > > > > > *** > > > > > > > > > > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli > wrote: > > > > > >> Got pinged about this offline. > > > > > >> > > > > > >> Thanks for keeping at it, Marton! > > > > > >> > > > > > >> I think there are two road-blocks here > > > > > >> (1) Is the mechanism using which the website is > > built good > > > >
Re: HADOOP-14163 proposal for new hadoop.apache.org
+1, New site looks great. Just one nit in README '--refresh' flag for hugo server no longer available. -Vinay On Mon, 3 Sep 2018, 10:21 am Shashikant Banerjee, wrote: > +1 > > Thanks > Shashi > > On 9/3/18, 9:23 AM, "Mukul Kumar Singh" wrote: > > +1, Thanks for working on this Marton. > > -Mukul > > On 03/09/18, 9:02 AM, "John Zhuge" wrote: > > +1 Like the new site. > > On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang > wrote: > > > That's really nice, +1. > > > > -- > > Weiwei > > > > On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan > wrote: > > > > > +1, thanks for working on this, Marton! > > > > > > Best, > > > Wangda > > > > > > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal < > aagar...@hortonworks.com > > > > > > wrote: > > > > > > > +1 > > > > > > > > Thanks for initiating this Marton. > > > > > > > > > > > > On 8/31/18, 1:07 AM, "Elek, Marton" wrote: > > > > > > > > Bumping this thread at last time. > > > > > > > > I have the following proposal: > > > > > > > > 1. I will request a new git repository hadoop-site.git > and import > > the > > > > new site to there (which has exactly the same content as > the > > existing > > > > site). > > > > > > > > 2. I will ask infra to use the new repository as the > source of > > > > hadoop.apache.org > > > > > > > > 3. I will sync manually all of the changes in the next > two months > > > back > > > > to the svn site from the git (release announcements, new > > committers) > > > > > > > > IN CASE OF ANY PROBLEM we can switch back to the svn > without any > > > > problem. > > > > > > > > If no-one objects within three days, I'll assume lazy > consensus and > > > > start with this plan. Please comment if you have > objections. > > > > > > > > Again: it allows immediate fallback at any time as svn > repo will be > > > > kept > > > > as is (+ I will keep it up-to-date in the next 2 months) > > > > > > > > Thanks, > > > > Marton > > > > > > > > > > > > On 06/21/2018 09:00 PM, Elek, Marton wrote: > > > > > > > > > > Thank you very much to bump up this thread. > > > > > > > > > > > > > > > About [2]: (Just for the clarification) the content of > the > > proposed > > > > > website is exactly the same as the old one. > > > > > > > > > > About [1]. I believe that the "mvn site" is perfect > for the > > > > > documentation but for website creation there are more > simple and > > > > > powerful tools. > > > > > > > > > > Hugo has more simple compared to jekyll. Just one > binary, without > > > > > dependencies, works everywhere (mac, linux, windows) > > > > > > > > > > Hugo has much more powerful compared to "mvn site". > Easier to > > > > create/use > > > > > more modern layout/theme, and easier to handle the > content (for > > > > example > > > > > new release announcements could be generated as part > of the > > release > > > > > process) > > > > > > > > > > I think it's very low risk to try out a new approach > for the site > > > > (and > > > > > easy to rollback in case of problems) > > > > > > > > > > Marton > > > > > > > > > > ps: I just updated the patch/preview site with the > recent > > releases: > > > > > > > > > > *** > > > > > * http://hadoop.anzix.net * > > > > > *** > > > > > > > > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote: > > > > >> Got pinged about this offline. > > > > >> > > > > >> Thanks for keeping at it, Marton! > > > > >> > > > > >> I think there are two road-blocks here > > > > >> (1) Is the mechanism using which the website is > built good > > > enough > > > > - > > > > >> mvn-site / hugo etc? > > > > >> (2) Is the new website good enough? > > > > >> > > > > >> For (1), I just think we need more committer > attention and get > > > > >> feedback rapidly and get it in. > > > > >> > > > > >> For (2), how about we do it in a different way in the > interest > > of >
Re: HADOOP-14163 proposal for new hadoop.apache.org
+1 Thanks Shashi On 9/3/18, 9:23 AM, "Mukul Kumar Singh" wrote: +1, Thanks for working on this Marton. -Mukul On 03/09/18, 9:02 AM, "John Zhuge" wrote: +1 Like the new site. On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang wrote: > That's really nice, +1. > > -- > Weiwei > > On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan wrote: > > > +1, thanks for working on this, Marton! > > > > Best, > > Wangda > > > > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal > > > wrote: > > > > > +1 > > > > > > Thanks for initiating this Marton. > > > > > > > > > On 8/31/18, 1:07 AM, "Elek, Marton" wrote: > > > > > > Bumping this thread at last time. > > > > > > I have the following proposal: > > > > > > 1. I will request a new git repository hadoop-site.git and import > the > > > new site to there (which has exactly the same content as the > existing > > > site). > > > > > > 2. I will ask infra to use the new repository as the source of > > > hadoop.apache.org > > > > > > 3. I will sync manually all of the changes in the next two months > > back > > > to the svn site from the git (release announcements, new > committers) > > > > > > IN CASE OF ANY PROBLEM we can switch back to the svn without any > > > problem. > > > > > > If no-one objects within three days, I'll assume lazy consensus and > > > start with this plan. Please comment if you have objections. > > > > > > Again: it allows immediate fallback at any time as svn repo will be > > > kept > > > as is (+ I will keep it up-to-date in the next 2 months) > > > > > > Thanks, > > > Marton > > > > > > > > > On 06/21/2018 09:00 PM, Elek, Marton wrote: > > > > > > > > Thank you very much to bump up this thread. > > > > > > > > > > > > About [2]: (Just for the clarification) the content of the > proposed > > > > website is exactly the same as the old one. > > > > > > > > About [1]. I believe that the "mvn site" is perfect for the > > > > documentation but for website creation there are more simple and > > > > powerful tools. > > > > > > > > Hugo has more simple compared to jekyll. Just one binary, without > > > > dependencies, works everywhere (mac, linux, windows) > > > > > > > > Hugo has much more powerful compared to "mvn site". Easier to > > > create/use > > > > more modern layout/theme, and easier to handle the content (for > > > example > > > > new release announcements could be generated as part of the > release > > > > process) > > > > > > > > I think it's very low risk to try out a new approach for the site > > > (and > > > > easy to rollback in case of problems) > > > > > > > > Marton > > > > > > > > ps: I just updated the patch/preview site with the recent > releases: > > > > > > > > *** > > > > * http://hadoop.anzix.net * > > > > *** > > > > > > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote: > > > >> Got pinged about this offline. > > > >> > > > >> Thanks for keeping at it, Marton! > > > >> > > > >> I think there are two road-blocks here > > > >> (1) Is the mechanism using which the website is built good > > enough > > > - > > > >> mvn-site / hugo etc? > > > >> (2) Is the new website good enough? > > > >> > > > >> For (1), I just think we need more committer attention and get > > > >> feedback rapidly and get it in. > > > >> > > > >> For (2), how about we do it in a different way in the interest > of > > > >> progress? > > > >> - We create a hadoop.apache.org/new-site/ where this new site > > > goes. > > > >> - We then modify the existing web-site to say that there is a > > new > > > >> site/experience that folks can click on a link and navigate to > > > >> - As this new website matures and gets feedback & fixes, we > > > finally > > > >> pull the
Re: HADOOP-14163 proposal for new hadoop.apache.org
+1, Thanks for working on this Marton. -Mukul On 03/09/18, 9:02 AM, "John Zhuge" wrote: +1 Like the new site. On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang wrote: > That's really nice, +1. > > -- > Weiwei > > On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan wrote: > > > +1, thanks for working on this, Marton! > > > > Best, > > Wangda > > > > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal > > > wrote: > > > > > +1 > > > > > > Thanks for initiating this Marton. > > > > > > > > > On 8/31/18, 1:07 AM, "Elek, Marton" wrote: > > > > > > Bumping this thread at last time. > > > > > > I have the following proposal: > > > > > > 1. I will request a new git repository hadoop-site.git and import > the > > > new site to there (which has exactly the same content as the > existing > > > site). > > > > > > 2. I will ask infra to use the new repository as the source of > > > hadoop.apache.org > > > > > > 3. I will sync manually all of the changes in the next two months > > back > > > to the svn site from the git (release announcements, new > committers) > > > > > > IN CASE OF ANY PROBLEM we can switch back to the svn without any > > > problem. > > > > > > If no-one objects within three days, I'll assume lazy consensus and > > > start with this plan. Please comment if you have objections. > > > > > > Again: it allows immediate fallback at any time as svn repo will be > > > kept > > > as is (+ I will keep it up-to-date in the next 2 months) > > > > > > Thanks, > > > Marton > > > > > > > > > On 06/21/2018 09:00 PM, Elek, Marton wrote: > > > > > > > > Thank you very much to bump up this thread. > > > > > > > > > > > > About [2]: (Just for the clarification) the content of the > proposed > > > > website is exactly the same as the old one. > > > > > > > > About [1]. I believe that the "mvn site" is perfect for the > > > > documentation but for website creation there are more simple and > > > > powerful tools. > > > > > > > > Hugo has more simple compared to jekyll. Just one binary, without > > > > dependencies, works everywhere (mac, linux, windows) > > > > > > > > Hugo has much more powerful compared to "mvn site". Easier to > > > create/use > > > > more modern layout/theme, and easier to handle the content (for > > > example > > > > new release announcements could be generated as part of the > release > > > > process) > > > > > > > > I think it's very low risk to try out a new approach for the site > > > (and > > > > easy to rollback in case of problems) > > > > > > > > Marton > > > > > > > > ps: I just updated the patch/preview site with the recent > releases: > > > > > > > > *** > > > > * http://hadoop.anzix.net * > > > > *** > > > > > > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote: > > > >> Got pinged about this offline. > > > >> > > > >> Thanks for keeping at it, Marton! > > > >> > > > >> I think there are two road-blocks here > > > >> (1) Is the mechanism using which the website is built good > > enough > > > - > > > >> mvn-site / hugo etc? > > > >> (2) Is the new website good enough? > > > >> > > > >> For (1), I just think we need more committer attention and get > > > >> feedback rapidly and get it in. > > > >> > > > >> For (2), how about we do it in a different way in the interest > of > > > >> progress? > > > >> - We create a hadoop.apache.org/new-site/ where this new site > > > goes. > > > >> - We then modify the existing web-site to say that there is a > > new > > > >> site/experience that folks can click on a link and navigate to > > > >> - As this new website matures and gets feedback & fixes, we > > > finally > > > >> pull the plug at a later point of time when we think we are good > > to > > > go. > > > >> > > > >> Thoughts? > > > >> > > > >> +Vinod > > > >> > > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton > > wrote: > > > >>> > > > >>> Hi, > > > >>> > > > >>> I would like to bump this thread up. > > > >>> > > > >>> TLDR; There is a proposed version of a new hadoop site which is > > > >>> available from here: > > https://elek.github.io/hadoop-site-proposal/ > > > and > > >
Re: HADOOP-14163 proposal for new hadoop.apache.org
+1 Like the new site. On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang wrote: > That's really nice, +1. > > -- > Weiwei > > On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan wrote: > > > +1, thanks for working on this, Marton! > > > > Best, > > Wangda > > > > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal > > > wrote: > > > > > +1 > > > > > > Thanks for initiating this Marton. > > > > > > > > > On 8/31/18, 1:07 AM, "Elek, Marton" wrote: > > > > > > Bumping this thread at last time. > > > > > > I have the following proposal: > > > > > > 1. I will request a new git repository hadoop-site.git and import > the > > > new site to there (which has exactly the same content as the > existing > > > site). > > > > > > 2. I will ask infra to use the new repository as the source of > > > hadoop.apache.org > > > > > > 3. I will sync manually all of the changes in the next two months > > back > > > to the svn site from the git (release announcements, new > committers) > > > > > > IN CASE OF ANY PROBLEM we can switch back to the svn without any > > > problem. > > > > > > If no-one objects within three days, I'll assume lazy consensus and > > > start with this plan. Please comment if you have objections. > > > > > > Again: it allows immediate fallback at any time as svn repo will be > > > kept > > > as is (+ I will keep it up-to-date in the next 2 months) > > > > > > Thanks, > > > Marton > > > > > > > > > On 06/21/2018 09:00 PM, Elek, Marton wrote: > > > > > > > > Thank you very much to bump up this thread. > > > > > > > > > > > > About [2]: (Just for the clarification) the content of the > proposed > > > > website is exactly the same as the old one. > > > > > > > > About [1]. I believe that the "mvn site" is perfect for the > > > > documentation but for website creation there are more simple and > > > > powerful tools. > > > > > > > > Hugo has more simple compared to jekyll. Just one binary, without > > > > dependencies, works everywhere (mac, linux, windows) > > > > > > > > Hugo has much more powerful compared to "mvn site". Easier to > > > create/use > > > > more modern layout/theme, and easier to handle the content (for > > > example > > > > new release announcements could be generated as part of the > release > > > > process) > > > > > > > > I think it's very low risk to try out a new approach for the site > > > (and > > > > easy to rollback in case of problems) > > > > > > > > Marton > > > > > > > > ps: I just updated the patch/preview site with the recent > releases: > > > > > > > > *** > > > > * http://hadoop.anzix.net * > > > > *** > > > > > > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote: > > > >> Got pinged about this offline. > > > >> > > > >> Thanks for keeping at it, Marton! > > > >> > > > >> I think there are two road-blocks here > > > >> (1) Is the mechanism using which the website is built good > > enough > > > - > > > >> mvn-site / hugo etc? > > > >> (2) Is the new website good enough? > > > >> > > > >> For (1), I just think we need more committer attention and get > > > >> feedback rapidly and get it in. > > > >> > > > >> For (2), how about we do it in a different way in the interest > of > > > >> progress? > > > >> - We create a hadoop.apache.org/new-site/ where this new site > > > goes. > > > >> - We then modify the existing web-site to say that there is a > > new > > > >> site/experience that folks can click on a link and navigate to > > > >> - As this new website matures and gets feedback & fixes, we > > > finally > > > >> pull the plug at a later point of time when we think we are good > > to > > > go. > > > >> > > > >> Thoughts? > > > >> > > > >> +Vinod > > > >> > > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton > > wrote: > > > >>> > > > >>> Hi, > > > >>> > > > >>> I would like to bump this thread up. > > > >>> > > > >>> TLDR; There is a proposed version of a new hadoop site which is > > > >>> available from here: > > https://elek.github.io/hadoop-site-proposal/ > > > and > > > >>> https://issues.apache.org/jira/browse/HADOOP-14163 > > > >>> > > > >>> Please let me know what you think about it. > > > >>> > > > >>> > > > >>> Longer version: > > > >>> > > > >>> This thread started long time ago to use a more modern hadoop > > site: > > > >>> > > > >>> Goals were: > > > >>> > > > >>> 1. To make it easier to manage it (the release entries could be > > > >>> created by a script as part of the release process) > > > >>> 2. To use a better look-and-feel > > > >>> 3. Move it out from svn to git > > > >>> > > > >>> I proposed to: > > > >>> > > > >>> 1. Move
[jira] [Resolved] (HADOOP-11688) Implement a native library version of IdMappingServiceProvider
[ https://issues.apache.org/jira/browse/HADOOP-11688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-11688. --- Resolution: Won't Fix > Implement a native library version of IdMappingServiceProvider > -- > > Key: HADOOP-11688 > URL: https://issues.apache.org/jira/browse/HADOOP-11688 > Project: Hadoop Common > Issue Type: New Feature >Reporter: Allen Wittenauer >Priority: Major > > There should be a native library version of a IdMappingServiceProvider, > especially since most of the requested functionality already exists. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
