Hi Luke,
great advice, reminds me of what Joe Armstrong say from time to time:
measure don't guess.
(=
On Mon, May 16, 2016 at 7:55 AM, Luke Bakken wrote:
> Hi Alex,
>
> Benchmarking is the only sure way to know if you need to add this
> additional complexity to your system for your own use-ca
Hi Luke,
Yes, I think I will go with /search instead; should be enough.
Thanks,
Alex
On Mon, May 16, 2016 at 6:55 PM, Luke Bakken wrote:
> Hi Alex,
>
> Benchmarking is the only sure way to know if you need to add this
> additional complexity to your system for your own use-case or if
> search
Hi Alex,
Benchmarking is the only sure way to know if you need to add this
additional complexity to your system for your own use-case or if
search in Riak 2.0 will suffice. I suspect the latter will be true.
--
Luke Bakken
Engineer
lbak...@basho.com
On Mon, May 16, 2016 at 6:08 AM, Alex De la r
Hi Fred,
Yeah, I realised that on my testing node with n_val of 3 I was getting the
triple of results in the count... that is not ideal.
I was just concerned on how much extra-work would get Riak to talk with
SOLR and compile data against hitting SOLR directly... For my tests these
days, seems th
Hi Alex,
Other people have chimed in, but let me repeat that while the internal_solr
interface is accessible via HTTP (and needs to be, at least from Riak
processes), you cannot use that interface to query Solr and expect a correct
result set (unless you are using a single node cluster with an
Technically speaking, /search runs against the cluster plan, not all nodes
right?
We actually steal the cluster plan every n searches, then use that to
search directly against the solr nodes...
That being said, banging on solr will have an effect on kv from our
experience.. YMMV.
On May 15, 2016
I think is just my fear of querying Riak... I had bad experiences in the
past with Riak 0.14 and Riak 1.4 when searching with MapReduce, Search or
2-i... nodes crashing, etc... so I try to avoid searching as much as
possible.
Maybe my fear is not justified anymore on Riak 2.0 and is search via
SOL
Keep in mind that the /search endpoint returns consolidated results (i.e. a
query runs over all nodes of a cluster), while /internal_solr is only for
the node you run it on.
I'm not sure what you mean by "extra stress", as running queries is exactly
what the /search endpoint is meant for. Having s
Hi Vitaly,
I know that you can access search via HTTP through Riak like this:
http://localhost:8098/search/query/famous?wt=json&q=leader:true AND
age_i:[25 TO *]
I didn't find documentation about this, but according to your words I could
access SOLR directly like this?
http://localhost:8093/int
There is, you can *query *Solr directly via HTTP, at least as of Riak 2.0.x
Have a look at http://:8093/internal_solr/#/ and
http://docs.basho.com/riak/kv/2.1.4/developing/usage/search/#querying
Vitaly
On Sun, May 15, 2016 at 10:49 AM, Alex De la rosa
wrote:
> Nobody knows if there is a way t
Nobody knows if there is a way to access SOLR right away without going
through RIAK's interface?
Thanks,
Alex
On Fri, May 13, 2016 at 11:07 PM, Alex De la rosa
wrote:
> Hi all,
>
> If I want to create a Disco cluster [ http://discoproject.org ] to build
> statistics and compile data attacking R
Hi all,
If I want to create a Disco cluster [ http://discoproject.org ] to build
statistics and compile data attacking Riak's SOLR directly without using
Riak, how can I do it?
In this way, I would leave Riak mainly for data IO (post/get) and leave the
heavy duty of searching and compiling data t
12 matches
Mail list logo
