[
https://issues.apache.org/jira/browse/LUCENE-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-1550:
Priority: Minor (was: Major)
not major
> Add N-Gram String Matching for Spell Checking
>
[
https://issues.apache.org/jira/browse/LUCENE-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated LUCENE-1516:
-
Attachment: LUCENE-1516.patch
* In IW.checkpoint, SegmentReaderPool.closeUnusedSegmentRe
[
https://issues.apache.org/jira/browse/LUCENE-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated LUCENE-1516:
-
Attachment: LUCENE-1516.patch
- Most tests pass. Because SegmentReaders are held by the
I've built the release artifacts, derived from revision 749403 on the
2.4 branch. Here are the changes:
http://people.apache.org/~mikemccand/staging-area/lucene2.4.1changes/Changes.html
Please vote to release these artifacts as 2.4.1:
http://people.apache.org/~mikemccand/staging-area/luc
My opinion is that if you want to enable sorting on multi-term fields,
you need a pluggable selection policy. I see someone wanting
biggest/smallest term represent a document when sorting. Or maybe a
function of the terms.
On Mon, Mar 2, 2009 at 20:34, Uwe Schindler wrote:
> I updated yesterday h
[
https://issues.apache.org/jira/browse/LUCENE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678045#action_12678045
]
Ning Li commented on LUCENE-1541:
-
An index size comparison will be great.
> Trie range -
I updated yesterday https://issues.apache.org/jira/browse/LUCENE-1372 (added
a relates), but my comment was not posted to this list (maybe relation
updates in JIRA issues will not post to java-dev?).
When working with Shalin Shekhar Mangar on SOLR-940 (where sorting of
TrieRange fields is needed),
I plan to start the release process shortly!
Mike
-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
Is it possible you accidentally allow two writers to try to open the
index?
That would explain this failure; the 2nd writer would fail to acquire
the lock, because the first writer has the index open.
Or, is it possible you're not closing a previously opened writer?
Mike
Ketan Deshpande
[
https://issues.apache.org/jira/browse/LUCENE-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1186.
Resolution: Fixed
> [PATCH] Clear ThreadLocal instances in close()
> -
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1486:
-
Attachment: TestComplexPhraseQuery.java
Updated Junit test to test for phrases with clauses that
Hi,
I am fairly new to Lucene, so forgive my elaborate explanation. We were
facing frequent issues with Lucene 1.2 (Unreleased write.lock() files). To
overcome the same, we have recently upgraded to Lucene 2.3.2 - however, we
observed the following LockObtainFailedException exception during
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1486:
-
Attachment: (was: TestComplexPhraseQuery.java)
> Wildcards, ORs etc inside Phrase queries
>
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1486:
-
Attachment: ComplexPhraseQueryParser.java
Updated to cater for phrase clauses that produce no ma
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1486:
-
Attachment: (was: ComplexPhraseQueryParser.java)
> Wildcards, ORs etc inside Phrase queries
[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677991#action_12677991
]
Mark Harwood commented on LUCENE-1500:
--
I struggle to see why endOffset Highlighter t
[
https://issues.apache.org/jira/browse/LUCENE-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1551:
---
Fix Version/s: 2.9
> Add reopen(IndexCommit) methods to IndexReader
> --
[
https://issues.apache.org/jira/browse/LUCENE-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1551:
--
Assignee: Michael McCandless
> Add reopen(IndexCommit) methods to IndexReader
Super, thanks!
Mike
Danil ŢORIN wrote:
https://issues.apache.org/jira/browse/LUCENE-1551
On Mon, Mar 2, 2009 at 13:40, Michael McCandless
wrote:
Ahh good point, that is missing. Can you open a Jira issue? Thanks.
Mike
Danil ŢORIN wrote:
I'm more interested in reopen(IndexCommit) so
Add reopen(IndexCommit) methods to IndexReader
--
Key: LUCENE-1551
URL: https://issues.apache.org/jira/browse/LUCENE-1551
Project: Lucene - Java
Issue Type: Improvement
Components: Index
https://issues.apache.org/jira/browse/LUCENE-1551
On Mon, Mar 2, 2009 at 13:40, Michael McCandless
wrote:
>
> Ahh good point, that is missing. Can you open a Jira issue? Thanks.
>
> Mike
>
> Danil ŢORIN wrote:
>
>> I'm more interested in reopen(IndexCommit) so I could have full
>> benefits of L
[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677983#action_12677983
]
Michael McCandless commented on LUCENE-1500:
bq. What did you think of my sugg
[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677968#action_12677968
]
Mark Harwood commented on LUCENE-1500:
--
Isn't your example predicated on being given
[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1500:
---
Lucene Fields: [New, Patch Available] (was: [Patch Available, New])
Fix Version/
Ahh good point, that is missing. Can you open a Jira issue? Thanks.
Mike
Danil ŢORIN wrote:
I'm more interested in reopen(IndexCommit) so I could have full
benefits of LUCENE-1483 (faster open, warm caches, less GC and so on)
but on specific commit point.
I'm not sure it's possible in curr
[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677963#action_12677963
]
Michael McCandless commented on LUCENE-1500:
The problem is, this hits a Strin
I'm more interested in reopen(IndexCommit) so I could have full
benefits of LUCENE-1483 (faster open, warm caches, less GC and so on)
but on specific commit point.
I'm not sure it's possible in current trunk, and if we have
open(IndexCommit) & company, maybe we should also have similar set of
meth
[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677956#action_12677956
]
Mark Harwood commented on LUCENE-1500:
--
My thoughts were that this exception solely t
[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677948#action_12677948
]
Michael McCandless commented on LUCENE-1500:
Patch looks great, thanks Mark!
This is already available, as of 2.4.
Mike
Danil ŢORIN wrote:
What about opening IndexReader/Searcher on certain commit point?
Will it be implemented in 2.9?
The use-case is similar to the one Michael Busch described, only I
would like to open (or reopen) a searcher on specific commit point.
30 matches
Mail list logo
