On Wed, Apr 22, 2009 at 5:12 AM, Earwin Burrfoot wrote:
> Your synonyms will break if you try searching for phrases.
> Building on your example, "food place in new york" will find nothing,
> because 'place' and 'in' share the same position.
It'd be great to get multi-word synonyms fully working.
Welcome Erick!
Because nextHighestPowerOfTwo methods are public, I think we cannot
change what they return, nor remove them. At most we could deprecate
them now (and remove in 3.0), though I think it's fine to simply keep
them around even though nothing inside Lucene uses them today: since
we are
> On Wed, Apr 22, 2009 at 5:12 AM, Earwin Burrfoot wrote:
>
>> Your synonyms will break if you try searching for phrases.
>> Building on your example, "food place in new york" will find nothing,
>> because 'place' and 'in' share the same position.
>
> It'd be great to get multi-word synonyms fully
Hi,
I was going through the Levenshtein distance code in
org.apache.lucene.search.FuzzyTermEnum.java of the 2.4.1 build. I
noticed that there can be a small, but effective optimization to the
distance calculation code (initialization). I have the code ready with
me. I can post it if anyone is inte
It'd be great to get multi-word synonyms fully working...
I agree -- this is something that seems to be useful for a wider bunch of
people.
How would you change how Lucene indexes token positions to do this "correctly"?
Kirill has some interesting points to this. I have a busy day today,
>> engine. So guys looking for "MSU CMC" really want to get "Московский
>> Государственный Университет, факультет ВМиК" and his friends.
> And? How often do they extend this particular phrase with further terms?
They don't need to. Variations of this phrase alone killed my first
several approaches
Thanks all. Despite my aesthetic preference for removing unused code,
I'm *really* not in favor of causing extra work (for myself or others) to
satisfy it .. Especially when there's reasonable expectations that the
code in question *will* be used in the foreseeable future.
Ok, I'll leave the c
[
https://issues.apache.org/jira/browse/LUCENE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701957#action_12701957
]
Paul Elschot commented on LUCENE-1252:
--
There is no patch for now.
HitCollectors sho
Eliminate synchronization contention on initial index reading in
TermInfosReader ensureIndexIsRead
---
Key: LUCENE-1609
URL: https://issues.apache.org/jira/browse/LUC
[
https://issues.apache.org/jira/browse/LUCENE-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Rosher updated LUCENE-1609:
---
Attachment: LUCENE-1609.patch
> Eliminate synchronization contention on initial index reading in
>
[
https://issues.apache.org/jira/browse/LUCENE-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701973#action_12701973
]
Uwe Schindler commented on LUCENE-1609:
---
Are you sure, this works correct? If the in
[
https://issues.apache.org/jira/browse/LUCENE-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701986#action_12701986
]
Earwin Burrfoot commented on LUCENE-1609:
-
The problem is not with indexState not
[
https://issues.apache.org/jira/browse/LUCENE-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701986#action_12701986
]
Earwin Burrfoot edited comment on LUCENE-1609 at 4/23/09 9:41 AM:
--
[
https://issues.apache.org/jira/browse/LUCENE-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701994#action_12701994
]
Uwe Schindler commented on LUCENE-1609:
---
You could fix this, if you put all these fi
[
https://issues.apache.org/jira/browse/LUCENE-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702011#action_12702011
]
Earwin Burrfoot commented on LUCENE-1609:
-
You cannot put all these fields into st
[
https://issues.apache.org/jira/browse/LUCENE-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702013#action_12702013
]
Uwe Schindler commented on LUCENE-1602:
---
Fixed the incomplete hashcode(), equals() a
[
https://issues.apache.org/jira/browse/LUCENE-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Keegan updated LUCENE-1341:
-
Attachment: lucene-1341-new-1.patch
As I was debugging a unit test for BoostingNearQuery, I disc
Just got off the train and ny to ct has a brilliant bar car, so lest I
forget:
1483 moved auto resolution from fshq to indexsearcher - which is a back
compat break if you were using a fshq without indexsearcher (Solr does
it - anyone could). Annoying. If I remember right, I did it to resolve
[
https://issues.apache.org/jira/browse/LUCENE-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702192#action_12702192
]
Otis Gospodnetic commented on LUCENE-1284:
--
Hm, I feel that because of these comm
19 matches
Mail list logo
