The data service provides for the creation of user data in the data layer.
TEST: data put 1 should add user data at path
All Xirsys services return a version id (ver) when you create or get a value.
This can be ignored unless you're going to update the value. Xirsys employs optimistic locking to make sure you don't overwrite someone elses changes. When you update a value make sure you include the ver in your updated object - you'll be warned if you forget with a _ver_missing error. If a new version of the object has been created since you received your version, you'll get a version_conflict error returned. If someone is in process of updating the object, then a locked error will be returned.
Although, you're required to supply the up to date version id, Xirsys, doesn't update in place. Instead we always save your old object, which you may retrieve via the time series. By never updating in place, Xirsys maintains an audit trail on all data.
TEST: data delete should delete 1 element
On successful delete you receive an ok, with the numer of elements deleted. For a single key delete this is always 1. However, by omitting the k, you can do a full path delete.
TEST: data delete path
Note: Paths are not stored indepently of keys, except for the _ns service. Therefore if you delete all keys in path the path itself is removed.
TEST: data get should get a value
TEST: data list should list two elements at same path
curl "https://user:secret@endpoint/_data/my/path?time_series=1"
The array structure returned has the following structure
[timestamp,whoperformedoperation,value]
Time series may be queried using the same syntax for stats queries, where gs/ge are group start/group end respectively, and broken into year:month:day:hour:minute:second
TEST: data time series should return all action at this path