[jira] [Resolved] (GEODE-1125) Number of region entries does not match with the expected number at the end of tests

[ https://issues.apache.org/jira/browse/GEODE-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun resolved GEODE-1125. Resolution: Fixed Fix Version/s: 1.2.0 > Number of region entries does not match with the expected

[jira] [Resolved] (GEODE-1190) Should the LuceneServiceProvider get API take a GemFireCache instead of a Cache?

[ https://issues.apache.org/jira/browse/GEODE-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun resolved GEODE-1190. Resolution: Fixed Fix Version/s: 1.2.0 > Should the LuceneServiceProvider get API take a

Re: Geode Native Release

John, I wish we could do that but Apache would require that geode-native be a fully qualified sub-project with all the headache that goes with that to "release" separately. On Thu, May 4, 2017 at 11:35 AM John Blum wrote: > A good reason to use separate repos. Individual

[jira] [Resolved] (GEODE-2870) BucketMovedException during function execution may lead to client missing results

[ https://issues.apache.org/jira/browse/GEODE-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh resolved GEODE-2870. Resolution: Fixed Fix Version/s: 1.2.0 > BucketMovedException during function execution may

Re: [gemfire-dev] New Client-Server Protocol Proposal

> > I wouldn't tackle that at this layer. I would suggest adding a layer > between the message and TCP that creates channels that are opaque to the > message layer above. The message layer wouldn't know if it was talking to > multiple sockets to the client or single socket with multiple channels.

Re: Geode Native Release

Jacob - Ah, sorry to hear that. On Thu, May 4, 2017 at 2:09 PM, Jacob Barrett wrote: > John, I wish we could do that but Apache would require that geode-native be > a fully qualified sub-project with all the headache that goes with that to > "release" separately. > > > On

Re: Review Request 58888: GEODE-2632: change dependencies on GemFireCacheImpl to InternalCache

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5/#review173942 ---

Re: Geode Native Release

It's the problem we are going to have with two distinctly different modules sharing the same project release cycle. The best we could do is branch release/v1.3 form the support/v1.2 branch until we are ready to release the breaking changes in the geode-native/develop branch. -Jake On Thu, May

[jira] [Commented] (GEODE-2853) Change of locator list request interval

[ https://issues.apache.org/jira/browse/GEODE-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997301#comment-15997301 ] ASF GitHub Bot commented on GEODE-2853: --- Github user masaki-yamakawa commented on the issue:

[GitHub] geode pull request #490: Feature/geode 2852

Github user ladyVader closed the pull request at: https://github.com/apache/geode/pull/490 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (GEODE-2852) Enforce WaitUntilFlushedFunction.waitUntilFlushed() timeout across all (local) buckets (not per bucket)

[ https://issues.apache.org/jira/browse/GEODE-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997380#comment-15997380 ] ASF GitHub Bot commented on GEODE-2852: --- Github user ladyVader closed the pull request at:

[jira] [Resolved] (GEODE-2852) Enforce WaitUntilFlushedFunction.waitUntilFlushed() timeout across all (local) buckets (not per bucket)

[ https://issues.apache.org/jira/browse/GEODE-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey resolved GEODE-2852. Resolution: Fixed Fix Version/s: 1.2.0 commit

[jira] [Created] (GEODE-2877) Auth handler: "Cannot pass a GCHandle across AppDomains" in GemStone::GemFire::Cache::IAuthInitialize

Jacob S. Barrett created GEODE-2877: --- Summary: Auth handler: "Cannot pass a GCHandle across AppDomains" in GemStone::GemFire::Cache::IAuthInitialize Key: GEODE-2877 URL:

[GitHub] geode issue #483: GEODE-2853: Change of locator list request interval

Github user masaki-yamakawa commented on the issue: https://github.com/apache/geode/pull/483 Thanks for the suggestion. I fixed that. @bschuchardt @kirklund --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your

Re: [gemfire-dev] New Client-Server Protocol Proposal

>>> a. Now these two chunks will go continuous. >>They would appear continuous to the object serialization layer. One benefit of messageHeader with chunk is that, it gives us ability to write different messages(multiplexing) on same socket. And if thread is ready it can write its message.

[jira] [Commented] (GEODE-2852) Enforce WaitUntilFlushedFunction.waitUntilFlushed() timeout across all (local) buckets (not per bucket)

[ https://issues.apache.org/jira/browse/GEODE-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997398#comment-15997398 ] ASF subversion and git services commented on GEODE-2852: Commit

[jira] [Resolved] (GEODE-2523) Collapse RegionTestableTypes combinations into a single enum types

[ https://issues.apache.org/jira/browse/GEODE-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh resolved GEODE-2523. Resolution: Fixed Assignee: Jason Huynh Fix Version/s: 1.2.0 > Collapse

[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 >

Re: [gemfire-dev] New Client-Server Protocol Proposal

It's becoming clear that the document needs a section on EventIds. EventIds aren't opaque to the server. They are comparable objects and are used by the cache to prevent replay of older (operation eventId < recorded eventId) operations on the cache and on subscription queues. They are also

Review Request 58996: GEODE-2876: Add logging to diagnose CI failure

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58996/ --- Review request for geode. Repository: geode Description --- GEODE-2876:

[jira] [Created] (GEODE-2876) CI Failure: org.apache.geode.management.internal.cli.commands.ConcurrentDeployDUnitTest#testMultipleGfshClientToOneServer

Jared Stewart created GEODE-2876: Summary: CI Failure: org.apache.geode.management.internal.cli.commands.ConcurrentDeployDUnitTest#testMultipleGfshClientToOneServer Key: GEODE-2876 URL:

Re: Review Request 58888: GEODE-2632: change dependencies on GemFireCacheImpl to InternalCache

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5/#review173912 ---

[jira] [Commented] (GEODE-2812) Add API to get list of live locators

[ https://issues.apache.org/jira/browse/GEODE-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997053#comment-15997053 ] ASF GitHub Bot commented on GEODE-2812: --- Github user masaki-yamakawa commented on the issue:

[GitHub] geode-native pull request #96: GEODE-2814 Remove curl dependency from native...

GitHub user gemfire-ci opened a pull request: https://github.com/apache/geode-native/pull/96 GEODE-2814 Remove curl dependency from native client build Signed-off-by: Scott Jewell You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (GEODE-2814) Native client test framework uses Xerces which depends on Curl

[ https://issues.apache.org/jira/browse/GEODE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997089#comment-15997089 ] ASF GitHub Bot commented on GEODE-2814: --- GitHub user gemfire-ci opened a pull request:

Re: [gemfire-dev] New Client-Server Protocol Proposal

+1 On Wed, May 3, 2017 at 5:43 PM Anthony Baker wrote: > > 2) I think we should pull out the message fragmentation support to avoid > some significant complexity. We can later add a fragmentation / envelope > layer on top without disrupting the current proposal. I do think

[jira] [Resolved] (GEODE-2612) Add option to invoke callbacks while loading a snapshot

[ https://issues.apache.org/jira/browse/GEODE-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barry Oglesby resolved GEODE-2612. -- Resolution: Fixed Fix Version/s: 1.2.0 > Add option to invoke callbacks while loading a

[jira] [Resolved] (GEODE-2553) After deleting and recreating my Lucene index and region, my Lucene query hung.

[ https://issues.apache.org/jira/browse/GEODE-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barry Oglesby resolved GEODE-2553. -- Resolution: Fixed > After deleting and recreating my Lucene index and region, my Lucene query

[jira] [Resolved] (GEODE-2230) LuceneIndex.waitUntilFlushed should not have to wait for the queue to be completely empty

[ https://issues.apache.org/jira/browse/GEODE-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barry Oglesby resolved GEODE-2230. -- Resolution: Fixed Fix Version/s: 1.2.0 > LuceneIndex.waitUntilFlushed should not have to

[jira] [Resolved] (GEODE-969) Various WAN dunit tests sometimes cause OOME during combineReports task

[ https://issues.apache.org/jira/browse/GEODE-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barry Oglesby resolved GEODE-969. - Resolution: Fixed Fix Version/s: 1.2.0 > Various WAN dunit tests sometimes cause OOME

[jira] [Resolved] (GEODE-1189) Should the LuceneQueryFactory create API throw a Lucene ParseException?

[ https://issues.apache.org/jira/browse/GEODE-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barry Oglesby resolved GEODE-1189. -- Resolution: Fixed Fix Version/s: 1.2.0 > Should the LuceneQueryFactory create API throw

[jira] [Assigned] (GEODE-2708) Update Gradle Wrapper to Gradle 3

[ https://issues.apache.org/jira/browse/GEODE-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bretl reassigned GEODE-2708: - Assignee: Mark Bretl > Update Gradle Wrapper to Gradle 3 > - > >

[jira] [Resolved] (GEODE-2708) Update Gradle Wrapper to Gradle 3

[ https://issues.apache.org/jira/browse/GEODE-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bretl resolved GEODE-2708. --- Resolution: Fixed Fix Version/s: 1.2.0 Gradle Wrapper now updated to 3.4.1 > Update Gradle

[jira] [Assigned] (GEODE-2879) LonerDistributionManager's Shutdown not being called in close()

[ https://issues.apache.org/jira/browse/GEODE-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun reassigned GEODE-2879: -- Assignee: nabarun > LonerDistributionManager's Shutdown not being called in close() >

[jira] [Resolved] (GEODE-2879) LonerDistributionManager's Shutdown not being called in close()

[ https://issues.apache.org/jira/browse/GEODE-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun resolved GEODE-2879. Resolution: Fixed Fix Version/s: 1.2.0 > LonerDistributionManager's Shutdown not being called in

Re: Review Request 58888: GEODE-2632: change dependencies on GemFireCacheImpl to InternalCache

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5/#review173929 --- Ship it! Ship It! - Jared Stewart On May 3, 2017, 10:10

[jira] [Commented] (GEODE-2611) Host geode-native docs on geode.apache.org

[ https://issues.apache.org/jira/browse/GEODE-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997195#comment-15997195 ] Anthony Baker commented on GEODE-2611: -- This will be completed when we do the first geode-native

Re: Geode Native Release

A good reason to use separate repos. Individual components of Geode, especially clear boundaries like Native Client, *Gfsh*, or Pulse, etc, should be separately and independently releasable to provide a smoother release cadence based on velocity and community need. Then, using a Maven "BOM", you

Re: Geode Native Release

I think it’s confusing to cut a release from different branches for geode, geode-examples, and geode-native but I don’t have a better idea. +0 Anthony > On May 4, 2017, at 7:29 AM, Jacob Barrett wrote: > > All, > > I want to start the discussion on releasing Geode

Re: [gemfire-dev] New Client-Server Protocol Proposal

Hi Anthony: Help me to understand data chunking here? >> bytes => arbitrary byte[] that can be chunked Message => MessageHeader MessageBody So lets say we want to send long byte[] into two chunks, then we will send two messages? And other side will combine those two messages using

Re: GEODE-2708: Upgrading Gradle Wrapper to 3.4.1

This is now checked in on Develop. Happy Building! --Mark On Tue, May 2, 2017 at 11:46 AM, Udo Kohlmeyer wrote: > +1, so have I > > > > On 5/2/17 11:09, Jared Stewart wrote: > >> +1 I've been running with Gradle 3+ without issues too >> >> On May 2, 2017, at 11:04 AM,

[jira] [Created] (GEODE-2879) LonerDistributionManager's Shutdown not being called in close()

nabarun created GEODE-2879: -- Summary: LonerDistributionManager's Shutdown not being called in close() Key: GEODE-2879 URL: https://issues.apache.org/jira/browse/GEODE-2879 Project: Geode Issue

Re: Review Request 58888: GEODE-2632: change dependencies on GemFireCacheImpl to InternalCache

> On May 4, 2017, 11:08 p.m., Ken Howe wrote: > > geode-core/src/main/java/org/apache/geode/internal/cache/PartitionedRegion.java > > Line 8918 (original), 8603 (patched) > > > > > > Was this intended to be

Re: Review Request 58888: GEODE-2632: change dependencies on GemFireCacheImpl to InternalCache

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5/#review173972 ---

[jira] [Created] (GEODE-2878) If an exception occurs after retrieving an XAConnection from the ConnectionProvider but before returning it to the application, the GemFireTransactionDataSource doesn't r

Barry Oglesby created GEODE-2878: Summary: If an exception occurs after retrieving an XAConnection from the ConnectionProvider but before returning it to the application, the GemFireTransactionDataSource doesn't return it to the pool

[jira] [Commented] (GEODE-2708) Update Gradle Wrapper to Gradle 3

[ https://issues.apache.org/jira/browse/GEODE-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997600#comment-15997600 ] ASF subversion and git services commented on GEODE-2708: Commit

[jira] [Commented] (GEODE-2708) Update Gradle Wrapper to Gradle 3

[ https://issues.apache.org/jira/browse/GEODE-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997601#comment-15997601 ] ASF subversion and git services commented on GEODE-2708: Commit

Re: [gemfire-dev] New Client-Server Protocol Proposal

+1 for that as well On Thu, May 4, 2017 at 5:21 PM Dan Smith wrote: > > > > I wouldn't tackle that at this layer. I would suggest adding a layer > > between the message and TCP that creates channels that are opaque to the > > message layer above. The message layer wouldn't

[jira] [Commented] (GEODE-2879) LonerDistributionManager's Shutdown not being called in close()

[ https://issues.apache.org/jira/browse/GEODE-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997666#comment-15997666 ] ASF subversion and git services commented on GEODE-2879: Commit

Re: Review Request 58813: GEODE-2776 After region is updated with loader, the ClientEvent is set with current entry version tag

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58813/ --- (Updated May 5, 2017, 3:57 a.m.) Review request for geode, Darrel Schneider,

Geode Native Release

All, I want to start the discussion on releasing Geode Native C++ and .NET clients with the next or near future Geode release. There are a few house keeping items left in the source release JIRA [1]. It would be great to get some help completing these tasks. If we start with a source only

[jira] [Assigned] (GEODE-234) remove deprecated MirrorType class

[ https://issues.apache.org/jira/browse/GEODE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avinash Dongre reassigned GEODE-234: Assignee: Avinash Dongre > remove deprecated MirrorType class >

Build failed in Jenkins: Geode-nightly #825

See Changes: [nnag] GEODE-2828: AEQ created before the Lucene user regions [eshu] GEODE-2847: Get correct version tags for retried bulk operations [eshu] GEODE-2847: Get correct version tags for retried bulk

Re: Review Request 58996: GEODE-2876: Add logging to diagnose CI failure

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58996/#review173938 --- Ship it! Ship It! - Kirk Lund On May 4, 2017, 5:12 p.m.,

Re: Geode Native Release

I don't see how they are different branches? If geode-Native has release/1.2 and Geode has release/1.2? Sent from my iPhone > On May 4, 2017, at 10:21 AM, Anthony Baker wrote: > > I think it’s confusing to cut a release from different branches for geode, > geode-examples,

Re: [gemfire-dev] New Client-Server Protocol Proposal

There would be one Message containing a single MessageHeader and a single MessageBody. A PDX EncodedValue containing 1242 bytes that are chunked would look something like this: PDX 1000 byte[1000] 242 byte[242] 0 Anthony > On May 4, 2017, at 10:38 AM, Hitesh Khamesra

Re: Geode Native Release

Let’s say we release geode-native along with geode 1.2. When it comes time to release 1.3 (and geode-native is not yet ready) we would be creating release branches from: geode: develop geode-example: develop geode-native: release/v1.2.0 Anthony > On May 4, 2017,

[jira] [Updated] (GEODE-1996) There are confusing references to "multicast" for locators ports

[ https://issues.apache.org/jira/browse/GEODE-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-1996: --- Description: The documentation seems to contain confusing terms when it comes to locators and

Re: [gemfire-dev] New Client-Server Protocol Proposal

And len 0 would indicate end of the message? a. Now these two chunks will go continuous. b. If its PDX encoded then pdx header(1byte:pdxid 4byte:len 4byte:typeId) requires size of all pdx serialized bytes. So we know "size" of data upfront here. c. Lets say region value is just long