4.3.84

Changes for 4.3.84

Changes to branch 4.3 after version 4.3.83.

Commits

• KZ00-41: handle number delete conflicts - by James Aimonetti

  Previously, when deleting the number document from the account

  database, a conflict almost always occurred on the first delete

  attempt as the number doc from the number database was used (which

  contained a different _rev).

  However, knm_phone_number:retry_conflicts/4 only had code for saving

  to the target database (the account). The result is that the number

  doc (now in the "available" state) would be ensure_saved to the

  account database, resulting in number listings for the account to both

  show the number belonging to the account and show it as "available",

  an internal state that clients should not see.

  This changeset provides additional context to handle_bulk_change about

  what type of change, 'delete' or 'save', and informs retry_conflicts

  of how to proceed.

  Secondly, the likelyhood of conflict is high when saving/deleting from

  the account database as the JSON object used is the number db's

  version. try_delete_from has been updated to use just the number as

  ID and lets kz_datamgr build the tombstone and delete accordingly.

• KCRO-7: new filter to find missing keys OR keys with empty values - by Karl Anderson

  If you want to find a document by missing a value for a parameter the only way currently is to use the filter for a missing key. However, this filter does not emit the document if the key is present but the value is empty/null. There is a has_value filter but no inverse of that. This adds a new query filter missing_value that will return a document if the key is missing OR the value is empty.