While I think "adaptively cache just hot parts of the row wherever
they are" is not feasible, the limitations you describe should be
fine. I think it's a clever idea, and probably widely useful.
On Mon, Jan 3, 2011 at 10:48 AM, Daniel Doubleday
wrote:
> Hi,
>
> we have a couple of use cases with
Hi,
we have a couple of use cases with wide rows with a small portion of hot data
in them.
Example:
Chatlog:
{
$userid1-$userid2: [{timestamp: message}, {timestamp: message} ...]
}
People tend to check only the most recent pages. So while the current row cache
doesn't work with the
