Re: A force push happened to geode-native develop!?!

+1 for no force push on shared branches. On Wed, Mar 8, 2017 at 4:59 PM, Mark Bretl wrote: > +1 For no force push > > --Mark > > On Wed, Mar 8, 2017 at 3:50 PM, Kevin Duling wrote: > > > +1. Don't turn to the dark side of the --force. > > > > On Mar 8,

[jira] [Assigned] (GEODE-2622) Fix failures in GMSMembershipManagerJUnitTest caused by upgrading to mockito 2.7.11

[ https://issues.apache.org/jira/browse/GEODE-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Manvi reassigned GEODE-2622: - Assignee: Srikanth Manvi > Fix failures in GMSMembershipManagerJUnitTest caused by

Build failed in Jenkins: Geode-nightly #770

See Changes: [dbarnes] GEODE-2591 User guide: Lucene headings should be reflected in navigation [klund] GEODE-2593: add port range to AvailablePortHelper to fix [huynhja] GEODE-2579: ClassCastException cannot

Re: [GSoC] Interested in GSoC 2017 ideas

Hi Kai: I have couple of ideas.. 1. Reliable event processing on Geode.2. New developer friendly apis on Geode. Let me know if you some query on this or you have some other idea. Thanks.Hitesh From: Kai Jiang To: dev@geode.apache.org Cc: William Markito Oliveira

[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 ] Diane Hardman updated GEODE-2617: - Component/s: lucene > LuceneResultStruct should be Serializable >

[GitHub] geode pull request #421: GEODE-2595: Change LuceneService.createIndex to use...

GitHub user upthewaterspout opened a pull request: https://github.com/apache/geode/pull/421 GEODE-2595: Change LuceneService.createIndex to use a factory Changing LuceneService.createIndex to createIndexFactory and using a factory pattern to create the index. This

[jira] [Commented] (GEODE-2595) Change LuceneService.createIndex to use a factory pattern

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

Re: Review Request 57206: let LuceneResultStruct to be Serializable, then customer does not have to defined their Serializable class to hold result

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57206/ --- (Updated March 9, 2017, 1:20 a.m.) Review request for geode, Barry Oglesby and

Re: A force push happened to geode-native develop!?!

+1 For no force push --Mark On Wed, Mar 8, 2017 at 3:50 PM, Kevin Duling wrote: > +1. Don't turn to the dark side of the --force. > > On Mar 8, 2017 3:12 PM, "Dan Smith" wrote: > > > Yeah, shared branches was kinda of a vague term. I am talking about > >

Review Request 57439: GEODE-2576: delete the zip file on locator after it's being streamed to client.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57439/ --- Review request for geode, Jared Stewart, Kevin Duling, Ken Howe, and Kirk Lund.

[jira] [Created] (GEODE-2638) A GatewaySender fails to start if it attempts to connect to a remote locator that is an unresolvable hostname

Barry Oglesby created GEODE-2638: Summary: A GatewaySender fails to start if it attempts to connect to a remote locator that is an unresolvable hostname Key: GEODE-2638 URL:

[jira] [Commented] (GEODE-2635) Create Lucene DUnit tests to check eviction attributes

[ https://issues.apache.org/jira/browse/GEODE-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902230#comment-15902230 ] ASF GitHub Bot commented on GEODE-2635: --- Github user upthewaterspout commented on a diff in the pull

[GitHub] geode pull request #420: GEODE-2635: Creating DUnit tests to test eviction i...

Github user upthewaterspout commented on a diff in the pull request: https://github.com/apache/geode/pull/420#discussion_r105061375 --- Diff: geode-lucene/src/test/java/org/apache/geode/cache/lucene/EvictionDUnitTest.java --- @@ -0,0 +1,145 @@ +/* + * Licensed to the

[jira] [Assigned] (GEODE-2599) `start locator` prints `null` in startup dots.

[ https://issues.apache.org/jira/browse/GEODE-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-2599: Assignee: Kirk Lund > `start locator` prints `null` in startup dots. >

[GitHub] geode pull request #420: GEODE-2635: Creating DUnit tests to test eviction i...

GitHub user nabarunnag opened a pull request: https://github.com/apache/geode/pull/420 GEODE-2635: Creating DUnit tests to test eviction in lucene * DUnit tests for eviction with local destroy and overflow * Refactored the integration tests for eviction

[jira] [Commented] (GEODE-2592) Document Lucene-related gfsh commands

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

Re: A force push happened to geode-native develop!?!

+1. Don't turn to the dark side of the --force. On Mar 8, 2017 3:12 PM, "Dan Smith" wrote: > Yeah, shared branches was kinda of a vague term. I am talking about > develop, master, and release*. > > I think in general if you are working on a feature branch with along other >

Re: [jira] [Commented] (GEODE-2576) delete the old exported zip on the locator

Agreed. There is NO value in holding onto it. -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: +1-631-835-4771 On Wed, Mar 8, 2017 at 6:34 PM, Swapnil Bawaskar (JIRA) wrote: > > [ https://issues.apache.org/jira/browse/GEODE-2576?page= >

[jira] [Reopened] (GEODE-2539) Upgrading Jetty causes RestSecurityIntegrationTest to fail

[ https://issues.apache.org/jira/browse/GEODE-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reopened GEODE-2539: - Integration test failed as a result of this change. Backed out until resolved > Upgrading Jetty

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #494 was SUCCESSFUL (with 1680 tests)

--- Spring Data GemFire > Nightly-ApacheGeode > #494 was successful (rerun once). --- This build was rerun by John Blum. 1682 tests in total.

Re: A force push happened to geode-native develop!?!

Yeah, shared branches was kinda of a vague term. I am talking about develop, master, and release*. I think in general if you are working on a feature branch with along other people, you also shouldn't force push that feature branch, but for the moment the proposal is just to protect develop,

Re: A force push happened to geode-native develop!?!

I believe it is (but would be good to verify). Anthony > On Mar 8, 2017, at 1:55 PM, Jared Stewart wrote: > > +1 to blocking force pushes on shared branches. It also would seem prudent > to block 'git push —delete’ on shared branches if that isn’t already blocked. > >>

Re: Review Request 57431: GEODE-2633: When turning on fine logging, GEODE logs the keystore password in clear text

> On March 8, 2017, 9:16 p.m., Jinmei Liao wrote: > > Any test changes? We probably can create a integrated/dunit test that would > > start a server with those ssl properties (including passwords) turned on, > > and have debug level truned on, and security truned on as well, and have > > gfsh

Re: A force push happened to geode-native develop!?!

When I say “shared branches”, I’m thinking of develop, master, and release-* as mentioned by Dan. > On Mar 8, 2017, at 3:03 PM, Dave Barnes wrote: > >> It also would seem prudent to block 'git push —delete’ on shared branches > > Isn't that how we clean up feature

Re: A force push happened to geode-native develop!?!

> It also would seem prudent to block 'git push —delete’ on shared branches Isn't that how we clean up feature branches? On Wed, Mar 8, 2017 at 1:55 PM, Jared Stewart wrote: > +1 to blocking force pushes on shared branches. It also would seem > prudent to block 'git push

Re: A force push happened to geode-native develop!?!

+1 to blocking force pushes on shared branches. It also would seem prudent to block 'git push —delete’ on shared branches if that isn’t already blocked. > On Mar 8, 2017, at 1:48 PM, Dan Smith wrote: > > Karen and I just spent a long time tracking down weird git history in

Re: [VOTE] Marking Redis Adapter as Experimental

+1. Good to know. I was just talking to a potential customer this morning that’s intent on replacing voldemort with an IMDG and wanting to merge whatever solution with their current Redis use cases. If its not ready I want to make sure I’m not giving bad information. Wayne Lund Advisory

Re: [VOTE] Marking Redis Adapter as Experimental

+1 for marking it experimental and going ahead with changing it. -Dan On Wed, Mar 8, 2017 at 2:21 PM, Michael Stolz wrote: > +1 to marking it experimental now > > Once we do that I think it will be fine for the community to make breaking > changes to it if we need to. > > --

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #494 has FAILED (1 tests failed)

--- Spring Data GemFire > Nightly-ApacheGeode > #494 failed. --- Scheduled 1/1682 tests failed. https://build.spring.io/browse/SGF-NAG-494/

Re: Review Request 57431: GEODE-2633: When turning on fine logging, GEODE logs the keystore password in clear text

> On March 8, 2017, 1:16 p.m., Jinmei Liao wrote: > > Any test changes? We probably can create a integrated/dunit test that would > > start a server with those ssl properties (including passwords) turned on, > > and have debug level truned on, and security truned on as well, and have > > gfsh

Re: A force push happened to geode-native develop!?!

You should never force push a shared branch, period. It's just luck that no one has pushed the changes you intended to remove *back* to develop. If someone has a copy of develop checked out and does a pull, git will merge your new copy of develop with their old copy of develop, and they'll push

[jira] [Commented] (GEODE-2553) Lucene search hangs on recreated region with no data

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

[jira] [Updated] (GEODE-2637) LuceneQueryFactory.setResultLimit() method should match LuceneQuery.getLimit()

[ https://issues.apache.org/jira/browse/GEODE-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-2637: --- Affects Version/s: 1.2.0 > LuceneQueryFactory.setResultLimit() method

[jira] [Created] (GEODE-2637) LuceneQueryFactory.setResultLimit() method should match LuceneQuery.getLimit()

Shelley Lynn Hughes-Godfrey created GEODE-2637: -- Summary: LuceneQueryFactory.setResultLimit() method should match LuceneQuery.getLimit() Key: GEODE-2637 URL:

[jira] [Assigned] (GEODE-2637) LuceneQueryFactory.setResultLimit() method should match LuceneQuery.getLimit()

[ https://issues.apache.org/jira/browse/GEODE-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reassigned GEODE-2637: -- Assignee: Shelley Lynn Hughes-Godfrey >

[jira] [Assigned] (GEODE-2636) Update exemplary code to follow library renaming

[ https://issues.apache.org/jira/browse/GEODE-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge reassigned GEODE-2636: Assignee: Michael Dodge > Update exemplary code to follow library renaming >

[jira] [Commented] (GEODE-2539) Upgrading Jetty causes RestSecurityIntegrationTest to fail

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

[jira] [Created] (GEODE-2636) Update exemplary code to follow library renaming

Michael Dodge created GEODE-2636: Summary: Update exemplary code to follow library renaming Key: GEODE-2636 URL: https://issues.apache.org/jira/browse/GEODE-2636 Project: Geode Issue Type:

Re: [VOTE] Marking Redis Adapter as Experimental

+1 to marking it experimental now Once we do that I think it will be fine for the community to make breaking changes to it if we need to. -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: +1-631-835-4771 On Wed, Mar 8, 2017 at 5:08 PM, Galen M O'Sullivan

[VOTE] Marking Redis Adapter as Experimental

Hi all, I think that we should mark the Redis adapter as experimental. This functionality comes from the initial code grant from GemFire. It is mentioned in the "Experimental" section of the GemFire docs [1], and as far as I can tell, the only reason it hasn't been marked as experimental in Geode

Re: Storing object in deserialized form in geode cache

Mike is correct that the first time you ask a VMCachedDeserializable for the deserialized value that the deserialized value will "stick" in the VMCachedDeserializable. If anyone then asks that VMCachedDeserializable for the serialized value it has to serialize it each time since it is now stuck as

[jira] [Commented] (GEODE-2513) Geode Native docs: rebrand to match open-source software

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

[GitHub] geode-native pull request #49: GEODE-2513 Unbrand docs section on Preserving...

GitHub user karensmolermiller opened a pull request: https://github.com/apache/geode-native/pull/49 GEODE-2513 Unbrand docs section on Preserving Data - Remove references to GemFire - Fix typos - Clarify links that leave the native-manual @davebarnes97

[jira] [Resolved] (GEODE-2616) A colocated paritioned region will leak memory when it is closed or destroyed

[ https://issues.apache.org/jira/browse/GEODE-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-2616. - Resolution: Fixed Fix Version/s: 1.2.0 > A colocated paritioned region will leak

Re: A force push happened to geode-native develop!?!

The force push was done to clean up a bunch of commits that broke develop on the longer list of targeted platforms and moved them to another branch. It could have been done with a series of reverts. Sorry for the confusion. Other pulls pending on Geode native were corrected. I did not see a pull

A force push happened to geode-native develop!?!

Karen and I just spent a long time tracking down weird git history in her checkout to discover that someone did a force push of the geode-native develop. That's not cool, because it screws over anyone with a copy of the branch and we potentially lost history. I think we need to do two things. 1)

[jira] [Created] (GEODE-2635) Create Lucene DUnit tests to check eviction attributes

nabarun created GEODE-2635: -- Summary: Create Lucene DUnit tests to check eviction attributes Key: GEODE-2635 URL: https://issues.apache.org/jira/browse/GEODE-2635 Project: Geode Issue Type: Bug

Re: Review Request 57431: GEODE-2633: When turning on fine logging, GEODE logs the keystore password in clear text

> On March 8, 2017, 9:16 p.m., Jinmei Liao wrote: > > Any test changes? We probably can create a integrated/dunit test that would > > start a server with those ssl properties (including passwords) turned on, > > and have debug level truned on, and security truned on as well, and have > > gfsh

Re: Review Request 57431: GEODE-2633: When turning on fine logging, GEODE logs the keystore password in clear text

> On March 8, 2017, 1:16 p.m., Jinmei Liao wrote: > > Any test changes? We probably can create a integrated/dunit test that would > > start a server with those ssl properties (including passwords) turned on, > > and have debug level truned on, and security truned on as well, and have > > gfsh

[jira] [Assigned] (GEODE-2594) Remove optional usage of Attach API

[ https://issues.apache.org/jira/browse/GEODE-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-2594: Assignee: Kirk Lund > Remove optional usage of Attach API > --- >

[jira] [Commented] (GEODE-2616) A colocated paritioned region will leak memory when it is closed or destroyed

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

Re: Review Request 57431: GEODE-2633: When turning on fine logging, GEODE logs the keystore password in clear text

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57431/#review168333 --- Any test changes? We probably can create a integrated/dunit test

[jira] [Created] (GEODE-2634) gfsh export logs command should be able to filter logs on log-level

Swapnil Bawaskar created GEODE-2634: --- Summary: gfsh export logs command should be able to filter logs on log-level Key: GEODE-2634 URL: https://issues.apache.org/jira/browse/GEODE-2634 Project:

Review Request 57431: GEODE-2633: When turning on fine logging, GEODE logs the keystore password in clear text

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57431/ --- Review request for geode, Jinmei Liao, Jared Stewart, Ken Howe, and Kirk Lund.

[jira] [Assigned] (GEODE-2633) When turning on fine logging, GEODE logs the keystore password in clear text

[ https://issues.apache.org/jira/browse/GEODE-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-2633: --- Assignee: Kevin Duling > When turning on fine logging, GEODE logs the keystore password in

[jira] [Updated] (GEODE-2633) When turning on fine logging, GEODE logs the keystore password in clear text

[ https://issues.apache.org/jira/browse/GEODE-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2633: Component/s: gfsh > When turning on fine logging, GEODE logs the keystore password in clear text >

[jira] [Created] (GEODE-2633) When turning on fine logging, GEODE logs the keystore password in clear text

Kevin Duling created GEODE-2633: --- Summary: When turning on fine logging, GEODE logs the keystore password in clear text Key: GEODE-2633 URL: https://issues.apache.org/jira/browse/GEODE-2633 Project:

[jira] [Resolved] (GEODE-2539) Upgrading Jetty causes RestSecurityIntegrationTest to fail

[ https://issues.apache.org/jira/browse/GEODE-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-2539. - Resolution: Fixed Fix Version/s: 1.2.0 > Upgrading Jetty causes

[jira] [Commented] (GEODE-1198) CI Failure: DistributedSystemDUnitTest.testConflictingUDPPort

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

[jira] [Commented] (GEODE-2614) Build generates javadoc warnings

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

[jira] [Commented] (GEODE-2539) Upgrading Jetty causes RestSecurityIntegrationTest to fail

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

[jira] [Commented] (GEODE-2614) Build generates javadoc warnings

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

[jira] [Commented] (GEODE-2267) Add gfsh command to export stat files

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

[jira] [Commented] (GEODE-2621) CI Failure: ExportLogsDUnitTest.testExportWithStartAndEndDateTimeFiltering

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

[jira] [Commented] (GEODE-1198) CI Failure: DistributedSystemDUnitTest.testConflictingUDPPort

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

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

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

[jira] [Created] (GEODE-2632) Integrated Security performance improvements

Jinmei Liao created GEODE-2632: -- Summary: Integrated Security performance improvements Key: GEODE-2632 URL: https://issues.apache.org/jira/browse/GEODE-2632 Project: Geode Issue Type:

Re: Storing object in deserialized form in geode cache

The rule is, if you deserialize the object in the server side, Geode keeps the deserialized version of it around. As for updating in place...this is the position that the docs for Commercial GemFire take on that subject: "If you do not have the cache copy-on-read attribute set to true, do not

[jira] [Commented] (GEODE-2614) Build generates javadoc warnings

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

[jira] [Assigned] (GEODE-2420) Warn a user if they try to export too much data

[ https://issues.apache.org/jira/browse/GEODE-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-2420: Assignee: Kirk Lund > Warn a user if they try to export too much data >

[jira] [Commented] (GEODE-2614) Build generates javadoc warnings

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

[jira] [Resolved] (GEODE-2614) Build generates javadoc warnings

[ https://issues.apache.org/jira/browse/GEODE-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-2614. Resolution: Fixed Fix Version/s: 1.2.0 > Build generates javadoc warnings >

[jira] [Assigned] (GEODE-2614) Build generates javadoc warnings

[ https://issues.apache.org/jira/browse/GEODE-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-2614: -- Assignee: Jinmei Liao > Build generates javadoc warnings > >

[GitHub] geode pull request #404: Geode 2469

Github user ggreen commented on a diff in the pull request: https://github.com/apache/geode/pull/404#discussion_r104974260 --- Diff: geode-core/src/main/java/org/apache/geode/redis/internal/executor/hash/HashInterpreter.java --- @@ -0,0 +1,126 @@ +/* + * Licensed to the

Re: Review Request 57206: let LuceneResultStruct to be Serializable, then customer does not have to defined their Serializable class to hold result

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57206/#review168312 --- Did this work? I think you need to register the DSFID. See

[jira] [Resolved] (GEODE-2579) ClassCastException cannot cast CompiledIn to CompiledJunction when querying with a junction containing an in clause

[ https://issues.apache.org/jira/browse/GEODE-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh resolved GEODE-2579. Resolution: Fixed Fix Version/s: 1.2.0 > ClassCastException cannot cast CompiledIn to

Re: Feature branch cleanup

I believe there must be some permission regarding "delete branch" that I don't have. I did the following and the command returns saying the branch is deleted, but the branch is STILL there. $ git push origin --delete cluster-config To https://git-wip-us.apache.org/repos/asf/geode.git - [deleted]

Errored: apache/geode-native#152 (develop - aff706b)

Build Update for apache/geode-native - Build: #152 Status: Errored Duration: 14 seconds Commit: aff706b (develop) Author: Danilo Chang Message: GEODE-2509: Build failed at openSUSE LEAP 42.2 This issue is when you use configure but does not specify lib folder

Re: Feature branch cleanup

> On Mar 6, 2017, at 7:46 AM, Anthony Baker wrote: > > Last chance to comment: I’ll be cleaning up these branches over the next few > days. > > Anthony I’ve listed the remaining branches below. If you know that a branch is no longer relevant (e.g. spotlessPlugin) feel

[GitHub] geode issue #397: Add junit to try parsing of simple XML file w pool ...

Github user oshvarts commented on the issue: https://github.com/apache/geode/pull/397 All checks completed, Travis and spotless are happy, could you accept? --- 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