On Fri, Jan 7, 2011 at 10:01 AM, Chris Tarnas <[email protected]> wrote:

> I was wondering how much impact on read and write performance a column
> family would have on rows where they don't contain any data?
>
> I'm testing out an indexing method where rather than have a separate table
> for storing indexes I just keep them in the same table in an INDEX column
> family. The construction of the rowkeys guarantees that an index value will
> never be the same as a rowkey of a normal row. This allows us to send all
> mutations for one row and its indexes in a single thrift call with a batch
> mutation rather than two thrift calls. Are there any serious back end
> downsides to this methodology?
>

How are you going to guarantee transaction of updating the actual
data row and the index row? Do you update them together in a putlist so that
you guarantee transaction?

Maybe It would be beneficial if you provide details and ask people to give
improvement suggestion.




>
> many thanks,
> -chris




-- 
--Sean

Reply via email to