I've been working on the highlighting component, and it's a little odd how
it works. For myself, if I want terms highlighted, I'd like those in the
return results. Solr, on the other hand, returns a separate xml node that
represents the portions of the results that are highlighted. I know that
i
Does anyone know what the patent situation is with Lucene and Solr? What
patents affect it, what you can and cannot do with it?
Thanks,
Lance
On 8/15/07, Jonathan Woods <[EMAIL PROTECTED]> wrote:
> I'm trying to understand how best to integrate directly with Solr
> (Java-to-Java in the same JVM) to make the most of its query optimisation -
> chiefly, its caching of queries which merely filter rather than rank
> results.
>
> I notice that
Dear Jan,
I just saw your post on the SOLR mailing list. I hope I'm not too late.
First of, I don't exactly match your required qualifications. I do
have 9 years at Verity and 1 year at Autonomy in enterprise search,
however. I'm in the middle of coming up to speed on SOLR and
applying
On 8/15/07, Lance Norskog <[EMAIL PROTECTED]> wrote:
> Is indexing via solrj faster than going through the web service? There are
> three cases:
> Read a file from a local file system and indexing it directly,
> Read a file on one machine and indexing it on another, and
> Run solrj and
Is anyone doing Solr installations with a SAN file system? Like IBM Storage
Tank or Apple XSAN or Red Hat GFS? What are your experiences?
Thanks,
Lance
Is indexing via solrj faster than going through the web service? There are
three cases:
Read a file from a local file system and indexing it directly,
Read a file on one machine and indexing it on another, and
Run solrj and read a file, then directly update the index.
I'm talking about
I'm trying to understand how best to integrate directly with Solr
(Java-to-Java in the same JVM) to make the most of its query optimisation -
chiefly, its caching of queries which merely filter rather than rank
results.
I notice that SolrIndexSearcher maintains a filter cache and so does
LuceneQu
Great. Thanks, guys. That's how what I thought.
Any of you know whether the new "q:*.*" query performs better than the
get-around solutions like using a ranged query? I would guess so, but I
haven't looked into the Lucene implementation.
regards,
-Hui
On 8/15/07, Yonik Seeley <[EMAIL PROTECTED
Thanks for adding in those facet examples. That should help me out a
great deal.
As for the highlighting, did you have any ideas about a good way to go
about it? I was thinking about taking a stab at it, but I want to get
your input first.
Thanks,
Charlie
-Original Message-
From: Jeff
Adding '.' to the PATH didn't work for me. I tried it many different
combinations -- in my .bashrc, in the script which starts my tomcat
and/or setting "
PATH=.:/bin:/usr/bin:/usr/local/bin ". None of the
following worked for me...
In my scripts --
export PATH=.:$JAVA_HOME/bin:/usr/bin:/bin
Di
On 8/15/07, Pieter Berkel <[EMAIL PROTECTED]> wrote:
> I'm not 100% certain but I believe this syntax was added in 1.2 (it
> certainly works in the svn trunk code), can anyone confirm this?
Yes, It was added to Lucene 2.1 (which Solr 1.2 uses)
http://svn.apache.org/viewvc/lucene/java/trunk/CHANGES
Hi Hui,
I'm not 100% certain but I believe this syntax was added in 1.2 (it
certainly works in the svn trunk code), can anyone confirm this?
cheers,
Piete
On 14/08/07, Yu-Hui Jin <[EMAIL PROTECTED]> wrote:
>
> Piete,
>
> I tried and it doesn't work for Solr 1.1. Is it supported for 1.2 or at
13 matches
Mail list logo
