provide a isClosed() method in Searcher class
-
Key: LUCENE-810
URL: https://issues.apache.org/jira/browse/LUCENE-810
Project: Lucene - Java
Issue Type: New Feature
Components: Search
Public API inconsistency
Key: LUCENE-811
URL: https://issues.apache.org/jira/browse/LUCENE-811
Project: Lucene - Java
Issue Type: Bug
Components: Index
Affects Versions: 2.1
Environment: 2.1.0
[
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475002
]
Mark Miller commented on LUCENE-794:
I have a patch coming tonight. It fixes a few odd mistakes and has a little
Unable to set LockFactory implementation via
${org.apache.lucene.store.FSDirectoryLockFactoryClass}
---
Key: LUCENE-812
URL: https://issues.apache.org/jira/browse/LUCE
[
https://issues.apache.org/jira/browse/LUCENE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-812:
-
Assignee: Michael McCandless
> Unable to set LockFactory implementation via
> ${
[
https://issues.apache.org/jira/browse/LUCENE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475096
]
Michael McCandless commented on LUCENE-812:
---
The no-argument constructors for Native/SimpleFSLockFactory w
[
https://issues.apache.org/jira/browse/LUCENE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475104
]
Doug Cutting commented on LUCENE-811:
-
Rather I think we should consider making SegmentInfos package-private agai
[
https://issues.apache.org/jira/browse/LUCENE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-811:
-
Assignee: Michael McCandless
> Public API inconsistency
> ---
[
https://issues.apache.org/jira/browse/LUCENE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475121
]
Michael McCandless commented on LUCENE-811:
---
Indeed I did this as part of LUCENE-701, but I can't remember
[
https://issues.apache.org/jira/browse/LUCENE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475124
]
Michael McCandless commented on LUCENE-811:
---
Sorry, make that 2.1.1 above!
> Public API inconsistency
> --
[
https://issues.apache.org/jira/browse/LUCENE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475130
]
Hoss Man commented on LUCENE-812:
-
I'm not sure if i understand what the bug is ... as far as i can tell,
LockFactor
[
https://issues.apache.org/jira/browse/LUCENE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475132
]
Hoss Man commented on LUCENE-811:
-
since SegmentInfos is final, and all of it's methods are (at best) package
protec
[
https://issues.apache.org/jira/browse/LUCENE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475138
]
Michael McCandless commented on LUCENE-812:
---
Actually it was your response to the original proposal for the
[
https://issues.apache.org/jira/browse/LUCENE-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475141
]
Hoss Man commented on LUCENE-810:
-
please consult the java-user mailing list with questions for discussion before
op
[
https://issues.apache.org/jira/browse/LUCENE-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved LUCENE-810.
-
Resolution: Won't Fix
> provide a isClosed() method in Searcher class
> -
[
https://issues.apache.org/jira/browse/LUCENE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475150
]
Hoss Man commented on LUCENE-812:
-
> Actually it was your response to the original proposal for the LockFactory
> ch
[
https://issues.apache.org/jira/browse/LUCENE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475151
]
Matthias Kerkhoff commented on LUCENE-812:
--
>From the perspective of Lucene user I would like to add ...
- i
[
https://issues.apache.org/jira/browse/LUCENE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475168
]
Michael McCandless commented on LUCENE-812:
---
> I just entered this issue as I thought that the behaviour of
[
https://issues.apache.org/jira/browse/LUCENE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-811:
--
Attachment: LUCENE-811.patch
Attaching proposed patch to change SegmentInfos (and all o
I think the getters need to be public, as it makes many of the 'cache
by segment' code much cleaner. Currently I cannot subclass and must
replace the class in the jar because I need access to much o this
information.
Is there some reason not to make the getters be public, (or copy on
read
Actually, scratch that request. As long as they are package level, I
can put the class in the same package. Problem was that in the past
some important states fields have been private.
On Feb 22, 2007, at 4:04 PM, robert engels wrote:
I think the getters need to be public, as it makes many o
[
https://issues.apache.org/jira/browse/LUCENE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475178
]
Doug Cutting commented on LUCENE-811:
-
I think making some methods public is fine, so long as the class is kept
[
https://issues.apache.org/jira/browse/LUCENE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475193
]
Andrzej Bialecki commented on LUCENE-811:
--
I'm fine with making these classes package-private - Luke alread
[
https://issues.apache.org/jira/browse/LUCENE-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen resolved LUCENE-804.
Resolution: Fixed
Fix Version/s: 2.2
Commited this.
Fixing of contrib/db/* to have downloada
[
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-794:
---
Attachment: spanhighlighter.patch
Forget all the .java files...just get spanhighlighter.patch and app
leading wildcard's don't work with trailing wildcard
Key: LUCENE-813
URL: https://issues.apache.org/jira/browse/LUCENE-813
Project: Lucene - Java
Issue Type: Bug
Reporter: Hoss
[
https://issues.apache.org/jira/browse/LUCENE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-813:
Attachment: qp-leading-wildcard.patch
patch demonstrating problem in testcase
> leading wildcard's don't w
27 matches
Mail list logo