On Thu, Aug 21, 2008 at 11:23 PM, Jason Rennie <[EMAIL PROTECTED]> wrote:
> Is there an option to perform less aggressive stemming in solr? We're using
> the Porter stemmer. I see that there is an option for Snowball, but my
> understanding is that Snowball is a refinement of Porter rather than
>
Hi Doug,
On Wed, Aug 13, 2008 at 8:25 PM, Doug Steigerwald
<[EMAIL PROTECTED]> wrote:
> When spellchecking 'blackberri wi', the collation returned is 'blackberry
> wii'. When spellchecking 'blackberr wi', the collation returned is
> 'blackberrywii'. 'blackber wi' returns 'blackberrwiiwi'.
It lo
Chris,
On Sat, Jan 26, 2008 at 2:30 AM, Chris Hostetter
<[EMAIL PROTECTED]> wrote:
> : I have the synonym filter only at query time coz i can't re-index data (or
> : portion of data) everytime i add a synonym and a couple of other reasons.
>
> Use cases like yours will *never* work as a query time
Hi Cuong,
On Tue, Jul 1, 2008 at 4:45 AM, climbingrose <[EMAIL PROTECTED]> wrote:
> I modified the original English Stemmer written in Snowball language and
> regenerate the Java implementation using Snowball compiler. It's been
> working for me so far. I certainly can share the modified Snowball
On 10/23/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> I've actually thought about it previously it would be nice for it
> to all work automatically for the user. Seems like the implementation
> should be based on the TokenFilter level, then things like synonym
> filters, stemmers, etc, would
On 9/27/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> The simple workarround: if you know all of your data is indexed with
> perfect 0.000second precision, then put "-1MILLI" at the end of your start
> and end date faceting params.
It fixed my problem. Thanks.
--
Guillaume
On 9/27/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> a better option (assuming a query parser change) would be a new option
> thta says wether each computed range should be enclusive of the low poin,t
> the high point, both end points, neither end points, or be "smart" (where
> smart is the sam
Hi all,
I'm now using date facetting to browse events. It works really fine
and is really useful. The only problem so far is that if I have an
event which is exactly on the boundary of two ranges, it is referenced
2 times.
If we admit that we have a gap of 6 hours starting from 2007-09-27
12:00,
Hi Patrick,
On 9/27/07, patrick o'leary <[EMAIL PROTECTED]> wrote:
> p.s after a little tidy up I'll be adding this to both lucene and solr's
> repositories if folks feel that it's a useful addition.
It's definitely very interesting. Did you compare performances of
Lucene with a database allowi
On 9/24/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> sorting on a tokenized field is definitely a no-no ... the only situation
> in which that will work is if your tokenizer produces only one token per
> document (ie: KeywrodTokenizer)
Yes, it works now. I have now based my sort field on the a
Hi Chris,
On 9/24/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> 1)
> 2)
In fact both were typos in my email: the code is right. It was a bit
late here. After a few hours of sleep, I think the problem is that I
sort on a tokenized value. Without a facet filter, I have enough
results to have o
Hi all,
I'm currently playing with solr (a nightly build of sep. 16) to see if
it can fit our needs. It's really a great piece of software and I
especially appreciate the facetting features.
I now have something that works really well and there's only one problem left:
- I want to sort the result
12 matches
Mail list logo
