[jira] [Commented] (GEODE-2236) Attempting to remove all CacheListeners from a Region using gfsh throws NullPointerException

2017-01-02 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/GEODE-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15794126#comment-15794126
 ] 

ASF GitHub Bot commented on GEODE-2236:
---

GitHub user deepakddixit opened a pull request:

https://github.com/apache/geode/pull/327

GEODE-2236: Remove all cache-listners using Gfsh

Added check before instantiating cache listner class. Added test to verify 
change.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/deepakddixit/incubator-geode bugfix/GEODE-2236

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/geode/pull/327.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #327


commit 8fe84be51f2ce5e4a604a440bcf0662f227d69ca
Author: Deepak Dixit 
Date:   2017-01-02T06:34:24Z

GEODE-2236: Remove all cache-listners using Gfsh
Added check before instantiating cache listner class. Added test to verify 
change.




> Attempting to remove all CacheListeners from a Region using gfsh throws 
> NullPointerException
> 
>
> Key: GEODE-2236
> URL: https://issues.apache.org/jira/browse/GEODE-2236
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Kevin Duling
>Assignee: Deepak Dixit
>
> The --cache-listener option to the alter region command replaces the existing 
> CacheListeners with the ones set in the option.
> What happens in RegionAlterFunction is that the existing CacheListeners not 
> included in the new list are removed, then the new ones are added.
> So, in theory, to remove all CacheListeners, an empty string could be passed 
> into the --cache-listener option like:
> {noformat}
> alter region --name=data --cache-listener=''
> Executing - alter region --name=data --cache-listener=""
> Member  | Status
> --- | 
> --
> server2 | ERROR: java.lang.NullPointerException
>   at com.gemstone.gemfire.manag..
> server1 | ERROR: java.lang.NullPointerException
>   at com.gemstone.gemfire.manag..
> {noformat}
> This actually works but it throws the NPE below.
> {noformat}
> [error 2016/09/13 09:48:59.943 PDT server1  
> tid=0x40] 
> java.lang.NullPointerException
>   at 
> com.gemstone.gemfire.management.internal.cli.functions.RegionAlterFunction.newInstance(RegionAlterFunction.java:320)
>   at 
> com.gemstone.gemfire.management.internal.cli.functions.RegionAlterFunction.alterRegion(RegionAlterFunction.java:228)
>   at 
> com.gemstone.gemfire.management.internal.cli.functions.RegionAlterFunction.execute(RegionAlterFunction.java:64)
>   at 
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:185)
>   at 
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:386)
>   at 
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:457)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at 
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:692)
>   at 
> com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1149)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> A work-around to this issue is to set a non-existent CacheListener in the 
> --cache-listener option like:
> {noformat}
> alter region --name=data --cache-listener=Fred
> Executing - alter region --name=data --cache-listener=Fred
> Member  | Status
> --- | --
> server1 | ERROR: Could not find class "Fred" specified for "cache-listener".
> server2 | ERROR: Could not find class "Fred" specified for "cache-listener".
> {noformat}
> This correctly throws the ClassNotFoundException below and also removes all 
> the existing CacheListeners.
> {noformat}
> [error 2016/09/13 09:46:40.537 PDT server1  
> tid=0x40] Could not find class "Fred" specified for "cache-listener".
> java.lang.RuntimeException: Could not find class "Fred" specified for 
> "cache-listener".
>   at 
> com.gemstone.gemfire.management.internal.cli.functions.RegionAlterFunction.forName(RegionAlterFunction.java:306)
>   at 
> com.gemstone.gemfire.management.internal.cli.functions.RegionAlterFunction.alterRegion(RegionAlterFunction.java:227)
>   at 
> com.gemstone.gemfire.management.internal.cli.func

[GitHub] geode pull request #327: GEODE-2236: Remove all cache-listners using Gfsh

2017-01-02 Thread deepakddixit 
GitHub user deepakddixit opened a pull request:

https://github.com/apache/geode/pull/327

GEODE-2236: Remove all cache-listners using Gfsh

Added check before instantiating cache listner class. Added test to verify 
change.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/deepakddixit/incubator-geode bugfix/GEODE-2236

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/geode/pull/327.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #327


commit 8fe84be51f2ce5e4a604a440bcf0662f227d69ca
Author: Deepak Dixit 
Date:   2017-01-02T06:34:24Z

GEODE-2236: Remove all cache-listners using Gfsh
Added check before instantiating cache listner class. Added test to verify 
change.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Review Request 55124: fix duplicate entries from list lucene index and search lucene index

2017-01-02 Thread xiaojian zhou 

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

Review request for geode and Dan Smith.


Bugs: geode-2241
https://issues.apache.org/jira/browse/geode-2241


Repository: geode


Description
---

list lucene index is at cache level, region might not be ready. But it's a 
light-weigh command, I just filter out the duplicated entries. 

search lucene index currently will be called on all members, which is bad. I 
pick one of the members with region to execute.


Diffs
-

  
geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/cli/LuceneIndexCommands.java
 0941834 

Diff: https://reviews.apache.org/r/55124/diff/


Testing
---


Thanks,

xiaojian zhou

Re: Review Request 55109: GEODE-1657 Remove silly ^M characters

2017-01-02 Thread Jens Deppe 

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



Probably want to keep these for `gfsh.bat`.

- Jens Deppe


On Dec. 31, 2016, 1:44 a.m., Anthony Baker wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/55109/
> ---
> 
> (Updated Dec. 31, 2016, 1:44 a.m.)
> 
> 
> Review request for geode.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-1657 Remove silly ^M characters
> 
> 
> Diffs
> -
> 
>   KEYS cbc535478664984b81f349178325d91d86b68004 
>   extensions/geode-modules-assembly/release/conf/cache-client.xml 
> 297b6a66c8f98bbefaeee2a3212bef146d03db66 
>   extensions/geode-modules-assembly/release/conf/cache-peer.xml 
> 0480dcac59f5377bd4be7ab2464c569ed7534b20 
>   extensions/geode-modules-assembly/release/conf/cache-server.xml 
> d67b456839de66cc8bc5f492e862285d51454946 
>   geode-assembly/src/main/dist/bin/gfsh.bat 
> 8206b6e7ab5c3e57f9557d87114fcb34b67fde6f 
>   
> geode-core/src/main/resources/org/apache/geode/distributed/internal/membership/gms/messenger/jgroups-config.xml
>  a12e28983c02e550ec74153eb7e74b916daeee50 
>   
> geode-core/src/test/resources/org/apache/geode/codeAnalysis/sanctionedSerializables.txt
>  03bb3ea9d4c388ea4a88d1f05d23c568d0ec87fd 
>   
> geode-core/src/test/resources/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventQueueValidationsJUnitTest.testParallelAsyncEventQueueConfiguredFromXmlUsesFilter.cache.xml
>  bc834377f5d22df76896fda55e267a3cbd5720f2 
>   
> geode-core/src/test/resources/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventQueueValidationsJUnitTest.testSerialAsyncEventQueueConfiguredFromXmlUsesFilter.cache.xml
>  7b823234615629b47f0d169b997ed0b962161eca 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/array.txt 
> 9209f95d39d6b22ad0cf5d46f2f952fad9fad4ef 
>   
> geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/attachment.txt 
> c5e90628243facb1b1011ee3be14b9e35f60d27b 
>   
> geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/attachment2.txt
>  a11ca0d52df25bb3beece9ed894754d99562f8f5 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/book.txt 
> fc297eea0c8ddfdd0f146cec72a5e0f7058e6595 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/image.txt 
> 304f2e2624b8ada1595f3a6eb3fd9cfa560f103b 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json1.txt 
> 61892f65e9112d7a7e72fd88b6489c9d39147afe 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json10.txt 
> 471744a481a3c924d69b08aeaa02696af81fd6e3 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json11.txt 
> ae91e50c97b6ed7de30edb159e4fc76fb1f11d8a 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json12.txt 
> c1943f4ff91c55ffe97d9d12cb04fc645e81902e 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json13.txt 
> 06f5ab8b7405081a1e606f1cc98c7df0e92472c0 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json14.txt 
> 618a20632f4f5ec2f8b7626bc52860095c4be339 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json16.txt 
> 50e30d32e5575f8015d9892c7612d32405f4f5ae 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json16_2.txt 
> 06b43e7c8beae703eefea17f3143e0cdf1f3070e 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json17.txt 
> a302da03d89e07be9a427b855c2cb9ce8e6c411a 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json18.txt 
> 82138f5beac4fc7351881288b56fff3b77bf608a 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json19.txt 
> 0b6e7f252e9ff595acdf286edf3475523e876cff 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json2.txt 
> f8fa3338bea31b883a5f1d8a7ca91031812f1192 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json20.txt 
> cfe5b555688d8141ba78b2590ffad0dea4b17acf 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json21.txt 
> cfe5b555688d8141ba78b2590ffad0dea4b17acf 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json22.txt 
> cfe5b555688d8141ba78b2590ffad0dea4b17acf 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json23.txt 
> d48f5d2bef9f5a0bfa64371d420e33cdb8e17d2c 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json24.txt 
> dc5bbca6dcfa57146f03dac01f4241b5fe2f354e 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json25.txt 
> f7a12e3a03b0150a6aea23006a08b304bff17c86 
>   geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json26.txt 
> a827405fe0af11aecfd389b3954adcefe3a282e5 
>   geode-core/src/test/res

RE: Off-Heap Annotations

2017-01-02 Thread Dor Ben Dov 
Dan
This means also that I can do this dynamically or is it static definition?

Dor

-Original Message-
From: Dan Smith [mailto:dsm...@pivotal.io] 
Sent: יום ב 02 ינואר 2017 19:46
To: dev@geode.apache.org
Subject: Re: Off-Heap Annotations

Hi Gal,

The way to control what is on or off heap is when you configure a region.
Regions that are configured with off-heap=true will store all of the values in 
off heap memory, regions with off-heap= false will store the values on the heap.

-Dan

On Mon, Jan 2, 2017 at 5:57 AM, Gal Palmery  wrote:

> Thanks Kirk.
>
> for example, before I call put, I'd like to indicate to geode server 
> that I want to keep specific data off heap. how can I do that?
> is there an api that will move data off or on heap?
>
> Gal
>
> -Original Message-
> From: Kirk Lund [mailto:kl...@apache.org]
> Sent: Tuesday, December 27, 2016 06:33
> To: dev@geode.apache.org
> Subject: Re: Off-Heap Annotations
>
> Those annotations are part of the internal implementation of Geode. 
> The developers used it as a way to help keep track of references to off-heap.
>
> -Kirk
>
>
> On Mon, Dec 26, 2016 at 1:34 AM, Gal Palmery 
> wrote:
>
> > Hi everyone,
> >
> > Is this feature:
> > https://cwiki.apache.org/confluence/display/GEODE/Off-Heap+Annotatio
> > ns a part of the last release? (1.0.0-incubating)
> >
> > thanks,
> > Gal
> >
> > This message and the information contained herein is proprietary and 
> > confidential and subject to the Amdocs policy statement, you may 
> > review at http://www.amdocs.com/email_disclaimer.asp
> >
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
>
> you may review at http://www.amdocs.com/email_disclaimer.asp
>
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at http://www.amdocs.com/email_disclaimer.asp

Re: Off-Heap Annotations

2017-01-02 Thread Dan Smith 
Hi Gal,

The way to control what is on or off heap is when you configure a region.
Regions that are configured with off-heap=true will store all of the values
in off heap memory, regions with off-heap= false will store the values on
the heap.

-Dan

On Mon, Jan 2, 2017 at 5:57 AM, Gal Palmery  wrote:

> Thanks Kirk.
>
> for example, before I call put, I'd like to indicate to geode server that
> I want to keep specific data off heap. how can I do that?
> is there an api that will move data off or on heap?
>
> Gal
>
> -Original Message-
> From: Kirk Lund [mailto:kl...@apache.org]
> Sent: Tuesday, December 27, 2016 06:33
> To: dev@geode.apache.org
> Subject: Re: Off-Heap Annotations
>
> Those annotations are part of the internal implementation of Geode. The
> developers used it as a way to help keep track of references to off-heap.
>
> -Kirk
>
>
> On Mon, Dec 26, 2016 at 1:34 AM, Gal Palmery 
> wrote:
>
> > Hi everyone,
> >
> > Is this feature:
> > https://cwiki.apache.org/confluence/display/GEODE/Off-Heap+Annotations
> > a part of the last release? (1.0.0-incubating)
> >
> > thanks,
> > Gal
> >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement, you may
> > review at http://www.amdocs.com/email_disclaimer.asp
> >
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at http://www.amdocs.com/email_disclaimer.asp
>

[jira] [Commented] (GEODE-1995) remove ReliableMessageQueueFactory, ReliableMessageQueue, and getReliableMessageQueueFactory

2017-01-02 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/GEODE-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15793163#comment-15793163
 ] 

ASF GitHub Bot commented on GEODE-1995:
---

Github user davinash commented on the issue:

https://github.com/apache/geode/pull/315
  
Is this PR looking good now ?


> remove ReliableMessageQueueFactory, ReliableMessageQueue, and 
> getReliableMessageQueueFactory
> 
>
> Key: GEODE-1995
> URL: https://issues.apache.org/jira/browse/GEODE-1995
> Project: Geode
>  Issue Type: Improvement
>  Components: regions
>Reporter: Darrel Schneider
>Assignee: Avinash Dongre
>
> ReliableMessageQueueFactory, ReliableMessageQueue, and 
> GemFireCacheImpl.getReliableMessageQueueFactory should all be removed. They 
> are internal and were never used. No tests exist for them.
> They are part of required Roles which is a deprecated feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] geode issue #315: GEODE-1995: Removed ReliableMessageQueue, ReliableMessageQ...

2017-01-02 Thread davinash 
Github user davinash commented on the issue:

https://github.com/apache/geode/pull/315
  
Is this PR looking good now ?


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Build failed in Jenkins: Geode-nightly #704

2017-01-02 Thread Apache Jenkins Server 
See 

--
[...truncated 544 lines...]
:geode-cq:compileTestJavaNote: Some input files use or override a deprecated 
API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-cq:processTestResources
:geode-cq:testClasses
:geode-cq:checkMissedTests
:geode-cq:spotlessJavaCheck
:geode-cq:spotlessCheck
:geode-cq:test
:geode-cq:check
:geode-cq:build
:geode-cq:distributedTest
:geode-cq:flakyTest
:geode-cq:integrationTest
:geode-json:assemble
:geode-json:compileTestJava UP-TO-DATE
:geode-json:processTestResources UP-TO-DATE
:geode-json:testClasses UP-TO-DATE
:geode-json:checkMissedTests UP-TO-DATE
:geode-json:spotlessJavaCheck
:geode-json:spotlessCheck
:geode-json:test UP-TO-DATE
:geode-json:check
:geode-json:build
:geode-json:distributedTest UP-TO-DATE
:geode-json:flakyTest UP-TO-DATE
:geode-json:integrationTest UP-TO-DATE
:geode-junit:javadoc
:geode-junit:javadocJar
:geode-junit:sourcesJar
:geode-junit:signArchives SKIPPED
:geode-junit:assemble
:geode-junit:compileTestJava
:geode-junit:processTestResources UP-TO-DATE
:geode-junit:testClasses
:geode-junit:checkMissedTests
:geode-junit:spotlessJavaCheck
:geode-junit:spotlessCheck
:geode-junit:test
:geode-junit:check
:geode-junit:build
:geode-junit:distributedTest
:geode-junit:flakyTest
:geode-junit:integrationTest
:geode-lucene:assemble
:geode-lucene:compileTestJavaNote: Some input files use or override a 
deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-lucene:processTestResources
:geode-lucene:testClasses
:geode-lucene:checkMissedTests
:geode-lucene:spotlessJavaCheck
:geode-lucene:spotlessCheck
:geode-lucene:test
:geode-lucene:check
:geode-lucene:build
:geode-lucene:distributedTest
:geode-lucene:flakyTest
:geode-lucene:integrationTest
:geode-old-client-support:assemble
:geode-old-client-support:compileTestJava
:geode-old-client-support:processTestResources UP-TO-DATE
:geode-old-client-support:testClasses
:geode-old-client-support:checkMissedTests
:geode-old-client-support:spotlessJavaCheck
:geode-old-client-support:spotlessCheck
:geode-old-client-support:test
:geode-old-client-support:check
:geode-old-client-support:build
:geode-old-client-support:distributedTest
:geode-old-client-support:flakyTest
:geode-old-client-support:integrationTest
:geode-pulse:assemble
:geode-pulse:compileTestJavaNote: 

 uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-pulse:processTestResources
:geode-pulse:testClasses
:geode-pulse:checkMissedTests
:geode-pulse:spotlessJavaCheck
:geode-pulse:spotlessCheck
:geode-pulse:test
:geode-pulse:check
:geode-pulse:build
:geode-pulse:distributedTest
:geode-pulse:flakyTest
:geode-pulse:integrationTest
:geode-rebalancer:assemble
:geode-rebalancer:compileTestJava
:geode-rebalancer:processTestResources UP-TO-DATE
:geode-rebalancer:testClasses
:geode-rebalancer:checkMissedTests
:geode-rebalancer:spotlessJavaCheck
:geode-rebalancer:spotlessCheck
:geode-rebalancer:test
:geode-rebalancer:check
:geode-rebalancer:build
:geode-rebalancer:distributedTest
:geode-rebalancer:flakyTest
:geode-rebalancer:integrationTest
:geode-wan:assemble
:geode-wan:compileTestJavaNote: Some input files use or override a deprecated 
API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-wan:processTestResources
:geode-wan:testClasses
:geode-wan:checkMissedTests
:geode-wan:spotlessJavaCheck
:geode-wan:spotlessCheck
:geode-wan:test
:geode-wan:check
:geode-wan:build
:geode-wan:distributedTest
:geode-wan:flakyTest
:geode-wan:integrationTest
:geode-web:assemble
:geode-web:compileTestJavaNote: Some input files use or override a deprecated 
API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-web:processTestResources UP-TO-DATE
:geode-web:testClasses
:geode-web:checkMissedTests
:geode-web:spotlessJavaCheck
:geode-web:spotlessCheck
:geode-web:test
:geode-web:check
:geode-web:build
:geode-web:distributedTest
:geode-web:flakyTest
:geode-web:integrationTest
:geode-web-api:assemble
:geode-web-api:compileTestJava UP-TO-DATE
:geode-web-api:processTestResources UP-TO-DATE
:geode-web-api:testClasses UP-TO-DATE
:geode-web-api:checkMissedTests UP-TO-DATE
:geode-web-api:spotlessJavaCheck
:geode-web-api:spotlessCheck
:geode-web-api:test UP-

RE: Off-Heap Annotations

2017-01-02 Thread Gal Palmery 
Thanks Kirk.

for example, before I call put, I'd like to indicate to geode server that I 
want to keep specific data off heap. how can I do that?
is there an api that will move data off or on heap?

Gal

-Original Message-
From: Kirk Lund [mailto:kl...@apache.org] 
Sent: Tuesday, December 27, 2016 06:33
To: dev@geode.apache.org
Subject: Re: Off-Heap Annotations

Those annotations are part of the internal implementation of Geode. The 
developers used it as a way to help keep track of references to off-heap.

-Kirk


On Mon, Dec 26, 2016 at 1:34 AM, Gal Palmery  wrote:

> Hi everyone,
>
> Is this feature:
> https://cwiki.apache.org/confluence/display/GEODE/Off-Heap+Annotations
> a part of the last release? (1.0.0-incubating)
>
> thanks,
> Gal
>
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement, you may 
> review at http://www.amdocs.com/email_disclaimer.asp
>
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at http://www.amdocs.com/email_disclaimer.asp