[jira] Commented: (LUCENE-2159) Tool to expand the index for perf/stress testing.

[ https://issues.apache.org/jira/browse/LUCENE-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12856869#action_12856869 ] John Wang commented on LUCENE-2159: --- Shai: You are right, we found this tool

[jira] Commented: (LUCENE-2159) Tool to expand the index for perf/stress testing.

[ https://issues.apache.org/jira/browse/LUCENE-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12856908#action_12856908 ] John Wang commented on LUCENE-2159: --- Shai: I am just stating our experiences. I am not

[jira] Commented: (LUCENE-2159) Tool to expand the index for perf/stress testing.

[ https://issues.apache.org/jira/browse/LUCENE-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12856913#action_12856913 ] John Wang commented on LUCENE-2159: --- Yeah, that sounds great! I will need to learn how

[jira] Commented: (LUCENE-2252) stored field retrieve slow

[ https://issues.apache.org/jira/browse/LUCENE-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848972#action_12848972 ] John Wang commented on LUCENE-2252: --- Hi Mike: Sorry for the late reply. We have

[jira] Created: (LUCENE-2252) stored field retrieve slow

stored field retrieve slow -- Key: LUCENE-2252 URL: https://issues.apache.org/jira/browse/LUCENE-2252 Project: Lucene - Java Issue Type: Improvement Components: Store Affects Versions: 3.0

[jira] Commented: (LUCENE-2252) stored field retrieve slow

[ https://issues.apache.org/jira/browse/LUCENE-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12830599#action_12830599 ] John Wang commented on LUCENE-2252: --- Thanks Uwe for the pointer. Will check that out!

[jira] Commented: (LUCENE-2252) stored field retrieve slow

[ https://issues.apache.org/jira/browse/LUCENE-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12830627#action_12830627 ] John Wang commented on LUCENE-2252: --- bq. I do not understand, I think the fdx index is

[jira] Commented: (LUCENE-2252) stored field retrieve slow

[ https://issues.apache.org/jira/browse/LUCENE-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12830628#action_12830628 ] John Wang commented on LUCENE-2252: --- Sorry, I meant LUCENE-1914 stored field retrieve

[jira] Commented: (LUCENE-2252) stored field retrieve slow

[ https://issues.apache.org/jira/browse/LUCENE-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12830641#action_12830641 ] John Wang commented on LUCENE-2252: --- bq. I still think 4 bytes/doc is too much (its too

[jira] Commented: (LUCENE-2120) Possible file handle leak in near real-time reader

[ https://issues.apache.org/jira/browse/LUCENE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12794998#action_12794998 ] John Wang commented on LUCENE-2120: --- Hi Michael: You are abs. right! By adding an

[jira] Commented: (LUCENE-2120) Possible file handle leak in near real-time reader

[ https://issues.apache.org/jira/browse/LUCENE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12794617#action_12794617 ] John Wang commented on LUCENE-2120: --- Michael: I wrote a little test to measure and

[jira] Commented: (LUCENE-2120) Possible file handle leak in near real-time reader

[ https://issues.apache.org/jira/browse/LUCENE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12793803#action_12793803 ] John Wang commented on LUCENE-2120: --- Yes we have done perf tests. We see no indexing

[jira] Created: (LUCENE-2159) Tool to expand the index for perf/stress testing.

Tool to expand the index for perf/stress testing. - Key: LUCENE-2159 URL: https://issues.apache.org/jira/browse/LUCENE-2159 Project: Lucene - Java Issue Type: New Feature Components:

[jira] Updated: (LUCENE-2159) Tool to expand the index for perf/stress testing.

[ https://issues.apache.org/jira/browse/LUCENE-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wang updated LUCENE-2159: -- Attachment: ExpandIndex.java I have put it under contrib/misc, in package org.apache.lucene.index

[jira] Created: (LUCENE-2160) Tool to rename a field

Tool to rename a field -- Key: LUCENE-2160 URL: https://issues.apache.org/jira/browse/LUCENE-2160 Project: Lucene - Java Issue Type: New Feature Components: contrib/* Affects Versions: 3.0

[jira] Updated: (LUCENE-2160) Tool to rename a field

[ https://issues.apache.org/jira/browse/LUCENE-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wang updated LUCENE-2160: -- Attachment: RenameField.java part of the code was originally posted on nabble, but is not removed:

[jira] Closed: (LUCENE-2007) Add DocsetQuery to turn a DocIdSet into a query

[ https://issues.apache.org/jira/browse/LUCENE-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wang closed LUCENE-2007. - Resolution: Won't Fix Add DocsetQuery to turn a DocIdSet into a query

[jira] Commented: (LUCENE-2160) Tool to rename a field

[ https://issues.apache.org/jira/browse/LUCENE-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12790797#action_12790797 ] John Wang commented on LUCENE-2160: --- Good point. But do you ever sort across fields?

[jira] Commented: (LUCENE-2160) Tool to rename a field

[ https://issues.apache.org/jira/browse/LUCENE-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12790809#action_12790809 ] John Wang commented on LUCENE-2160: --- Just did a test: You are right,

[jira] Updated: (LUCENE-2160) Tool to rename a field

[ https://issues.apache.org/jira/browse/LUCENE-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wang updated LUCENE-2160: -- Attachment: RenameField.java Fixed a problem with cfs files. Tool to rename a field

[jira] Commented: (LUCENE-2120) Possible file handle leak in near real-time reader

[ https://issues.apache.org/jira/browse/LUCENE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12790985#action_12790985 ] John Wang commented on LUCENE-2120: --- bq. is this what the private static int

[jira] Commented: (LUCENE-2160) Tool to rename a field

[ https://issues.apache.org/jira/browse/LUCENE-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791046#action_12791046 ] John Wang commented on LUCENE-2160: --- Did some more digging around the issue on field

[jira] Commented: (LUCENE-2160) Tool to rename a field

[ https://issues.apache.org/jira/browse/LUCENE-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791051#action_12791051 ] John Wang commented on LUCENE-2160: --- Looked at the file format wiki more closely, I see

[jira] Commented: (LUCENE-2146) DisjunctionMaxQuery has incorrect hashCode() implementation

[ https://issues.apache.org/jira/browse/LUCENE-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12790107#action_12790107 ] wang commented on LUCENE-2146: -- Thanks Michael and Uwe. i understand it is not a bug.

[jira] Commented: (LUCENE-2120) Possible file handle leak in near real-time reader

[ https://issues.apache.org/jira/browse/LUCENE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12790506#action_12790506 ] John Wang commented on LUCENE-2120: --- Hi Michael: bq: Why does Zoie even retain 3

[jira] Updated: (LUCENE-2146) DisjunctionMaxQuery has incorrect hashCode() implementation

[ https://issues.apache.org/jira/browse/LUCENE-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wang updated LUCENE-2146: - Attachment: LUCENE-2146.patch this patch can fix this bug. DisjunctionMaxQuery has incorrect hashCode()

[jira] Updated: (LUCENE-2146) DisjunctionMaxQuery has incorrect hashCode() implementation

[ https://issues.apache.org/jira/browse/LUCENE-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wang updated LUCENE-2146: - Attachment: (was: LUCENE-2146.patch) DisjunctionMaxQuery has incorrect hashCode() implementation

[jira] Updated: (LUCENE-2146) DisjunctionMaxQuery has incorrect hashCode() implementation

[ https://issues.apache.org/jira/browse/LUCENE-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wang updated LUCENE-2146: - Attachment: DisjunctionMaxQueryTest.java DisjunctionMaxQuery has incorrect hashCode() implementation

[jira] Created: (LUCENE-2146) DisjunctionMaxQuery has incorrect hashCode() implementation

DisjunctionMaxQuery has incorrect hashCode() implementation Key: LUCENE-2146 URL: https://issues.apache.org/jira/browse/LUCENE-2146 Project: Lucene - Java Issue Type: Bug

[jira] Updated: (LUCENE-2146) DisjunctionMaxQuery has incorrect hashCode() implementation

[ https://issues.apache.org/jira/browse/LUCENE-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wang updated LUCENE-2146: - Attachment: LUCENE-2146.patch DisjunctionMaxQuery has incorrect hashCode() implementation

[jira] Updated: (LUCENE-2146) DisjunctionMaxQuery has incorrect hashCode() implementation

[ https://issues.apache.org/jira/browse/LUCENE-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wang updated LUCENE-2146: - Description: The DisjunctionMaxQuery class hashCode() implementation is non-deterministic. It uses

[jira] Created: (LUCENE-2131) the method equals in ConstantScoreRangeQuery does not compare collator property fully, this bug is similar to LUCENE-1587

the method equals in ConstantScoreRangeQuery does not compare collator property fully, this bug is similar to LUCENE-1587 - Key: LUCENE-2131

[jira] Commented: (LUCENE-1613) TermEnum.docFreq() is not updated with there are deletes

[ https://issues.apache.org/jira/browse/LUCENE-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12786750#action_12786750 ] John Wang commented on LUCENE-1613: --- Maybe to just add a javadoc comment on the call to

[jira] Commented: (LUCENE-1526) For near real-time search, use paged copy-on-write BitVector impl

[ https://issues.apache.org/jira/browse/LUCENE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12786408#action_12786408 ] John Wang commented on LUCENE-1526: --- Yes, we still see the issue. The performance/stress

[jira] Commented: (LUCENE-1526) For near real-time search, use paged copy-on-write BitVector impl

[ https://issues.apache.org/jira/browse/LUCENE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12776739#action_12776739 ] John Wang commented on LUCENE-1526: --- Correction: We are NOT using BalancedMergePolicy

[jira] Commented: (LUCENE-1526) For near real-time search, use paged copy-on-write BitVector impl

[ https://issues.apache.org/jira/browse/LUCENE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12775930#action_12775930 ] John Wang commented on LUCENE-1526: --- bq. we need to see it in the real-world context of

[jira] Commented: (LUCENE-1526) For near real-time search, use paged copy-on-write BitVector impl

[ https://issues.apache.org/jira/browse/LUCENE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12776085#action_12776085 ] John Wang commented on LUCENE-1526: --- bq. Zoie will take 64 msec longer than Lucene, due

[jira] Commented: (LUCENE-1526) For near real-time search, use paged copy-on-write BitVector impl

[ https://issues.apache.org/jira/browse/LUCENE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12776282#action_12776282 ] John Wang commented on LUCENE-1526: --- wrote a little pgm on my mac pro (8 core 16GM mem

[jira] Commented: (LUCENE-1526) For near real-time search, use paged copy-on-write BitVector impl

[ https://issues.apache.org/jira/browse/LUCENE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12774743#action_12774743 ] John Wang commented on LUCENE-1526: --- Michael: I think I confused you by not giving

[jira] Commented: (LUCENE-1526) For near real-time search, use paged copy-on-write BitVector impl

[ https://issues.apache.org/jira/browse/LUCENE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12774662#action_12774662 ] John Wang commented on LUCENE-1526: --- The issue of not using a BitSet/BitVector is not

[jira] Commented: (LUCENE-1526) For near real-time search, use paged copy-on-write BitVector impl

[ https://issues.apache.org/jira/browse/LUCENE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12774671#action_12774671 ] John Wang commented on LUCENE-1526: --- We do not hold the deleted set for a long period

[jira] Commented: (LUCENE-2026) Refactoring of IndexWriter

[ https://issues.apache.org/jira/browse/LUCENE-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12773329#action_12773329 ] John Wang commented on LUCENE-2026: --- +1 Refactoring of IndexWriter

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772710#action_12772710 ] John Wang commented on LUCENE-1997: --- Hi Michael: Any plans/decisions on moving

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772754#action_12772754 ] John Wang commented on LUCENE-1997: --- Hi Michael: Thanks for the heads up. I will

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772764#action_12772764 ] John Wang commented on LUCENE-1997: --- I just looked at the most recent patch. Every entry

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772790#action_12772790 ] John Wang commented on LUCENE-1997: --- Mark: 100th page at the same time index is

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772794#action_12772794 ] John Wang commented on LUCENE-1997: --- Mark: The point of discussion is memory,

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772877#action_12772877 ] John Wang commented on LUCENE-1997: --- Another observation, with multiQ approach, seems

[jira] Created: (LUCENE-2007) Add DocsetQuery to turn a DocIdSet into a query

Add DocsetQuery to turn a DocIdSet into a query --- Key: LUCENE-2007 URL: https://issues.apache.org/jira/browse/LUCENE-2007 Project: Lucene - Java Issue Type: New Feature Components:

[jira] Updated: (LUCENE-2007) Add DocsetQuery to turn a DocIdSet into a query

[ https://issues.apache.org/jira/browse/LUCENE-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wang updated LUCENE-2007: -- Attachment: LUCENE-2007.patch contributed from bobo. Still work needed: 1) reader.isDeleted is now

[jira] Updated: (LUCENE-2007) Add DocsetQuery to turn a DocIdSet into a query

[ https://issues.apache.org/jira/browse/LUCENE-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wang updated LUCENE-2007: -- Attachment: LUCENE-2007-2.patch fixed to use reader.termDocs(null) for delete check. Add

[jira] Commented: (LUCENE-2007) Add DocsetQuery to turn a DocIdSet into a query

[ https://issues.apache.org/jira/browse/LUCENE-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12769674#action_12769674 ] John Wang commented on LUCENE-2007: --- Both Paul and Uwe are absolutely correct! I had

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12769116#action_12769116 ] John Wang commented on LUCENE-1997: --- I think I found the reason for the discrepancy: 32

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12769119#action_12769119 ] John Wang commented on LUCENE-1997: --- wrote a small test and verified that 64bit vm's

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12769045#action_12769045 ] John Wang commented on LUCENE-1997: --- My machine HW spec: Model Name: MacBook Pro

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12769090#action_12769090 ] John Wang commented on LUCENE-1997: --- bq: topn:100 I had made changes to sortBench.py to

[jira] Commented: (LUCENE-1969) adding kamikaze to lucene contrib

[ https://issues.apache.org/jira/browse/LUCENE-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12765306#action_12765306 ] John Wang commented on LUCENE-1969: --- My bad! The build.xml is not updated with the

[jira] Updated: (LUCENE-1969) adding kamikaze to lucene contrib

[ https://issues.apache.org/jira/browse/LUCENE-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wang updated LUCENE-1969: -- Attachment: build.xml updated build.xml with package name changes. adding kamikaze to lucene

[jira] Updated: (LUCENE-1969) adding kamikaze to lucene contrib

[ https://issues.apache.org/jira/browse/LUCENE-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wang updated LUCENE-1969: -- Attachment: kamikaze.contrib.patch2 again it was the package name. redid local run and all tests

[jira] Created: (LUCENE-1969) adding kamikaze to lucene contrib

adding kamikaze to lucene contrib - Key: LUCENE-1969 URL: https://issues.apache.org/jira/browse/LUCENE-1969 Project: Lucene - Java Issue Type: New Feature Components: contrib/* Affects Versions:

[jira] Updated: (LUCENE-1969) adding kamikaze to lucene contrib

[ https://issues.apache.org/jira/browse/LUCENE-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wang updated LUCENE-1969: -- Attachment: kamikaze-contrib.patch kamikaze contrib adding kamikaze to lucene contrib

[jira] Commented: (LUCENE-1458) Further steps towards flexible indexing

[ https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12762224#action_12762224 ] John Wang commented on LUCENE-1458: --- Hi Yonik: These are indeed useful features.

[jira] Created: (LUCENE-1931) no hits query - query object that returns no hits

no hits query - query object that returns no hits - Key: LUCENE-1931 URL: https://issues.apache.org/jira/browse/LUCENE-1931 Project: Lucene - Java Issue Type: New Feature Components:

[jira] Updated: (LUCENE-1931) no hits query - query object that returns no hits

[ https://issues.apache.org/jira/browse/LUCENE-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wang updated LUCENE-1931: -- Attachment: nohitsquery.patch 2 classes: NoHitsQuery.java: query implementation

[jira] Commented: (LUCENE-1931) no hits query - query object that returns no hits

[ https://issues.apache.org/jira/browse/LUCENE-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760268#action_12760268 ] John Wang commented on LUCENE-1931: --- Good to know! Thanks -John no hits query -

[jira] Commented: (LUCENE-1458) Further steps towards flexible indexing

[ https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12759910#action_12759910 ] John Wang commented on LUCENE-1458: --- Hi Mike: Truly awesome work! Quick

[jira] Created: (LUCENE-1925) In IndexSearcher class, make subReader and docCount arrays protected so sub classes can access them

In IndexSearcher class, make subReader and docCount arrays protected so sub classes can access them --- Key: LUCENE-1925 URL:

[jira] Commented: (LUCENE-1924) BalancedSegmentMergePolicy, contributed from the Zoie project for realtime indexing

[ https://issues.apache.org/jira/browse/LUCENE-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12759108#action_12759108 ] John Wang commented on LUCENE-1924: --- I had put them in the core package under

[jira] Commented: (LUCENE-1458) Further steps towards flexible indexing

[ https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12759110#action_12759110 ] John Wang commented on LUCENE-1458: --- Hi Mike: We have been using Kamikaze in our

[jira] Commented: (LUCENE-1458) Further steps towards flexible indexing

[ https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12759112#action_12759112 ] John Wang commented on LUCENE-1458: --- Just a FYI: Kamikaze was originally started as our

[jira] Commented: (LUCENE-1458) Further steps towards flexible indexing

[ https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12759116#action_12759116 ] John Wang commented on LUCENE-1458: --- Hi Uwe: Thanks for the pointer to the

[jira] Commented: (LUCENE-1924) BalancedSegmentMergePolicy, contributed from the Zoie project for realtime indexing

[ https://issues.apache.org/jira/browse/LUCENE-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12759132#action_12759132 ] John Wang commented on LUCENE-1924: --- Awesome, didn't realize! Thanks -John

[jira] Commented: (LUCENE-1458) Further steps towards flexible indexing

[ https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12758968#action_12758968 ] John Wang commented on LUCENE-1458: --- This is awesome! Feel free to take code from

[jira] Created: (LUCENE-1924) BalancedSegmentMergePolicy, contributed from the Zoie project for realtime indexing

BalancedSegmentMergePolicy, contributed from the Zoie project for realtime indexing --- Key: LUCENE-1924 URL: https://issues.apache.org/jira/browse/LUCENE-1924 Project:

[jira] Created: (LUCENE-1922) exposing the ability to get the number of unique term count per field

exposing the ability to get the number of unique term count per field - Key: LUCENE-1922 URL: https://issues.apache.org/jira/browse/LUCENE-1922 Project: Lucene - Java Issue

[jira] Created: (LUCENE-1914) allow for custom segment files

allow for custom segment files -- Key: LUCENE-1914 URL: https://issues.apache.org/jira/browse/LUCENE-1914 Project: Lucene - Java Issue Type: Improvement Components: Index Affects Versions: 2.9

[jira] Commented: (LUCENE-1819) MatchAllDocsQuery.toString(String field) does not honor the javadoc contract

[ https://issues.apache.org/jira/browse/LUCENE-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744530#action_12744530 ] John Wang commented on LUCENE-1819: --- Thanks Mark for taking care of this issue! w.r.t.

[jira] Created: (LUCENE-1819) MatchAllDocsQuery.toString(String field) does not honor the javadoc contract

MatchAllDocsQuery.toString(String field) does not honor the javadoc contract Key: LUCENE-1819 URL: https://issues.apache.org/jira/browse/LUCENE-1819 Project: Lucene - Java

[jira] Commented: (LUCENE-1574) PooledSegmentReader, pools SegmentReader underlying byte arrays

[ https://issues.apache.org/jira/browse/LUCENE-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737950#action_12737950 ] John Wang commented on LUCENE-1574: --- Re: Zoie and deleted docs: That is no longer true,

[jira] Commented: (LUCENE-1642) IndexWriter.addIndexesNoOptimize ignores the compound file setting of the destination index

[ https://issues.apache.org/jira/browse/LUCENE-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12710620#action_12710620 ] John Wang commented on LUCENE-1642: --- 2.4.0 branch: IndexWriter.java, method:

[jira] Commented: (LUCENE-1634) LogMergePolicy should use the number of deleted docs when deciding which segments to merge

[ https://issues.apache.org/jira/browse/LUCENE-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708989#action_12708989 ] John Wang commented on LUCENE-1634: --- Comment on implementing a custom merge policy: As

[jira] Commented: (LUCENE-1634) LogMergePolicy should use the number of deleted docs when deciding which segments to merge

[ https://issues.apache.org/jira/browse/LUCENE-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708995#action_12708995 ] John Wang commented on LUCENE-1634: --- The current lucene implementation, optimize(int)

[jira] Commented: (LUCENE-1634) LogMergePolicy should use the number of deleted docs when deciding which segments to merge

[ https://issues.apache.org/jira/browse/LUCENE-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12709003#action_12709003 ] John Wang commented on LUCENE-1634: --- So let's proceed with this patch, once you've

[jira] Commented: (LUCENE-1634) LogMergePolicy should use the number of deleted docs when deciding which segments to merge

[ https://issues.apache.org/jira/browse/LUCENE-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12709024#action_12709024 ] John Wang commented on LUCENE-1634: --- I mean a setter/getter to turn on/off taking

[jira] Commented: (LUCENE-1632) boolean docid set iterator improvement

[ https://issues.apache.org/jira/browse/LUCENE-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708659#action_12708659 ] John Wang commented on LUCENE-1632: --- I think we have an improvement for ConjuctionScorer

[jira] Created: (LUCENE-1632) boolean docid set iterator improvement

boolean docid set iterator improvement -- Key: LUCENE-1632 URL: https://issues.apache.org/jira/browse/LUCENE-1632 Project: Lucene - Java Issue Type: Improvement Affects Versions: 2.4

[jira] Updated: (LUCENE-1632) boolean docid set iterator improvement

[ https://issues.apache.org/jira/browse/LUCENE-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wang updated LUCENE-1632: -- Attachment: Lucene-1632-patch.txt boolean docid set iterator improvement

[jira] Commented: (LUCENE-1613) TermEnum.docFreq() is not updated with there are deletes

[ https://issues.apache.org/jira/browse/LUCENE-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12702691#action_12702691 ] John Wang commented on LUCENE-1613: --- Michael: We ran into this actually in facet search.

[jira] Commented: (LUCENE-1612) expose lastDocId in the posting from the TermEnum API

[ https://issues.apache.org/jira/browse/LUCENE-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12702692#action_12702692 ] John Wang commented on LUCENE-1612: --- Excellent point Michael! What do you suggest on how

[jira] Commented: (LUCENE-1612) expose lastDocId in the posting from the TermEnum API

[ https://issues.apache.org/jira/browse/LUCENE-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12702827#action_12702827 ] John Wang commented on LUCENE-1612: --- I am fine with waiting for LUCENE-1458. But

[jira] Created: (LUCENE-1612) expose lastDocId in the posting from the TermEnum API

expose lastDocId in the posting from the TermEnum API - Key: LUCENE-1612 URL: https://issues.apache.org/jira/browse/LUCENE-1612 Project: Lucene - Java Issue Type: Improvement

[jira] Updated: (LUCENE-1612) expose lastDocId in the posting from the TermEnum API

[ https://issues.apache.org/jira/browse/LUCENE-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wang updated LUCENE-1612: -- Attachment: lucene-1612-patch.txt Patch attach with test. Index is not backwards compatible. expose

[jira] Created: (LUCENE-1613) TermEnum.docFreq() is not updated with there are deletes

TermEnum.docFreq() is not updated with there are deletes Key: LUCENE-1613 URL: https://issues.apache.org/jira/browse/LUCENE-1613 Project: Lucene - Java Issue Type: Bug

[jira] Updated: (LUCENE-1613) TermEnum.docFreq() is not updated with there are deletes

[ https://issues.apache.org/jira/browse/LUCENE-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wang updated LUCENE-1613: -- Attachment: TestDeleteAndDocFreq.java Test showing docFreq not updated when there are deletes.

[jira] Commented: (LUCENE-1613) TermEnum.docFreq() is not updated with there are deletes

[ https://issues.apache.org/jira/browse/LUCENE-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12702649#action_12702649 ] John Wang commented on LUCENE-1613: --- I understand this is a rather difficult problem to

[jira] Commented: (LUCENE-1506) Adding FilteredDocIdSet and FilteredDocIdSetIterator

[ https://issues.apache.org/jira/browse/LUCENE-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12669105#action_12669105 ] John Wang commented on LUCENE-1506: --- Thanks Michael! Adding FilteredDocIdSet and

[jira] Commented: (LUCENE-1506) Adding FilteredDocIdSet and FilteredDocIdSetIterator

[ https://issues.apache.org/jira/browse/LUCENE-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12668668#action_12668668 ] John Wang commented on LUCENE-1506: --- sure, will work on that. Adding FilteredDocIdSet

[jira] Updated: (LUCENE-1506) Adding FilteredDocIdSet and FilteredDocIdSetIterator

[ https://issues.apache.org/jira/browse/LUCENE-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wang updated LUCENE-1506: -- Attachment: filteredDocidset2.txt javadoc and unit test added Adding FilteredDocIdSet and

[jira] Commented: (LUCENE-1506) Adding FilteredDocIdSet and FilteredDocIdSetIterator

[ https://issues.apache.org/jira/browse/LUCENE-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12668244#action_12668244 ] John Wang commented on LUCENE-1506: --- Filter calculates a DocSet given an IndexReader.

[jira] Commented: (LUCENE-1345) Allow Filter as clause to BooleanQuery

[ https://issues.apache.org/jira/browse/LUCENE-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12662673#action_12662673 ] John Wang commented on LUCENE-1345: --- Filters by definition (afaik) does not participate

  1   2   >