Possibly heading into wishlist rather than practical territory here, but you did ask...
> What we need is to introduce an interface which will convert a pair of > key-value objects into a row. This row will be used to store data and to > get fields from it. Rather than mapping objects to a row, how about mapping to a more general “internal storage” interface? Assuming that all the data for a row is stored together makes it difficult to implement any optimisations that spans multiple rows. Think of a string state field where there are only five known values… we currently repeat the text over and over. Or a full column store backend. Regards, Stephen
