On Sat, Jul 2, 2011 at 7:34 PM, Benson Margulies wrote:
> Hey, I don't suppose you could easily tell me the rev in which ngroups
> arrived?
1137037 I believe. Grouping originated in Solr, was refactored to a
shared lucene/solr module, including the ability to get the total
number of groups, and
Hey, I don't suppose you could easily tell me the rev in which ngroups arrived?
Also, how does ngroups compare to the 'matches' value inside each group?
On Sat, Jul 2, 2011 at 3:06 PM, Yonik Seeley wrote:
> 2011/7/1 Tomás Fernández Löbbe :
>> I'm not sure I understand what you want to do. To p
2011/7/1 Tomás Fernández Löbbe :
> I'm not sure I understand what you want to do. To paginate with groups you
> can use "start" and "rows" as with ungrouped queries. with "group.ngroups"
> (Something I found a couple of days ago) you can show the total number of
> groups. "group.limit" tells Solr h
OK, I tried a quick test of 1.4.1 vs 3x on optimized indexes
(unoptimized had different numbers of segments so I didn't try that).
3x (as of today) was 28% faster at a large filter query (300 terms in
one big disjunction, with each term matching ~1000 docs).
-Yonik
http://www.lucidimagination.com
I believe you should be able to get results ordered so that the
documents you want will always come first, so you can truncate the
results efficiently on the client side.
You could also try a regexp query (untested):
a b c -/~(a|b|c)/
-Mike
On 7/1/2011 7:50 PM, Spyros Kapnissis wrote:
Hello
Thanks Stefan.
/update/csv handler was not defined in my solrconfig.xml. After defining it
in the solconfig I could get the CSV files indexed using following two
commands:
> java -Dcommit=no -Durl=http://localhost:8983/solr/core0/update/csv -jar
post.jar books.csv
> java -Dcommit=yes -Durl=http:/
Yes, from an utilitarian perspective you're absolutely right.
Mine is actually a more academic exercise.
I will be more clear on the steps that I would like to take:
1) Call the analyzer of Solr that returns me an XML response in the
following format (just a snippet as example)
Sandeep,
did you check that this handler is defined in your solrconfig?
Otherwise it will not work, and you'll get an HTTP 404
Regards
Stefan
Am 02.07.2011 17:15, schrieb sandeep:
post.jar is used to post xml files. You can use curl to feed csv.
http://wiki.apache.org/solr/UpdateCSV
I tried
> post.jar is used to post xml files. You can use curl to feed csv.
> http://wiki.apache.org/solr/UpdateCSV
I tried using curl as well to post the CSV data using following command.
curl http://localhost:8983/solr/core0/update/csv --data-binary @books.csv -H
'Content-type:text/plain;charset=utf-
Hi Lox,
But I would also like to retain the original non-analyzed field for
>
diplaying purposes.
>
Actually, for stored fields, Solr always retains the original non-analyzed
content, which is the one included in the response. So, if I'm not missing
something, you don't need to separate the analy
Hi,
I'm trying to achieve a sort of better separation between the analysis of a
document (tokenizing, filtering ecc.) and the indexing (storing).
Now, I would like my application to call the analyzer (/analysis/document)
via REST which returns the various tokens in xml format, then feed these
data
> I am trying to index CSV data in
> multicore setup using post.jar.
>
> Here is what I have tried so far:
> 1) Started the server using "java
> -Dsolr.solr.home=multicore -jar
> start.jar"
>
> 2a) Tried to post to "localhost:8983/solr/core0/update/csv"
> using "java
> -Dcommit=no -Durl=http://lo
Hello,
I'm still struggling with wildcard search in solr.
I installed the ComplexPhraseQueryParser which essentially accomplishes what
I'm looking for: I can search in my field "GOK" using phrases with wildcards,
e.g. GOK:"POF 15?".
This works with either solr 1.4.2 or 3.3.
What irritates me is
13 matches
Mail list logo
