Questions about *using* the lucene APIs should be sent to the *user* list
... the dev list is for discusion about the development of the internals.
Please ask your question on that list, but before doing so you may want to
check out the FAQ on TooManyClauses and search the archives for
"prefix To
See http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/141/changes
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/LUCENE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510001
]
Mike Klaas commented on LUCENE-850:
---
Tim: That is typically done by adding an optional implicit phrase query:
joh
[
https://issues.apache.org/jira/browse/LUCENE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509998
]
Mike Klaas commented on LUCENE-850:
---
Hi Doron,
The main use case is the same as for documents (and to a lesser ext
Hi,
lucene documentation seems to be very confusing... here is my predicament
I have an object like the following:
public class PropertyImpl implements Property {
String id;
List names = new ArrayList();
String address = "";
String city = "";
[
https://issues.apache.org/jira/browse/LUCENE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509993
]
Tim Sturge commented on LUCENE-850:
---
I just asked for a product scored BooleanQuery on java-users and Mike pointed
[
https://issues.apache.org/jira/browse/LUCENE-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509958
]
Mark Miller commented on LUCENE-831:
I think this patch is great. Not only does it make all of the sort caching
Ahh, right, I will update fileformats.xml & re-build html/PDF
(with Forrest 0.8) before committing.
The only downside I have now is if you do flush by RAM (which gives
best performance), you have to be very careful to work around
LUCENE-845 by also setting maxBufferedDocs to be something "around"
AnalyzingQueryParser can't work with leading wildcards.
---
Key: LUCENE-949
URL: https://issues.apache.org/jira/browse/LUCENE-949
Project: Lucene - Java
Issue Type: Bug
Components
[
https://issues.apache.org/jira/browse/LUCENE-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-948:
--
Attachment: LUCENE-948-core-2.2.0.take2.jar
LUCENE-948.take2.patch
Anot
[
https://issues.apache.org/jira/browse/LUCENE-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-948:
--
Attachment: LUCENE-948-core-2.2.0.jar
LUCENE-948.patch
Attached patch &
Mike,
Nice piece of work here. One caveat, I think you mentioned you
needed to update fileformats.xml (don't forget to generate the site
and commit those changes too), but I don't see that in the patch.
Also, do you see any downsides to this patch? Do you think it would
ever be the case
Writers on two machines over NFS can hit FNFE due to stale NFS client caching
-
Key: LUCENE-948
URL: https://issues.apache.org/jira/browse/LUCENE-948
Project: Lucene - Java
On Jul 2, 2007, at 4:18 PM, Yonik Seeley wrote:
On 7/2/07, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
2. or, at a minimum, do a tag of the trunk right before committing.
I just find explicit tags make it easier to rollback or compare diffs
if need be
You can always use an explicit revision
14 matches
Mail list logo
