Hi Team,
I am trying to run mapreduce in erlang.
curl -XPUT http://localhost:8098/buckets/training/keys/foo -H
'Content-Type: text/plain' -d 'caremad data goes here'
curl -XPUT http://localhost:8098/buckets/training/keys/bar -H
'Content-Type: text/plain' -d 'caremad caremad caremad caremad'
curl
It’s worth noting that secondary indexes (2i) has some other advantages over
solr search. If you _can_ model your queries in 2i then I'd recommend it.
Secondary indexes have a richer API than is currently documented, if you look
at https://docs.basho.com/riak/1.4.7/dev/using/2i/ you’ll see that
Hi Russell,
It is really helpful, thank you a lot.
We are suffering from solr crash now, are considering to switch to 2i.
Br,
Alex
2017-02-06 16:53 GMT+08:00 Russell Brown :
> It’s worth noting that secondary indexes (2i) has some other advantages
> over solr search. If you _can_ model your que
Hi Alex,
org.apache.solr.client.solrj.SolrServerException: IOException occured when
>> talking to server at: http://nosql-2.dsdb:8093/inter
>> nal_solr/production_scheduling
>>
>>
Please check that there is no other process, including an instance of Solr,
running on your machine that may own the T
On 3 February 2017 at 18:31, raghuveer sj wrote:
> Hi Team,
>
> I am trying to run mapreduce in erlang.
>
> curl -XPUT http://localhost:8098/buckets/training/keys/foo -H
> 'Content-Type: text/plain' -d 'caremad data goes here'
> curl -XPUT http://localhost:8098/buckets/training/keys/bar -H
> 'Con
Dear Riak Team,
I and my team used riak as database for my production with an cluster
including 5 nodes.
While production run, we meet an critical bug that is sometimes fail to
update document.
I and my colleagues performed debug and detected an issue with the scenario
as follow:
+ fetch documen
Originally I suspected the context which allows Riak to resolve conflicts was
not present in your data, but I see it in your map structure. Thanks for
supplying such a detailed description.
How fast is your turnaround time between an update and a fetch? Even if the
cluster is healthy it’s not i
What operation are you performing? It looks like the map is a single level map
of last-write-wins registers. Are you updating a value? Is there a chance that
the time on the node handling the update is behind the value in the
lww-register?
Have you tried using the `modify_type` operation in ria
