Hi Doğacan, Thanks for the update.
> While I agree with the "table per fetch" issue, I would like to postpone it > until after the merge. This issue is tricky for a couple of reasons. For > example, AFAIK, cassandra's latest released version > does not support live schema updates so you can not add/delete tables on a > running cassandra machine. I guess we can use super columns as our tables, > then use columns to store > data but that may be sub-optimal. > Interesting point. OK with your suggestion to postpone it and port the trunk to GORA after we managed to get nutchbase to work with the SQL backend. My assumption was that this was doable with all the backends as-is but since it's not the case it's better to move on and come back to it later. As AB also pointed out earlier in the discussion we'd need to measure the performance impact of the 'table per fetch' compared to the current design, which we could do using Hbase a bit later. Thanks J. -- DigitalPebble Ltd Open Source Solutions for Text Engineering http://www.digitalpebble.com
