Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Date: Tue, 6 Oct 2015 16:56:20 -0700 (MST)
From: z11373 <z11373@outlook.com>
To: dev@accumulo.apache.org
Message-ID: <1444175780356-15328.post@n5.nabble.com>
In-Reply-To: <56141F85.8050007@gmail.com>
References: <1443560577203-15286.post@n5.nabble.com>
 <CAGUtCHqz+FfiahvzOpFJh-A=qvN24-y+MKMFrtjtM8ogBfEo5g@mail.gmail.com>
 <1443635776808-15296.post@n5.nabble.com>
 <CAGUtCHrcWKLXwaMLWHwdpAQVWxoo+92WD7_uyMeZnhLP2g5kVw@mail.gmail.com>
 <1443713212233-15302.post@n5.nabble.com> <560D55F6.9060008@gmail.com>
 <1444058716385-15320.post@n5.nabble.com>
 <CAOyNEs7kE1M1uq=0eq0TF_G8AWnjy=eB9R_AXYBVmOrg10O1Xg@mail.gmail.com>
 <1444085846345-15324.post@n5.nabble.com> <56141F85.8050007@gmail.com>
Subject: Re: scan command hung
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Josh,
Thanks for the reply and the explanation. It does make sense indeed, in fact
I was thinking the same yesterday after playing with it more via shell. The
reason I came up with current design is mostly because it's convenient and
satisfy our needs. However, what works doesn't mean it is the right thing to
do :-)

I think the option #1 you suggested will work, i.e. embed that customer id
as part of the row id.
For option #2 (i.e. using second table as index), the same row id value can
belong to different customer id, which means I have to embed the customer id
to the row id to make it unique, which also means it's same as option #1,
hence no need second table.


Thanks,
Z


--
View this message in context: http://apache-accumulo.1065345.n5.nabble.com/scan-command-hung-tp15286p15328.html
Sent from the Developers mailing list archive at Nabble.com.