hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wilm Schumacher <wilm.schumac...@gmail.com>
Subject Re: Fwd: data base design question
Date Fri, 13 Feb 2015 13:56:32 GMT
Hi,

Am 13.02.2015 um 04:08 schrieb Jignesh Patel:
> How about Option 1: Create an embedded entity of results and store it as
> list object inside order table as one of the column field.
the problem is, that a hbase cell value must be a byte array. Thus you
have to convert the "list object" to a byte array. One option could be
e.g. the json representation.

But now, when you want to look at the results for one order you have to
parse the e.g. json array. If you have to do that over and over again
you produce very high CPU costs. If the main task of your application is
to show or manipulate the results your main task on server side is to
parse and create json strings. This gets more and more problematic as
the number of results per order grow.

Another point is that by this design you cannot address a result directly.

But in the end: your plan would work. But there are some problems with that.

Best wishes

Wilm



Mime
View raw message