Mike Gerwitz

Activist for User Freedom

path: root/doc
diff options
authorMike Gerwitz <mike.gerwitz@rtspecialty.com>2019-02-07 09:57:45 -0500
committerMike Gerwitz <mike.gerwitz@rtspecialty.com>2019-02-07 09:57:45 -0500
commit13716d240ba1ab522219c3a975900b2cf992af0c (patch)
treefb51e542ae999a4f3f9899f201ef8254959fab6a /doc
parent833017c359ee6a02130dd50a4d060d31d3598f22 (diff)
server: Correct liza_timestamp_initial_rated to be a vector
The metabucket expects vectors, not scalars. This causes the value to be inaccessible when loaded by the ProcessManager for rating, because it uses the Bucket implementation expecting vectors. This wasn't noticed at first because it works through TAME's map. * doc/bucket.texi (Metabucket): Clarify expected data format. * src/server/db/MongoServerDao.js (saveQuote): Store `meta.liza_timestamp_initial_rated' as a vector.
Diffstat (limited to 'doc')
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/bucket.texi b/doc/bucket.texi
index a944143..181d7ff 100644
--- a/doc/bucket.texi
+++ b/doc/bucket.texi
@@ -122,12 +122,20 @@ A diff is applied to the underlying bucket by invoking
@node Metabucket
@section Metabucket
@cindex Metabucket
-The @dfn{metabucket} is a loosely-structured key/value store
+The @dfn{metabucket} is a bucket-like key/value store
separate from the data bucket.@footnote{
It is stored in the @code{meta} field on the Mongo document.}
It should be used to save data that should be accessible only to the server,
but never the client.
+Data must still be formatted as a vector,
+ but unlike the data Bucket,
+ vector values are sometimes structured data instead of strings.
+@devnote{A standard still needs to be devised to provide guidance for
+ when storing structured data is appropriate,
+ rather than a vector of strings.}
The client has no means by which to access the metabucket.
Custom fields can be populated by server-side DataAPIs
(@pxref{Server-Side Data API Calls}).