Back in 2006 we became aware of problems storing large numbers of
rows in a single table in cluster. Johan Andersson and Yves
Trudeau have each blogged about the problem and the common
workaround here and here.
We've since then done some cleanup to provide a more proper
"Table is full" error message when running into this
As explained in the referenced blog posts, the problem is the result of a limitation on the size of the hash index of each …