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: domain of jej2003@gmail.com designates
 209.85.219.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAL5zq9Zn2qWKGRMqCVKgN-Zfbsobpk6wbgmHL5ZAuBU57EUq+g@mail.gmail.com>
References: 
 <CAL3VrCe4TgYBYQE9_iR=CDjeJSwKmdP6Nerp_6GvZFy4hV=ULA@mail.gmail.com>
	<CAL5zq9Zn2qWKGRMqCVKgN-Zfbsobpk6wbgmHL5ZAuBU57EUq+g@mail.gmail.com>
Date: Sun, 26 Jan 2014 08:11:33 -0500
Message-ID: 
 <CAL3VrCevLDj4ge1t=+cCZqmnwMVdxA5pttTJijDrJexU+=2pKQ@mail.gmail.com>
Subject: Re: Key length limitations
From: Jamie Johnson <jej2003@gmail.com>
To: user@accumulo.apache.org
Content-Type: multipart/alternative; boundary=089e013a18228cfe9c04f0df548f

--089e013a18228cfe9c04f0df548f
Content-Type: text/plain; charset=ISO-8859-1

Sorry for the basic question, but by key segment do you mean row key,
column family column qualifier?  So each should be less than a kilobyte or
total?  I think either way we are below that but I just want to make sure I
understand the terminology.  Again thanks for the reply.


On Sun, Jan 26, 2014 at 2:12 AM, Christopher <ctubbsii@apache.org> wrote:

> On the order of a kilobyte, or less, per key segment is probably
> ideal. Beyond that, you may want to experiment to see what works for
> you.
>
> Up to the order of a megabyte may work fine in newer versions (at
> least 1.4), but I'd start having concerns about your schema decisions
> after that, even if your performance was fine... since ultimately,
> Accumulo tables are a sorted index, and I'd wonder what kind of index
> needs such large keys.
>
> I suspect a few hundred bytes is probably plenty for most applications.
>
> --
> Christopher L Tubbs II
> http://gravatar.com/ctubbsii
>
>
> On Sat, Jan 25, 2014 at 9:06 AM, Jamie Johnson <jej2003@gmail.com> wrote:
> > I've read that in HBase there is a recommended limit on key lengths
> because
> > they're passed around quite a bit. Is the same true of accumulo?  Are
> there
> > any recommendations in this regard?
>

--089e013a18228cfe9c04f0df548f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Sorry for the basic question, but by key segment do you me=
an row key, column family column qualifier? =A0So each should be less than =
a kilobyte or total? =A0I think either way we are below that but I just wan=
t to make sure I understand the terminology. =A0Again thanks for the reply.=
</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sun, Jan 2=
6, 2014 at 2:12 AM, Christopher <span dir=3D"ltr">&lt;<a href=3D"mailto:ctu=
bbsii@apache.org" target=3D"_blank">ctubbsii@apache.org</a>&gt;</span> wrot=
e:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On the order of a kilobyte, or less, per key=
 segment is probably<br>
ideal. Beyond that, you may want to experiment to see what works for<br>
you.<br>
<br>
Up to the order of a megabyte may work fine in newer versions (at<br>
least 1.4), but I&#39;d start having concerns about your schema decisions<b=
r>
after that, even if your performance was fine... since ultimately,<br>
Accumulo tables are a sorted index, and I&#39;d wonder what kind of index<b=
r>
needs such large keys.<br>
<br>
I suspect a few hundred bytes is probably plenty for most applications.<br>
<br>
--<br>
Christopher L Tubbs II<br>
<a href=3D"http://gravatar.com/ctubbsii" target=3D"_blank">http://gravatar.=
com/ctubbsii</a><br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On Sat, Jan 25, 2014 at 9:06 AM, Jamie Johnson &lt;<a href=3D"mailto:jej200=
3@gmail.com">jej2003@gmail.com</a>&gt; wrote:<br>
&gt; I&#39;ve read that in HBase there is a recommended limit on key length=
s because<br>
&gt; they&#39;re passed around quite a bit. Is the same true of accumulo? =
=A0Are there<br>
&gt; any recommendations in this regard?<br>
</div></div></blockquote></div><br></div>

--089e013a18228cfe9c04f0df548f--