On Jan 21, 2008 10:23 AM, Doug Steigerwald
<[EMAIL PROTECTED]> wrote:
> Is there any support for DisMax (or any search request handlers) in search
> components, or is that
> something that still needs to be done? It seems like it isn't supported at
> the moment.
I was curious about this, too ..
it is the
> right sort of feature. You'd like to see the top N matches for
> each value of the author field, right?
>
> wunder
>
> On 1/6/08 3:25 PM, "Charles Hornberger" <[EMAIL PROTECTED]>
> wrote:
>
> > I've got a problem that I'm n
I've got a problem that I'm not quite sure how to solve and am wondering if
anyone has any insight or similar experience to share.
Here's the situation: Documents in our Solr index include a field
identifying their author (we have 1000s of authors). When displaying an
individual document, we also
FAST calls them "navigators" (which I think is a terrible term - YMMV
of course :-))
I tend to think that "filters" -- or perhaps "dynamic filters" --
captures the essential function.
On Dec 11, 2007 2:38 AM, "DAVIGNON Andre - CETE NP/DIODé/PANDOC"
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> > So, has a
https://issues.apache.org/jira/browse/SOLR-426
On Dec 5, 2007 9:57 AM, Ryan McKinley <[EMAIL PROTECTED]> wrote:
>
> Charles Hornberger wrote:
> > On Dec 4, 2007 6:25 PM, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> >> i'm not sure what you mean by &q
On Dec 4, 2007 6:25 PM, Chris Hostetter <[EMAIL PROTECTED]> wrote:
>
> i'm not sure what you mean by "applied to 1.2" ... releases are static:
> once published they are never changed. in the event of serious bugs (ie:
> security holes or crash related bugs) then point releases may be published
> (
http://martin.nobilitas.com/java/sizeof.html)
Does that seem right?
-Charlie
On Dec 4, 2007 12:31 PM, Charles Hornberger
<[EMAIL PROTECTED]> wrote:
> > See Lucene's FieldCache.StringIndex
>
> To understand just what's getting stored for each string field, you
> may
> See Lucene's FieldCache.StringIndex
To understand just what's getting stored for each string field, you
may also want to look at the createValue() method of the inner Cache
object instantiated as stringsIndexCache in FieldCacheImpl.java (line
399 in HEAD):
http://svn.apache.org/viewvc/lucene/ja
LIke others before me, I stumbled across this bug, where
solr/bin/commit warns that a commit failed when in fact it succeeded
quite nicely, while getting collection distribution up & running
today:
http://www.mail-archive.com/solr-user@lucene.apache.org/msg04585.html
It's a trivial fix, and i
Store a copy with the string reversed in another field. Then you can
search that field for gniht* ...
Also, I believe I saw some comments about prefix wildcards being
available in some upcoming release (1.3?) ... sorry I can't remember
any better than that. Google may help ...
-Charlie
On Nov 29
, Charles Hornberger
<[EMAIL PROTECTED]> wrote:
> I'm confused by some behavior I'm seeing in Solr (i'm using 1.2.0). I
> have a field named "description", declared with the following
> fieldType:
>
> positionIncrementGap="100" >
>
I'm confused by some behavior I'm seeing in Solr (i'm using 1.2.0). I
have a field named "description", declared with the following
fieldType:
The problem I'm having is that when I search for description:deck*, I
get th
I'm experimenting with the new solr.py from
http://issues.apache.org/jira/browse/SOLR-216 think perhaps I'm
confused about how batching is are supposed to work.
I wrote this test script:
import solr
client = solr.SolrConnection('http://localhost:8080/solr')
client.begin_batch()
client.add
On 11/5/07, Charles Hornberger <[EMAIL PROTECTED]> wrote:
> Also, it seems a bit inefficient to bother allocating an array
> containing an entry for each document when only some small percentage
> of the documents actually contain values for the field. Would it be
> worth investi
On 10/31/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> the biggest factor to worry about is the number of "sources" ... the key
> to understanidng the performance risks is to understand that:
> 1) no matter how many documents do or don't have a value for a given
> field, when you sort on thta
Hi --
I'm building a Solr index to replace an existing RDBMS-based system,
and I have one requirement that I'm not sure how to best satisfy.
Documents in our collection can have user-generated ratings associated
with them; these user-generated ratings are aggregated by source
(sources are basicall
I'm about to do a prototype deployment of Solr for a pretty
high-volume site, and I've been following this thread with some
interest.
One thing I want to confirm: It's really possible for Solr to handle a
constant stream of 10K updates/min (>150 updates/sec) to a
25M-document index? I new Solr and
IIRC you can also also simply stop the servlet container, delete the
contents of the data directory by hand, then restart the container.
-Charlie
On 8/20/07, Pieter Berkel <[EMAIL PROTECTED]> wrote:
> If you are using solr 1.2 the following command (followed by a commit /
> optimize) should do th
For what it's worth, I recently did a quick implementation of the
spellchecker feature, and I simply created another field in my schema
(Iike 'spell' in Tristan's example below). After feeding content into
my search index, I used the spell field into add one single-field
document for every distinc
19 matches
Mail list logo
