[jira] [Commented] (LUCENE-6015) Revisit DocIdSetBuilder's heuristic to switch to FixedBitSet
[ https://issues.apache.org/jira/browse/LUCENE-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178115#comment-14178115 ] ASF subversion and git services commented on LUCENE-6015: - Commit 1633306 from [~jpountz] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1633306 ] LUCENE-6015: DocIdSetBuilder: Use the sparse set until more than 1/16 of the longs have one bit set. > Revisit DocIdSetBuilder's heuristic to switch to FixedBitSet > > > Key: LUCENE-6015 > URL: https://issues.apache.org/jira/browse/LUCENE-6015 > Project: Lucene - Core > Issue Type: Bug >Reporter: Adrien Grand >Assignee: Adrien Grand >Priority: Minor > Attachments: LUCENE-6015.patch > > > DocIdSetBuilder starts with a SparseFixedBitSet and then upgrades to a > FixedBitSet when the cardinality grows larger than maxDoc >>> 14. However > Robert improved SparseFixedBitSet performance quite significantly in > LUCENE-6003 so we should see if it makes sense to update this heuristic. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Resolved] (LUCENE-5889) AnalyzingInfixSuggester should expose commit()
[ https://issues.apache.org/jira/browse/LUCENE-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-5889. Resolution: Fixed > AnalyzingInfixSuggester should expose commit() > -- > > Key: LUCENE-5889 > URL: https://issues.apache.org/jira/browse/LUCENE-5889 > Project: Lucene - Core > Issue Type: Improvement > Components: modules/spellchecker >Reporter: Mike Sokolov > Fix For: 5.0, Trunk > > Attachments: LUCENE-5889.patch, LUCENE-5889.patch > > > There is no way short of close() for a user of AnalyzingInfixSuggester to > cause it to commit() its underlying index: only refresh() is provided. But > callers might want to ensure the index is flushed to disk without closing. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-6015) Revisit DocIdSetBuilder's heuristic to switch to FixedBitSet
[ https://issues.apache.org/jira/browse/LUCENE-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178114#comment-14178114 ] ASF subversion and git services commented on LUCENE-6015: - Commit 1633305 from [~jpountz] in branch 'dev/trunk' [ https://svn.apache.org/r1633305 ] LUCENE-6015: DocIdSetBuilder: Use the sparse set until more than 1/16 of the longs have one bit set. > Revisit DocIdSetBuilder's heuristic to switch to FixedBitSet > > > Key: LUCENE-6015 > URL: https://issues.apache.org/jira/browse/LUCENE-6015 > Project: Lucene - Core > Issue Type: Bug >Reporter: Adrien Grand >Assignee: Adrien Grand >Priority: Minor > Attachments: LUCENE-6015.patch > > > DocIdSetBuilder starts with a SparseFixedBitSet and then upgrades to a > FixedBitSet when the cardinality grows larger than maxDoc >>> 14. However > Robert improved SparseFixedBitSet performance quite significantly in > LUCENE-6003 so we should see if it makes sense to update this heuristic. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (LUCENE-6016) Stempel converts trailing 1 (and prior character) to ć
Jeff Stein created LUCENE-6016: -- Summary: Stempel converts trailing 1 (and prior character) to ć Key: LUCENE-6016 URL: https://issues.apache.org/jira/browse/LUCENE-6016 Project: Lucene - Core Issue Type: Bug Components: modules/analysis Affects Versions: 4.8.1 Reporter: Jeff Stein In the stempel analysis module, the StempelFilter TokenFilter converts a trailing numeric one into a ć character, while also consuming the prior character. This was also filed against the downstream [elasticsearch-analysis-stempel project|https://github.com/elasticsearch/elasticsearch-analysis-stempel/issues/31]. I did not find any errors with other numbers in the trailing position. Example: || input || output || | foo1 | foć | | foo11 | fooć | -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-6013) Remove IndexableFieldType.indexed()
[ https://issues.apache.org/jira/browse/LUCENE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178088#comment-14178088 ] ASF subversion and git services commented on LUCENE-6013: - Commit 1633296 from [~mikemccand] in branch 'dev/trunk' [ https://svn.apache.org/r1633296 ] LUCENE-6013: remove IndexableFieldType.indexed and FieldInfo.indexed (it's redundant with IndexOptions != null) > Remove IndexableFieldType.indexed() > --- > > Key: LUCENE-6013 > URL: https://issues.apache.org/jira/browse/LUCENE-6013 > Project: Lucene - Core > Issue Type: Improvement >Reporter: Michael McCandless >Assignee: Michael McCandless > Fix For: 5.0, Trunk > > Attachments: LUCENE-6013.patch, LUCENE-6013.patch, LUCENE-6013.patch, > LUCENE-6013.patch > > > Like LUCENE-6006, here's another pre-cursor for LUCENE-6005 > ... because I think it's important to nail down Lucene's low-schema > (FieldType/FieldInfos) semantics before adding a high-schema. > IndexableFieldType.indexed() is redundant with > IndexableFieldType.indexOptions() != null, so we should remove it, > codecs shouldn't have to write/read it, high-schema should not configure it, > etc. > Similarly, the FieldInfo.indexed bit is redundant, so I removed it, but I > left the sugar API (FieldInfo.isIndexed) and implement it as just > checking IndexOptions != null. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org