Hi Joseph,
Ah okay, I see what you are saying now. That's a good idea, and a nice
simplification to the code. Thanks for the suggestion!
This is now tracked here: https://issues.basho.com/show_bug.cgi?id=870
Best,
Rusty
On Thu, Nov 4, 2010 at 8:02 PM, Joseph Lambert
wrote:
> Disregard that las
Disregard that last message. What I meant was, in a Solr query, all the
results are returned and then it sorts and then takes the chunk that is
requested by the start and count parameters. Why not instead make the
results of the search() function the input of a MapReduce job, and if the
user adds s
Rusty,
Sorry, I meant Lucene search. Solr can be passed start and count, Lucene
search can't be, but they share functions in the Erlang code.
- Joe Lambert
joseph.g.lamb...@gmail.com
+86 13656213284
On Fri, Nov 5, 2010 at 2:15 AM, Rusty Klophaus wrote:
> Hi Joseph,
>
> Answers inline below.
Hi Joseph,
Answers inline below.
On Thu, Nov 4, 2010 at 12:49 AM, Joseph Lambert
wrote:
> I am using the PHP library for a project and was looking through the code
> to see what differentiates the Solr HTTP interface query versus the Lucene
> search (besides the syntax and the interface, etc) as
