Make sure you check the padding of the number. I can no longer locate in the
wiki where it said you need to pad integer types, but as far as I remember
you need to pad the integer out to at least 10 digits. You should be able to
set a custom padding size like so:
{field, [ {name, "account"}, {type
Per the advice from my earlier question (about retrieving records in a
particular sort order), I've been playing with Riak Search in an attempt to use
a range query over a numeric field to get the sort order that I want (or at
least the right range).
For the life of me, I can't get Riak Search
Alex Sicular posted about this on his blog the other day:
http://siculars.posterous.com/paginating-with-riak Basically, he uses a
combination of Riak and Redis to manage pagination.
If you're absolutely opposed to using multiple data stores, Eric's approach
should work. Otherwise, I'd offload sort
That's one way of looking at it. The other viewpoint is that given the
choice between returning a partial (a.k.a. incorrect) result set vs. failing
loudly, the safest option is to fail loudly.
Ideally there would be a way to return a partial result set with an
indication in Solr that the result se
That sounds like a bug rather that a feature to me. For instance if I wrote
100,001 blog entries, the search engine breaks hard for a query trying to
find my latest tweets.
Is that what would happen?
-- Forwarded message --
From: "Rusty Klophaus"
Date: Jan 16, 2011 8:42 AM
Subject
Hi Eric,
This is a failsafe that is applied prior to the 'rows' parameter.
It is applied separately to provide a hard system limit, intended to allow
the cluster administrator to guard against a malicious user, a client
application that accidentally requests too much data, etc.
Best,
Rusty
On S
Would using the rows URL parameter fix this or is the error occurring prior
to the result being limited?
-- Forwarded message --
From: "Rusty Klophaus"
Date: Jan 16, 2011 8:34 AM
Subject: Re: too_many_results error
To: "Malka Feldman"
Cc:
Hi Malka,
The error you see is caused b
Hi Malka,
The error you see is caused by a protective configuration setting that is
new in the 0.14 release. By default, the system will stop the query after
100,000 results and return an error to the system. It is intended to prevent
Riak Search from grabbing all available memory when faced with
Hi
I try to get results from query through solr , but I get the error of too
many results
the query is :
http://79.125.59.136:8098/solr/user_profile/select?q=country:USA
I know I can have hundreds of thousands of answers, can it hold them?
the error :
{error,
{throw,
{too_many_results
I have also been toying with the idea of a linked list using a "next"
links on entries. Theoretically I could use link walking to get the
next 19 entries given a "HEAD" entry. It feels like a maintenance
nightmare though.
On Sat, Jan 15, 2011 at 7:23 PM, Gary William Flake wrote:
> I am buildin
First, check out Riak Search. It can sort your records by dates and
your can use it for
filtering on secondary indexes. If your criteria for listing the
records is pretty simple and can be expressed with a search query,
that may be your best bet. For instance, listing a user's blog
entries is as
11 matches
Mail list logo
