I have a family which contains an array, or list, of values. I don't mind whether it is an array or a list or even an arraylist :) At the moment I have gone down the quick and dirty route of serializing my list into one column. While functionally this works sufficiently well to allow me to keep developing my app this does not seem an appropriate solution for HBase based persistence as the column could grow to be a significant size. My (limited) understanding of Hbase is that it is great for tables with lots of rows and also for rows with lots of columns. Having one column with lots of data (i.e. one huge column in each row) does not seem the greatest idea to me.
Any suggestions as to how I should approach this would be great. Many thanks. -- View this message in context: http://www.nabble.com/Best-practice-design-query-for-storing-a-list-array-of-values-tp25530827p25530827.html Sent from the HBase User mailing list archive at Nabble.com.
