Re: Index management

[Dan Smith]

+1 - You should only be able to remove an index from the whole region.

-Dan

On Mon, May 23, 2016 at 9:49 AM, Jens Deppe  wrote:

> ​Just recently I had reason to look​ at the gfsh *destroy index* call [1].
> I noticed that an index can be destroyed using *any one* of the following
> attributes: index name, region name, member name and group name.
>
> Deleting an index by name or removing all indexes from a region makes
> sense. However what does it mean to remove an index from a single member or
> from a group? Wouldn't that result in the possibility of having an
> 'unbalanced' set of indexes where some members hosting a region have an
> index defined, but other members don't? Seems like a recipe for serious
> misconfiguration. I really don't understand the semantics of these two
> scenarios. (I also couldn't find anything in the docs which explained this
> more). Even the QueryService interface has no methods to delete indexes by
> member or group.
>
> Unless there is an obvious scenario I don't understand, I'd like to propose
> we remove the ability (in gfsh at least) to destroy an index by *member* or
> *group*.
>
> --Jens
>
> [1]
>
> https://github.com/apache/incubator-geode/blob/8a3c351abd971ba740e77364a431aee7d5cc5b10/geode-core/src/main/java/com/gemstone/gemfire/management/internal/cli/commands/IndexCommands.java#L327
>

Re: Index management

[Anilkumar Gingade]

Agree

The indexes are operated using api/xml at a peer/server node level; there
is no client-server index operation command; one reason index destroy is
supported on member, to simulate what api is supported...As you mentioned
it may not make sense to have it from Gfsh.

-Anil.


On Mon, May 23, 2016 at 9:49 AM, Jens Deppe  wrote:

> ​Just recently I had reason to look​ at the gfsh *destroy index* call [1].
> I noticed that an index can be destroyed using *any one* of the following
> attributes: index name, region name, member name and group name.
>
> Deleting an index by name or removing all indexes from a region makes
> sense. However what does it mean to remove an index from a single member or
> from a group? Wouldn't that result in the possibility of having an
> 'unbalanced' set of indexes where some members hosting a region have an
> index defined, but other members don't? Seems like a recipe for serious
> misconfiguration. I really don't understand the semantics of these two
> scenarios. (I also couldn't find anything in the docs which explained this
> more). Even the QueryService interface has no methods to delete indexes by
> member or group.
>
> Unless there is an obvious scenario I don't understand, I'd like to propose
> we remove the ability (in gfsh at least) to destroy an index by *member* or
> *group*.
>
> --Jens
>
> [1]
>
> https://github.com/apache/incubator-geode/blob/8a3c351abd971ba740e77364a431aee7d5cc5b10/geode-core/src/main/java/com/gemstone/gemfire/management/internal/cli/commands/IndexCommands.java#L327
>

Re: Review Request 47686: GEODE-11: Added changes to Lucene AEQ, to propagate destroy events due to eviction and expiration (by setting the flag ignoreEvictionAndExpiration()).

[anilkumar gingade]

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

(Updated May 24, 2016, 12:05 a.m.)


Review request for geode, anilkumar gingade, Barry Oglesby, nabarun nag, Dan 
Smith, and xiaojian zhou.


Changes
---

Revoved the commented expiration action in the test.


Repository: geode


Description
---

GEODE-11: Added changes to Lucene AEQ, to propagate destroy events due to 
eviction and expiration (by setting the flag ignoreEvictionAndExpiration()).
  
Added test to verify, the lucene index gets updated with expiration destroy 
operation.   
Also added support to specify wild-char as leading wild character with Lucene 
Query.


Diffs (updated)
-

  
geode-lucene/src/main/java/com/gemstone/gemfire/cache/lucene/internal/LuceneIndexForPartitionedRegion.java
 d22ca4a196df3b1a457b56c92da694bdbf792cc2 
  
geode-lucene/src/main/java/com/gemstone/gemfire/cache/lucene/internal/StringQueryProvider.java
 1e2b63d0fc5c7fad79063199c473bbd9d4e6fd00 
  
geode-lucene/src/test/java/com/gemstone/gemfire/cache/lucene/LuceneIndexMaintenanceIntegrationTest.java
 07780ca06a297851c8ff4cb498a09f726a0785d5 
  
geode-lucene/src/test/java/com/gemstone/gemfire/cache/lucene/LuceneQueriesIntegrationTest.java
 15f5747231097df5223d97bb49110229efe6a824 

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


Testing
---


Thanks,

anilkumar gingade

Re: Review Request 47686: GEODE-11: Added changes to Lucene AEQ, to propagate destroy events due to eviction and expiration (by setting the flag ignoreEvictionAndExpiration()).

[anilkumar gingade]

> On May 23, 2016, 3:54 p.m., Jason Huynh wrote:
> > geode-lucene/src/test/java/com/gemstone/gemfire/cache/lucene/LuceneIndexMaintenanceIntegrationTest.java,
> >  line 120
> > 
> >
> > is this supposed to be commented out?

Good catch...Its not supposed to be commented...Uploaded the latest changes for 
review.


- anilkumar


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


On May 21, 2016, 12:57 a.m., anilkumar gingade wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47686/
> ---
> 
> (Updated May 21, 2016, 12:57 a.m.)
> 
> 
> Review request for geode, anilkumar gingade, Barry Oglesby, nabarun nag, Dan 
> Smith, and xiaojian zhou.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-11: Added changes to Lucene AEQ, to propagate destroy events due to 
> eviction and expiration (by setting the flag ignoreEvictionAndExpiration()).  
> 
> Added test to verify, the lucene index gets updated with expiration destroy 
> operation.   
> Also added support to specify wild-char as leading wild character with Lucene 
> Query.
> 
> 
> Diffs
> -
> 
>   
> geode-lucene/src/main/java/com/gemstone/gemfire/cache/lucene/internal/LuceneIndexForPartitionedRegion.java
>  d22ca4a196df3b1a457b56c92da694bdbf792cc2 
>   
> geode-lucene/src/main/java/com/gemstone/gemfire/cache/lucene/internal/StringQueryProvider.java
>  1e2b63d0fc5c7fad79063199c473bbd9d4e6fd00 
>   
> geode-lucene/src/test/java/com/gemstone/gemfire/cache/lucene/LuceneIndexMaintenanceIntegrationTest.java
>  07780ca06a297851c8ff4cb498a09f726a0785d5 
>   
> geode-lucene/src/test/java/com/gemstone/gemfire/cache/lucene/LuceneQueriesIntegrationTest.java
>  15f5747231097df5223d97bb49110229efe6a824 
> 
> Diff: https://reviews.apache.org/r/47686/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> anilkumar gingade
> 
>

Re: Review Request 46243: GEODE-1209: Added new attribute to forward eviction/expiration to AEQ. Tested with manual testing.

[anilkumar gingade]

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

(Updated May 23, 2016, 11:56 p.m.)


Review request for geode, anilkumar gingade, Barry Oglesby, Jason Huynh, 
nabarun nag, Dan Smith, and xiaojian zhou.


Changes
---

Removed debug messages from the test.


Repository: geode


Description
---

GEODE-1209: Added new attribute to forward eviction/expiration to AEQ. Tested 
with manual testing.

Sending the changes for early feedback on attribute/method names...

Need to add support for xml, gfsh...And new tests...


Diffs (updated)
-

  
geode-core/src/test/java/com/gemstone/gemfire/cache/asyncqueue/AsyncEventQueueEvictionAndExpirationJUnitTest.java
 5efac05 

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


Testing
---

Did manual testing with AEQ with and without eviction and expiration.


Thanks,

anilkumar gingade

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

[Spring CI]

---
Spring Data GemFire > Nightly-ApacheGeode > #318 was successful.
---
Scheduled
1400 tests in total.

https://build.spring.io/browse/SGF-NAG-318/





--
This message is automatically generated by Atlassian Bamboo

Review Request 47745: remove sqlf code in GemFireCacheImpl

[Darrel Schneider]

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

Review request for geode, Eric Shu and Sai Boorlagadda.


Bugs: GEODE-1426
https://issues.apache.org/jira/browse/GEODE-1426


Repository: geode


Description
---

The sqlf instance variables and all subsequent callers of them have been 
removed.


Diffs
-

  geode-core/src/main/java/com/gemstone/gemfire/cache/AttributesFactory.java 
fe7910a2028cbaff6d6bd796a326722c43e3600c 
  
geode-core/src/main/java/com/gemstone/gemfire/distributed/internal/InternalDistributedSystem.java
 91fa558144d18d22b6e563c9286dc47fa77ac5af 
  
geode-core/src/main/java/com/gemstone/gemfire/distributed/internal/membership/gms/mgr/GMSMembershipManager.java
 e3f1050945c554c3ab7ce916280ffd8939dad487 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/AbstractRegionMap.java
 5248d3d89fd5c61bad82e25c2299a5a18a453fea 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/CacheServerImpl.java
 edc44d38bbc100d31458e4c957a859ad80791c24 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/ControllerAdvisor.java
 ab03d8c5316b346217b166c545026eab9d548a16 
  geode-core/src/main/java/com/gemstone/gemfire/internal/cache/EntriesSet.java 
e527d395010095c0c4ac7f4be3fcb054b494f0b8 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/EntryEventImpl.java
 b833ecb8b629a34870bd495ef4ed5f4f039dfa81 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/GemFireCacheImpl.java
 c44f3b7bab1b65770431dbc2d3c08991ee5ce008 
  geode-core/src/main/java/com/gemstone/gemfire/internal/cache/GridAdvisor.java 
7c7ac12c16f03a733dcf003caf9bdf8045543c08 
  geode-core/src/main/java/com/gemstone/gemfire/internal/cache/LocalRegion.java 
d28496cc6e58cf061ce996d45526f3a0bd3ab10f 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/PartitionedRegion.java
 4460a8afb46df4005c9fe3cb2303e85e37d18353 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/TXRemoteCommitMessage.java
 cd75864d2f60b0eb8810c6988da3f2e970e48e5b 
  geode-core/src/main/java/com/gemstone/gemfire/internal/cache/TXState.java 
617873c0553b7ea064f7ffbb4f59c347405efbd9 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/AcceptorImpl.java
 eeb611e339ac1545f46c314bb19dfd329115c0d2 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/ServerConnection.java
 e608db3c18047421a03578d96798379b86dd1a65 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/command/GatewayReceiverCommand.java
 fce11755c774269a5cbdc907565aaa2fc4f53952 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/command/Put.java
 35cc085067cc4dd8086a070e16862b3dc7482cf6 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/command/Put61.java
 cc4c1d6e041b7b7f8c0c26ba51b192857d4e6f1a 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/command/Put65.java
 9be1390afbeceae4b4f2c385bfed76969f1e2d7a 
  
geode-core/src/test/java/com/gemstone/gemfire/cache30/DistributedAckRegionCCEDUnitTest.java
 8f922a0299ead806b5742dd8f3bfa9de2b21c3ad 
  
geode-core/src/test/java/com/gemstone/gemfire/internal/cache/tier/sockets/AcceptorImplJUnitTest.java
 e43797c1b6e657554c51a920fc03700e6b3ae2d5 
  
geode-core/src/test/resources/com/gemstone/gemfire/codeAnalysis/sanctionedSerializables.txt
 b8ef985ec37260eb741aed6e0bf177247af84a77 

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


Testing
---

precheckin


Thanks,

Darrel Schneider

Review Request 47744: deliver event synchronously if it is rejected

[Darrel Schneider]

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

Review request for geode, Scott Jewell and Ken Howe.


Bugs: GEODE-1428
https://issues.apache.org/jira/browse/GEODE-1428


Repository: geode


Description
---

If the event is rejected by the async thread pool then process it synchronously 
instead of logging a warning.

Changed unit test to use close instead of emergencyClose.
Doing this caused an event to be sent after the async thread
pool was shutdown which resulted in a suspect warning without
this fix.


Diffs
-

  geode-core/src/main/java/com/gemstone/gemfire/internal/cache/LocalRegion.java 
d28496cc6e58cf061ce996d45526f3a0bd3ab10f 
  
geode-core/src/test/java/com/gemstone/gemfire/internal/cache/GemFireCacheImplTest.java
 7f95cadd68ad218f32129f6369198ae4ed968454 

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


Testing
---

precheckin


Thanks,

Darrel Schneider

Re: Review Request 47675: GEODE-1389, GEODE-1012: Cleaning up some persistence tests in LuceneIndexRecoveryHAIntegrationTest

[xiaojian zhou]

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


Ship it!




Ship It!

- xiaojian zhou


On May 20, 2016, 10:18 p.m., Dan Smith wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47675/
> ---
> 
> (Updated May 20, 2016, 10:18 p.m.)
> 
> 
> Review request for geode, anilkumar gingade, Barry Oglesby, Jason Huynh, and 
> xiaojian zhou.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> There were two tests in LuceneIndexRecoveryHAIntegrationTest that used
> disk resources. Moved the overflow test too a LuceneQueriesPersistence
> suite, where it will be cleaned up by the DiskRule.
> 
> The recovery test was pretty much the same as an existing test in
> LuceneIndexCreationPersistent.
> 
> 
> Diffs
> -
> 
>   
> geode-lucene/src/test/java/com/gemstone/gemfire/cache/lucene/LuceneIndexCreationPersistenceIntegrationTest.java
>  96b4e93eee313ae98fe9af6463b6e9fc3a7b35c3 
>   
> geode-lucene/src/test/java/com/gemstone/gemfire/cache/lucene/LuceneQueriesPersistenceIntegrationTest.java
>  PRE-CREATION 
>   
> geode-lucene/src/test/java/com/gemstone/gemfire/cache/lucene/internal/LuceneIndexRecoveryHAIntegrationTest.java
>  d32e6d858b1ee0599f257d5866635c38e0f9946c 
> 
> Diff: https://reviews.apache.org/r/47675/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Dan Smith
> 
>

Re: Review Request 47740: GEODE-17: create muti-user security DUnit tests

[Jinmei Liao]

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

(Updated May 23, 2016, 8:49 p.m.)


Review request for geode, Jens Deppe, Kevin Duling, and Kirk Lund.


Summary (updated)
-

GEODE-17: create muti-user security DUnit tests


Repository: geode


Description
---

GEODE-17: create muti-user security DUnit tests


Diffs
-

  
geode-core/src/main/java/com/gemstone/gemfire/management/internal/cli/commands/IndexCommands.java
 b863737538bde99e2756ba4e1a1b9a4d93c17b12 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/cli/commands/CliCommandTestBase.java
 a0966f9d70eec7b7835126cdcb05adeb1cc84269 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/security/CliCommandsSecurityTest.java
 3ccd71c48db8bb3a64c03d58f8c45ec3339a0a93 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/security/GeodeSecurityUtilWithIniFileJUnitTest.java
 63bf4473232f955ee67d94e33083867a8fe954a1 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/security/GfshCommandsSecurityTest.java
 1a153679e98b7c26652793c60b687f6db398426c 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/security/SecurityDUnitTest.java
 PRE-CREATION 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/security/TestCommand.java
 4b482a97ba401e3e300bfc43587dd6a12ec84295 

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


Testing
---

precheckin running


Thanks,

Jinmei Liao

Review Request 47740: GEODE-17: region access needed for destroy index on a specific region

[Jinmei Liao]

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

Review request for geode, Jens Deppe, Kevin Duling, and Kirk Lund.


Repository: geode


Description
---

GEODE-17: create muti-user security DUnit tests


Diffs
-

  
geode-core/src/main/java/com/gemstone/gemfire/management/internal/cli/commands/IndexCommands.java
 b863737538bde99e2756ba4e1a1b9a4d93c17b12 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/cli/commands/CliCommandTestBase.java
 a0966f9d70eec7b7835126cdcb05adeb1cc84269 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/security/CliCommandsSecurityTest.java
 3ccd71c48db8bb3a64c03d58f8c45ec3339a0a93 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/security/GeodeSecurityUtilWithIniFileJUnitTest.java
 63bf4473232f955ee67d94e33083867a8fe954a1 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/security/GfshCommandsSecurityTest.java
 1a153679e98b7c26652793c60b687f6db398426c 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/security/SecurityDUnitTest.java
 PRE-CREATION 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/security/TestCommand.java
 4b482a97ba401e3e300bfc43587dd6a12ec84295 

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


Testing
---

precheckin running


Thanks,

Jinmei Liao

Re: Stats command

[Barry Oglesby]

Here are a couple scripts that use SystemAdmin to dump specific stats.

Make sure to have JAVA_HOME and GEODE environment variables set.

To run the dumpstats.sh script, just give it a stats file like:

./dumpstats.sh cacheserver.gfs
Maximum Memory (GB): 63.136
Average Free Memory (GB): 61.067
Average Used Memory (GB): 2.068
Average Open File Descriptors: 134.65
Maximum Open File Descriptors: 209
Maximum GC Time (ms): 0
Load Average (15): 0.8
Maximum CPU (%): 13.59
Reply Timeouts: 0
Mimumum Nodes: 5
Maximum Nodes: 5
Average Current Clients: 3.06
Average Current Client Connections: 14.86
Maximum Client Thread Queue Size: 0
Average Client Thread Queue Size: 0
Maximum Client Accepts In Progress: 5
Average Client Accepts In Progress: 0.01
Client Failed Connection Attempts: 0
Partitioned Region Statistics:
/envelope
name=/data
bucketCount max=22
putsCompleted max=4031158
putTime max=0
primaryBucketCount max=22


Thanks,
Barry Oglesby


On Mon, May 23, 2016 at 9:30 AM, Darrel Schneider 
wrote:

> I don't know of a way to analyze offline stat archives using gfsh.
>
> But the code for the old gemfire stats command is still in the geode
> source.
> It is: com.gemstone.gemfire.internal.SystemAdmin
> Its "main" is what the old gemfire script executed. Just keep in mind that
> this class is not used by geode so it could go away.
>
> I think it is a good idea to add off-line stat archive analysis to gfsh
> and the "stats" command in SystemAdmin could be used to aid this
> implementation.
>
>
> On Sun, May 22, 2016 at 6:18 AM, Daniel Farcovich <
> daniel.farcov...@amdocs.com> wrote:
>
>> Hi Everyone,
>> Is earlier versions of Gemfire there was a command named stats, which
>> printed statistic values from a statistic archive file.
>> How can I use it in GEODE? Is there a gfsh corresponding command?
>>
>> Thanks,
>> Daniel Farcovich
>>
>>
>> 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
>>
>
>


dumpstats.sh
Description: Bourne shell script


systemadmin.sh
Description: Bourne shell script

GfshParserJUnitTest

[Kirk Lund]

GfshParserJUnitTest is currently failing due to a change I introduced last
Friday. I'll check in a fix soon.

-Kirk

Index management

[Jens Deppe]

​Just recently I had reason to look​ at the gfsh *destroy index* call [1].
I noticed that an index can be destroyed using *any one* of the following
attributes: index name, region name, member name and group name.

Deleting an index by name or removing all indexes from a region makes
sense. However what does it mean to remove an index from a single member or
from a group? Wouldn't that result in the possibility of having an
'unbalanced' set of indexes where some members hosting a region have an
index defined, but other members don't? Seems like a recipe for serious
misconfiguration. I really don't understand the semantics of these two
scenarios. (I also couldn't find anything in the docs which explained this
more). Even the QueryService interface has no methods to delete indexes by
member or group.

Unless there is an obvious scenario I don't understand, I'd like to propose
we remove the ability (in gfsh at least) to destroy an index by *member* or
*group*.

--Jens

[1]
https://github.com/apache/incubator-geode/blob/8a3c351abd971ba740e77364a431aee7d5cc5b10/geode-core/src/main/java/com/gemstone/gemfire/management/internal/cli/commands/IndexCommands.java#L327

Re: Stats command

[Darrel Schneider]

I don't know of a way to analyze offline stat archives using gfsh.

But the code for the old gemfire stats command is still in the geode source.
It is: com.gemstone.gemfire.internal.SystemAdmin
Its "main" is what the old gemfire script executed. Just keep in mind that
this class is not used by geode so it could go away.

I think it is a good idea to add off-line stat archive analysis to gfsh and
the "stats" command in SystemAdmin could be used to aid this implementation.


On Sun, May 22, 2016 at 6:18 AM, Daniel Farcovich <
daniel.farcov...@amdocs.com> wrote:

> Hi Everyone,
> Is earlier versions of Gemfire there was a command named stats, which
> printed statistic values from a statistic archive file.
> How can I use it in GEODE? Is there a gfsh corresponding command?
>
> Thanks,
> Daniel Farcovich
>
>
> 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
>

Review Request 47731: GEODE-17: region access needed for destroy index on a specific region

[Jinmei Liao]

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

Review request for geode, Jens Deppe, Kevin Duling, and Kirk Lund.


Repository: geode


Description
---

GEODE-17: region access needed for destroy index on a specific region

When user do "destroy index --region=regionA" it will require 
DATA:MANAGE:regionA permission,
if he does "destroy index --name=foo" or "destroy index --memberId=memberA", it 
will require DATA:MANAGE permission

also clean up some tests


Diffs
-

  
geode-core/src/main/java/com/gemstone/gemfire/management/internal/cli/commands/IndexCommands.java
 b863737538bde99e2756ba4e1a1b9a4d93c17b12 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/security/CliCommandsSecurityTest.java
 3ccd71c48db8bb3a64c03d58f8c45ec3339a0a93 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/security/GeodeSecurityUtilWithIniFileJUnitTest.java
 63bf4473232f955ee67d94e33083867a8fe954a1 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/security/GfshCommandsSecurityTest.java
 1a153679e98b7c26652793c60b687f6db398426c 
  
geode-core/src/test/java/com/gemstone/gemfire/management/internal/security/TestCommand.java
 4b482a97ba401e3e300bfc43587dd6a12ec84295 

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


Testing
---

security tests


Thanks,

Jinmei Liao

Re: Review Request 47686: GEODE-11: Added changes to Lucene AEQ, to propagate destroy events due to eviction and expiration (by setting the flag ignoreEvictionAndExpiration()).

[Jason Huynh]

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




geode-lucene/src/test/java/com/gemstone/gemfire/cache/lucene/LuceneIndexMaintenanceIntegrationTest.java
 (line 120)


is this supposed to be commented out?


- Jason Huynh


On May 21, 2016, 12:57 a.m., anilkumar gingade wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47686/
> ---
> 
> (Updated May 21, 2016, 12:57 a.m.)
> 
> 
> Review request for geode, anilkumar gingade, Barry Oglesby, nabarun nag, Dan 
> Smith, and xiaojian zhou.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-11: Added changes to Lucene AEQ, to propagate destroy events due to 
> eviction and expiration (by setting the flag ignoreEvictionAndExpiration()).  
> 
> Added test to verify, the lucene index gets updated with expiration destroy 
> operation.   
> Also added support to specify wild-char as leading wild character with Lucene 
> Query.
> 
> 
> Diffs
> -
> 
>   
> geode-lucene/src/main/java/com/gemstone/gemfire/cache/lucene/internal/LuceneIndexForPartitionedRegion.java
>  d22ca4a196df3b1a457b56c92da694bdbf792cc2 
>   
> geode-lucene/src/main/java/com/gemstone/gemfire/cache/lucene/internal/StringQueryProvider.java
>  1e2b63d0fc5c7fad79063199c473bbd9d4e6fd00 
>   
> geode-lucene/src/test/java/com/gemstone/gemfire/cache/lucene/LuceneIndexMaintenanceIntegrationTest.java
>  07780ca06a297851c8ff4cb498a09f726a0785d5 
>   
> geode-lucene/src/test/java/com/gemstone/gemfire/cache/lucene/LuceneQueriesIntegrationTest.java
>  15f5747231097df5223d97bb49110229efe6a824 
> 
> Diff: https://reviews.apache.org/r/47686/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> anilkumar gingade
> 
>

Re: how to build native client on linux

[Jacob Barrett]

The initial software grant of Native Client is not going to compile out of
the box. The build process has dependencies on items that are not publicly
accessible at this time. As we replace the old build process with a new
process that is not dependent on internal resources we will update the
sources available on the ASF archive. There is work remaining to convert
the old Ant based build process to CMake.

-Jake


On Mon, May 23, 2016 at 1:54 AM Gal Palmery  wrote:

> Hi All,
>
> I'm trying to build the native client on Linux, can anyone point me where
> to start?
>
> 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
>

Build failed in Jenkins: Geode-nightly #477

[Apache Jenkins Server]

See 

Changes:

[ukohlmeyer] GEODE-1146: Cleaned up QueryUsingPoolDUnitTest.java to use proper 
client

--
[...truncated 510 lines...]
:geode-assembly: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-assembly:processTestResources
:geode-assembly:testClasses
:geode-assembly:checkMissedTests
:geode-assembly:installDist
:geode-assembly:test
:geode-assembly:check
:geode-assembly:build
:geode-assembly:distributedTest
:geode-assembly:integrationTest
:geode-common:assemble
:geode-common:compileTestJava
:geode-common:processTestResources UP-TO-DATE
:geode-common:testClasses
:geode-common:checkMissedTests
:geode-common:test
:geode-common:check
:geode-common:build
:geode-common:distributedTest
:geode-common:integrationTest
:geode-core:assemble
:geode-core:checkMissedTests
:geode-core:test

com.gemstone.gemfire.management.internal.cli.GfshParserJUnitTest > testParse 
FAILED
java.lang.NullPointerException
at 
com.gemstone.gemfire.management.internal.cli.exceptions.ExceptionHandler.handleOptionValueException(ExceptionHandler.java:95)
at 
com.gemstone.gemfire.management.internal.cli.exceptions.ExceptionHandler.handleOptionException(ExceptionHandler.java:78)
at 
com.gemstone.gemfire.management.internal.cli.exceptions.ExceptionHandler.handleException(ExceptionHandler.java:42)
at 
com.gemstone.gemfire.management.internal.cli.GfshParser.parse(GfshParser.java:969)
at 
com.gemstone.gemfire.management.internal.cli.GfshParserJUnitTest.testParse(GfshParserJUnitTest.java:937)

2304 tests completed, 1 failed, 12 skipped
:geode-core:test FAILED
:geode-core:distributedTest
:geode-core:integrationTest
:geode-cq:assemble
: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:test
:geode-cq:check
:geode-cq:build
:geode-cq:distributedTest
:geode-cq:integrationTest
:geode-joptsimple:assemble
:geode-joptsimple:compileTestJava UP-TO-DATE
:geode-joptsimple:processTestResources UP-TO-DATE
:geode-joptsimple:testClasses UP-TO-DATE
:geode-joptsimple:checkMissedTests UP-TO-DATE
:geode-joptsimple:test UP-TO-DATE
:geode-joptsimple:check
:geode-joptsimple:build
:geode-joptsimple:distributedTest UP-TO-DATE
:geode-joptsimple:integrationTest UP-TO-DATE
: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:test UP-TO-DATE
:geode-json:check
:geode-json:build
:geode-json:distributedTest 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:test
:geode-junit:check
:geode-junit:build
:geode-junit:distributedTest
:geode-junit:integrationTest
:geode-lucene:assemble
:geode-lucene:compileTestJava:109:
 warning: non-varargs call of varargs method with inexact argument type for 
last parameter;
verifyQueryKeys(queryWithStandardAnalyzer, expectedKeys);
   ^
  cast to Object for a varargs call
  cast to Object[] for a non-varargs call and to suppress this warning
Note: 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.
1 warning

:geode-lucene:processTestResources
:geode-lucene:testClasses
:geode-lucene:checkMissedTests
:geode-lucene:test
:geode-lucene:check
:geode-lucene:build
:geode-lucene:distributedTest
:geode-lucene:integrationTest
:geode-pulse:assemble
:geode-pulse: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-pulse:processTestResources
:geode-pulse:testClasses
:geode-pulse:checkMissedTests
:geode-pulse:test
:geode-pulse:check
:geode-pulse:build
:geode-pulse:distributedTest
:geode-pulse:integrationTest
:geode-rebalancer:jar
:geode-rebalancer:javadoc
:geode-rebalancer:javadocJar
:geode-rebalancer:sourcesJar
:geode-rebal

how to build native client on linux

[Gal Palmery]

Hi All,

I'm trying to build the native client on Linux, can anyone point me where to 
start?

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