[jira] Commented: (LUCENE-935) Improve maven artifacts

[ https://issues.apache.org/jira/browse/LUCENE-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531700 ] Michael Busch commented on LUCENE-935: -- Does our build machine have local access to /www/people.apache.org/mav

Exceptions in TestConcurrentMergeScheduler

Hi, I noticed the following exception in TestConcurrentMergeScheduler: [junit] Testsuite: org.apache.lucene.index.TestConcurrentMergeScheduler [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 17.765 sec [junit] - Standard Error - [junit] Excepti

[jira] Updated: (LUCENE-743) IndexReader.reopen()

[ https://issues.apache.org/jira/browse/LUCENE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Busch updated LUCENE-743: - Attachment: lucene-743-take2.patch I'm attaching a new version of the patch that has a lot of cha

using FieldCache or storing quality score in lucene term index

Hi, This is probably a question for the user list. However, as it relates to the performance issue, also Lucene index format, I think better to ask the gurus in this list ;-) In my application, I have implemented a quality score for each document. For each search performed, the relevancy score is

Re: Geographical indexing in Lucene

Quadtrees and R-trees have been used as special "domain" indexes in Oracle RDBMS for Spatial: http://www.oracle.com/technology/products/spatial/htdocs/data_sheet_9i/9iR2_spatial_ds.html Some lectures and papers: http://csiweb.ucd.ie/staff/mbertolotto/home/lecture-notes4025-07-08.htm http://ieeex

Re: Geographical indexing in Lucene

Great work, Evgeny! I'm certainly interested in this area and will be dissecting this in some detail. I've done similar work before but making use of JTS (Java Topology Suite), using the OpenGIS standards for spatial features/queries and 2-pass spatial queries (first rough pass is MBB only,

[jira] Commented: (LUCENE-994) Change defaults in IndexWriter to maximize "out of the box" performance

[ https://issues.apache.org/jira/browse/LUCENE-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531623 ] Hoss Man commented on LUCENE-994: - lucene's "commitment" to backward compatibility requires that 2.X be API compatib

Geographical indexing in Lucene

Hello, As part of my MSc project this summer I developed geoLucene, a modified version of Lucene (based on 2.3-dev checked out on 05.07) that can index geographical data using R-trees. It has been shown to be faster on geographic queries than the unmodified Lucene. The code is hosted at https://so

[jira] Commented: (LUCENE-1007) 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_12531517 ] Michael McCandless commented on LUCENE-1007: Whoa, good catch! OK I'll divide by 8. > Flexibility to t

[jira] Commented: (LUCENE-1007) 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_12531513 ] Ning Li commented on LUCENE-1007: - One more thing about the approximation of actual bytes used for buffered delete

[jira] Commented: (LUCENE-1012) Problems with maxMergeDocs parameter

[ https://issues.apache.org/jira/browse/LUCENE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531510 ] Yonik Seeley commented on LUCENE-1012: -- > We could just fix the javadocs to match the current approach? That so

[jira] Commented: (LUCENE-1013) IndexWriter.setMaxMergeDocs gives non-backwards-compatible exception "out of the box"

[ https://issues.apache.org/jira/browse/LUCENE-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531509 ] Yonik Seeley commented on LUCENE-1013: -- > fix LogByteSizeMergePolicy to allow setting of the max by either MB o

[jira] Commented: (LUCENE-1012) Problems with maxMergeDocs parameter

[ https://issues.apache.org/jira/browse/LUCENE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531440 ] Michael McCandless commented on LUCENE-1012: > - It seems that DocumentsWriter does not obey the maxMerg

[jira] Created: (LUCENE-1014) IndexWriter.optimize() does not respect maxMergeDocs

IndexWriter.optimize() does not respect maxMergeDocs Key: LUCENE-1014 URL: https://issues.apache.org/jira/browse/LUCENE-1014 Project: Lucene - Java Issue Type: Bug Components: In

[jira] Created: (LUCENE-1013) IndexWriter.setMaxMergeDocs gives non-backwards-compatible exception "out of the box"

IndexWriter.setMaxMergeDocs gives non-backwards-compatible exception "out of the box" - Key: LUCENE-1013 URL: https://issues.apache.org/jira/browse/LUCENE-1013 Projec

[jira] Commented: (LUCENE-994) Change defaults in IndexWriter to maximize "out of the box" performance

[ https://issues.apache.org/jira/browse/LUCENE-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531434 ] Michael McCandless commented on LUCENE-994: --- > It was my impression that this Lucene release would be unus

[jira] Commented: (LUCENE-994) Change defaults in IndexWriter to maximize "out of the box" performance

[ https://issues.apache.org/jira/browse/LUCENE-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531433 ] Michael McCandless commented on LUCENE-994: --- > While trying Solr with the latest Lucene, I ran into this

[jira] Commented: (LUCENE-1011) Two or more writers over NFS can cause index corruption

[ https://issues.apache.org/jira/browse/LUCENE-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531428 ] Michael McCandless commented on LUCENE-1011: > i'm not an expert on file Locking (either in Lucene, or i