I have started designing a data model/schema for a new application that will use Accumulo as data storage. I am looking for a good way to document my model in a way that makes it understandable for other developers that will use the same data in the future.

Does anybody here have good experience how to do it?

My first thought was using a spreadsheet just listing and describe the combinations of Family, Qualifier and requirements on the values.

Even though this is not an Accumulo, but HBase related presentation Irecommend reviewing it.HBase, Cassandra and Accumulo are all based on BigTable design andlots of best practices apply - speciallybetween HBase and Accumulo:

On Thu, Aug 16, 2012 at 1:53 PM, Magnus Runesson <[EMAIL PROTECTED]> wrote:> I have started designing a data model/schema for a new application that will> use Accumulo as data storage. I am looking for a good way to document my> model in a way that makes it understandable for other developers that will> use the same data in the future.>> Does anybody here have good experience how to do it?>> My first thought was using a spreadsheet just listing and describe the> combinations of Family, Qualifier and requirements on the values.>> Regards,> /Magnus

> I have started designing a data model/schema for a new application that> will use Accumulo as data storage. I am looking for a good way to document> my model in a way that makes it understandable for other developers that> will use the same data in the future.>> Does anybody here have good experience how to do it?>> My first thought was using a spreadsheet just listing and describe the> combinations of Family, Qualifier and requirements on the values.>> Regards,> /Magnus>

On Thu, Aug 16, 2012 at 2:54 PM, Billie Rinaldi <[EMAIL PROTECTED]> wrote:> On Thu, Aug 16, 2012 at 1:53 PM, Magnus Runesson <[EMAIL PROTECTED]>> wrote:>>>> I have started designing a data model/schema for a new application that>> will use Accumulo as data storage. I am looking for a good way to document>> my model in a way that makes it understandable for other developers that>> will use the same data in the future.>>>> Does anybody here have good experience how to do it?>>>> My first thought was using a spreadsheet just listing and describe the>> combinations of Family, Qualifier and requirements on the values.>>>> Regards,>> /Magnus>>> There are a couple of different representations in these slides:> http://people.apache.org/~afuchs/slides/accumulo_table_design.pdf> The hierarchical method can provide additional clarity when used alongside> the spreadsheet method.>> Billie

> On Thu, Aug 16, 2012 at 2:54 PM, Billie Rinaldi <[EMAIL PROTECTED]> wrote:> > On Thu, Aug 16, 2012 at 1:53 PM, Magnus Runesson <[EMAIL PROTECTED]>> > wrote:> >>> >> I have started designing a data model/schema for a new application that> >> will use Accumulo as data storage. I am looking for a good way to> document> >> my model in a way that makes it understandable for other developers that> >> will use the same data in the future.> >>> >> Does anybody here have good experience how to do it?> >>> >> My first thought was using a spreadsheet just listing and describe the> >> combinations of Family, Qualifier and requirements on the values.> >>> >> Regards,> >> /Magnus> >> >> > There are a couple of different representations in these slides:> > http://people.apache.org/~afuchs/slides/accumulo_table_design.pdf> > The hierarchical method can provide additional clarity when used> alongside> > the spreadsheet method.> >> > Billie>

On 2012-08-16 20:37, Edmon Begoli wrote:> Hi Magnus,>> Even though this is not an Accumulo, but HBase related presentation I> recommend reviewing it.> HBase, Cassandra and Accumulo are all based on BigTable design and> lots of best practices apply - specially> between HBase and Accumulo:>> http://www.cloudera.com/resource/hadoop-world-2011-presentation-slides-advanced-hbase-schema-design/>> Best regards,> Edmon>> On Thu, Aug 16, 2012 at 1:53 PM, Magnus Runesson <[EMAIL PROTECTED]> wrote:>> I have started designing a data model/schema for a new application that will>> use Accumulo as data storage. I am looking for a good way to document my>> model in a way that makes it understandable for other developers that will>> use the same data in the future.>>>> Does anybody here have good experience how to do it?>>>> My first thought was using a spreadsheet just listing and describe the>> combinations of Family, Qualifier and requirements on the values.>>>> Regards,>> /Magnus

NEW: Monitor These Apps!

All projects made searchable here are trademarks of the Apache Software Foundation.
Service operated by Sematext