[jira] [Assigned] (GEODE-2103) start locator command should include --http-service-port and --http-service-bind-address

[ https://issues.apache.org/jira/browse/GEODE-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit reassigned GEODE-2103: --- Assignee: Deepak Dixit > start locator command should include --http-service-port and > --ht

Re: Review Request 54943: GEODE-2197: refactor cluster config

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/54943/#review160103 --- Ship it! Ship It! - Kirk Lund On Dec. 22, 2016, 6:48 a.m., J

[jira] [Commented] (GEODE-2243) Modify path to spotless formatter

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

[jira] [Commented] (GEODE-2231) Create new partitioning example

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

[jira] [Commented] (GEODE-2243) Modify path to spotless formatter

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

[jira] [Commented] (GEODE-2240) unexpected NullPointerException from Tombstone service

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

[jira] [Commented] (GEODE-2238) Member may fail to receive cluster configuration from locator

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

[jira] [Commented] (GEODE-2243) Modify path to spotless formatter

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

[jira] [Commented] (GEODE-2234) Lucene query hit stats shows number higher than number of calls

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

[jira] [Commented] (GEODE-2242) Destroy operations on PRELOADED regions are not applied in the receiving WAN site

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

[jira] [Commented] (GEODE-165) Add build support for generating antlr classes from grammar

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

[jira] [Commented] (GEODE-165) Add build support for generating antlr classes from grammar

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

[jira] [Commented] (GEODE-2099) Race condition in ConnectToLocatorSSLDUnitTest

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

[jira] [Commented] (GEODE-2109) calling submit on ExecutionService can cause exceptions to be lost

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

[jira] [Commented] (GEODE-2231) Create new partitioning example

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

[jira] [Commented] (GEODE-2231) Create new partitioning example

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

Re: Nightly build takes too long

+1 Twelve hours is a long time. On Fri, Dec 23, 2016 at 11:55 AM, Kirk Lund wrote: > Nevermind. This one failed due to a BindException. > > It's still probably a good idea to break up the nightly build since it's > taking over 12 hours. > > -Kirk > > > On Fri, Dec 23, 2016 at 11:51 AM, Kirk Lun

[jira] [Commented] (GEODE-2239) CI failure: org.apache.geode.pdx.JSONFormatterJUnitTest.testJSONFormatterAPIs

[ https://issues.apache.org/jira/browse/GEODE-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15773599#comment-15773599 ] Darrel Schneider commented on GEODE-2239: - I think this test can be safely changed

Re: Strategy for Updating Public API Changes

+1 that's exactly what deprecation is for -- Mike Stolz Principal Engineer - Gemfire Product Manager Mobile: 631-835-4771 On Dec 23, 2016 2:37 PM, "Darrel Schneider" wrote: > If changing an external API would break existing applications I think it > would be better to introduce a new API that ha

Re: Nightly build takes too long

Nevermind. This one failed due to a BindException. It's still probably a good idea to break up the nightly build since it's taking over 12 hours. -Kirk On Fri, Dec 23, 2016 at 11:51 AM, Kirk Lund wrote: > Geode-nightly #694 failed again because it took too long (over 12 hours). > > What can w

Nightly build takes too long

Geode-nightly #694 failed again because it took too long (over 12 hours). What can we do to break up the nightly build to avoid this? Divide it into two jobs: 1) test and integrationTest, 2) distributedTest? Thanks, Kirk

[jira] [Commented] (GEODE-1577) Unhelpful generic types on Execution.execute

[ https://issues.apache.org/jira/browse/GEODE-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15773558#comment-15773558 ] ASF GitHub Bot commented on GEODE-1577: --- Github user kirklund commented on the issue

[GitHub] geode issue #321: [GEODE-1577] Unhelpful generic types on Execution.execute

Github user kirklund commented on the issue: https://github.com/apache/geode/pull/321 @dalyssakim @metatype @upthewaterspout GEODE-1577 is interesting because Dan labelled it "starter" which would imply that a new contributor should be able to pick it up and run with it without having

Re: Strategy for Updating Public API Changes

If changing an external API would break existing applications I think it would be better to introduce a new API that has the improved behavior. Deprecate the old external API with a comment saying that you should use the new one instead. Then in the next release we can remove the old external depre

[jira] [Commented] (GEODE-2235) test is missing @Test: PrCqUsingPoolDUnitTest.testCqOnAccessorServerWithUpdatesResultingInDestroyedCQEvents

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

[GitHub] geode pull request #324: GEODE-2235 : Adding missing test annotation

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/324 --- 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 enabl

[jira] [Commented] (GEODE-2235) test is missing @Test: PrCqUsingPoolDUnitTest.testCqOnAccessorServerWithUpdatesResultingInDestroyedCQEvents

[ https://issues.apache.org/jira/browse/GEODE-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15773534#comment-15773534 ] ASF GitHub Bot commented on GEODE-2235: --- Github user asfgit closed the pull request

Re: snappy-java dependency version

Just to tie this thread up, use of SnappyCompressor (using org.iq80.snappy) does work on Solaris: gfsh>create region --type=REPLICATE --name=region1 --compressor=org.apache.geode.compression.SnappyCompressor Member | Status --- | -- server1 | Region "/regio

Re: Review Request 54945: GEODE-419: Added test to test fail over to javax properties if ssl enabled but relevant properties are not set

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/54945/#review160098 --- Ship it! Add use of RestoreSystemProperties rule and then Ship

Re: Review Request 54945: GEODE-419: Added test to test fail over to javax properties if ssl enabled but relevant properties are not set

> On Dec. 22, 2016, 6:34 p.m., Bruce Schuchardt wrote: > > I think you should save the system properties in a @Before and restore them > > in an @After Just add RestoreSystemProperties as a JUnit Rule: @Rule public RestoreSystemProperties restoreSystemProperties = new RestoreSystemProperties(

Re: Review Request 54943: GEODE-2197: refactor cluster config

> On Dec. 21, 2016, 8:52 p.m., Bruce Schuchardt wrote: > > geode-core/src/main/java/org/apache/geode/distributed/internal/SharedConfiguration.java, > > line 743 > > > > > > I can't tell from the diff if this method

Re: WAN Get-Initial-Image

Oh yeah, I meant to mention local replication too but forgot. What kind of Region-level API are you thinking of? Something that the new cluster could call via a pool to pull the data for a region? -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: 631-835-4771 On Fri, Dec 23, 201

Review Request 55017: cleaning up code in a few places

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55017/ --- Review request for geode, Galen O'Sullivan, Hitesh Khamesra, and Udo Kohlmeyer.

[GitHub] geode issue #325: merge new version

Github user metatype commented on the issue: https://github.com/apache/geode/pull/325 Thanks for the contribution. However, I'm currently -1 until you clarify the purpose of the change and follow some of the recommendations included in our project contribution guidelines such as:

Re: WAN Get-Initial-Image

I don’t know of anyway current API that behaves the way you want. Snapshot imports (`gfsh import data`) avoid firing listeners AND wan replication. Getting that working correctly was pretty hairy :-) I think you would want to avoid local replication costs associated with a put() as well. Per

[GitHub] geode pull request #325: merge new version

GitHub user zmyer opened a pull request: https://github.com/apache/geode/pull/325 merge new version You can merge this pull request into a Git repository by running: $ git pull https://github.com/zmyer/incubator-geode develop Alternatively you can review and apply these chang

[jira] [Closed] (GEODE-2245) .

[ https://issues.apache.org/jira/browse/GEODE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling closed GEODE-2245. --- > . > - > > Key: GEODE-2245 > URL: https://issues.apache.org/jira/browse/G

[jira] [Resolved] (GEODE-2245) .

[ https://issues.apache.org/jira/browse/GEODE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-2245. - Resolution: Done > . > - > > Key: GEODE-2245 > URL: https://issues

[jira] [Updated] (GEODE-2245) .

[ https://issues.apache.org/jira/browse/GEODE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2245: Summary: . (was: CI Failure: beforeConnectMBeans and registeredMBeans mismatch Diff : [GemFire:ser

[jira] [Updated] (GEODE-2245) CI Failure: beforeConnectMBeans and registeredMBeans mismatch Diff : [GemFire:service=CacheService,name=LuceneService,type=Member,member=managinggemfire2_rs-OperationsBTT

[ https://issues.apache.org/jira/browse/GEODE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2245: Attachment: (was: vm_6_managing1_rs-OperationsBTTest-2016-12-22-22-37-12-client-1_19961.log) >

[jira] [Updated] (GEODE-2245) CI Failure: beforeConnectMBeans and registeredMBeans mismatch Diff : [GemFire:service=CacheService,name=LuceneService,type=Member,member=managinggemfire2_rs-OperationsBTT

[ https://issues.apache.org/jira/browse/GEODE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2245: Component/s: (was: management) > CI Failure: beforeConnectMBeans and registeredMBeans mismatch D

[jira] [Updated] (GEODE-2245) CI Failure: beforeConnectMBeans and registeredMBeans mismatch Diff : [GemFire:service=CacheService,name=LuceneService,type=Member,member=managinggemfire2_rs-OperationsBTT

[ https://issues.apache.org/jira/browse/GEODE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2245: Description: (was: {code} CLIENT vm_6_thr_7_managing1_rs-OperationsBTTest-2016-12-22-22-37-12-cl

WAN Get-Initial-Image

One way to get a new site populated with data would be through a WAN gateway by doing a put(k, get(k)) on every local entry in a Partitioned Region via a server side function. That has the unfortunate side-effect of firing CacheWriters, CacheListeners and AsyncEventListeners though. Is there a mec

[jira] [Updated] (GEODE-2245) CI Failure: beforeConnectMBeans and registeredMBeans mismatch Diff : [GemFire:service=CacheService,name=LuceneService,type=Member,member=managinggemfire2_rs-OperationsBTT

[ https://issues.apache.org/jira/browse/GEODE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2245: Description: {code} CLIENT vm_6_thr_7_managing1_rs-OperationsBTTest-2016-12-22-22-37-12-client-1_19

[jira] [Updated] (GEODE-2245) CI Failure: beforeConnectMBeans and registeredMBeans mismatch Diff : [GemFire:service=CacheService,name=LuceneService,type=Member,member=managinggemfire2_rs-OperationsBTT

[ https://issues.apache.org/jira/browse/GEODE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2245: Attachment: vm_6_managing1_rs-OperationsBTTest-2016-12-22-22-37-12-client-1_19961.log > CI Failure:

[jira] [Created] (GEODE-2245) CI Failure: beforeConnectMBeans and registeredMBeans mismatch Diff : [GemFire:service=CacheService,name=LuceneService,type=Member,member=managinggemfire2_rs-OperationsBTT

Kevin Duling created GEODE-2245: --- Summary: CI Failure: beforeConnectMBeans and registeredMBeans mismatch Diff : [GemFire:service=CacheService,name=LuceneService,type=Member,member=managinggemfire2_rs-OperationsBTTest-2016-12-22-22-37-12-client-1_19

Re: New proposal for type definitons

This is pretty interesting actually. It brings back the good parts of formal schema design. -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: 631-835-4771 On Fri, Dec 23, 2016 at 11:09 AM, Bruce Schuchardt wrote: > I wonder if it would be helpful to use JSON Schema < > http://js

Re: New proposal for type definitons

I wonder if it would be helpful to use JSON Schema as a starting point for this effort? Le 12/22/2016 à 6:45 PM, Udo Kohlmeyer a écrit : Ok, I will try and explain all of this better. --Udo On 12/22/16 16:42, Darrel Schneider wrote: The @refTypeId is hard to unders

Build failed in Jenkins: Geode-nightly #694

See Changes: [adongre] GEODE-165: Removed OQL generated files and added the target into [upthewaterspout] GEODE-2238: Fix how peers discover locators with cluster config [boglesby] GEODE-2234: Query stats are now calculated per member i