[jira] [Resolved] (GEODE-1775) CI failure: ParallelWANPropagationClientServerDUnitTest.testParallelPropagationWithClientServer

[ https://issues.apache.org/jira/browse/GEODE-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou resolved GEODE-1775. -- Resolution: Fixed Fix Version/s: 1.2.0 > CI failure: >

[jira] [Updated] (GEODE-2824) FunctionException: No target node found when executing hasNext on Lucene result

[ https://issues.apache.org/jira/browse/GEODE-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou updated GEODE-2824: - Fix Version/s: 1.2.0 > FunctionException: No target node found when executing hasNext on Lucene

[jira] [Resolved] (GEODE-2824) FunctionException: No target node found when executing hasNext on Lucene result

[ https://issues.apache.org/jira/browse/GEODE-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou resolved GEODE-2824. -- Resolution: Fixed > FunctionException: No target node found when executing hasNext on Lucene >

[jira] [Resolved] (GEODE-1734) Lucene search for a single entry is returning multiple results

[ https://issues.apache.org/jira/browse/GEODE-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou resolved GEODE-1734. -- Resolution: Fixed Fixed in GEODE-2241 revision 0182a1bb744d25fe490d142dfed7d9a6f20b2713 >

[jira] [Updated] (GEODE-2848) While destroying a LuceneIndex, the AsyncEventQueue region is destroyed in remote members before stopping the AsyncEventQueue

[ https://issues.apache.org/jira/browse/GEODE-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou updated GEODE-2848: - Fix Version/s: 1.2.0 > While destroying a LuceneIndex, the AsyncEventQueue region is destroyed in

[jira] [Resolved] (GEODE-2848) While destroying a LuceneIndex, the AsyncEventQueue region is destroyed in remote members before stopping the AsyncEventQueue

[ https://issues.apache.org/jira/browse/GEODE-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou resolved GEODE-2848. -- Resolution: Fixed fix in revision d4ece31fa23bbe74c8be0a82ff4b9d143bad79b3 > While destroying

[jira] [Assigned] (GEODE-2824) FunctionException: No target node found when executing hasNext on Lucene result

[ https://issues.apache.org/jira/browse/GEODE-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou reassigned GEODE-2824: Assignee: xiaojian zhou > FunctionException: No target node found when executing hasNext

[jira] [Commented] (GEODE-2848) While destroying a LuceneIndex, the AsyncEventQueue region is destroyed in remote members before stopping the AsyncEventQueue

[ https://issues.apache.org/jira/browse/GEODE-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991583#comment-15991583 ] xiaojian zhou commented on GEODE-2848: -- I think it does not worth to introduce complexity of new

[jira] [Reopened] (GEODE-1988) CI failure: RegisterInterestKeysPRDUnitTest fails intermittently

[ https://issues.apache.org/jira/browse/GEODE-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou reopened GEODE-1988: -- It is reproduced in CI FlakeyTest #569 and #564

[jira] [Resolved] (GEODE-2806) when batch is dispatched, if the bucket is not primary, we should still destroy the event from queue

[ https://issues.apache.org/jira/browse/GEODE-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou resolved GEODE-2806. -- Resolution: Fixed > when batch is dispatched, if the bucket is not primary, we should still >

[jira] [Assigned] (GEODE-2806) when batch is dispatched, if the bucket is not primary, we should still destroy the event from queue

[ https://issues.apache.org/jira/browse/GEODE-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou reassigned GEODE-2806: Assignee: xiaojian zhou > when batch is dispatched, if the bucket is not primary, we

[jira] [Created] (GEODE-2806) when batch is dispatched, if the bucket is not primary, we should still destroy the event from queue

xiaojian zhou created GEODE-2806: Summary: when batch is dispatched, if the bucket is not primary, we should still destroy the event from queue Key: GEODE-2806 URL:

[jira] [Resolved] (GEODE-2787) state flush did not wait for notifyGateway

[ https://issues.apache.org/jira/browse/GEODE-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou resolved GEODE-2787. -- Resolution: Fixed > state flush did not wait for notifyGateway >

[jira] [Updated] (GEODE-2787) state flush did not wait for notifyGateway

[ https://issues.apache.org/jira/browse/GEODE-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou updated GEODE-2787: - Labels: lucene (was: ) > state flush did not wait for notifyGateway >

[jira] [Assigned] (GEODE-2787) state flush did not wait for notifyGateway

[ https://issues.apache.org/jira/browse/GEODE-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou reassigned GEODE-2787: Assignee: xiaojian zhou > state flush did not wait for notifyGateway >

[jira] [Created] (GEODE-2787) state flush did not wait for notifyGateway

xiaojian zhou created GEODE-2787: Summary: state flush did not wait for notifyGateway Key: GEODE-2787 URL: https://issues.apache.org/jira/browse/GEODE-2787 Project: Geode Issue Type: Bug

[jira] [Commented] (GEODE-1894) SerialGatewaySenderOperationsDUnitTest test hangs

[ https://issues.apache.org/jira/browse/GEODE-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947572#comment-15947572 ] xiaojian zhou commented on GEODE-1894: -- It was not reproducible but we found the root cause and fixed

[jira] [Issue Comment Deleted] (GEODE-1894) SerialGatewaySenderOperationsDUnitTest test hangs

[ https://issues.apache.org/jira/browse/GEODE-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou updated GEODE-1894: - Comment: was deleted (was: Re-run the test using the current revision and even Sep 12's revision,

[jira] [Resolved] (GEODE-2683) Lucene query did not match region values

[ https://issues.apache.org/jira/browse/GEODE-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou resolved GEODE-2683. -- Resolution: Fixed > Lucene query did not match region values >

[jira] [Updated] (GEODE-2683) Lucene query did not match region values

[ https://issues.apache.org/jira/browse/GEODE-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou updated GEODE-2683: - Description: There're several root causes. This one is due to the fix in #45782 changed the

[jira] [Updated] (GEODE-2617) LuceneResultStruct should be Serializable

[ https://issues.apache.org/jira/browse/GEODE-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou updated GEODE-2617: - Fix Version/s: 1.2.0 > LuceneResultStruct should be Serializable >

[jira] [Resolved] (GEODE-2617) LuceneResultStruct should be Serializable

[ https://issues.apache.org/jira/browse/GEODE-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou resolved GEODE-2617. -- Resolution: Fixed > LuceneResultStruct should be Serializable >

[jira] [Assigned] (GEODE-2617) LuceneResultStruct should be Serializable

[ https://issues.apache.org/jira/browse/GEODE-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou reassigned GEODE-2617: Assignee: xiaojian zhou > LuceneResultStruct should be Serializable >

[jira] [Created] (GEODE-2617) LuceneResultStruct should be Serializable

xiaojian zhou created GEODE-2617: Summary: LuceneResultStruct should be Serializable Key: GEODE-2617 URL: https://issues.apache.org/jira/browse/GEODE-2617 Project: Geode Issue Type: Bug

[jira] [Resolved] (GEODE-2471) AsyncEventListenerOffHeapDUnitTest.testParallelAsyncEventQueueMoveBucketAndMoveItBackDuringDispatching

[ https://issues.apache.org/jira/browse/GEODE-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou resolved GEODE-2471. -- Resolution: Fixed >

[jira] [Assigned] (GEODE-2471) AsyncEventListenerOffHeapDUnitTest.testParallelAsyncEventQueueMoveBucketAndMoveItBackDuringDispatching

[ https://issues.apache.org/jira/browse/GEODE-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou reassigned GEODE-2471: Assignee: xiaojian zhou >

[jira] [Created] (GEODE-2471) AsyncEventListenerOffHeapDUnitTest.testParallelAsyncEventQueueMoveBucketAndMoveItBackDuringDispatching

xiaojian zhou created GEODE-2471: Summary: AsyncEventListenerOffHeapDUnitTest.testParallelAsyncEventQueueMoveBucketAndMoveItBackDuringDispatching Key: GEODE-2471 URL:

[jira] [Resolved] (GEODE-2400) PR accessors and client should have a way to wait for a lucene index to be flushed

[ https://issues.apache.org/jira/browse/GEODE-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou resolved GEODE-2400. -- Resolution: Fixed > PR accessors and client should have a way to wait for a lucene index to be

[jira] [Assigned] (GEODE-2400) PR accessors and client should have a way to wait for a lucene index to be flushed

[ https://issues.apache.org/jira/browse/GEODE-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou reassigned GEODE-2400: Assignee: xiaojian zhou > PR accessors and client should have a way to wait for a lucene

[jira] [Resolved] (GEODE-2384) Lucene index cannot be created on accessor if there's persistent region

[ https://issues.apache.org/jira/browse/GEODE-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou resolved GEODE-2384. -- Resolution: Fixed > Lucene index cannot be created on accessor if there's persistent region >

[jira] [Created] (GEODE-2384) Lucene index cannot be created on accessor if there's persistent region

xiaojian zhou created GEODE-2384: Summary: Lucene index cannot be created on accessor if there's persistent region Key: GEODE-2384 URL: https://issues.apache.org/jira/browse/GEODE-2384 Project: Geode

[jira] [Resolved] (GEODE-2241) gfsh lucene will generate duplicate results

[ https://issues.apache.org/jira/browse/GEODE-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou resolved GEODE-2241. -- Resolution: Fixed > gfsh lucene will generate duplicate results >

[jira] [Updated] (GEODE-2263) CliUtil.getRegionAssociatedMembers()'s returnAll parameter is not used

[ https://issues.apache.org/jira/browse/GEODE-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou updated GEODE-2263: - Description: And DataCommands has a same name method which did use returnAll parameter. I think

[jira] [Created] (GEODE-2241) gfsh lucene will generate duplicate results

xiaojian zhou created GEODE-2241: Summary: gfsh lucene will generate duplicate results Key: GEODE-2241 URL: https://issues.apache.org/jira/browse/GEODE-2241 Project: Geode Issue Type: Bug

[jira] [Resolved] (GEODE-2175) CI failure from TopEntriesFunctionCollectorJUnitTest.expectErrorAfterWaitTime

[ https://issues.apache.org/jira/browse/GEODE-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou resolved GEODE-2175. -- Resolution: Fixed > CI failure from