Hi,
Riak CS 2 moved to a new Ubuntu/Debian repository, at packagecloud.io.
However attempts to use it as per the documentation result in the message
"Incorrect username or token" and an HTTP status of 401.
This is because the docs give the URL as similar to:
deb https://packagecloud.io/basho/riak_
Hi all,
I am new to the list and have been playing around with Riak over the
last couple of months. I've come up on a client project to evaluate an
alternative DB to their MS SQL server for a specific issue they are having.
I am having some big problems with Riak... so any guidance, help,
a
Hi Zee,
Sorry for the extremely late response and I would to say , I'm highly
thankful for your time.
Antonio
2015-04-07 18:29 GMT+01:00 Zeeshan Lakhani :
> Hello Antonio,
>
> Firstly, please always reply to the list and not via personal email.
>
> In regards to your question, I wrote a test th
I read it already. I just wanted to confirm sequence of rolling upgrades.
Did I get it right?
Thank you,
Konstantin
On Jun 2, 2015 2:12 PM, "Matthew Brender" wrote:
> Hi Konstantin,
>
> A good deal of detail should be considered as you upgrade. The
> additional recommendations are outlined in th
Hi Konstantin,
A good deal of detail should be considered as you upgrade. The
additional recommendations are outlined in the documentation here:
http://docs.basho.com/riak/latest/upgrade-v20/
Thanks to CMJ for reminding me of these details.
Matt Brender | Developer Advocacy Lead
Basho Technologi
Hello,
Has anyone had to run 1.2.1 on Ubuntu Trusty? I was hoping to obtain
an apt package, but I see that there is no 1.2.1 Trusty build, nor are
there any builds for Trusty before 2.0 (which is on package cloud). As
we seek to bump up our versions, we'd hope to have packages of all
versions for
Hi Sinh,
The other issue here, I suspect, is that the default Solr install does not
come with the jar files containing JtsSpatialContextFactory. You will need
to install them yourself. (Fwiw, there was an issue opened recently
requesting that this get included with Riak by default, here:
https://g
I’m simulating a failure with a concurrent update on a strongly consistent
bucket/entry.
This fails as it should for the second update, however the error message/code
is not entirely useful.
com.basho.riak.client.core.netty.RiakResponseException: failed
We’ve investigated this and the error