Joe Eli McIlvain

> I tried first to only implement the suggestion (provide opt as parameter to the lookup_try call in add_special), but this failed to build Can you give more detail -...

To make it work, we need to add `opt` everywhere - if it's not in scope, we need to make sure it is in scope by adding it to the...

> why `ast_error` does not generate an error message at all ??? No textual output is generated The `ast_error` appends an error into the error list held at `opt->check.errors`. It...

My suggested approach is still the same as in my previous comment - that the code should be updated in whatever was is necessary to make it no longer assume...

Yes, I think so.

@ipapapa - Just to clarify - this would effectively translate to a "last write wins" strategy for cross-datacenter conflicts? Of course, this would have the caveat that latency of replication...

> There are thoughts of extending the current implementation by adding timestamps for conflict resolution and reconciliation. Please feel free to contribute as well. I'd definitely be interested to at...

@timiblossom when you say timestamp I'm assuming you're talking about using a wall clock timestamp to determine order of events - have you considered using some form of logical clock...

It would require something like each node tracking the revision number for each key, incrementing when a request to set/mutate that key arrives. For a vector clock in particular, the...

If you were keeping a vector clock in memory without persistence, and the node dies, it could try to retrieve the latest vector clock info through communication with the other...