[jira] [Commented] (LUCENE-5128) Calling IndexSearcher.searchAfter beyond the number of stored documents causes ArrayIndexOutOfBoundsException
[ https://issues.apache.org/jira/browse/LUCENE-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721801#comment-13721801 ] crocket commented on LUCENE-5128: - Man, I was so foolish. It was my mistake. {noformat}TopDocs searchResult=searcher.search(query, hitsPerPage, sort); for(Integer p=1; ppage; ++p) { searchResult=searcher.searchAfter( searchResult.scoreDocs[searchResult.scoreDocs.length-1], query, hitsPerPage, sort); System.out.println(searchResult.scoreDocs.length); }{noformat} In the above code snippet, searchResult.scoreDocs.length becomes 0 when I search beyond the number of documents. But my code executes searchResult.scoreDocs[searchResult.scoreDocs.length-1] even if searchResult.scoreDocs.length becomes 0. That's why I faced that exception. Sorry for that. if I reported a false issue, what issue did you solve, then? Calling IndexSearcher.searchAfter beyond the number of stored documents causes ArrayIndexOutOfBoundsException - Key: LUCENE-5128 URL: https://issues.apache.org/jira/browse/LUCENE-5128 Project: Lucene - Core Issue Type: Bug Components: core/search Affects Versions: 4.2 Reporter: crocket Assignee: Shai Erera Fix For: 5.0, 4.5 Attachments: LUCENE-5128.patch, LUCENE-5128.patch ArrayIndexOutOfBoundsException makes it harder to reason about the cause. Is there a better way to notify programmers of the cause? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-5128) Calling IndexSearcher.searchAfter beyond the number of stored documents causes ArrayIndexOutOfBoundsException
[ https://issues.apache.org/jira/browse/LUCENE-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721801#comment-13721801 ] crocket edited comment on LUCENE-5128 at 7/27/13 11:41 PM: --- Man, I was so foolish. It was my mistake. {noformat}TopDocs searchResult=searcher.search(query, hitsPerPage, sort); for(Integer p=1; ppage; ++p) { searchResult=searcher.searchAfter( searchResult.scoreDocs[searchResult.scoreDocs.length-1], query, hitsPerPage, sort); System.out.println(searchResult.scoreDocs.length); }{noformat} In the above code snippet, searchResult.scoreDocs.length becomes 0 when I search beyond the number of documents. But my code executes searchResult.scoreDocs[searchResult.scoreDocs.length-1] even after searchResult.scoreDocs.length becomes 0. That's why I faced that exception. Sorry for that. if I reported a false issue, what issue did you solve, then? was (Author: crocket): Man, I was so foolish. It was my mistake. {noformat}TopDocs searchResult=searcher.search(query, hitsPerPage, sort); for(Integer p=1; ppage; ++p) { searchResult=searcher.searchAfter( searchResult.scoreDocs[searchResult.scoreDocs.length-1], query, hitsPerPage, sort); System.out.println(searchResult.scoreDocs.length); }{noformat} In the above code snippet, searchResult.scoreDocs.length becomes 0 when I search beyond the number of documents. But my code executes searchResult.scoreDocs[searchResult.scoreDocs.length-1] even if searchResult.scoreDocs.length becomes 0. That's why I faced that exception. Sorry for that. if I reported a false issue, what issue did you solve, then? Calling IndexSearcher.searchAfter beyond the number of stored documents causes ArrayIndexOutOfBoundsException - Key: LUCENE-5128 URL: https://issues.apache.org/jira/browse/LUCENE-5128 Project: Lucene - Core Issue Type: Bug Components: core/search Affects Versions: 4.2 Reporter: crocket Assignee: Shai Erera Fix For: 5.0, 4.5 Attachments: LUCENE-5128.patch, LUCENE-5128.patch ArrayIndexOutOfBoundsException makes it harder to reason about the cause. Is there a better way to notify programmers of the cause? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-5128) Calling IndexSearcher.searchAfter beyond the number of stored documents causes ArrayIndexOutOfBoundsException
[ https://issues.apache.org/jira/browse/LUCENE-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13717621#comment-13717621 ] crocket commented on LUCENE-5128: - Wait until this weekend. I'm going to check the stacktrace this saturday. Calling IndexSearcher.searchAfter beyond the number of stored documents causes ArrayIndexOutOfBoundsException - Key: LUCENE-5128 URL: https://issues.apache.org/jira/browse/LUCENE-5128 Project: Lucene - Core Issue Type: Bug Components: core/search Affects Versions: 4.2 Reporter: crocket Assignee: Shai Erera Fix For: 5.0, 4.5 Attachments: LUCENE-5128.patch, LUCENE-5128.patch ArrayIndexOutOfBoundsException makes it harder to reason about the cause. Is there a better way to notify programmers of the cause? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (LUCENE-5128) Calling IndexSearcher.searchAfter beyond the number of stored documents causes ArrayIndexOutOfBoundsException
crocket created LUCENE-5128: --- Summary: Calling IndexSearcher.searchAfter beyond the number of stored documents causes ArrayIndexOutOfBoundsException Key: LUCENE-5128 URL: https://issues.apache.org/jira/browse/LUCENE-5128 Project: Lucene - Core Issue Type: Bug Components: core/search Affects Versions: 4.2 Reporter: crocket ArrayIndexOutOfBoundsException makes it harder to reason about the cause. Is there a better way to notify programmers of the cause? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4912) ArrayIndexOutOfBoundsException from FastCountingFacetsAggregator.java:86
[ https://issues.apache.org/jira/browse/LUCENE-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4912: Description: I have a play framework project that uses lucene, which is hosted on git://snowberry.me/ZeroIrcLog.git When I stopped a running instance of it with Ctrl+D(play framework supports this shortcut), it generated some exceptions. After then, whenever I try to run it, I see Exception in thread Thread-5 java.lang.ArrayIndexOutOfBoundsException: 2 at org.apache.lucene.facet.search.FastCountingFacetsAggregator.aggregate(FastCountingFacetsAggregator.java:86) at lucene42fix.FacetsAccumulatorWithDimensionFix.accumulate(FacetsAccumulatorWithDimensionFix.java:37) at org.apache.lucene.facet.search.FacetsCollector.getFacetResults(FacetsCollector.java:207) at org.zeroirclog.LuceneLoggerWorker.processControlMessage(LuceneLoggerWorker.java:292) at org.zeroirclog.LuceneLoggerWorker.run(LuceneLoggerWorker.java:191) at org.zeromq.ZThread$ShimThread.run(ZThread.java:48) Can you reproduce this bug? was: I have a play framework project that uses lucene. When I stopped a running instance of it with Ctrl+D(play framework supports this shortcut), it generated some exceptions. After then, whenever I try to run it, I see Exception in thread Thread-5 java.lang.ArrayIndexOutOfBoundsException: 2 at org.apache.lucene.facet.search.FastCountingFacetsAggregator.aggregate(FastCountingFacetsAggregator.java:86) at lucene42fix.FacetsAccumulatorWithDimensionFix.accumulate(FacetsAccumulatorWithDimensionFix.java:37) at org.apache.lucene.facet.search.FacetsCollector.getFacetResults(FacetsCollector.java:207) at org.zeroirclog.LuceneLoggerWorker.processControlMessage(LuceneLoggerWorker.java:292) at org.zeroirclog.LuceneLoggerWorker.run(LuceneLoggerWorker.java:191) at org.zeromq.ZThread$ShimThread.run(ZThread.java:48) Can you reproduce this bug? ArrayIndexOutOfBoundsException from FastCountingFacetsAggregator.java:86 Key: LUCENE-4912 URL: https://issues.apache.org/jira/browse/LUCENE-4912 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical I have a play framework project that uses lucene, which is hosted on git://snowberry.me/ZeroIrcLog.git When I stopped a running instance of it with Ctrl+D(play framework supports this shortcut), it generated some exceptions. After then, whenever I try to run it, I see Exception in thread Thread-5 java.lang.ArrayIndexOutOfBoundsException: 2 at org.apache.lucene.facet.search.FastCountingFacetsAggregator.aggregate(FastCountingFacetsAggregator.java:86) at lucene42fix.FacetsAccumulatorWithDimensionFix.accumulate(FacetsAccumulatorWithDimensionFix.java:37) at org.apache.lucene.facet.search.FacetsCollector.getFacetResults(FacetsCollector.java:207) at org.zeroirclog.LuceneLoggerWorker.processControlMessage(LuceneLoggerWorker.java:292) at org.zeroirclog.LuceneLoggerWorker.run(LuceneLoggerWorker.java:191) at org.zeromq.ZThread$ShimThread.run(ZThread.java:48) Can you reproduce this bug? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (LUCENE-4912) ArrayIndexOutOfBoundsException from FastCountingFacetsAggregator.java:86
crocket created LUCENE-4912: --- Summary: ArrayIndexOutOfBoundsException from FastCountingFacetsAggregator.java:86 Key: LUCENE-4912 URL: https://issues.apache.org/jira/browse/LUCENE-4912 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical I have a play framework project that uses lucene. When I stopped a running instance of it with Ctrl+D(play framework supports this shortcut), it generated some exceptions. After then, whenever I try to run it, I see Exception in thread Thread-5 java.lang.ArrayIndexOutOfBoundsException: 2 at org.apache.lucene.facet.search.FastCountingFacetsAggregator.aggregate(FastCountingFacetsAggregator.java:86) at lucene42fix.FacetsAccumulatorWithDimensionFix.accumulate(FacetsAccumulatorWithDimensionFix.java:37) at org.apache.lucene.facet.search.FacetsCollector.getFacetResults(FacetsCollector.java:207) at org.zeroirclog.LuceneLoggerWorker.processControlMessage(LuceneLoggerWorker.java:292) at org.zeroirclog.LuceneLoggerWorker.run(LuceneLoggerWorker.java:191) at org.zeromq.ZThread$ShimThread.run(ZThread.java:48) Can you reproduce this bug? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4912) ArrayIndexOutOfBoundsException from FastCountingFacetsAggregator.java:86
[ https://issues.apache.org/jira/browse/LUCENE-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4912: Priority: Blocker (was: Critical) ArrayIndexOutOfBoundsException from FastCountingFacetsAggregator.java:86 Key: LUCENE-4912 URL: https://issues.apache.org/jira/browse/LUCENE-4912 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Blocker I have a play framework project that uses lucene, which is hosted on git://snowberry.me/ZeroIrcLog.git After stopping a running instance of it with Ctrl+D(play framework supports this shortcut), whenever I try to run it by play run, I see Exception in thread Thread-5 java.lang.ArrayIndexOutOfBoundsException: 2 at org.apache.lucene.facet.search.FastCountingFacetsAggregator.aggregate(FastCountingFacetsAggregator.java:86) at lucene42fix.FacetsAccumulatorWithDimensionFix.accumulate(FacetsAccumulatorWithDimensionFix.java:37) at org.apache.lucene.facet.search.FacetsCollector.getFacetResults(FacetsCollector.java:207) at org.zeroirclog.LuceneLoggerWorker.processControlMessage(LuceneLoggerWorker.java:292) at org.zeroirclog.LuceneLoggerWorker.run(LuceneLoggerWorker.java:191) at org.zeromq.ZThread$ShimThread.run(ZThread.java:48) Can you reproduce this bug? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4912) ArrayIndexOutOfBoundsException from FastCountingFacetsAggregator.java:86
[ https://issues.apache.org/jira/browse/LUCENE-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4912: Description: I have a play framework project that uses lucene, which is hosted on git://snowberry.me/ZeroIrcLog.git After stopping a running instance of it with Ctrl+D(play framework supports this shortcut), whenever I try to run it by play run, I see Exception in thread Thread-5 java.lang.ArrayIndexOutOfBoundsException: 2 at org.apache.lucene.facet.search.FastCountingFacetsAggregator.aggregate(FastCountingFacetsAggregator.java:86) at lucene42fix.FacetsAccumulatorWithDimensionFix.accumulate(FacetsAccumulatorWithDimensionFix.java:37) at org.apache.lucene.facet.search.FacetsCollector.getFacetResults(FacetsCollector.java:207) at org.zeroirclog.LuceneLoggerWorker.processControlMessage(LuceneLoggerWorker.java:292) at org.zeroirclog.LuceneLoggerWorker.run(LuceneLoggerWorker.java:191) at org.zeromq.ZThread$ShimThread.run(ZThread.java:48) Can you reproduce this bug? was: I have a play framework project that uses lucene, which is hosted on git://snowberry.me/ZeroIrcLog.git When I stopped a running instance of it with Ctrl+D(play framework supports this shortcut), it generated some exceptions. After then, whenever I try to run it, I see Exception in thread Thread-5 java.lang.ArrayIndexOutOfBoundsException: 2 at org.apache.lucene.facet.search.FastCountingFacetsAggregator.aggregate(FastCountingFacetsAggregator.java:86) at lucene42fix.FacetsAccumulatorWithDimensionFix.accumulate(FacetsAccumulatorWithDimensionFix.java:37) at org.apache.lucene.facet.search.FacetsCollector.getFacetResults(FacetsCollector.java:207) at org.zeroirclog.LuceneLoggerWorker.processControlMessage(LuceneLoggerWorker.java:292) at org.zeroirclog.LuceneLoggerWorker.run(LuceneLoggerWorker.java:191) at org.zeromq.ZThread$ShimThread.run(ZThread.java:48) Can you reproduce this bug? ArrayIndexOutOfBoundsException from FastCountingFacetsAggregator.java:86 Key: LUCENE-4912 URL: https://issues.apache.org/jira/browse/LUCENE-4912 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical I have a play framework project that uses lucene, which is hosted on git://snowberry.me/ZeroIrcLog.git After stopping a running instance of it with Ctrl+D(play framework supports this shortcut), whenever I try to run it by play run, I see Exception in thread Thread-5 java.lang.ArrayIndexOutOfBoundsException: 2 at org.apache.lucene.facet.search.FastCountingFacetsAggregator.aggregate(FastCountingFacetsAggregator.java:86) at lucene42fix.FacetsAccumulatorWithDimensionFix.accumulate(FacetsAccumulatorWithDimensionFix.java:37) at org.apache.lucene.facet.search.FacetsCollector.getFacetResults(FacetsCollector.java:207) at org.zeroirclog.LuceneLoggerWorker.processControlMessage(LuceneLoggerWorker.java:292) at org.zeroirclog.LuceneLoggerWorker.run(LuceneLoggerWorker.java:191) at org.zeromq.ZThread$ShimThread.run(ZThread.java:48) Can you reproduce this bug? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4912) ArrayIndexOutOfBoundsException from FastCountingFacetsAggregator.java:86
[ https://issues.apache.org/jira/browse/LUCENE-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4912: Description: I have a play framework project that uses lucene, which is hosted on git://snowberry.me/ZeroIrcLog.git After stopping a running instance of it with Ctrl+D(play framework supports this shortcut), whenever I try to run it by play run, I see Exception in thread Thread-5 java.lang.ArrayIndexOutOfBoundsException: 2 at org.apache.lucene.facet.search.FastCountingFacetsAggregator.aggregate(FastCountingFacetsAggregator.java:86) at lucene42fix.FacetsAccumulatorWithDimensionFix.accumulate(FacetsAccumulatorWithDimensionFix.java:37) at org.apache.lucene.facet.search.FacetsCollector.getFacetResults(FacetsCollector.java:207) at org.zeroirclog.LuceneLoggerWorker.processControlMessage(LuceneLoggerWorker.java:292) at org.zeroirclog.LuceneLoggerWorker.run(LuceneLoggerWorker.java:191) at org.zeromq.ZThread$ShimThread.run(ZThread.java:48) It seems TaxonomyWriter creates org.apache.lucene.store.MMapDirectory\@ instead of the actual taxonomy index directory. was: I have a play framework project that uses lucene, which is hosted on git://snowberry.me/ZeroIrcLog.git After stopping a running instance of it with Ctrl+D(play framework supports this shortcut), whenever I try to run it by play run, I see Exception in thread Thread-5 java.lang.ArrayIndexOutOfBoundsException: 2 at org.apache.lucene.facet.search.FastCountingFacetsAggregator.aggregate(FastCountingFacetsAggregator.java:86) at lucene42fix.FacetsAccumulatorWithDimensionFix.accumulate(FacetsAccumulatorWithDimensionFix.java:37) at org.apache.lucene.facet.search.FacetsCollector.getFacetResults(FacetsCollector.java:207) at org.zeroirclog.LuceneLoggerWorker.processControlMessage(LuceneLoggerWorker.java:292) at org.zeroirclog.LuceneLoggerWorker.run(LuceneLoggerWorker.java:191) at org.zeromq.ZThread$ShimThread.run(ZThread.java:48) Can you reproduce this bug? ArrayIndexOutOfBoundsException from FastCountingFacetsAggregator.java:86 Key: LUCENE-4912 URL: https://issues.apache.org/jira/browse/LUCENE-4912 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Blocker I have a play framework project that uses lucene, which is hosted on git://snowberry.me/ZeroIrcLog.git After stopping a running instance of it with Ctrl+D(play framework supports this shortcut), whenever I try to run it by play run, I see Exception in thread Thread-5 java.lang.ArrayIndexOutOfBoundsException: 2 at org.apache.lucene.facet.search.FastCountingFacetsAggregator.aggregate(FastCountingFacetsAggregator.java:86) at lucene42fix.FacetsAccumulatorWithDimensionFix.accumulate(FacetsAccumulatorWithDimensionFix.java:37) at org.apache.lucene.facet.search.FacetsCollector.getFacetResults(FacetsCollector.java:207) at org.zeroirclog.LuceneLoggerWorker.processControlMessage(LuceneLoggerWorker.java:292) at org.zeroirclog.LuceneLoggerWorker.run(LuceneLoggerWorker.java:191) at org.zeromq.ZThread$ShimThread.run(ZThread.java:48) It seems TaxonomyWriter creates org.apache.lucene.store.MMapDirectory\@ instead of the actual taxonomy index directory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Closed] (LUCENE-4912) ArrayIndexOutOfBoundsException from FastCountingFacetsAggregator.java:86
[ https://issues.apache.org/jira/browse/LUCENE-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket closed LUCENE-4912. --- Resolution: Invalid This is not an issue, but a mistake by a user ArrayIndexOutOfBoundsException from FastCountingFacetsAggregator.java:86 Key: LUCENE-4912 URL: https://issues.apache.org/jira/browse/LUCENE-4912 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Blocker I have a play framework project that uses lucene, which is hosted on git://snowberry.me/ZeroIrcLog.git After stopping a running instance of it with Ctrl+D(play framework supports this shortcut), whenever I try to run it by play run, I see Exception in thread Thread-5 java.lang.ArrayIndexOutOfBoundsException: 2 at org.apache.lucene.facet.search.FastCountingFacetsAggregator.aggregate(FastCountingFacetsAggregator.java:86) at lucene42fix.FacetsAccumulatorWithDimensionFix.accumulate(FacetsAccumulatorWithDimensionFix.java:37) at org.apache.lucene.facet.search.FacetsCollector.getFacetResults(FacetsCollector.java:207) at org.zeroirclog.LuceneLoggerWorker.processControlMessage(LuceneLoggerWorker.java:292) at org.zeroirclog.LuceneLoggerWorker.run(LuceneLoggerWorker.java:191) at org.zeromq.ZThread$ShimThread.run(ZThread.java:48) It seems TaxonomyWriter creates org.apache.lucene.store.MMapDirectory\@ instead of the actual taxonomy index directory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4912) ArrayIndexOutOfBoundsException from FastCountingFacetsAggregator.java:86
[ https://issues.apache.org/jira/browse/LUCENE-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624400#comment-13624400 ] crocket commented on LUCENE-4912: - I made a mistake by passing org.apache.lucene.store.Directory as iDir to 'categoryDir = FSDirectory.open(new File(iDir + -category));' I should have passed String instead. I'm closing this issue. ArrayIndexOutOfBoundsException from FastCountingFacetsAggregator.java:86 Key: LUCENE-4912 URL: https://issues.apache.org/jira/browse/LUCENE-4912 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Blocker I have a play framework project that uses lucene, which is hosted on git://snowberry.me/ZeroIrcLog.git After stopping a running instance of it with Ctrl+D(play framework supports this shortcut), whenever I try to run it by play run, I see Exception in thread Thread-5 java.lang.ArrayIndexOutOfBoundsException: 2 at org.apache.lucene.facet.search.FastCountingFacetsAggregator.aggregate(FastCountingFacetsAggregator.java:86) at lucene42fix.FacetsAccumulatorWithDimensionFix.accumulate(FacetsAccumulatorWithDimensionFix.java:37) at org.apache.lucene.facet.search.FacetsCollector.getFacetResults(FacetsCollector.java:207) at org.zeroirclog.LuceneLoggerWorker.processControlMessage(LuceneLoggerWorker.java:292) at org.zeroirclog.LuceneLoggerWorker.run(LuceneLoggerWorker.java:191) at org.zeromq.ZThread$ShimThread.run(ZThread.java:48) It seems TaxonomyWriter creates org.apache.lucene.store.MMapDirectory\@ instead of the actual taxonomy index directory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4894) Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations.
[ https://issues.apache.org/jira/browse/LUCENE-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620245#comment-13620245 ] crocket commented on LUCENE-4894: - However, without facet user guide, I wouldn't have known that it ever existed. You may still need to advertise the facet module in http://lucene.apache.org/core/4_x_x/index.html Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations. Key: LUCENE-4894 URL: https://issues.apache.org/jira/browse/LUCENE-4894 Project: Lucene - Core Issue Type: Bug Components: general/website, modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Minor * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. Beginners may not be able to see this until after they think through it for a long time, which most of them including me wouldn't do. However, facet user guide doesn't explain the rationale clearly. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4894) Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations.
[ https://issues.apache.org/jira/browse/LUCENE-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620245#comment-13620245 ] crocket edited comment on LUCENE-4894 at 4/2/13 8:29 PM: - However, without facet user guide, I wouldn't have known that it ever existed. You may still need to advertise the facet module in http://lucene.apache.org/core/4_x_x/index.html It's good to leave an advertisement in the core index(?) page. was (Author: crocket): However, without facet user guide, I wouldn't have known that it ever existed. You may still need to advertise the facet module in http://lucene.apache.org/core/4_x_x/index.html Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations. Key: LUCENE-4894 URL: https://issues.apache.org/jira/browse/LUCENE-4894 Project: Lucene - Core Issue Type: Bug Components: general/website, modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Minor * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. Beginners may not be able to see this until after they think through it for a long time, which most of them including me wouldn't do. However, facet user guide doesn't explain the rationale clearly. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4894) Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations.
[ https://issues.apache.org/jira/browse/LUCENE-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619601#comment-13619601 ] crocket commented on LUCENE-4894: - Including documentations in javadocs might do the job. Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations. Key: LUCENE-4894 URL: https://issues.apache.org/jira/browse/LUCENE-4894 Project: Lucene - Core Issue Type: Bug Components: general/website, modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Minor * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. Beginners may not be able to see this until after they think through it for a long time, which most of them including me wouldn't do. However, facet user guide doesn't explain the rationale clearly. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4897) Add a sugar API for traversing categories.
[ https://issues.apache.org/jira/browse/LUCENE-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619602#comment-13619602 ] crocket commented on LUCENE-4897: - I don't know much about IntIterator, but I surmise it'd do the job. Add a sugar API for traversing categories. -- Key: LUCENE-4897 URL: https://issues.apache.org/jira/browse/LUCENE-4897 Project: Lucene - Core Issue Type: Improvement Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Trivial Mike McCandless said in lucene-java-user mailing list. Maybe we could add some simple sugar APIs? Eg something like CollectionCategoryPath getChildren(int parentOrd)? (Or maybe it returns IteratorCategoryPath?) What about CollectionInteger getChildren(int parentOrd)? Integer would be more versatile and can easily be converted to CategoryPath with TaxonomyReader.getPath. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4897) Add a sugar API for traversing categories.
[ https://issues.apache.org/jira/browse/LUCENE-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619602#comment-13619602 ] crocket edited comment on LUCENE-4897 at 4/2/13 7:42 AM: - I don't know much about IntIterator, but I surmise it'll do. was (Author: crocket): I don't know much about IntIterator, but I surmise it'd do. Add a sugar API for traversing categories. -- Key: LUCENE-4897 URL: https://issues.apache.org/jira/browse/LUCENE-4897 Project: Lucene - Core Issue Type: Improvement Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Trivial Mike McCandless said in lucene-java-user mailing list. Maybe we could add some simple sugar APIs? Eg something like CollectionCategoryPath getChildren(int parentOrd)? (Or maybe it returns IteratorCategoryPath?) What about CollectionInteger getChildren(int parentOrd)? Integer would be more versatile and can easily be converted to CategoryPath with TaxonomyReader.getPath. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4897) Add a sugar API for traversing categories.
[ https://issues.apache.org/jira/browse/LUCENE-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619602#comment-13619602 ] crocket edited comment on LUCENE-4897 at 4/2/13 7:42 AM: - I don't know much about IntIterator, but I surmise it'd do. was (Author: crocket): I don't know much about IntIterator, but I surmise it'd do the job. Add a sugar API for traversing categories. -- Key: LUCENE-4897 URL: https://issues.apache.org/jira/browse/LUCENE-4897 Project: Lucene - Core Issue Type: Improvement Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Trivial Mike McCandless said in lucene-java-user mailing list. Maybe we could add some simple sugar APIs? Eg something like CollectionCategoryPath getChildren(int parentOrd)? (Or maybe it returns IteratorCategoryPath?) What about CollectionInteger getChildren(int parentOrd)? Integer would be more versatile and can easily be converted to CategoryPath with TaxonomyReader.getPath. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4897) Add a sugar API for traversing categories.
[ https://issues.apache.org/jira/browse/LUCENE-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619602#comment-13619602 ] crocket edited comment on LUCENE-4897 at 4/2/13 7:42 AM: - I don't know much about IntIterator, but I surmise it'll do good enough. was (Author: crocket): I don't know much about IntIterator, but I surmise it'll suffice. Add a sugar API for traversing categories. -- Key: LUCENE-4897 URL: https://issues.apache.org/jira/browse/LUCENE-4897 Project: Lucene - Core Issue Type: Improvement Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Trivial Mike McCandless said in lucene-java-user mailing list. Maybe we could add some simple sugar APIs? Eg something like CollectionCategoryPath getChildren(int parentOrd)? (Or maybe it returns IteratorCategoryPath?) What about CollectionInteger getChildren(int parentOrd)? Integer would be more versatile and can easily be converted to CategoryPath with TaxonomyReader.getPath. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4897) Add a sugar API for traversing categories.
[ https://issues.apache.org/jira/browse/LUCENE-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619602#comment-13619602 ] crocket edited comment on LUCENE-4897 at 4/2/13 7:42 AM: - I don't know much about IntIterator, but I surmise it'll suffice. was (Author: crocket): I don't know much about IntIterator, but I surmise it'll do. Add a sugar API for traversing categories. -- Key: LUCENE-4897 URL: https://issues.apache.org/jira/browse/LUCENE-4897 Project: Lucene - Core Issue Type: Improvement Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Trivial Mike McCandless said in lucene-java-user mailing list. Maybe we could add some simple sugar APIs? Eg something like CollectionCategoryPath getChildren(int parentOrd)? (Or maybe it returns IteratorCategoryPath?) What about CollectionInteger getChildren(int parentOrd)? Integer would be more versatile and can easily be converted to CategoryPath with TaxonomyReader.getPath. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (LUCENE-4894) Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations.
crocket created LUCENE-4894: --- Summary: Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations. Key: LUCENE-4894 URL: https://issues.apache.org/jira/browse/LUCENE-4894 Project: Lucene - Core Issue Type: Bug Components: general/website, modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Minor * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. But beginners may not be able to see this until after they think through it for a long time. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4894) Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations.
[ https://issues.apache.org/jira/browse/LUCENE-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4894: Description: * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. However, facet user guide doesn't explain the rationale clearly. But beginners may not be able to see this until after they think through it for a long time, which most of them wouldn't do. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. was: * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. But beginners may not be able to see this until after they think through it for a long time. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations. Key: LUCENE-4894 URL: https://issues.apache.org/jira/browse/LUCENE-4894 Project: Lucene - Core Issue Type: Bug Components: general/website, modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Minor * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. However, facet user guide doesn't explain the rationale clearly. But beginners may not be able to see this until after they think through it for a long time, which most of them wouldn't do. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4894) Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations.
[ https://issues.apache.org/jira/browse/LUCENE-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4894: Description: * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. Beginners may not be able to see this until after they think through it for a long time, which most of them including me wouldn't do. However, facet user guide doesn't explain the rationale clearly. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. was: * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. However, facet user guide doesn't explain the rationale clearly. But beginners may not be able to see this until after they think through it for a long time, which most of them including me wouldn't do. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations. Key: LUCENE-4894 URL: https://issues.apache.org/jira/browse/LUCENE-4894 Project: Lucene - Core Issue Type: Bug Components: general/website, modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Minor * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. Beginners may not be able to see this until after they think through it for a long time, which most of them including me wouldn't do. However, facet user guide doesn't explain the rationale clearly. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4894) Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations.
[ https://issues.apache.org/jira/browse/LUCENE-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4894: Description: * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. Beginners may not be able to see this until after they think through it for a long time, which most of them including me wouldn't do. However, facet user guide doesn't explain the rationale clearly. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. was: * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. Beginners may not be able to see this until after they think through it for a long time, which most of them including me wouldn't do. However, facet user guide doesn't explain the rationale clearly. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations. Key: LUCENE-4894 URL: https://issues.apache.org/jira/browse/LUCENE-4894 Project: Lucene - Core Issue Type: Bug Components: general/website, modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Minor * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. Beginners may not be able to see this until after they think through it for a long time, which most of them including me wouldn't do. However, facet user guide doesn't explain the rationale clearly. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4894) Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations.
[ https://issues.apache.org/jira/browse/LUCENE-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4894: Description: * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. However, facet user guide doesn't explain the rationale clearly. But beginners may not be able to see this until after they think through it for a long time, which most of them including me wouldn't do. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. was: * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. However, facet user guide doesn't explain the rationale clearly. But beginners may not be able to see this until after they think through it for a long time, which most of them wouldn't do. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. Facet User Guide for lucene 4.2 has deleted classes/methods and needs more explanations. Key: LUCENE-4894 URL: https://issues.apache.org/jira/browse/LUCENE-4894 Project: Lucene - Core Issue Type: Bug Components: general/website, modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Minor * Concurrent Indexing and Search There is no clear explanation regarding those points below. 1. TaxonomyReader should be reopened after IndexReader. 2. TaxonomyWriter should be committed before IndexWriter. TaxonomyWriter should be closed before IndexWriter. The rationale is that it's ok to see categories to which no document belongs but not ok the other way around. However, facet user guide doesn't explain the rationale clearly. But beginners may not be able to see this until after they think through it for a long time, which most of them including me wouldn't do. * DocumentBuilder FacetSearchParams.addFacetRequest They no longer exist in lucene 4.2, but they are used in code examples. * FacetResultNode.getLabel(TaxonomyReader) It doesn't eixst in 4.2, but it is mentioned in Multiple Facet Requests * ETC I don't know if there are other points to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (LUCENE-4897) Add a sugar API for retrieving child categories.
crocket created LUCENE-4897: --- Summary: Add a sugar API for retrieving child categories. Key: LUCENE-4897 URL: https://issues.apache.org/jira/browse/LUCENE-4897 Project: Lucene - Core Issue Type: Improvement Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Minor Mike McCandless said in lucene-java-user mailing list. Maybe we could add some simple sugar APIs? Eg something like CollectionCategoryPath getChildren(int parentOrd)? (Or maybe it returns IteratorCategoryPath?) What about CollectionInteger getChildren(int parentOrd)? Integer would be more versatile and can easily be converted to CategoryPath with TaxonomyReader.getPath. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4897) Add a sugar API for traversing categories.
[ https://issues.apache.org/jira/browse/LUCENE-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4897: Summary: Add a sugar API for traversing categories. (was: Add a sugar API for retrieving child categories.) Add a sugar API for traversing categories. -- Key: LUCENE-4897 URL: https://issues.apache.org/jira/browse/LUCENE-4897 Project: Lucene - Core Issue Type: Improvement Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Minor Mike McCandless said in lucene-java-user mailing list. Maybe we could add some simple sugar APIs? Eg something like CollectionCategoryPath getChildren(int parentOrd)? (Or maybe it returns IteratorCategoryPath?) What about CollectionInteger getChildren(int parentOrd)? Integer would be more versatile and can easily be converted to CategoryPath with TaxonomyReader.getPath. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4897) Add a sugar API for traversing categories.
[ https://issues.apache.org/jira/browse/LUCENE-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4897: Priority: Trivial (was: Minor) Add a sugar API for traversing categories. -- Key: LUCENE-4897 URL: https://issues.apache.org/jira/browse/LUCENE-4897 Project: Lucene - Core Issue Type: Improvement Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Trivial Mike McCandless said in lucene-java-user mailing list. Maybe we could add some simple sugar APIs? Eg something like CollectionCategoryPath getChildren(int parentOrd)? (Or maybe it returns IteratorCategoryPath?) What about CollectionInteger getChildren(int parentOrd)? Integer would be more versatile and can easily be converted to CategoryPath with TaxonomyReader.getPath. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4893) Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetsCollector.getFacetResults is called.
[ https://issues.apache.org/jira/browse/LUCENE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618308#comment-13618308 ] crocket commented on LUCENE-4893: - LUCENE-4893.patch has some typos in comments. Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetsCollector.getFacetResults is called. Key: LUCENE-4893 URL: https://issues.apache.org/jira/browse/LUCENE-4893 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Attachments: LUCENE-4893.patch In lucene 4.1, only StandardFacetsAccumulator could be instantiated. And as of lucene 4.2, it became possible to instantiate FacetsAccumulator. I invoked FacetsCollector.getFacetResults twice, and I saw doubled facet counts. If I invoke it three times, I see facet counts multiplied three times. It all happens in FacetsAccumulator.accumulate. StandardFacetsAccumulator doesn't have this bug since it frees facetArrays whenever StandardFacetsAccumulator.accumulate is called. Is it a feature or a bug? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616653#comment-13616653 ] crocket edited comment on LUCENE-4891 at 3/30/13 7:48 AM: -- I made a test with LUCENE-4882.patch applied locally and a test with OrdinalPolicy.ALL_PARENTS. Please clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it.(or visit http://gitweb.snowberry.me/?p=LuceneTest.git;a=summary and read the code) It tests lucene 4.2. * Test result 1) LUCENE-4882.patch fixes LUCENE-4891 and LUCENE-4882. 2) OrdinalPolicy.ALL_PARENTS fixes LUCENE-4891 but not LUCENE-4882. Without LUCENE-4882.patch and OrdinalPolicy.ALL_PARENTS, CountingListBuilder.build(IntsRef ordinals, IterableCategoryPath categories) removes the last element from ordinals when it meets me category. Thus, if CountingListBuilder.build is given type/CHAT, me, and network/hanirc/chan/#anything, then CountingListBuilder.build removes network/hanirc/chan/#anything but adds its parents. You could track how CountingListBuilder.build works in a debugger. I think LUCENE-4882.patch fixes LUCENE-4891, but please test git://snowberry.me/LuceneTest.git to make sure I am not wrong. was (Author: crocket): I made a test with LUCENE-4882.patch applied locally and a test with OrdinalPolicy.ALL_PARENTS. Please clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it.(or visit http://gitweb.snowberry.me/?p=LuceneTest.git;a=summary and read the code) It tests lucene 4.2. * Test result 1) LUCENE-4882.patch fixes LUCENE-4891 and LUCENE-4882. 2) OrdinalPolicy.ALL_PARENTS fixes LUCENE-4891 but not LUCENE-4882. Without LUCENE-4882.patch and OrdinalPolicy.ALL_PARENTS, CountingListBuilder.build(IntsRef ordinals, IterableCategoryPath categories) removes the last element from ordinals when it meets me category. Thus, if CountingListBuilder.build is given type/CHAT, me, and network/hanirc/chan/#anything, then CountingListBuilder.build removes network/hanirc/chan/#anything but adds its parents since network/hanirc/chan/#anything comes after me. I think LUCENE-4882.patch fixes LUCENE-4891, but please test git://snowberry.me/LuceneTest.git to make sure I am not wrong. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (LUCENE-4893) Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetCollector.getFacetResults is called.
crocket created LUCENE-4893: --- Summary: Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetCollector.getFacetResults is called. Key: LUCENE-4893 URL: https://issues.apache.org/jira/browse/LUCENE-4893 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket In lucene 4.1, only StandardFacetsAccumulator was instantiable. And FacetsAccumulator became instantiable as of lucene 4.2 I invoked FacetCollector.getFacetResults twice, and I saw doubled facet counts. If I invoke it three times, I see facet counts multiplied three times. It all happens in FacetsAccumulator.accumulate. StandardFacetsAccumulator doesn't have this bug since it frees facetArrays whenever StandardFacetsAccumulator.accumulate is called. Is it a feature or a bug? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4893) Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetCollector.getFacetResults is called.
[ https://issues.apache.org/jira/browse/LUCENE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4893: Description: In lucene 4.1, only StandardFacetsAccumulator could be instantiated. And as of lucene 4.2, it became possible to instantiate FacetsAccumulator. I invoked FacetCollector.getFacetResults twice, and I saw doubled facet counts. If I invoke it three times, I see facet counts multiplied three times. It all happens in FacetsAccumulator.accumulate. StandardFacetsAccumulator doesn't have this bug since it frees facetArrays whenever StandardFacetsAccumulator.accumulate is called. Is it a feature or a bug? was: In lucene 4.1, only StandardFacetsAccumulator was instantiable. And FacetsAccumulator became instantiable as of lucene 4.2 I invoked FacetCollector.getFacetResults twice, and I saw doubled facet counts. If I invoke it three times, I see facet counts multiplied three times. It all happens in FacetsAccumulator.accumulate. StandardFacetsAccumulator doesn't have this bug since it frees facetArrays whenever StandardFacetsAccumulator.accumulate is called. Is it a feature or a bug? Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetCollector.getFacetResults is called. --- Key: LUCENE-4893 URL: https://issues.apache.org/jira/browse/LUCENE-4893 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket In lucene 4.1, only StandardFacetsAccumulator could be instantiated. And as of lucene 4.2, it became possible to instantiate FacetsAccumulator. I invoked FacetCollector.getFacetResults twice, and I saw doubled facet counts. If I invoke it three times, I see facet counts multiplied three times. It all happens in FacetsAccumulator.accumulate. StandardFacetsAccumulator doesn't have this bug since it frees facetArrays whenever StandardFacetsAccumulator.accumulate is called. Is it a feature or a bug? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4893) Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetCollector.getFacetResults is called.
[ https://issues.apache.org/jira/browse/LUCENE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4893: Description: In lucene 4.1, only StandardFacetsAccumulator could be instantiated. And as of lucene 4.2, it became possible to instantiate FacetsAccumulator. I invoked FacetCollector.getFacetResults twice, and I saw doubled facet counts. If I invoke it three times, I see facet counts multiplied three times. It all happens in FacetsAccumulator.accumulate. StandardFacetsAccumulator doesn't have this bug since it frees facetArrays whenever StandardFacetsAccumulator.accumulate is called. Is it a feature or a bug? was: In lucene 4.1, only StandardFacetsAccumulator could be instantiated. And as of lucene 4.2, it became possible to instantiate FacetsAccumulator. I invoked FacetCollector.getFacetResults twice, and I saw doubled facet counts. If I invoke it three times, I see facet counts multiplied three times. It all happens in FacetsAccumulator.accumulate. StandardFacetsAccumulator doesn't have this bug since it frees facetArrays whenever StandardFacetsAccumulator.accumulate is called. Is it a feature or a bug? Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetCollector.getFacetResults is called. --- Key: LUCENE-4893 URL: https://issues.apache.org/jira/browse/LUCENE-4893 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket In lucene 4.1, only StandardFacetsAccumulator could be instantiated. And as of lucene 4.2, it became possible to instantiate FacetsAccumulator. I invoked FacetCollector.getFacetResults twice, and I saw doubled facet counts. If I invoke it three times, I see facet counts multiplied three times. It all happens in FacetsAccumulator.accumulate. StandardFacetsAccumulator doesn't have this bug since it frees facetArrays whenever StandardFacetsAccumulator.accumulate is called. Is it a feature or a bug? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618145#comment-13618145 ] crocket commented on LUCENE-4891: - I think, as long as I didn't make a mistake in my test, it can be resolved as duplicate of 4882. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618145#comment-13618145 ] crocket edited comment on LUCENE-4891 at 3/30/13 8:17 PM: -- I think, as long as I didn't make a mistake in my test, it can be resolved as duplicate of 4882. However, the test is repeatable. was (Author: crocket): I think, as long as I didn't make a mistake in my test, it can be resolved as duplicate of 4882. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618145#comment-13618145 ] crocket edited comment on LUCENE-4891 at 3/30/13 8:17 PM: -- I think, as long as I didn't make a mistake in my test, it can be resolved as duplicate of 4882. However, the test is reproducible. was (Author: crocket): I think, as long as I didn't make a mistake in my test, it can be resolved as duplicate of 4882. However, the test is repeatable. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4893) Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetsCollector.getFacetResults is called.
[ https://issues.apache.org/jira/browse/LUCENE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4893: Summary: Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetsCollector.getFacetResults is called. (was: Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetCollector.getFacetResults is called.) Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetsCollector.getFacetResults is called. Key: LUCENE-4893 URL: https://issues.apache.org/jira/browse/LUCENE-4893 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket In lucene 4.1, only StandardFacetsAccumulator could be instantiated. And as of lucene 4.2, it became possible to instantiate FacetsAccumulator. I invoked FacetCollector.getFacetResults twice, and I saw doubled facet counts. If I invoke it three times, I see facet counts multiplied three times. It all happens in FacetsAccumulator.accumulate. StandardFacetsAccumulator doesn't have this bug since it frees facetArrays whenever StandardFacetsAccumulator.accumulate is called. Is it a feature or a bug? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4893) Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetsCollector.getFacetResults is called.
[ https://issues.apache.org/jira/browse/LUCENE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4893: Description: In lucene 4.1, only StandardFacetsAccumulator could be instantiated. And as of lucene 4.2, it became possible to instantiate FacetsAccumulator. I invoked FacetsCollector.getFacetResults twice, and I saw doubled facet counts. If I invoke it three times, I see facet counts multiplied three times. It all happens in FacetsAccumulator.accumulate. StandardFacetsAccumulator doesn't have this bug since it frees facetArrays whenever StandardFacetsAccumulator.accumulate is called. Is it a feature or a bug? was: In lucene 4.1, only StandardFacetsAccumulator could be instantiated. And as of lucene 4.2, it became possible to instantiate FacetsAccumulator. I invoked FacetCollector.getFacetResults twice, and I saw doubled facet counts. If I invoke it three times, I see facet counts multiplied three times. It all happens in FacetsAccumulator.accumulate. StandardFacetsAccumulator doesn't have this bug since it frees facetArrays whenever StandardFacetsAccumulator.accumulate is called. Is it a feature or a bug? Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetsCollector.getFacetResults is called. Key: LUCENE-4893 URL: https://issues.apache.org/jira/browse/LUCENE-4893 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket In lucene 4.1, only StandardFacetsAccumulator could be instantiated. And as of lucene 4.2, it became possible to instantiate FacetsAccumulator. I invoked FacetsCollector.getFacetResults twice, and I saw doubled facet counts. If I invoke it three times, I see facet counts multiplied three times. It all happens in FacetsAccumulator.accumulate. StandardFacetsAccumulator doesn't have this bug since it frees facetArrays whenever StandardFacetsAccumulator.accumulate is called. Is it a feature or a bug? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4893) Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetsCollector.getFacetResults is called.
[ https://issues.apache.org/jira/browse/LUCENE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618147#comment-13618147 ] crocket commented on LUCENE-4893: - I assumed FacetsCollector.getFacetResults was a simple getter method, so I didn't optimize my code to call it once. After discovering LUCENE-4893, I modified my code to call it once. It may be a good idea to throw an exception or return am empty list if one calls it again. There will be only so many lucene beginners with no knowledge of its side effects. Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetsCollector.getFacetResults is called. Key: LUCENE-4893 URL: https://issues.apache.org/jira/browse/LUCENE-4893 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket In lucene 4.1, only StandardFacetsAccumulator could be instantiated. And as of lucene 4.2, it became possible to instantiate FacetsAccumulator. I invoked FacetsCollector.getFacetResults twice, and I saw doubled facet counts. If I invoke it three times, I see facet counts multiplied three times. It all happens in FacetsAccumulator.accumulate. StandardFacetsAccumulator doesn't have this bug since it frees facetArrays whenever StandardFacetsAccumulator.accumulate is called. Is it a feature or a bug? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4893) Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetsCollector.getFacetResults is called.
[ https://issues.apache.org/jira/browse/LUCENE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618147#comment-13618147 ] crocket edited comment on LUCENE-4893 at 3/30/13 8:27 PM: -- I assumed FacetsCollector.getFacetResults was a simple getter method, so I didn't optimize my code to call it once. After discovering LUCENE-4893, I modified my code to call it once. It may be a good idea to throw an exception or return an empty list if one calls it again. There will be only so many lucene beginners with no knowledge of its side effects. was (Author: crocket): I assumed FacetsCollector.getFacetResults was a simple getter method, so I didn't optimize my code to call it once. After discovering LUCENE-4893, I modified my code to call it once. It may be a good idea to throw an exception or return am empty list if one calls it again. There will be only so many lucene beginners with no knowledge of its side effects. Facet counts in FacetsAccumulator.facetArrays are multiplied as many times as FacetsCollector.getFacetResults is called. Key: LUCENE-4893 URL: https://issues.apache.org/jira/browse/LUCENE-4893 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket In lucene 4.1, only StandardFacetsAccumulator could be instantiated. And as of lucene 4.2, it became possible to instantiate FacetsAccumulator. I invoked FacetsCollector.getFacetResults twice, and I saw doubled facet counts. If I invoke it three times, I see facet counts multiplied three times. It all happens in FacetsAccumulator.accumulate. StandardFacetsAccumulator doesn't have this bug since it frees facetArrays whenever StandardFacetsAccumulator.accumulate is called. Is it a feature or a bug? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13617968#comment-13617968 ] crocket commented on LUCENE-4891: - Update.1 In https://issues.apache.org/jira/browse/LUCENE-4882?focusedCommentId=13614616page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13614616 you mentioned that So you can choose between overriding FacetIndexParams.getCategoryListParams() to always return a CLP which specifies OP.ALL_PARENTS for all categories, or extend CLB and apply the fix locally., so I initially overrode FacetIndexParams.getCategoryListParams() to always return a CLP which specifies OP.ALL_PARENTS for all categories and thought that I applied LUCENE-4882.patch to my code. But I was wrong. Overriding FacetIndexParams.getCategoryListParams() doesn't fix this issue, but applying LUCENE-4882.patch except the part for TestFacetsCollector.java locally fixes the issue completely. So I updated git://snowberry.me/LuceneTest.git to make it reflect my discovery. With LUCENE-4882.patch applied, the order of categories is not important. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13617968#comment-13617968 ] crocket edited comment on LUCENE-4891 at 3/30/13 3:29 AM: -- Update.1 In https://issues.apache.org/jira/browse/LUCENE-4882?focusedCommentId=13614616page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13614616 you mentioned that So you can choose between overriding FacetIndexParams.getCategoryListParams() to always return a CLP which specifies OP.ALL_PARENTS for all categories, or extend CLB and apply the fix locally., so I initially overrode FacetIndexParams.getCategoryListParams() and thought that I applied LUCENE-4882.patch to my code. But I was wrong. Overriding FacetIndexParams.getCategoryListParams() doesn't fix this issue, but applying LUCENE-4882.patch except the part for TestFacetsCollector.java locally fixes the issue completely. So I updated git://snowberry.me/LuceneTest.git to make it reflect my discovery. With LUCENE-4882.patch applied, the order of categories is not important. was (Author: crocket): Update.1 In https://issues.apache.org/jira/browse/LUCENE-4882?focusedCommentId=13614616page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13614616 you mentioned that So you can choose between overriding FacetIndexParams.getCategoryListParams() to always return a CLP which specifies OP.ALL_PARENTS for all categories, or extend CLB and apply the fix locally., so I initially overrode FacetIndexParams.getCategoryListParams() to always return a CLP which specifies OP.ALL_PARENTS for all categories and thought that I applied LUCENE-4882.patch to my code. But I was wrong. Overriding FacetIndexParams.getCategoryListParams() doesn't fix this issue, but applying LUCENE-4882.patch except the part for TestFacetsCollector.java locally fixes the issue completely. So I updated git://snowberry.me/LuceneTest.git to make it reflect my discovery. With LUCENE-4882.patch applied, the order of categories is not important. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Issue Comment Deleted] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4891: Comment: was deleted (was: Update.1 In https://issues.apache.org/jira/browse/LUCENE-4882?focusedCommentId=13614616page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13614616 you mentioned that So you can choose between overriding FacetIndexParams.getCategoryListParams() to always return a CLP which specifies OP.ALL_PARENTS for all categories, or extend CLB and apply the fix locally., so I initially overrode FacetIndexParams.getCategoryListParams() and thought that I applied LUCENE-4882.patch to my code. But I was wrong. Overriding FacetIndexParams.getCategoryListParams() doesn't fix this issue, but applying LUCENE-4882.patch except the part for TestFacetsCollector.java locally fixes the issue completely. So I updated git://snowberry.me/LuceneTest.git to make it reflect my discovery. With LUCENE-4882.patch applied, the order of categories is not important.) Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616653#comment-13616653 ] crocket edited comment on LUCENE-4891 at 3/30/13 5:35 AM: -- I made a test with LUCENE-4882.patch applied locally and a test with OrdinalPolicy.ALL_PARENTS. Please clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2. ** Test result 1) LUCENE-4882.patch fixes LUCENE-4891 and LUCENE-4882. 2) OrdinalPolicy.ALL_PARENTS fixes LUCENE-4891 but not LUCENE-4882. Without LUCENE-4882.patch and OrdinalPolicy.ALL_PARENTS, CountingListBuilder.build(IntsRef ordinals, IterableCategoryPath categories) removes the last element from ordinals when it meets me category. Thus, CountingListBuilder.build removes network/hanirc/chan/#anything but adds its parents if network/hanirc/chan/#anything comes after me. I think LUCENE-4882.patch fixes this, but please test git://snowberry.me/LuceneTest.git to make sure I am not wrong. was (Author: crocket): I made a test with LUCENE-4882.patch applied locally and a test with OrdinalPolicy.ALL_PARENTS. Please clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2. ** Test result ** 1) LUCENE-4882.patch fixes LUCENE-4891 and LUCENE-4882. 2) OrdinalPolicy.ALL_PARENTS fixes LUCENE-4891 but not LUCENE-4882. Without LUCENE-4882.patch and OrdinalPolicy.ALL_PARENTS, CountingListBuilder.build(IntsRef ordinals, IterableCategoryPath categories) removes the last element from ordinals when it meets me category. Thus, CountingListBuilder.build removes network/hanirc/chan/#anything but adds its parents if network/hanirc/chan/#anything comes after me. I think LUCENE-4882.patch fixes this, but please test git://snowberry.me/LuceneTest.git to make sure I am not wrong. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616653#comment-13616653 ] crocket edited comment on LUCENE-4891 at 3/30/13 5:35 AM: -- I made a test with LUCENE-4882.patch applied locally and a test with OrdinalPolicy.ALL_PARENTS. Please clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2. ** Test result ** 1) LUCENE-4882.patch fixes LUCENE-4891 and LUCENE-4882. 2) OrdinalPolicy.ALL_PARENTS fixes LUCENE-4891 but not LUCENE-4882. Without LUCENE-4882.patch and OrdinalPolicy.ALL_PARENTS, CountingListBuilder.build(IntsRef ordinals, IterableCategoryPath categories) removes the last element from ordinals when it meets me category. Thus, CountingListBuilder.build removes network/hanirc/chan/#anything but adds its parents if network/hanirc/chan/#anything comes after me. I think LUCENE-4882.patch fixes this, but please test git://snowberry.me/LuceneTest.git to make sure I am not wrong. was (Author: crocket): I made tests for LUCENE-4882 and me. You can clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2, and the test result is that the presence of LUCENE-4882 doesn't make a difference and that network/hanirc/chan/#sdgsdgsd is added as network/hanirc/chan with the presence of me category. Actually, according to my test, any category after me in a list is added with the tail element removed. For example, if network/hanirc/chan comes after me, it is added as network/hanirc Is any of my tests incorrect? Please tell me more about it. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616653#comment-13616653 ] crocket edited comment on LUCENE-4891 at 3/30/13 5:35 AM: -- I made a test with LUCENE-4882.patch applied locally and a test with OrdinalPolicy.ALL_PARENTS. Please clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2. * Test result 1) LUCENE-4882.patch fixes LUCENE-4891 and LUCENE-4882. 2) OrdinalPolicy.ALL_PARENTS fixes LUCENE-4891 but not LUCENE-4882. Without LUCENE-4882.patch and OrdinalPolicy.ALL_PARENTS, CountingListBuilder.build(IntsRef ordinals, IterableCategoryPath categories) removes the last element from ordinals when it meets me category. Thus, CountingListBuilder.build removes network/hanirc/chan/#anything but adds its parents if network/hanirc/chan/#anything comes after me. I think LUCENE-4882.patch fixes this, but please test git://snowberry.me/LuceneTest.git to make sure I am not wrong. was (Author: crocket): I made a test with LUCENE-4882.patch applied locally and a test with OrdinalPolicy.ALL_PARENTS. Please clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2. ** Test result 1) LUCENE-4882.patch fixes LUCENE-4891 and LUCENE-4882. 2) OrdinalPolicy.ALL_PARENTS fixes LUCENE-4891 but not LUCENE-4882. Without LUCENE-4882.patch and OrdinalPolicy.ALL_PARENTS, CountingListBuilder.build(IntsRef ordinals, IterableCategoryPath categories) removes the last element from ordinals when it meets me category. Thus, CountingListBuilder.build removes network/hanirc/chan/#anything but adds its parents if network/hanirc/chan/#anything comes after me. I think LUCENE-4882.patch fixes this, but please test git://snowberry.me/LuceneTest.git to make sure I am not wrong. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616653#comment-13616653 ] crocket edited comment on LUCENE-4891 at 3/30/13 5:38 AM: -- I made a test with LUCENE-4882.patch applied locally and a test with OrdinalPolicy.ALL_PARENTS. Please clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2. * Test result 1) LUCENE-4882.patch fixes LUCENE-4891 and LUCENE-4882. 2) OrdinalPolicy.ALL_PARENTS fixes LUCENE-4891 but not LUCENE-4882. Without LUCENE-4882.patch and OrdinalPolicy.ALL_PARENTS, CountingListBuilder.build(IntsRef ordinals, IterableCategoryPath categories) removes the last element from ordinals when it meets me category. Thus, if CountingListBuilder.build is given type/CHAT, me, and network/hanirc/chan/#anything, then CountingListBuilder.build removes network/hanirc/chan/#anything but adds its parents since network/hanirc/chan/#anything comes after me. I think LUCENE-4882.patch fixes LUCENE-4891, but please test git://snowberry.me/LuceneTest.git to make sure I am not wrong. was (Author: crocket): I made a test with LUCENE-4882.patch applied locally and a test with OrdinalPolicy.ALL_PARENTS. Please clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2. * Test result 1) LUCENE-4882.patch fixes LUCENE-4891 and LUCENE-4882. 2) OrdinalPolicy.ALL_PARENTS fixes LUCENE-4891 but not LUCENE-4882. Without LUCENE-4882.patch and OrdinalPolicy.ALL_PARENTS, CountingListBuilder.build(IntsRef ordinals, IterableCategoryPath categories) removes the last element from ordinals when it meets me category. Thus, if CountingListBuilder.build is given type/CHAT, me, and network/hanirc/chan/#anything, then CountingListBuilder.build removes network/hanirc/chan/#anything but adds its parents since network/hanirc/chan/#anything comes after me. I think LUCENE-4882.patch fixes this, but please test git://snowberry.me/LuceneTest.git to make sure I am not wrong. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616653#comment-13616653 ] crocket edited comment on LUCENE-4891 at 3/30/13 5:37 AM: -- I made a test with LUCENE-4882.patch applied locally and a test with OrdinalPolicy.ALL_PARENTS. Please clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2. * Test result 1) LUCENE-4882.patch fixes LUCENE-4891 and LUCENE-4882. 2) OrdinalPolicy.ALL_PARENTS fixes LUCENE-4891 but not LUCENE-4882. Without LUCENE-4882.patch and OrdinalPolicy.ALL_PARENTS, CountingListBuilder.build(IntsRef ordinals, IterableCategoryPath categories) removes the last element from ordinals when it meets me category. Thus, if CountingListBuilder.build is given type/CHAT, me, and network/hanirc/chan/#anything, then CountingListBuilder.build removes network/hanirc/chan/#anything but adds its parents since network/hanirc/chan/#anything comes after me. I think LUCENE-4882.patch fixes this, but please test git://snowberry.me/LuceneTest.git to make sure I am not wrong. was (Author: crocket): I made a test with LUCENE-4882.patch applied locally and a test with OrdinalPolicy.ALL_PARENTS. Please clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2. * Test result 1) LUCENE-4882.patch fixes LUCENE-4891 and LUCENE-4882. 2) OrdinalPolicy.ALL_PARENTS fixes LUCENE-4891 but not LUCENE-4882. Without LUCENE-4882.patch and OrdinalPolicy.ALL_PARENTS, CountingListBuilder.build(IntsRef ordinals, IterableCategoryPath categories) removes the last element from ordinals when it meets me category. Thus, CountingListBuilder.build removes network/hanirc/chan/#anything but adds its parents if network/hanirc/chan/#anything comes after me. I think LUCENE-4882.patch fixes this, but please test git://snowberry.me/LuceneTest.git to make sure I am not wrong. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616653#comment-13616653 ] crocket edited comment on LUCENE-4891 at 3/30/13 5:47 AM: -- I made a test with LUCENE-4882.patch applied locally and a test with OrdinalPolicy.ALL_PARENTS. Please clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it.(or visit http://gitweb.snowberry.me/?p=LuceneTest.git;a=summary and read the code) It tests lucene 4.2. * Test result 1) LUCENE-4882.patch fixes LUCENE-4891 and LUCENE-4882. 2) OrdinalPolicy.ALL_PARENTS fixes LUCENE-4891 but not LUCENE-4882. Without LUCENE-4882.patch and OrdinalPolicy.ALL_PARENTS, CountingListBuilder.build(IntsRef ordinals, IterableCategoryPath categories) removes the last element from ordinals when it meets me category. Thus, if CountingListBuilder.build is given type/CHAT, me, and network/hanirc/chan/#anything, then CountingListBuilder.build removes network/hanirc/chan/#anything but adds its parents since network/hanirc/chan/#anything comes after me. I think LUCENE-4882.patch fixes LUCENE-4891, but please test git://snowberry.me/LuceneTest.git to make sure I am not wrong. was (Author: crocket): I made a test with LUCENE-4882.patch applied locally and a test with OrdinalPolicy.ALL_PARENTS. Please clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2. * Test result 1) LUCENE-4882.patch fixes LUCENE-4891 and LUCENE-4882. 2) OrdinalPolicy.ALL_PARENTS fixes LUCENE-4891 but not LUCENE-4882. Without LUCENE-4882.patch and OrdinalPolicy.ALL_PARENTS, CountingListBuilder.build(IntsRef ordinals, IterableCategoryPath categories) removes the last element from ordinals when it meets me category. Thus, if CountingListBuilder.build is given type/CHAT, me, and network/hanirc/chan/#anything, then CountingListBuilder.build removes network/hanirc/chan/#anything but adds its parents since network/hanirc/chan/#anything comes after me. I think LUCENE-4882.patch fixes LUCENE-4891, but please test git://snowberry.me/LuceneTest.git to make sure I am not wrong. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616092#comment-13616092 ] crocket edited comment on LUCENE-4891 at 3/28/13 6:13 AM: -- You should have written Arrays.asList( new CategoryPath(type, CHAT), new CategoryPath(me), new CategoryPath(network, hanirc, chan, #sdgsdgsd) ) That's what I used. How's the result with my code? was (Author: crocket): You should have written Arrays.asList( new CategoryPath(type, CHAT), new CategoryPath(me), new CategoryPath(network, hanirc, chan, #sdgsdgsd) ) That's what I used. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616092#comment-13616092 ] crocket commented on LUCENE-4891: - You should have written Arrays.asList( new CategoryPath(type, CHAT), new CategoryPath(me), new CategoryPath(network, hanirc, chan, #sdgsdgsd) ) That's what I used. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616092#comment-13616092 ] crocket edited comment on LUCENE-4891 at 3/28/13 6:14 AM: -- You should have written Arrays.asList( new CategoryPath(type, CHAT), new CategoryPath(me), new CategoryPath(network, hanirc, chan, #sdgsdgsd) ) That's what I used. new CategoryPath(network, hanirc, chan, #sdgsdgsd) ).toString() is equal to network/hanirc/chan/#sdgsdgsd How's the result with my code? was (Author: crocket): You should have written Arrays.asList( new CategoryPath(type, CHAT), new CategoryPath(me), new CategoryPath(network, hanirc, chan, #sdgsdgsd) ) That's what I used. How's the result with my code? Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616092#comment-13616092 ] crocket edited comment on LUCENE-4891 at 3/28/13 6:15 AM: -- You should have written Arrays.asList( new CategoryPath(type, CHAT), new CategoryPath(me), new CategoryPath(network, hanirc, chan, #sdgsdgsd) ) That's what I used, and I have this issue on lucene 4.2 new CategoryPath(network, hanirc, chan, #sdgsdgsd) ).toString() is equal to network/hanirc/chan/#sdgsdgsd How's the result with my code? was (Author: crocket): You should have written Arrays.asList( new CategoryPath(type, CHAT), new CategoryPath(me), new CategoryPath(network, hanirc, chan, #sdgsdgsd) ) That's what I used. new CategoryPath(network, hanirc, chan, #sdgsdgsd) ).toString() is equal to network/hanirc/chan/#sdgsdgsd How's the result with my code? Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616092#comment-13616092 ] crocket edited comment on LUCENE-4891 at 3/28/13 6:16 AM: -- You should have written Arrays.asList( new CategoryPath(type, CHAT), new CategoryPath(me), new CategoryPath(network, hanirc, chan, #sdgsdgsd) ) That's what I used, and I have this issue on lucene 4.2 new CategoryPath(network, hanirc, chan, #sdgsdgsd) ).toString() is equal to network/hanirc/chan/#sdgsdgsd, and I'm sorry about the confusion. How's the result with my code? was (Author: crocket): You should have written Arrays.asList( new CategoryPath(type, CHAT), new CategoryPath(me), new CategoryPath(network, hanirc, chan, #sdgsdgsd) ) That's what I used, and I have this issue on lucene 4.2 new CategoryPath(network, hanirc, chan, #sdgsdgsd) ).toString() is equal to network/hanirc/chan/#sdgsdgsd How's the result with my code? Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Issue Comment Deleted] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4891: Comment: was deleted (was: You should have written Arrays.asList( new CategoryPath(type, CHAT), new CategoryPath(me), new CategoryPath(network, hanirc, chan, #sdgsdgsd) ) That's what I used, and I have this issue on lucene 4.2 new CategoryPath(network, hanirc, chan, #sdgsdgsd) ).toString() is equal to network/hanirc/chan/#sdgsdgsd, and I'm sorry about the confusion. How's the result with my code?) Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616653#comment-13616653 ] crocket commented on LUCENE-4891: - I made tests for LUCENE-4882 and me. You can clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2, and the test result is that the presence of LUCENE-4882 doesn't make a difference and that network/hanirc/chan/#sdgsdgsd is added as network/hanirc/chan with the presence of me category. Is any of my test incorrect? Please tell me more about it. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616653#comment-13616653 ] crocket edited comment on LUCENE-4891 at 3/28/13 9:48 PM: -- I made tests for LUCENE-4882 and me. You can clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2, and the test result is that the presence of LUCENE-4882 doesn't make a difference and that network/hanirc/chan/#sdgsdgsd is added as network/hanirc/chan with the presence of me category. Is any of my tests incorrect? Please tell me more about it. was (Author: crocket): I made tests for LUCENE-4882 and me. You can clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2, and the test result is that the presence of LUCENE-4882 doesn't make a difference and that network/hanirc/chan/#sdgsdgsd is added as network/hanirc/chan with the presence of me category. Is any of my test incorrect? Please tell me more about it. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616653#comment-13616653 ] crocket edited comment on LUCENE-4891 at 3/28/13 11:21 PM: --- I made tests for LUCENE-4882 and me. You can clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2, and the test result is that the presence of LUCENE-4882 doesn't make a difference and that network/hanirc/chan/#sdgsdgsd is added as network/hanirc/chan with the presence of me category. Actually, according to my test, any category after me in a list is added with the tail element removed. Is any of my tests incorrect? Please tell me more about it. was (Author: crocket): I made tests for LUCENE-4882 and me. You can clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2, and the test result is that the presence of LUCENE-4882 doesn't make a difference and that network/hanirc/chan/#sdgsdgsd is added as network/hanirc/chan with the presence of me category. Is any of my tests incorrect? Please tell me more about it. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616653#comment-13616653 ] crocket edited comment on LUCENE-4891 at 3/28/13 11:22 PM: --- I made tests for LUCENE-4882 and me. You can clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2, and the test result is that the presence of LUCENE-4882 doesn't make a difference and that network/hanirc/chan/#sdgsdgsd is added as network/hanirc/chan with the presence of me category. Actually, according to my test, any category after me in a list is added with the tail element removed. For example, if network/hanirc/chan comes after me, it is added as network/hanirc Is any of my tests incorrect? Please tell me more about it. was (Author: crocket): I made tests for LUCENE-4882 and me. You can clone the tests from git://snowberry.me/LuceneTest.git and run mvn test in it. It tests lucene 4.2, and the test result is that the presence of LUCENE-4882 doesn't make a difference and that network/hanirc/chan/#sdgsdgsd is added as network/hanirc/chan with the presence of me category. Actually, according to my test, any category after me in a list is added with the tail element removed. Is any of my tests incorrect? Please tell me more about it. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4886) new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory
[ https://issues.apache.org/jira/browse/LUCENE-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13615789#comment-13615789 ] crocket commented on LUCENE-4886: - That snippet seems to work. Please mark it as resolved. new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory - Key: LUCENE-4886 URL: https://issues.apache.org/jira/browse/LUCENE-4886 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical I made a taxonomy directory with categoryDir=FSDirectory.open(new File(category)); taxoWriter=new DirectoryTaxonomyWriter(categoryDir, OpenMode.CREATE_OR_APPEND); Right after creating DirectoryTaxonomyWriter, I created a DirectoryTaxonomyReader with taxoReader=new DirectoryTaxonomyReader(categoryDir); which throws IndexNotFoundException. It used to work fine with lucene 4.1. If I invoke new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) on a new taxonomy directory, no exception is thrown. Below is the exception stack trace. org.apache.lucene.index.IndexNotFoundException: no segments* file found in org.apache.lucene.store.MMapDirectory@/home/elisa/repos/mine/ZeroIrcLog/irclog-category lockFactory=org.apache.lucene.store.NativeFSLockFactory@373983f: files: [write.lock, _0.si, _0.fnm, _0.fdt, _0_Lucene41_0.tim, _0_Lucene41_0.pos, _0.fdx, _0_Lucene41_0.doc, _0_Lucene41_0.tip] at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:741) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:52) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:65) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.openIndexReader(DirectoryTaxonomyReader.java:218) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.init(DirectoryTaxonomyReader.java:99) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.zeroirclog.LuceneLoggerWorker.init(LuceneLoggerWorker.java:141) ~[na:na] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (LUCENE-4891) Only a part of CategoryPath is recorded under a certain condition
crocket created LUCENE-4891: --- Summary: Only a part of CategoryPath is recorded under a certain condition Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] to a document and add the document to a writer as below, Only network/hanirc, not networkk/hanirc/chan/#sdgsdgsd] seems to be recorded into a taxonomy directory. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4891) Only a part of CategoryPath is recorded with me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4891: Summary: Only a part of CategoryPath is recorded with me category. (was: Only a part of CategoryPath is recorded under a certain condition) Only a part of CategoryPath is recorded with me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] to a document and add the document to a writer as below, Only network/hanirc, not networkk/hanirc/chan/#sdgsdgsd] seems to be recorded into a taxonomy directory. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4891) Only a part of CategoryPath is recorded with me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4891: Description: If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc, not networkk/hanirc/chan/#sdgsdgsd] seems to be recorded into a taxonomy directory. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? was: If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] to a document and add the document to a writer as below, Only network/hanirc, not networkk/hanirc/chan/#sdgsdgsd] seems to be recorded into a taxonomy directory. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? Only a part of CategoryPath is recorded with me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc, not networkk/hanirc/chan/#sdgsdgsd] seems to be recorded into a taxonomy directory. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4891) Only a part of CategoryPath is recorded with me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4891: Description: If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc, not networkk/hanirc/chan/#sdgsdgsd seems to be recorded into a taxonomy directory. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? was: If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc, not networkk/hanirc/chan/#sdgsdgsd] seems to be recorded into a taxonomy directory. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? Only a part of CategoryPath is recorded with me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc, not networkk/hanirc/chan/#sdgsdgsd seems to be recorded into a taxonomy directory. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4891: Summary: Only a part of CategoryPath is recorded if I add me category. (was: Only a part of CategoryPath is recorded with me category.) Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc, not networkk/hanirc/chan/#sdgsdgsd seems to be recorded into a taxonomy directory. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4891: Description: If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not networkk/hanirc/chan/#sdgsdgsd seems to be recorded into a taxonomy directory. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? was: If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc, not networkk/hanirc/chan/#sdgsdgsd seems to be recorded into a taxonomy directory. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not networkk/hanirc/chan/#sdgsdgsd seems to be recorded into a taxonomy directory. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4891: Description: If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not networkk/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? was: If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not networkk/hanirc/chan/#sdgsdgsd seems to be recorded into a taxonomy directory. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not networkk/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4891: Description: If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not networkk/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? was: If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not networkk/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, the full path of network/hanirc/chan/#sdgsdgsd is recorded. What's wrong with me category? Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not networkk/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4891: Description: If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not networkk/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. was: If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not networkk/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not networkk/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4891) Only a part of CategoryPath is recorded if I add me category.
[ https://issues.apache.org/jira/browse/LUCENE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4891: Description: If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. was: If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not networkk/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. Only a part of CategoryPath is recorded if I add me category. --- Key: LUCENE-4891 URL: https://issues.apache.org/jira/browse/LUCENE-4891 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket If I add [type/CHAT, me, network/hanirc/chan/#sdgsdgsd] as categories to a document and add the document to a writer as below, Only network/hanirc/chan, not network/hanirc/chan/#sdgsdgsd is recorded into a taxonomy directory. type/CHAT and me are recorded well. I confirmed it with a test. FacetFields ff = new FacetFields(taxoWriter); ff.addFields(doc, categories); nrtWriter.addDocument(doc); If I add [type/CHAT, network/hanirc/chan/#sdgsdgsd] to a document, everything is recorded fine. What's wrong with me category? You could clone git://snowberry.me/ZeroIrcLog.git and read the code if you want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (LUCENE-4886) new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory
crocket created LUCENE-4886: --- Summary: new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory Key: LUCENE-4886 URL: https://issues.apache.org/jira/browse/LUCENE-4886 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical I made a taxonomy directory with categoryDir=FSDirectory.open(new File(category)); taxoWriter=new DirectoryTaxonomyWriter(categoryDir, OpenMode.CREATE_OR_APPEND); Right after creating DirectoryTaxonomyWriter, I created a DirectoryTaxonomyReader with taxoReader=new DirectoryTaxonomyRriter(categoryDir); which throws IndexNotFoundException. It used to work fine with lucene 4.1. If I invoke new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) on a new taxonomy directory, no exception is thrown. Below is the exception stack trace. org.apache.lucene.index.IndexNotFoundException: no segments* file found in org.apache.lucene.store.MMapDirectory@/home/elisa/repos/mine/ZeroIrcLog/irclog-category lockFactory=org.apache.lucene.store.NativeFSLockFactory@373983f: files: [write.lock, _0.si, _0.fnm, _0.fdt, _0_Lucene41_0.tim, _0_Lucene41_0.pos, _0.fdx, _0_Lucene41_0.doc, _0_Lucene41_0.tip] at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:741) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:52) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:65) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.openIndexReader(DirectoryTaxonomyReader.java:218) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.init(DirectoryTaxonomyReader.java:99) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.zeroirclog.LuceneLoggerWorker.init(LuceneLoggerWorker.java:141) ~[na:na] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4886) new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory
[ https://issues.apache.org/jira/browse/LUCENE-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4886: Description: I made a taxonomy directory with categoryDir=FSDirectory.open(new File(category)); taxoWriter=new DirectoryTaxonomyWriter(categoryDir, OpenMode.CREATE_OR_APPEND); Right after creating DirectoryTaxonomyWriter, I created a DirectoryTaxonomyReader with taxoReader=new DirectoryTaxonomyReader(categoryDir); which throws IndexNotFoundException. It used to work fine with lucene 4.1. If I invoke new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) on a new taxonomy directory, no exception is thrown. Below is the exception stack trace. org.apache.lucene.index.IndexNotFoundException: no segments* file found in org.apache.lucene.store.MMapDirectory@/home/elisa/repos/mine/ZeroIrcLog/irclog-category lockFactory=org.apache.lucene.store.NativeFSLockFactory@373983f: files: [write.lock, _0.si, _0.fnm, _0.fdt, _0_Lucene41_0.tim, _0_Lucene41_0.pos, _0.fdx, _0_Lucene41_0.doc, _0_Lucene41_0.tip] at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:741) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:52) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:65) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.openIndexReader(DirectoryTaxonomyReader.java:218) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.init(DirectoryTaxonomyReader.java:99) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.zeroirclog.LuceneLoggerWorker.init(LuceneLoggerWorker.java:141) ~[na:na] was: I made a taxonomy directory with categoryDir=FSDirectory.open(new File(category)); taxoWriter=new DirectoryTaxonomyWriter(categoryDir, OpenMode.CREATE_OR_APPEND); Right after creating DirectoryTaxonomyWriter, I created a DirectoryTaxonomyReader with taxoReader=new DirectoryTaxonomyRriter(categoryDir); which throws IndexNotFoundException. It used to work fine with lucene 4.1. If I invoke new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) on a new taxonomy directory, no exception is thrown. Below is the exception stack trace. org.apache.lucene.index.IndexNotFoundException: no segments* file found in org.apache.lucene.store.MMapDirectory@/home/elisa/repos/mine/ZeroIrcLog/irclog-category lockFactory=org.apache.lucene.store.NativeFSLockFactory@373983f: files: [write.lock, _0.si, _0.fnm, _0.fdt, _0_Lucene41_0.tim, _0_Lucene41_0.pos, _0.fdx, _0_Lucene41_0.doc, _0_Lucene41_0.tip] at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:741) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:52) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:65) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.openIndexReader(DirectoryTaxonomyReader.java:218) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.init(DirectoryTaxonomyReader.java:99) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.zeroirclog.LuceneLoggerWorker.init(LuceneLoggerWorker.java:141) ~[na:na] new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory - Key: LUCENE-4886 URL: https://issues.apache.org/jira/browse/LUCENE-4886 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical I made a taxonomy directory with categoryDir=FSDirectory.open(new File(category)); taxoWriter=new DirectoryTaxonomyWriter(categoryDir, OpenMode.CREATE_OR_APPEND); Right after creating DirectoryTaxonomyWriter, I created a DirectoryTaxonomyReader with taxoReader=new DirectoryTaxonomyReader(categoryDir); which throws IndexNotFoundException. It used to work fine with lucene 4.1. If I invoke new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) on a new taxonomy directory, no exception is thrown. Below is
[jira] [Commented] (LUCENE-4886) new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory
[ https://issues.apache.org/jira/browse/LUCENE-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614568#comment-13614568 ] crocket commented on LUCENE-4886: - Why did it work fine on lucene 4.1? new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory - Key: LUCENE-4886 URL: https://issues.apache.org/jira/browse/LUCENE-4886 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical I made a taxonomy directory with categoryDir=FSDirectory.open(new File(category)); taxoWriter=new DirectoryTaxonomyWriter(categoryDir, OpenMode.CREATE_OR_APPEND); Right after creating DirectoryTaxonomyWriter, I created a DirectoryTaxonomyReader with taxoReader=new DirectoryTaxonomyReader(categoryDir); which throws IndexNotFoundException. It used to work fine with lucene 4.1. If I invoke new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) on a new taxonomy directory, no exception is thrown. Below is the exception stack trace. org.apache.lucene.index.IndexNotFoundException: no segments* file found in org.apache.lucene.store.MMapDirectory@/home/elisa/repos/mine/ZeroIrcLog/irclog-category lockFactory=org.apache.lucene.store.NativeFSLockFactory@373983f: files: [write.lock, _0.si, _0.fnm, _0.fdt, _0_Lucene41_0.tim, _0_Lucene41_0.pos, _0.fdx, _0_Lucene41_0.doc, _0_Lucene41_0.tip] at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:741) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:52) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:65) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.openIndexReader(DirectoryTaxonomyReader.java:218) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.init(DirectoryTaxonomyReader.java:99) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.zeroirclog.LuceneLoggerWorker.init(LuceneLoggerWorker.java:141) ~[na:na] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4886) new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory
[ https://issues.apache.org/jira/browse/LUCENE-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614568#comment-13614568 ] crocket edited comment on LUCENE-4886 at 3/26/13 9:49 PM: -- SegmentInfos$FindSegmentsFile.run seems almost the same on both 4.1 and 4.2. Why did it work fine on lucene 4.1? was (Author: crocket): Why did it work fine on lucene 4.1? new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory - Key: LUCENE-4886 URL: https://issues.apache.org/jira/browse/LUCENE-4886 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical I made a taxonomy directory with categoryDir=FSDirectory.open(new File(category)); taxoWriter=new DirectoryTaxonomyWriter(categoryDir, OpenMode.CREATE_OR_APPEND); Right after creating DirectoryTaxonomyWriter, I created a DirectoryTaxonomyReader with taxoReader=new DirectoryTaxonomyReader(categoryDir); which throws IndexNotFoundException. It used to work fine with lucene 4.1. If I invoke new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) on a new taxonomy directory, no exception is thrown. Below is the exception stack trace. org.apache.lucene.index.IndexNotFoundException: no segments* file found in org.apache.lucene.store.MMapDirectory@/home/elisa/repos/mine/ZeroIrcLog/irclog-category lockFactory=org.apache.lucene.store.NativeFSLockFactory@373983f: files: [write.lock, _0.si, _0.fnm, _0.fdt, _0_Lucene41_0.tim, _0_Lucene41_0.pos, _0.fdx, _0_Lucene41_0.doc, _0_Lucene41_0.tip] at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:741) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:52) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:65) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.openIndexReader(DirectoryTaxonomyReader.java:218) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.init(DirectoryTaxonomyReader.java:99) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.zeroirclog.LuceneLoggerWorker.init(LuceneLoggerWorker.java:141) ~[na:na] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4882) FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath.
[ https://issues.apache.org/jira/browse/LUCENE-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614597#comment-13614597 ] crocket commented on LUCENE-4882: - Should I override methods in both FacetsAccumulator.java and CountingListBuilder.java to make it work? FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath. --- Key: LUCENE-4882 URL: https://issues.apache.org/jira/browse/LUCENE-4882 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Assignee: Shai Erera Priority: Critical Fix For: 5.0, 4.3 Attachments: LUCENE-4882.patch When I wanted to count root categories, I used to pass new CategoryPath(new String[0]) to a CountFacetRequest. Since upgrading lucene from 4.1 to 4.2, that threw ArrayIndexOfOutBoundsException, so I passed CategoryPath.EMPTY to a CountFacetRequest instead, and this time I got NullPointerException. It all originates from FacetsAccumulator.java:185 Does someone conspire to prevent others from counting root categories? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4882) FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath.
[ https://issues.apache.org/jira/browse/LUCENE-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614597#comment-13614597 ] crocket edited comment on LUCENE-4882 at 3/26/13 9:55 PM: -- I decided to stick to 4.2 for a while. Should I override methods in both FacetsAccumulator.java and CountingListBuilder.java to make it work? was (Author: crocket): Should I override methods in both FacetsAccumulator.java and CountingListBuilder.java to make it work? FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath. --- Key: LUCENE-4882 URL: https://issues.apache.org/jira/browse/LUCENE-4882 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Assignee: Shai Erera Priority: Critical Fix For: 5.0, 4.3 Attachments: LUCENE-4882.patch When I wanted to count root categories, I used to pass new CategoryPath(new String[0]) to a CountFacetRequest. Since upgrading lucene from 4.1 to 4.2, that threw ArrayIndexOfOutBoundsException, so I passed CategoryPath.EMPTY to a CountFacetRequest instead, and this time I got NullPointerException. It all originates from FacetsAccumulator.java:185 Does someone conspire to prevent others from counting root categories? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4882) FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath.
[ https://issues.apache.org/jira/browse/LUCENE-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614607#comment-13614607 ] crocket commented on LUCENE-4882: - I have a facet me that doesn't have a subcategory. Does it mean I need to modify CountingListBuilder as well as FacetsAccumulator or just use StandardFacetsAccumulator? FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath. --- Key: LUCENE-4882 URL: https://issues.apache.org/jira/browse/LUCENE-4882 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Assignee: Shai Erera Priority: Critical Fix For: 5.0, 4.3 Attachments: LUCENE-4882.patch When I wanted to count root categories, I used to pass new CategoryPath(new String[0]) to a CountFacetRequest. Since upgrading lucene from 4.1 to 4.2, that threw ArrayIndexOfOutBoundsException, so I passed CategoryPath.EMPTY to a CountFacetRequest instead, and this time I got NullPointerException. It all originates from FacetsAccumulator.java:185 Does someone conspire to prevent others from counting root categories? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4886) new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory
[ https://issues.apache.org/jira/browse/LUCENE-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614613#comment-13614613 ] crocket commented on LUCENE-4886: - I now use new DirectoryTaxnomyReader(DirectoryTaxonomyWriter). It is near-real time reader. Is it ok to use that with StandardFacetsAccumulator.create(fsp, searcher.getIndexReader(), taxoReader); when searcher is acquired by NRTManager.acquire? searcher.getIndexReader() and taxoReader are both near-real time, and there might be collisions between two. new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory - Key: LUCENE-4886 URL: https://issues.apache.org/jira/browse/LUCENE-4886 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical I made a taxonomy directory with categoryDir=FSDirectory.open(new File(category)); taxoWriter=new DirectoryTaxonomyWriter(categoryDir, OpenMode.CREATE_OR_APPEND); Right after creating DirectoryTaxonomyWriter, I created a DirectoryTaxonomyReader with taxoReader=new DirectoryTaxonomyReader(categoryDir); which throws IndexNotFoundException. It used to work fine with lucene 4.1. If I invoke new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) on a new taxonomy directory, no exception is thrown. Below is the exception stack trace. org.apache.lucene.index.IndexNotFoundException: no segments* file found in org.apache.lucene.store.MMapDirectory@/home/elisa/repos/mine/ZeroIrcLog/irclog-category lockFactory=org.apache.lucene.store.NativeFSLockFactory@373983f: files: [write.lock, _0.si, _0.fnm, _0.fdt, _0_Lucene41_0.tim, _0_Lucene41_0.pos, _0.fdx, _0_Lucene41_0.doc, _0_Lucene41_0.tip] at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:741) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:52) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:65) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.openIndexReader(DirectoryTaxonomyReader.java:218) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.init(DirectoryTaxonomyReader.java:99) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.zeroirclog.LuceneLoggerWorker.init(LuceneLoggerWorker.java:141) ~[na:na] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4882) FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath.
[ https://issues.apache.org/jira/browse/LUCENE-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614607#comment-13614607 ] crocket edited comment on LUCENE-4882 at 3/26/13 10:16 PM: --- 1) I have a facet me that doesn't have a subcategory. Does it mean I need to modify CountingListBuilder as well as FacetsAccumulator or just use StandardFacetsAccumulator? 2) I tried to use StandardFacetsAccumulator, but FacetsCollector.getFacetResults still throws java.lang.ArrayIndexOutOfBoundsException: 0 FacetsAccumulator sfa=StandardFacetsAccumulator.create(fsp, searcher.getIndexReader(), taxoReader); FacetsCollector fc = FacetsCollector.create(sfa); Does it mean I need to apply your patch to my project? was (Author: crocket): I have a facet me that doesn't have a subcategory. Does it mean I need to modify CountingListBuilder as well as FacetsAccumulator or just use StandardFacetsAccumulator? FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath. --- Key: LUCENE-4882 URL: https://issues.apache.org/jira/browse/LUCENE-4882 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Assignee: Shai Erera Priority: Critical Fix For: 5.0, 4.3 Attachments: LUCENE-4882.patch When I wanted to count root categories, I used to pass new CategoryPath(new String[0]) to a CountFacetRequest. Since upgrading lucene from 4.1 to 4.2, that threw ArrayIndexOfOutBoundsException, so I passed CategoryPath.EMPTY to a CountFacetRequest instead, and this time I got NullPointerException. It all originates from FacetsAccumulator.java:185 Does someone conspire to prevent others from counting root categories? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4886) new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory
[ https://issues.apache.org/jira/browse/LUCENE-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614662#comment-13614662 ] crocket commented on LUCENE-4886: - I haven't tested the behavior of DirectoryTaxonomyReader on lucene 4.2, but new DirectoryTaxonomyReader(Directory) could see changes and new categories without being reopened on lucene 4.1 new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory - Key: LUCENE-4886 URL: https://issues.apache.org/jira/browse/LUCENE-4886 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical I made a taxonomy directory with categoryDir=FSDirectory.open(new File(category)); taxoWriter=new DirectoryTaxonomyWriter(categoryDir, OpenMode.CREATE_OR_APPEND); Right after creating DirectoryTaxonomyWriter, I created a DirectoryTaxonomyReader with taxoReader=new DirectoryTaxonomyReader(categoryDir); which throws IndexNotFoundException. It used to work fine with lucene 4.1. If I invoke new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) on a new taxonomy directory, no exception is thrown. Below is the exception stack trace. org.apache.lucene.index.IndexNotFoundException: no segments* file found in org.apache.lucene.store.MMapDirectory@/home/elisa/repos/mine/ZeroIrcLog/irclog-category lockFactory=org.apache.lucene.store.NativeFSLockFactory@373983f: files: [write.lock, _0.si, _0.fnm, _0.fdt, _0_Lucene41_0.tim, _0_Lucene41_0.pos, _0.fdx, _0_Lucene41_0.doc, _0_Lucene41_0.tip] at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:741) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:52) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:65) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.openIndexReader(DirectoryTaxonomyReader.java:218) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.init(DirectoryTaxonomyReader.java:99) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.zeroirclog.LuceneLoggerWorker.init(LuceneLoggerWorker.java:141) ~[na:na] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4882) FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath.
[ https://issues.apache.org/jira/browse/LUCENE-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614916#comment-13614916 ] crocket edited comment on LUCENE-4882 at 3/27/13 4:36 AM: -- It turned out that StandardFacetsAccumulator inherited create from FacetsAccumulator. Thus, when I invoked StandardFacetsAccumulator.create, FacetsAccumulator.create was called actually. After replacing StandardFacetsAccumulator.create with new StandardFacetsAccumulator, it worked. I'll replace StandardFacetsAccumulator with something else when 4.3 comes around. I guess it is safe to close the issue. was (Author: crocket): It turned out that StandardFacetsAccumulator inherited create from FacetsAccumulator. Thus, when I invoked StandardFacetsAccumulator.create, FacetsAccumulator.create was called actually. After replacing StandardFacetsAccumulator.create, it worked. I'll replace StandardFacetsAccumulator with something else when 4.3 comes around. I guess it is safe to close the issue. FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath. --- Key: LUCENE-4882 URL: https://issues.apache.org/jira/browse/LUCENE-4882 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Assignee: Shai Erera Priority: Critical Fix For: 5.0, 4.3 Attachments: LUCENE-4882.patch When I wanted to count root categories, I used to pass new CategoryPath(new String[0]) to a CountFacetRequest. Since upgrading lucene from 4.1 to 4.2, that threw ArrayIndexOfOutBoundsException, so I passed CategoryPath.EMPTY to a CountFacetRequest instead, and this time I got NullPointerException. It all originates from FacetsAccumulator.java:185 Does someone conspire to prevent others from counting root categories? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4882) FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath.
[ https://issues.apache.org/jira/browse/LUCENE-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614916#comment-13614916 ] crocket commented on LUCENE-4882: - It turned out that StandardFacetsAccumulator inherited create from FacetsAccumulator. Thus, when I invoked StandardFacetsAccumulator.create, FacetsAccumulator.create was called actually. After replacing StandardFacetsAccumulator.create, it worked. I'll replace StandardFacetsAccumulator with something else when 4.3 comes around. I guess it is safe to close the issue. FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath. --- Key: LUCENE-4882 URL: https://issues.apache.org/jira/browse/LUCENE-4882 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Assignee: Shai Erera Priority: Critical Fix For: 5.0, 4.3 Attachments: LUCENE-4882.patch When I wanted to count root categories, I used to pass new CategoryPath(new String[0]) to a CountFacetRequest. Since upgrading lucene from 4.1 to 4.2, that threw ArrayIndexOfOutBoundsException, so I passed CategoryPath.EMPTY to a CountFacetRequest instead, and this time I got NullPointerException. It all originates from FacetsAccumulator.java:185 Does someone conspire to prevent others from counting root categories? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4886) new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory
[ https://issues.apache.org/jira/browse/LUCENE-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614662#comment-13614662 ] crocket edited comment on LUCENE-4886 at 3/27/13 4:38 AM: -- I haven't tested the behavior of DirectoryTaxonomyReader on lucene 4.2, but new DirectoryTaxonomyReader(Directory) could see changes and new categories without reopening it on lucene 4.1. By the way, how do I reopen DirectoryTaxonomyReader(DirectoryTaxonomyWriter)? Should I retrieve a new instance with new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) whenever I want to reopen it? was (Author: crocket): I haven't tested the behavior of DirectoryTaxonomyReader on lucene 4.2, but new DirectoryTaxonomyReader(Directory) could see changes and new categories without being reopened on lucene 4.1. By the way, how do I reopen DirectoryTaxonomyReader(DirectoryTaxonomyWriter)? Should I retrieve a new instance with new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) whenever I want to reopen it? new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory - Key: LUCENE-4886 URL: https://issues.apache.org/jira/browse/LUCENE-4886 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical I made a taxonomy directory with categoryDir=FSDirectory.open(new File(category)); taxoWriter=new DirectoryTaxonomyWriter(categoryDir, OpenMode.CREATE_OR_APPEND); Right after creating DirectoryTaxonomyWriter, I created a DirectoryTaxonomyReader with taxoReader=new DirectoryTaxonomyReader(categoryDir); which throws IndexNotFoundException. It used to work fine with lucene 4.1. If I invoke new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) on a new taxonomy directory, no exception is thrown. Below is the exception stack trace. org.apache.lucene.index.IndexNotFoundException: no segments* file found in org.apache.lucene.store.MMapDirectory@/home/elisa/repos/mine/ZeroIrcLog/irclog-category lockFactory=org.apache.lucene.store.NativeFSLockFactory@373983f: files: [write.lock, _0.si, _0.fnm, _0.fdt, _0_Lucene41_0.tim, _0_Lucene41_0.pos, _0.fdx, _0_Lucene41_0.doc, _0_Lucene41_0.tip] at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:741) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:52) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:65) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.openIndexReader(DirectoryTaxonomyReader.java:218) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.init(DirectoryTaxonomyReader.java:99) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.zeroirclog.LuceneLoggerWorker.init(LuceneLoggerWorker.java:141) ~[na:na] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4886) new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory
[ https://issues.apache.org/jira/browse/LUCENE-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614662#comment-13614662 ] crocket edited comment on LUCENE-4886 at 3/27/13 4:37 AM: -- I haven't tested the behavior of DirectoryTaxonomyReader on lucene 4.2, but new DirectoryTaxonomyReader(Directory) could see changes and new categories without being reopened on lucene 4.1. By the way, how do I reopen DirectoryTaxonomyReader(DirectoryTaxonomyWriter)? Should I retrieve a new instance with new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) whenever I want to reopen it? was (Author: crocket): I haven't tested the behavior of DirectoryTaxonomyReader on lucene 4.2, but new DirectoryTaxonomyReader(Directory) could see changes and new categories without being reopened on lucene 4.1 new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory - Key: LUCENE-4886 URL: https://issues.apache.org/jira/browse/LUCENE-4886 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical I made a taxonomy directory with categoryDir=FSDirectory.open(new File(category)); taxoWriter=new DirectoryTaxonomyWriter(categoryDir, OpenMode.CREATE_OR_APPEND); Right after creating DirectoryTaxonomyWriter, I created a DirectoryTaxonomyReader with taxoReader=new DirectoryTaxonomyReader(categoryDir); which throws IndexNotFoundException. It used to work fine with lucene 4.1. If I invoke new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) on a new taxonomy directory, no exception is thrown. Below is the exception stack trace. org.apache.lucene.index.IndexNotFoundException: no segments* file found in org.apache.lucene.store.MMapDirectory@/home/elisa/repos/mine/ZeroIrcLog/irclog-category lockFactory=org.apache.lucene.store.NativeFSLockFactory@373983f: files: [write.lock, _0.si, _0.fnm, _0.fdt, _0_Lucene41_0.tim, _0_Lucene41_0.pos, _0.fdx, _0_Lucene41_0.doc, _0_Lucene41_0.tip] at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:741) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:52) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:65) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.openIndexReader(DirectoryTaxonomyReader.java:218) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.init(DirectoryTaxonomyReader.java:99) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.zeroirclog.LuceneLoggerWorker.init(LuceneLoggerWorker.java:141) ~[na:na] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4886) new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory
[ https://issues.apache.org/jira/browse/LUCENE-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614662#comment-13614662 ] crocket edited comment on LUCENE-4886 at 3/27/13 4:39 AM: -- I haven't tested the behavior of DirectoryTaxonomyReader on lucene 4.2, but I remember that new DirectoryTaxonomyReader(Directory) could see changes and new categories without reopening it on lucene 4.1. By the way, how do I reopen DirectoryTaxonomyReader(DirectoryTaxonomyWriter)? Should I retrieve a new instance with new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) whenever I want to reopen it? was (Author: crocket): I haven't tested the behavior of DirectoryTaxonomyReader on lucene 4.2, but new DirectoryTaxonomyReader(Directory) could see changes and new categories without reopening it on lucene 4.1. By the way, how do I reopen DirectoryTaxonomyReader(DirectoryTaxonomyWriter)? Should I retrieve a new instance with new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) whenever I want to reopen it? new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory - Key: LUCENE-4886 URL: https://issues.apache.org/jira/browse/LUCENE-4886 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical I made a taxonomy directory with categoryDir=FSDirectory.open(new File(category)); taxoWriter=new DirectoryTaxonomyWriter(categoryDir, OpenMode.CREATE_OR_APPEND); Right after creating DirectoryTaxonomyWriter, I created a DirectoryTaxonomyReader with taxoReader=new DirectoryTaxonomyReader(categoryDir); which throws IndexNotFoundException. It used to work fine with lucene 4.1. If I invoke new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) on a new taxonomy directory, no exception is thrown. Below is the exception stack trace. org.apache.lucene.index.IndexNotFoundException: no segments* file found in org.apache.lucene.store.MMapDirectory@/home/elisa/repos/mine/ZeroIrcLog/irclog-category lockFactory=org.apache.lucene.store.NativeFSLockFactory@373983f: files: [write.lock, _0.si, _0.fnm, _0.fdt, _0_Lucene41_0.tim, _0_Lucene41_0.pos, _0.fdx, _0_Lucene41_0.doc, _0_Lucene41_0.tip] at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:741) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:52) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:65) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.openIndexReader(DirectoryTaxonomyReader.java:218) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.init(DirectoryTaxonomyReader.java:99) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.zeroirclog.LuceneLoggerWorker.init(LuceneLoggerWorker.java:141) ~[na:na] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-4886) new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory
[ https://issues.apache.org/jira/browse/LUCENE-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614662#comment-13614662 ] crocket edited comment on LUCENE-4886 at 3/27/13 4:41 AM: -- I haven't tested the behavior of DirectoryTaxonomyReader on lucene 4.2, but as far as I remember, new DirectoryTaxonomyReader(Directory) could see changes and new categories without reopening it on lucene 4.1. By the way, how do I reopen DirectoryTaxonomyReader(DirectoryTaxonomyWriter)? Should I retrieve a new instance with new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) whenever I want to reopen it? was (Author: crocket): I haven't tested the behavior of DirectoryTaxonomyReader on lucene 4.2, but I remember that new DirectoryTaxonomyReader(Directory) could see changes and new categories without reopening it on lucene 4.1. By the way, how do I reopen DirectoryTaxonomyReader(DirectoryTaxonomyWriter)? Should I retrieve a new instance with new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) whenever I want to reopen it? new DirectoryTaxonomyReader(Directory) throws IndexNotFoundException: no segments* file found on a new taxonomy directory - Key: LUCENE-4886 URL: https://issues.apache.org/jira/browse/LUCENE-4886 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical I made a taxonomy directory with categoryDir=FSDirectory.open(new File(category)); taxoWriter=new DirectoryTaxonomyWriter(categoryDir, OpenMode.CREATE_OR_APPEND); Right after creating DirectoryTaxonomyWriter, I created a DirectoryTaxonomyReader with taxoReader=new DirectoryTaxonomyReader(categoryDir); which throws IndexNotFoundException. It used to work fine with lucene 4.1. If I invoke new DirectoryTaxonomyReader(DirectoryTaxonomyWriter) on a new taxonomy directory, no exception is thrown. Below is the exception stack trace. org.apache.lucene.index.IndexNotFoundException: no segments* file found in org.apache.lucene.store.MMapDirectory@/home/elisa/repos/mine/ZeroIrcLog/irclog-category lockFactory=org.apache.lucene.store.NativeFSLockFactory@373983f: files: [write.lock, _0.si, _0.fnm, _0.fdt, _0_Lucene41_0.tim, _0_Lucene41_0.pos, _0.fdx, _0_Lucene41_0.doc, _0_Lucene41_0.tip] at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:741) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:52) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:65) ~[lucene-core-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:25:29] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.openIndexReader(DirectoryTaxonomyReader.java:218) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.apache.lucene.facet.taxonomy.directory.DirectoryTaxonomyReader.init(DirectoryTaxonomyReader.java:99) ~[lucene-facet-4.2.0.jar:4.2.0 1453694 - rmuir - 2013-03-06 22:26:53] at org.zeroirclog.LuceneLoggerWorker.init(LuceneLoggerWorker.java:141) ~[na:na] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (LUCENE-4882) FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath.
crocket created LUCENE-4882: --- Summary: FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath. Key: LUCENE-4882 URL: https://issues.apache.org/jira/browse/LUCENE-4882 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical When I want to count root categories, I used to pass new CategoryPath(new String[0]) to a CountFacetRequest. Since upgrading lucene from 4.1 to 4.2, that threw ArrayIndexOfOutBoundsException, so I passed CategoryPath.EMPTY to a CountFacetRequest instead, and this time I got NullPointerException. It all originates from FacetsAccumulator.java:185 Does someone conspire to prevent others from counting root categories? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4882) FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath.
[ https://issues.apache.org/jira/browse/LUCENE-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] crocket updated LUCENE-4882: Description: When I wanted to count root categories, I used to pass new CategoryPath(new String[0]) to a CountFacetRequest. Since upgrading lucene from 4.1 to 4.2, that threw ArrayIndexOfOutBoundsException, so I passed CategoryPath.EMPTY to a CountFacetRequest instead, and this time I got NullPointerException. It all originates from FacetsAccumulator.java:185 Does someone conspire to prevent others from counting root categories? was: When I want to count root categories, I used to pass new CategoryPath(new String[0]) to a CountFacetRequest. Since upgrading lucene from 4.1 to 4.2, that threw ArrayIndexOfOutBoundsException, so I passed CategoryPath.EMPTY to a CountFacetRequest instead, and this time I got NullPointerException. It all originates from FacetsAccumulator.java:185 Does someone conspire to prevent others from counting root categories? FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath. --- Key: LUCENE-4882 URL: https://issues.apache.org/jira/browse/LUCENE-4882 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical When I wanted to count root categories, I used to pass new CategoryPath(new String[0]) to a CountFacetRequest. Since upgrading lucene from 4.1 to 4.2, that threw ArrayIndexOfOutBoundsException, so I passed CategoryPath.EMPTY to a CountFacetRequest instead, and this time I got NullPointerException. It all originates from FacetsAccumulator.java:185 Does someone conspire to prevent others from counting root categories? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4882) FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath.
[ https://issues.apache.org/jira/browse/LUCENE-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13613506#comment-13613506 ] crocket commented on LUCENE-4882: - Thanks for a quick response, man. FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath. --- Key: LUCENE-4882 URL: https://issues.apache.org/jira/browse/LUCENE-4882 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Priority: Critical Attachments: LUCENE-4882.patch When I wanted to count root categories, I used to pass new CategoryPath(new String[0]) to a CountFacetRequest. Since upgrading lucene from 4.1 to 4.2, that threw ArrayIndexOfOutBoundsException, so I passed CategoryPath.EMPTY to a CountFacetRequest instead, and this time I got NullPointerException. It all originates from FacetsAccumulator.java:185 Does someone conspire to prevent others from counting root categories? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4882) FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath.
[ https://issues.apache.org/jira/browse/LUCENE-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13613518#comment-13613518 ] crocket commented on LUCENE-4882: - What about 4.2.1? And when will 4.3 be released? FacetsAccumulator.java:185 throws NullPointerException if it's given an empty CategoryPath. --- Key: LUCENE-4882 URL: https://issues.apache.org/jira/browse/LUCENE-4882 Project: Lucene - Core Issue Type: Bug Components: modules/facet Affects Versions: 4.2 Reporter: crocket Assignee: Shai Erera Priority: Critical Fix For: 5.0, 4.3 Attachments: LUCENE-4882.patch When I wanted to count root categories, I used to pass new CategoryPath(new String[0]) to a CountFacetRequest. Since upgrading lucene from 4.1 to 4.2, that threw ArrayIndexOfOutBoundsException, so I passed CategoryPath.EMPTY to a CountFacetRequest instead, and this time I got NullPointerException. It all originates from FacetsAccumulator.java:185 Does someone conspire to prevent others from counting root categories? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org