@Ted - awesome, I can edit now (havent tried saving anything yet though). @Andrew, @Stack - no worries, we can put it into the book, whatever works. I can make it plain-text if needed. Some of the stuff will be long-lived (architecture, etc) and some will change with the versions (the scripts and the params, etc).
@Doug - That works, thanks for the pointer. How do I put stuff into the book? Is html code for the book in the svn repo somewhere? If its easier as text in a jira or ms-word doc, that works too. On 10/19/11 3:38 PM, "Stack" <[email protected]> wrote: >On Wed, Oct 19, 2011 at 8:34 AM, Karthik Ranganathan ><[email protected]> wrote: >> There seemed to be a fair amount of interest in the Hbase backup >>solution, so I created HBASE-4618 as an umbrella task for figuring out >>how to opensource the backup solution we are building internally, and >>continue building the rest of it in opensource itself. >> > >Sweet. > >> One small question: There is a fair bit of definitions, architecture >>overview, setup instructions, etc that we put in an internal wikiŠ >>wondering what is a good place to put them? The purpose of this is for >>people newly wanting to investigate Hbase backups (what they are, how to >>setup, etc) as well as a reference location for people who already know >>about Hbase backups but want to lookup the steps to set them up. Javadoc >>may not be the ideal location for this. >> > >What are the export options on your wiki Karthick? If plain text or >xml or something structured -- even msword -- we can hack it into >docbook with find/replace/openoffice, etc (I volunteer). As Doug >says, we've been trying to get stuff into the book rather than up on >wiki; wiki for transient stuff, book for stuff we need to keep up with >the releases. > >Good stuff, >St.Ack
