in it.
Any suggestions?
-Stuart Sierra
I'm using lucene-core-2.4-dev.jar from the Solr 1.3.0 distribution.
Solr doesn't include lucene-misc, so I used lucene-misc-2.4.jar from
the Lucene 2.4.0 distribution.
But I had the exact same problem when I wrote my own index merge tool
using just the Solr distribution jars.
-Stuart Sierra
To Solr users:
I'm curious: do you store everything in a database and just use Solr
for indexing/searching, or do you store everything in Solr so that
your search results come back with context? Or something in between?
(I know if you want highlighting you have to store those fields.)
At the
On Jan 14, 2008 11:55 AM, Ryan McKinley [EMAIL PROTECTED] wrote:
the example.xsl is an example using XSLT to format results. Check:
http://wiki.apache.org/solr/XsltResponseWriter
To add to the above: I think the XsltResponseWriter is not intended
for formatting results for display on your web
On Jan 11, 2008 10:44 AM, Evgeniy Strokin [EMAIL PROTECTED] wrote:
Hello. If I need documents which has number of fields but also I have number
of other documents which related to the first one one-to-many. For example a
person, could have several addresses. I want to have all of them in
records from the
database just to display a list of search results. On the other hand,
if your database records are small and you don't need highlighting, it
may be faster to only store database ID's in the index.
Hope this sheds some light,
-Stuart Sierra
AltLaw.org
On Nov 18, 2007 1:50 AM, Dave C. [EMAIL PROTECTED] wrote:
Maybe you can help me with this related problem I am having.
My query is: q=description:(test)!(type:10)!(type:14).
However, my results are not as expected (55 results instead of the expected
23)
The response header shows:
On Nov 18, 2007 10:50 AM, Eswar K [EMAIL PROTECTED] wrote:
We have a scenario, where we want to find out documents which are similar in
content. To elaborate a little more on what we mean here, lets take an
example.
The example of this email chain in which we are interacting on, can be best
