[
https://issues.apache.org/jira/browse/LUCENE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo F. Ochoa updated LUCENE-724:
Lucene Fields: [New, Patch Available] (was: [Patch Available, New])
Affects
[
https://issues.apache.org/jira/browse/LUCENE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo F. Ochoa updated LUCENE-724:
Attachment: ojvm-09-27-07.tar.gz
This new release includes:
* Synchronized with latest
[
https://issues.apache.org/jira/browse/LUCENE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530709
]
Grant Ingersoll commented on LUCENE-724:
Is the intent of this to be committed as a contrib module (I notice
QueryParser doesn't accept empty string
---
Key: LUCENE-1006
URL: https://issues.apache.org/jira/browse/LUCENE-1006
Project: Lucene - Java
Issue Type: Bug
Reporter: Yonik Seeley
foo:
[
https://issues.apache.org/jira/browse/LUCENE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-1006:
-
Attachment: queryparser.patch
Attaching patch. Unless anyone sees a reason why should be
We were currently using lucene 1.4.3 jar for the last 1 year and have index
files with size 25gb. Now iam planning to upgrade to lucene 2.2 jar. Should
i delete all the current indexes and create new index from scratch or is it
enough to run updates to update existing index files when i have new
Flexibility to turn on/off any flush triggers
-
Key: LUCENE-1007
URL: https://issues.apache.org/jira/browse/LUCENE-1007
Project: Lucene - Java
Issue Type: Improvement
Components: Index
[
https://issues.apache.org/jira/browse/LUCENE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ning Li updated LUCENE-1007:
Attachment: LUCENE-1007.patch
Just got around to do the patch:
- The patch includes changes to
Hmmm, going from 1.4.3 to 2.2, I guess I would recommend re-
indexing. I suppose, in theory , you could go from 1.4.3 - 1.9 -
2.0 - 2.1 - 2.2 or whatever the appropriate combination of versions
is there, but if you have the option of indexing fresh in 2.2 I guess
I would do it.
Also, see
[
https://issues.apache.org/jira/browse/LUCENE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1007:
--
Assignee: Michael McCandless
Flexibility to turn on/off any flush triggers
[
https://issues.apache.org/jira/browse/LUCENE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530858
]
Michael McCandless commented on LUCENE-1007:
Thanks Ning! I will have a look at the patch.
One
[
https://issues.apache.org/jira/browse/LUCENE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530875
]
Karl Wettin commented on LUCENE-550:
Oups, the patch is of course granted ASF licence.
InstantiatedIndex -
[
https://issues.apache.org/jira/browse/LUCENE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wettin updated LUCENE-550:
---
Attachment: LUCENE-550_20070928_no_core_changes.txt
New in this patch:
* Payloads added to
[
https://issues.apache.org/jira/browse/LUCENE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ning Li updated LUCENE-1007:
Attachment: LUCENE-1007.take2.patch
Take2 counts buffered delete terms towards ram buffer used. A test
14 matches
Mail list logo