This was on hector-users this morning as well. It has been addressed
and is now in trunk.
-Nate
On Thu, May 6, 2010 at 2:35 PM, Jonathan Ellis wrote:
> That's kind of an odd API wart for Hector. You should file an issue
> on http://github.com/rantav/hector
>
> On Thu, May 6, 2010 at 11:36 AM, J
That's kind of an odd API wart for Hector. You should file an issue
on http://github.com/rantav/hector
On Thu, May 6, 2010 at 11:36 AM, Jonathan Shook wrote:
> I found the issue. Timestamp ordering was broken because:
> I generated a timestamp for the group of operations. Then, I used
> hector's
I found the issue. Timestamp ordering was broken because:
I generated a timestamp for the group of operations. Then, I used
hector's remove, which generates its own internal timestamp.
I then re-used the timestamp, not wary of the missing timestamp field
on the remove operation.
The fix was to sim
When I try to replace a set of columns, like this:
1) remove all columns under a CF/row
2) batch insert columns into the same CF/row
.. the columns cease to exist.
Is this expected?
This is just across 2 nodes with Replication Factor 2 and Consistency
Level QUOROM.
