Re: Migrating to riak 2.1.4, selecting a specific multi-backend from the Java Client

2016-08-10 Thread Henning Verbeek
Good morning Alex, On Tue, Aug 9, 2016 at 8:47 PM, Alex Moore wrote: >> >> Is this equivalent to specifying a bucket type? > > > Not exactly, that code will set the backend for that bucket, which is in the > default bucket type. > If you need to specify a bucket-type, it's just an extra parameter

Re: Migrating to riak 2.1.4, selecting a specific multi-backend from the Java Client

2016-08-10 Thread Henning Verbeek
Hi Magnus, On Wed, Aug 10, 2016 at 9:21 AM, Magnus Kessler wrote: > On 9 August 2016 at 15:42, Henning Verbeek wrote: >> >> We're slowly migrating our application from Riak KV 1.4 to Riak KV >> 2.1.4, and at the same time riak-java-client 1.4.x to riak-java-client >> 2.0.6. We are doing this by

Re: Migrating to riak 2.1.4, selecting a specific multi-backend from the Java Client

2016-08-10 Thread Magnus Kessler
On 9 August 2016 at 15:42, Henning Verbeek wrote: > We're slowly migrating our application from Riak KV 1.4 to Riak KV > 2.1.4, and at the same time riak-java-client 1.4.x to riak-java-client > 2.0.6. We are doing this by adding seven new Riak KV 2.1 nodes to the > ring, and later removing the se

Re: Migrating to riak 2.1.4, selecting a specific multi-backend from the Java Client

2016-08-09 Thread Alex Moore
Hey Henning, Almost everything is stored in bitcask, but for some > progress-information-items, we are using the memory backend with > automatic expiration. Thus, the multibackend is being configured > (app.config for the old nodes, riak.conf for the new nodes). In the > past, I have configured bu