I only mention this as I too have a small userbase/data footprint for one of my
projects and in that project I have "squashed" all fields together in a
catchall field within a json blob exactly because of this problem. Because of
the project size doing so is an acceptable performance hit in term
On Tue, Dec 18, 2012 at 11:24 AM, Ryan Zezeski wrote:
>
>
>
> On Sat, Dec 15, 2012 at 12:43 AM, Matt Painter wrote:
>
>
> The fork of Riak used by Yokozuna is extremely minimal. It mostly consist
> of bundling the yokozuna library and sending the KV data so it can be
> indexed. The goal is and
On Sat, Dec 15, 2012 at 12:43 AM, Matt Painter wrote:
> Thanks so much Ryan - yokozuna sounds most promising. If I were building a
> small system (relatively simple, small user base) that will be
> production-ready in a few months, do you think that Yokozuna could cut the
> mustard? I see that it
Thanks so much Ryan - yokozuna sounds most promising. If I were building a
small system (relatively simple, small user base) that will be
production-ready in a few months, do you think that Yokozuna could cut the
mustard? I see that it's officially an experimental prototype, but do you
think it's s
Matt, comments inline
On Tue, Dec 11, 2012 at 3:35 AM, Matt Painter wrote:
>
>
> Apart from a single default value, is it possible for Riak Search to
> search for a keyword across all fields in a document without having to
> specify the field up front as a prefix in one's search term?
>
A field
Hi,
Apart from a single default value, is it possible for Riak Search to
search for a keyword across all fields in a document without having to
specify the field up front as a prefix in one's search term?
I'm guessing that one solution could be a post-commit hook which
recursively iterates over a
