Thanks for the http://blog.csdn.net/macyang/article/details/6425628 pointer. Regarding the JIRA, I presume that the old reference for the hbaseblog will be changed by some updated location/content. I have also checked the 0.92 documentation from a link you previously posted http://people.apache.org/~stack/hbase-0.92.0-candidate-2/, beside few properties of co-processor I don't see any documentation on this feature, is it intended? I mean the HFile V2 is quite documented, should it be the same for major HBase feature/functionality?
BTW for getting an in development version build, should I searching the mailing list (you posted such email few days ago from which i took the link above)? Don't you intend to have in the download area of the site a directory for RC version? Is there another way? Thanks Mikael.S On Tue, Dec 27, 2011 at 7:07 AM, Stack <[email protected]> wrote: > I found the 'text' for Mingjie's CP blog here: > http://blog.csdn.net/macyang/article/details/6425628. We should wrap > this into the manual before it disappears. The Internet Archive has > the hbaseblog.com homepage and a few of the articles we had posted > there: http://web.archive.org/web/20110207202749/http://hbaseblog.com/ > (but not CP article of course but we should roll in Gary's article on > Security too?). > > St.Ack > > > On Mon, Dec 26, 2011 at 3:52 PM, Stack <[email protected]> wrote: > > On Sun, Dec 25, 2011 at 2:29 AM, Mikael Sitruk <[email protected]> > wrote: > >> I also saw the hbaseblog.com referenced in JIRA, especially when I was > >> looking for coprocessor documentation/design and was unable to find > >> something. > >> So first is there an "official" place to get coprocessor documentation > >> (design, usage)? > >> > > > > The 'design' is up in the JIRAs. > > > > The high-level overview and some usage was up on hbaseblog (Mingjie, > > do you have the original content? Perhaps we could rehydrate your > > articles as content in hbase book?) > > > >> Generally (and please do not understand me wrong - I'm not criticizing > >> anyone) > > > > We ain't so sensitive that you need to preface your remarks so Mikael > (smile). > > > >> shouldn't development document, architecture design be in the > >> wiki/official hbase site instead of pointers to external blog, or in > JIRA? > > > > Yes. > > > > IIRC, it was done as wiki article before it was committed to code-base. > > > >> Last, don't you think that there should be different documentation pages > >> for different version of HBase, like it is done for hadoop, or pig? > >> > > > > Again yes. There is version documentation that ships with each hbase > > release and then there is keeping these versions up on the website. > > Its the latter to which I believe you refer. > > > > We used do this keeping all versions of api doc up on the website. > > After the switch to maven where we started to use it to generate our > > site, we got lazy about keeping up old versions; rare did we change > > major versions so it mattered little. Around the same time as our > > switch to maven, we moved to use docbook instead of xdoc+wiki keeping > > up our documentation. We've been busy back-filling out the reference > > guide -- well, Doug has mostly -- with explanation and for the most > > part its been non-version specific, or rather its all been about > > version 0.90.x HBase, but that is starting to change now that 0.92.0 > > is looming. For 0.92.x specifics we've been adding 'since version > > X.X.X' above the sections that are 0.92.x particular. This will start > > to breakdown as the versions diverge. > > > > We'll do a better job going forward. > > > > St.Ack > > St.Ack > -- Mikael.S
