This group is announcement-only. You cannot post messages because you are not a manager.
Description:
Groups together all mailing lists for easy search and reference from myNoSQL blog
|
|
|
saving meta data always wraps value in an array
|
| |
hello,
I searched the archives and I didn't see this mentioned; I'm sure I'm
missing something here.
I'm using riak-client 1.2, riak 1.3.1, and the http interface. When I add
a string metadata and store the object, it returns an array. If I store it
again, it returns an array where the first element is the json string of... more »
|
|
|
Java client and siblings question
|
| |
Hi, I am currently using the latest java client, and I have a question regarding updating data in a bucket where siblings are allowed (i.e. allowSiblings = true). I finally understand the whole read-resolve-mutate-write cycle, and also doing an update / store using previously fetched data (i.e. not in the same "transaction").... more »
|
|
|
Single key - Multiple Buckets
|
| |
I'm evaluating Riak for an implementation I have planned.
I'd like to know if a single key can be referenced from multiple buckets as
to create the following scenario:
johnsFriends contains bettysProfile
davesFriends contains bettysProfile
betty contains bettysProfile
betty updates profile and all inferences to the profile receive the benefit... more »
|
|
|
How to achieve good performance with Riak on AWS
|
| |
We have deployed a 4 node riak cluster on AWS with eLevelDB backend. We have
been benchmarking it for last couple of days using basho-bench, with
_unimpressive_
results. Attached "app.config" and "basho-bench.config".
Following are the only changes made to "vm.args"
...+K true
+A 16
We did following two tests.... more »
|
|
|
First Write Wins
|
| |
For automatic conflict resolution, often times, the easiest thing to do is
impose a Last Write Wins policy.
However, in certain circumstances, First Write Wins makes more sense. For
example, suppose you are handling user creation. Creating a single user
will populate values for two keys:
User Id => User data... more »
|
|
|
Questions about HBase replication
|
| |
Hi,
I have a couple of questions about HBase replication...
1) When we ship edits to slave cluster - do we retain the timestamps in the
edits - if we don't, I can imagine hitting some inconsistencies ?
2) When a region server fails, the master renames the directory containing
WAL(s). Does this impact reading of those logs for replication ?... more »
|
|
|
Yokozuna 0.6.0
|
| |
Riak Users,
Today I'm pleased to announce the 0.6.0 release of Yokozuna. Two
highlights of this release are:
1. Initial protobuff support at parity with Riak Search. This means that
existing Riak clients which have Riak Search/PB support should now be able
to query Yokozuna. Please note that, currently, having both Riak Search... more »
|
|
|
Best way to query geo hashed data?
|
| |
Hi
I'm looking at Riak as a solution for handling this type of data:
A map is divided into sectors, and on the map there are many objects with
each object being in 1 or more sectors. (An object can be in more than 1
sector if it is larger than the sector). Objects can move, so object 323
could move from sector 5 to sector 10.... more »
|
|
|
Repair of tombstones
|
| |
There has been a lot of discussion on the list recently concerning issues with repair, runtime, etc.
We recently have had issues with this cassandra bug:
[link]
Basically, if you do regular staggered repairs, and you have tombstones that can be gc_graced, those tombstones may never be cleaned up if those tombstones don't get compacted away before the next repair. This is because these tombstones are essentially recopied to other nodes during the next repair. This has been fixed in 1.2, however, we aren't ready to make the jump to 1.2 yet.... more »
|
|
|
Some Hbase questions
|
| |
Hi,
I am pretty new to HBase so it would be great if someone could help me out with my below queries;
(Ours is a time series data and all the queries will be range scan on composite row keys)
a) What is the usual practice of storing data types.
We have noticed that converting datatypes to bytes render unreadable data while debugging.... more »
|
|
|
