Where is KeyExists in 2.0 client

Hi Ingenthr, Jeff,

The problem I’m seeing is not an issue with checking for durability requirements per se but with using the method to check if a document exists as Jeff suggested.

All tests are done with no durability requirements (i.e. ReplicateTo.Zero and PersistTo.Zero)

  1. If I call observe with an existing key and no CAS then I get get ObserveResponse.DurabilityNotSatisfied
  2. If I call observe with an existing key and the CAS then I get get ObserveResponse.DurabilitySatisfied
  3. If I call observe with an non-existing key and no CAS then I get get ObserveResponse.DurabilitySatisfied

Now if these are the expected responses then I can code this in (i.e. set CAS to 0 and if the return is NotSatisfied then the document exists, else it doesn’t) I would just like to confirm this is the case.

It does seem a tad odd though as I would you would not know the difference between a document that has matched the durability requirements and one that simple doesn’t exist.

Thanks for your help,

Nick