Re: Behavior of daos_kv_get for non-existent Keys
Sorry for not sending this earlier, but I have landed some changes to the KV API to:
1) enable using & checking the conditional flags in the put/get/punch operations
2) Add separate open / close operations for the KV object instead of the base open close. Note that this requires a change to your existing code to use the kv open / close. This is really to align with like the array api which has it's own API for open close and require we set some feature flags on the oid for KV object.
Please see the kv test or the simple object program for some simple example usage:
All that should be available in latest master or the 1.1.1 tag.
On 8/25/20, 9:17 AM, "email@example.com on behalf of Steffen Christgau" <firstname.lastname@example.org on behalf of email@example.com> wrote:
On 8/25/20 3:19 PM, Chaarawi, Mohamad wrote:
> We have recently added conditional operations to the DAOS object and KV api to allow for such conditional operations:
> DAOS_COND_KEY_INSERT/UPDATE/FETCH/PUNCH (for the daos_kv_* API)
> Which would give you what you need.
Thanks for pointing that out, Mohamad.
> However for the KV API, I actually see an issue where these flags are not properly set.
> I will push a patch to fix this soon and let you know.
Great. Looking forward for a notification.
Just to be sure: Given that the API would work correctly, these
conditional operations are passed with the flags parameter which are
marked as "currently ignored"?!