Just as the commentors above, I was looking through the documentation about the key-value functionality but didn't find anything regarding how to use it. I'll create a bug report for the Web UI, because it shouldn't confirm the saving for primitives. ArangoDB is a JSON-document store from the usage standpoint, which can be used in a key-value fashion by not adding/using secondary indexes but only primary key lookups, no joins, leaving the default shard key to _key for linear scalability etc. In arangojs, would this be db.collection('kvtest').save( would be the minimal solution. Let's say I want to have a collection that is 100% K/V with indexes on the key. Played around with this more and I'm even more confused. It shouldn't make a difference from a performance standpoint however, because a new document revision is created anyway (append-only).
#Arangodb sharding update#
UPDATE is for partial document updates, which is strictly speaking not a key-value pattern anymore because the value/document isn't treated as opaque piece of information. Translated to AQL it means that you can look up a value (=document) like:įOR doc IN coll FILTER doc._key = "" LIMIT 1 RETURN doc If sharding is done using different shard keys, then a lookup of a single key involves asking all the shards and thus does not scale linearly. If the key attribute is the only sharding attribute, then sharding is done with the primary key and all operations scale linearly.
The only sensible operations in this context are single key lookups and key/value pair insertions and updates.
Absent secondary indexes, the collection always behaves as a simple key/value store. ArangoDB implements the Key/Value store as a document collection that always has a primary key attribute.
0 kommentar(er)
