Sure. Optimization is for later.
(just to be sure, the limitation is on the 'column family', not on the
'column')
Just tell us if you need help to progress on the integration tests.
Maybe you could have more unit tests that will help you assess the
functionality is correctly implemented: e.g. save two messages, count
must return 2.
Thx.
On 17/08/11 16:18, Ioan Eugen Stan wrote:
2011/8/17 Eric Charles<e...@apache.org>:
Hi Ioan,
Didn't jump to my eyes reading the code, but schema showed clearly showed
it.
HBase is known to outperform for with many column families per table
(http://hbase.apache.org/book/number.of.cfs.html), and you are using 5
column families in the Messages table.
I remind from HBase mailing list, max 2 column families per table, and even
1 if there is no strong reason for more.
I know. I have a TODO for reducing the number of column. It's in
HBaseSessionMapper. I can reduce the Messages table to 3 columns easy,
probably 2 if I scratch my head, but I want to pass the integration
tests before I get serious with performance issues.
I think I'm making some progress here, but it's kind of slow.
--
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
