[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-2181:
Attachment: LUCENE-2181.patch.zip
Attached .zip'd patch (over 10MB because of the 4 languages' Lin
[
https://issues.apache.org/jira/browse/LUCENE-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795918#action_12795918
]
Robert Muir commented on LUCENE-2034:
-
I am going to look at this one last time and co
[
https://issues.apache.org/jira/browse/LUCENE-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2187:
Attachment: scoring.pdf
document with some simple results from the 3 collections i tested thus far
improve lucene's similarity algorithm defaults
--
Key: LUCENE-2187
URL: https://issues.apache.org/jira/browse/LUCENE-2187
Project: Lucene - Java
Issue Type: Improvement
Components: Query/
[
https://issues.apache.org/jira/browse/LUCENE-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795897#action_12795897
]
Uwe Schindler commented on LUCENE-2186:
---
Is this patch for flex, as it contains Code
[
https://issues.apache.org/jira/browse/LUCENE-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795895#action_12795895
]
Chris Male commented on LUCENE-2147:
Okay, I will remove them from the other patches a
[
https://issues.apache.org/jira/browse/LUCENE-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795892#action_12795892
]
Simon Willnauer commented on LUCENE-2147:
-
{quote}
I'd say that we remove the flux
[
https://issues.apache.org/jira/browse/LUCENE-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795885#action_12795885
]
Robert Muir commented on LUCENE-2034:
-
Ah I see, you are right. This getStopWordSet()
[
https://issues.apache.org/jira/browse/LUCENE-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795882#action_12795882
]
Simon Willnauer commented on LUCENE-2034:
-
Robert, I see what you are alluding to.
[
https://issues.apache.org/jira/browse/LUCENE-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2186:
---
Attachment: LUCENE-2186.patch
> First cut at column-stride fields (index values stor
First cut at column-stride fields (index values storage)
Key: LUCENE-2186
URL: https://issues.apache.org/jira/browse/LUCENE-2186
Project: Lucene - Java
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/LUCENE-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795861#action_12795861
]
Toke Eskildsen commented on LUCENE-1990:
The first section if for 1M values in the
On Jan 2, 2010, at 7:46 AM, Robert Muir wrote:
>> I also want backward compatibility. Or at least control over it. That is, I
>> need for indexes to work fully but want an easy path to upgrade/replace an
>> index with better analyzer/filter combos. This stemmer is not backward
>> compatible.
>
[
https://issues.apache.org/jira/browse/LUCENE-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795860#action_12795860
]
Robert Muir commented on LUCENE-2034:
-
I am back on a real computer and (as mentioned
[
https://issues.apache.org/jira/browse/LUCENE-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795859#action_12795859
]
Chris Male commented on LUCENE-2184:
I agree. I will build a patch to that effect unl
> I also want backward compatibility. Or at least control over it. That is, I
> need for indexes to work fully but want an easy path to upgrade/replace an
> index with better analyzer/filter combos. This stemmer is not backward
> compatible.
But the Analyzers can be (we can have the old stemmer
Just my 2 cents from a user perspective to the whole thread:
I want the best and an easy way to identify the best. Preferably, it will be
the default by current version.
The best should also have the best name. Because of the backward compatibility
policy, we're painted into a box, into name hel
[
https://issues.apache.org/jira/browse/LUCENE-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795858#action_12795858
]
Grant Ingersoll commented on LUCENE-2147:
-
I'd say that we remove the flux warning
[
https://issues.apache.org/jira/browse/LUCENE-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795857#action_12795857
]
Grant Ingersoll commented on LUCENE-2184:
-
I think the API should pass in the max
GenitiveSwedishStemmer? Not perfect, but it puts the focus on what was
improved.
On Jan 2, 2010, at 6:10 AM, Karl Wettin wrote:
>
> 1 jan 2010 kl. 14.28 skrev Grant Ingersoll:
>
>> Please, no Swedish2 or any variant like that. How about something that
>> let's users know what it is and why
1 jan 2010 kl. 14.28 skrev Grant Ingersoll:
Please, no Swedish2 or any variant like that. How about something
that let's users know what it is and why they should use it?
In my view Swedish2 is a better name than
MoreSupportForGenitiveCaseSufficesThanSwedishStemmer. Such a name can
turn
I'm actually not sure I understand the question. Afaik backwards
compatibillity with the current SwedishStemmer could only be acheived
by stemming using both classes and make diffing output synonyms.
I just did a bit of testing and the problems I've identified in 1515
is also available in S
22 matches
Mail list logo
