Sanket -
One other thought. Could you please change the name of your module to
something other than "precommit"? That is the atom being used for
precommit hooks and maybe that's causing an issue.
--
Luke Bakken
Engineer
lbak...@basho.com
On Fri, May 13, 2016 at 7:05 AM, Luke Bakken wrote:
> Hi
Hi Sanket -
Could you please try *removing* the precommit hook from the "uuid_log"
bucket and define it on the "test_kv_wo" bucket type instead?
Removal:
curl -4vvv -H 'Content-Type: application/json' -X PUT
localhost:8098/types/test_kv_wo/buckets/uuid_log/props -d
'{"props":{"precommit":[]}}'
C
Hi Kyle,
Riak TS is not yet compatible with Riak Security. Dropping or
truncating tables has been requested but is not in the 1.3 release.
Comprehensive docs for Riak TS are located here:
http://docs.basho.com/riak/ts/1.3.0/using/
--
Luke Bakken
Engineer
lbak...@basho.com
On Wed, May 11, 2016
Hi Luke,
I renamed precommit to pre_triggers, and then re-associated the hook to
bucket type instead of bucket as you suggested. Also, started redbug on all
three consoles, and confirmed that it started. Then, I made the call that
should trigger the hooks, but nothing triggered. The module shows u
Hi all,
Imaging I have an index called "*posts*" where I index the following fields
and I reuse the index in 3 buckets: "status", "photos" and "videos"... then
I do the following:
*results = client.fulltext_search('posts', 'likes_counter:[100 TO *]',
sort='likes_counter desc', ro
Hi Alex,
'likes_counter:[100 TO *] AND _yz_rb:photos' will limit query results to
the photos bucket only. Similarly, "_yz_rt" is for a bucket type.
Searching for anything in an index can be done with "*:*" (any field, any
value).
Regards,
Vitaly
On Fri, May 13, 2016 at 9:40 PM, Alex De la rosa
Oh!! silly me... *_yz_rb* and *_yz_rt*... how didn't I think of that?...
thanks also for the "*:*" tip ; )
Thanks!
Alex
On Fri, May 13, 2016 at 10:50 PM, Vitaly <13vitam...@gmail.com> wrote:
> Hi Alex,
>
> 'likes_counter:[100 TO *] AND _yz_rb:photos' will limit query results to
> the photos buc
Another question... if I have a set of tags for the elements... like
photo.set['tags'] with things like: ["holidays", "Hawaii", "2016"]... will
it be indexed like this?
Thanks,
Alex
On Fri, May 13, 2016 at 10:52 PM, Alex De la rosa
wrote:
> Oh!! silly me... *_yz_rb* and *_yz_rt*... how didn't
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
In general, Riak/Solr is capable of indexing multi-valued properties (i.g.
lists). You're right thinking that multiValued = "true" should be used for
it. That said, check if it works with your client library (it's Python,
isn't it?). I believe it does.
Regards,
Vitaly
On Fri, May 13, 2016 at 9:59
Yes, using Python client. I'm able to store sets without problem into Riak,
just wondered if indexing them in SOLR would be as simple as just adding
the multiValued attribute to the "set" field... seems is going to be that
way :)
Thanks,
Alex
On Fri, May 13, 2016 at 11:15 PM, Vitaly <13vitam...@g
@Alex please kindly take a look at the default solr schema for Riak Search.
You should have based your custom schema on this (if you've created a
custom schema):
https://docs.basho.com/riak/kv/2.1.4/developing/usage/search-schemas/ ->
https://raw.githubusercontent.com/basho/yokozuna/develop/priv/de
Oh, nice snippets! thanks Drew!
Alex
On Fri, May 13, 2016 at 11:28 PM, Drew Kerrigan wrote:
> @Alex please kindly take a look at the default solr schema for Riak
> Search. You should have based your custom schema on this (if you've created
> a custom schema):
> https://docs.basho.com/riak/kv/2.
13 matches
Mail list logo
