Just want to add: driver (client) dev is listening!
Adding this our clients is a fairly easy thing, and I'll ad it to our todo list.
- Roach
On Wed, Mar 26, 2014 at 4:03 PM, Alexander Sicular wrote:
> Agree with a lot of your points, Elias. But I've found that as a solo
> developer pushing prod
Agree with a lot of your points, Elias. But I've found that as a solo developer
pushing product in my organization, and I would venture to say there are others
like mine, Riak's ops proposition trumps some of these developer issues. Not
having to hire ops personnel to babysit a Riak app is a big
On Wed, Mar 26, 2014 at 10:36 AM, Eric Redmond wrote:
> That is correct. Storing values in solr make the values redundant. That's
> because solr and Riak are different systems with different storage
> strategies. Since we only return the solr results, the only way we can
> access the kv values wo
That is correct. Storing values in solr make the values redundant. That's
because solr and Riak are different systems with different storage
strategies. Since we only return the solr results, the only way we can
access the kv values would be to make a separate call, which is not much
different from
On 25 Mar 2014, at 11:05, Paul Walk wrote:
> I presume Riak::Links are being retained - it's just the link-walking
> functionality which is being deprecated?
Link-walking itself has been removed from the 2.0 ruby-client. We still store
and retrieve the metadata, and you can access it, but we do
On Wed, Mar 26, 2014 at 9:44 AM, Eric Redmond wrote:
> The newest Riak Search 2 (yokozuna) allows you to create custom solr
> schemas. One of the field options is to save the values you wish to index.
> Then when you perform a search request, you can retrieve any of the stored
> values with a fie
The newest Riak Search 2 (yokozuna) allows you to create custom solr
schemas. One of the field options is to save the values you wish to index.
Then when you perform a search request, you can retrieve any of the stored
values with a field list (fl) property
Eric
On Mar 26, 2014 9:37 AM, "Elias Lev
Are there any plans to introduce a Riak Search API that will allow a search
to return matching documents, rather than references to matching documents?
Its seems rather cumbersome to have to generate at least two round trips,
or more, to satisfy a query.
I suppose this would also require Riak KV
Thanks Christian - that’s nice and clear.
Paul
On 26 Mar 2014, at 08:15, Christian Dahlqvist wrote:
> Hi Paul,
>
> CRDTs are stored as a normal object in Riak, although in a format that allows
> Riak to resolve conflicts automatically, meaning that the normal restrictions
> on object size ap
Hi Paul,
CRDTs are stored as a normal object in Riak, although in a format that
allows Riak to resolve conflicts automatically, meaning that the normal
restrictions on object size applies. As secondary indexes do not have to be
related to the data in any way, Riak would not be able to determine ho
10 matches
Mail list logo
