Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@accumulo.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: "Perko, Ralph J" <Ralph.Perko@pnnl.gov>
To: "user@accumulo.apache.org" <user@accumulo.apache.org>
Date: Wed, 6 Jun 2012 13:46:30 -0700
Subject: Table design
Thread-Topic: Table design
Thread-Index: Ac1EJY5Jq8exG8gXSaW+MW7znyNYQA==
Message-ID: <CBF50FB5.3119%ralph.perko@pnnl.gov>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.2.120421
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi,  I am in the process of designing some Accumulo tables for an app and h=
ave some questions:

Lookup Table:
The data's natural qualifier is a title.  This title can be any length.  So=
me are as long as 200 characters.
I am using this title as a row id and also as a column qualifier in other p=
laces.
Is it considered good practice to have a lookup table for these titles (lik=
e RDBMS), replacing them with some incremented integer value, or should I j=
ust continue to use these long titles as row ids?

Multiple Tables:
What are the best practices around when to create a new table?  I have been=
 breaking up my tables based on row id semantics.  For example, title row i=
ds are in a different table than row ids based on some analysis count.
Does breaking up data into multiple tables, help/hurt/ or do nothing for ac=
cumulo performance?

Thanks,
Ralph
__________________________________________________
Ralph Perko
Pacific Northwest National Laboratory