[jira] Commented: (LUCENE-1995) ArrayIndexOutOfBoundsException during indexing
[ https://issues.apache.org/jira/browse/LUCENE-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12767541#action_12767541 ] Aaron McKee commented on LUCENE-1995: - I make no claims to the reasonableness of these settings, I only recently began efforts to tune our prototype. =) useCompoundFile: false mergeFactor: 10 maxBufferedDocs: 500 ramBufferSizeMB: 8192 maxFieldLength: 1 reopenReaders: true My system has 24gb and my index is typically ~16gb, so I set some of these values a bit high. If the ram buffer is being indexed with an int, that could certainly be my issue; I feel a bit silly for not having thought of that, already. I'll try setting it down to 2048 and see if the problem disappears. ArrayIndexOutOfBoundsException during indexing -- Key: LUCENE-1995 URL: https://issues.apache.org/jira/browse/LUCENE-1995 Project: Lucene - Java Issue Type: Bug Components: Index Affects Versions: 2.9 Reporter: Yonik Seeley Fix For: 2.9.1 http://search.lucidimagination.com/search/document/f29fc52348ab9b63/arrayindexoutofboundsexception_during_indexing -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
[jira] Created: (LUCENE-1949) FilterManager uses unsafe keys for its filter cache
FilterManager uses unsafe keys for its filter cache --- Key: LUCENE-1949 URL: https://issues.apache.org/jira/browse/LUCENE-1949 Project: Lucene - Java Issue Type: Bug Components: Search Affects Versions: 2.9 Reporter: Aaron McKee Priority: Minor re: FilterManager.getFilter(Filter filter) FilterManager is using the filter's hash code as the key to its filter cache, however hash codes are intrinsically not guaranteed to be distinct; different filters may hash to the same value. Although the chance of a conflict is hopefully low, given reasonable implementations of hashCode, it's certainly not impossible. When a conflict does occur, an unintended filter may be returned. I'm unaware to what extent this class is actively being used, but noticed the issue during a code browse and thought I'd at least mention it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
