[jira] [Commented] (GEODE-4863) refactor jdbc commands to use this public api

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4863:


Commit 4bc6c5a9b9abe9cf0e3c8e68802262efcdb9c735 in geode's branch 
refs/heads/feature/GEODE-5057 from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4bc6c5a ]

GEODE-4863: refactor jdbc commands to use this public cluster configuration api 
(#1802)

   fix a NullPointer in CCService.getCustomCacheElement

> refactor jdbc commands to use this public api
> -
>
> Key: GEODE-4863
> URL: https://issues.apache.org/jira/browse/GEODE-4863
> Project: Geode
>  Issue Type: Sub-task
>  Components: configuration
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> they will need to create a custom config object based on their own xsd.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-5057) Remove 'experimental' from JDBC Connector code

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-5057:


Commit 3291e7d414c8c4c2328421e0ac82eb0df641847e in geode's branch 
refs/heads/feature/GEODE-5057 from [~agingade]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3291e7d ]

Merge branch 'develop' into feature/GEODE-5057


> Remove 'experimental' from JDBC Connector code
> --
>
> Key: GEODE-5057
> URL: https://issues.apache.org/jira/browse/GEODE-5057
> Project: Geode
>  Issue Type: Task
>  Components: extensions, regions
>Affects Versions: 1.6.0
>Reporter: Anilkumar Gingade
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Remove 'experimental' from JDBC Connector code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4955) Improve spotless -- Remove empty javadocs and block comments

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4955:


Commit 5707de5e0edea1ae94b1f5c99d62b2fb6700f0d2 in geode's branch 
refs/heads/feature/GEODE-5057 from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5707de5 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  non 
geode-core module tests (#1788)



> Improve spotless -- Remove empty javadocs and block comments
> 
>
> Key: GEODE-4955
> URL: https://issues.apache.org/jira/browse/GEODE-4955
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> This should be executed after GEODE-4654, since the removal of javadoc stubs 
> may yield a now-empty javadoc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-5068) Upgrade Jackson to 2.9.5

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-5068:


Commit 82092e83725bf9b879256dfd46de25fdbdc38266 in geode's branch 
refs/heads/feature/GEODE-5057 from [~gosullivan]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=82092e8 ]

GEODE-5068: bump Jackson version. (#1796)

GEODE-5068: bump Jackson version to 2.9.5.


> Upgrade Jackson to 2.9.5
> 
>
> Key: GEODE-5068
> URL: https://issues.apache.org/jira/browse/GEODE-5068
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> We're a patch version behind, let's try to stay on the latest.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-5068) Upgrade Jackson to 2.9.5

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-5068:


Commit 82092e83725bf9b879256dfd46de25fdbdc38266 in geode's branch 
refs/heads/feature/GEODE-5057 from [~gosullivan]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=82092e8 ]

GEODE-5068: bump Jackson version. (#1796)

GEODE-5068: bump Jackson version to 2.9.5.


> Upgrade Jackson to 2.9.5
> 
>
> Key: GEODE-5068
> URL: https://issues.apache.org/jira/browse/GEODE-5068
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> We're a patch version behind, let's try to stay on the latest.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4954) Improve spotless -- remove trivial javadoc stubs

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4954:


Commit 50573481dd71d40d9d441fb313906611b3605fb2 in geode's branch 
refs/heads/feature/GEODE-5057 from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5057348 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  
geode-core (#1786)



> Improve spotless -- remove trivial javadoc stubs
> 
>
> Key: GEODE-4954
> URL: https://issues.apache.org/jira/browse/GEODE-4954
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> For instance, the block
> {noformat}
> @param myparam
> @param secondParam
> @throws Exception
> {noformat}
> is entirely implicit by the method's signature, which is included in the 
> javadoc itself.  Javadoc stubs that do not include description of a given 
> term is trivial, redundant, and should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-5057) Remove 'experimental' from JDBC Connector code

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-5057:


Commit 7960b70cc60162fa713f3d025ca2484e21f2e849 in geode's branch 
refs/heads/feature/GEODE-5057 from [~agingade]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7960b70 ]

Merge branch 'develop' into feature/GEODE-5057


> Remove 'experimental' from JDBC Connector code
> --
>
> Key: GEODE-5057
> URL: https://issues.apache.org/jira/browse/GEODE-5057
> Project: Geode
>  Issue Type: Task
>  Components: extensions, regions
>Affects Versions: 1.6.0
>Reporter: Anilkumar Gingade
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Remove 'experimental' from JDBC Connector code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4955) Improve spotless -- Remove empty javadocs and block comments

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4955:


Commit 50573481dd71d40d9d441fb313906611b3605fb2 in geode's branch 
refs/heads/feature/GEODE-5057 from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5057348 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  
geode-core (#1786)



> Improve spotless -- Remove empty javadocs and block comments
> 
>
> Key: GEODE-4955
> URL: https://issues.apache.org/jira/browse/GEODE-4955
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> This should be executed after GEODE-4654, since the removal of javadoc stubs 
> may yield a now-empty javadoc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4384) gfsh command to destroy jndi binding

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4384:


Commit ac7db5b2950af134233c976b3f63f3e48e8d3fb9 in geode's branch 
refs/heads/feature/GEODE-5057 from Karen Miller
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ac7db5b ]

GEODE-4384 Add docs for gfsh destroy jndi-binding command (#1780)



> gfsh command to destroy jndi binding
> 
>
> Key: GEODE-4384
> URL: https://issues.apache.org/jira/browse/GEODE-4384
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Barbara Pruijn
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> In cache.xml user can specify jndi binding like so:
> {code:java}
>   
>  jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin"
>   password="changeme" 
> connection-url="jdbc:postgresql://localhost:5432/gemfire_db">
>   
>   
> {code}
> A user should be able to delete a datasource using the gfsh command {{destroy 
> jndi-binding --name=jndi-binding-name}}
>  Then the datasource will be deleted from the cluster and the binding will be 
> deleted without the user having to restart the existing server(s).
> Please look at Geode's schema for a list of attributes that can be set: 
> [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4954) Improve spotless -- remove trivial javadoc stubs

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4954:


Commit 5707de5e0edea1ae94b1f5c99d62b2fb6700f0d2 in geode's branch 
refs/heads/feature/GEODE-5057 from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5707de5 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  non 
geode-core module tests (#1788)



> Improve spotless -- remove trivial javadoc stubs
> 
>
> Key: GEODE-4954
> URL: https://issues.apache.org/jira/browse/GEODE-4954
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> For instance, the block
> {noformat}
> @param myparam
> @param secondParam
> @throws Exception
> {noformat}
> is entirely implicit by the method's signature, which is included in the 
> javadoc itself.  Javadoc stubs that do not include description of a given 
> term is trivial, redundant, and should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-3926) Lucene Query should throw an exception while lucene index is being built on existing region

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3926:


Commit 83c667b12c510f7a10aca57179b9e61f29cfddbb in geode's branch 
refs/heads/feature/GEODE-5057 from [~huynhja]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=83c667b ]

GEODE-3926: Catching exception from lucene query computing thread (#1774)



> Lucene Query should throw an exception while lucene index is being built on 
> existing region
> ---
>
> Key: GEODE-3926
> URL: https://issues.apache.org/jira/browse/GEODE-3926
> Project: Geode
>  Issue Type: Sub-task
>  Components: lucene
>Reporter: Jason Huynh
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> When GEODE-3928 is complete, we will have a process to index existing data in 
> a region when a lucene index is added. That process may take some time. While 
> indexing is going on queries should not block for a long period of time or 
> return incorrect results. Instead the query should throw an exception 
> indicating that the index does not exist/is not built yet.
> Acceptance:
> Queries executed while indexing is going on throw an exception, rather than 
> blocking or returning incorrect results.
> Implementation Details:
> GEODE-3928 is about modifying computeRepository to actually do the indexing. 
> Queries also call compute repository, so they will block until 
> computeRepository is done.
> To avoid blocking, we can make  computeRepo to return an IndexRepository in 
> an "building" state. That index repo could contain an asynchronous task that 
> is actually indexing the data. Until the asynchronous task is complete, the 
> IndexRepostory could throw exceptions from query operations. This has the 
> advantage of making sure that whenever computeRepository is called, we always 
> at least start or make sure there is a task running to index the data.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4863) refactor jdbc commands to use this public api

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4863:


Commit 4bc6c5a9b9abe9cf0e3c8e68802262efcdb9c735 in geode's branch 
refs/heads/develop from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4bc6c5a ]

GEODE-4863: refactor jdbc commands to use this public cluster configuration api 
(#1802)

   fix a NullPointer in CCService.getCustomCacheElement

> refactor jdbc commands to use this public api
> -
>
> Key: GEODE-4863
> URL: https://issues.apache.org/jira/browse/GEODE-4863
> Project: Geode
>  Issue Type: Sub-task
>  Components: configuration
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> they will need to create a custom config object based on their own xsd.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4956) Windows packer errors after chocolatey install

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4956:


Commit 5d2ca737c8ea74e9709f49c14df8f88af666a551 in geode-native's branch 
refs/heads/develop from M. Oleske
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=5d2ca73 ]

GEODE-4956: revert to latest chocolatey (#276)



> Windows packer errors after chocolatey install
> --
>
> Key: GEODE-4956
> URL: https://issues.apache.org/jira/browse/GEODE-4956
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Michael Oleske
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> *Current Behavior:* Installs latest Chocolatey (0.10.9), then errors out with 
> non zero exit status
> *Expected Behavior:* No non zero exit
> *Steps to reproduce it:*
> {code:bash}
> packer build -var-file=default.json -var source_ami=LATEST_AMI_ID -var 
> aws_access_key=AWS_ACCESS_KEY -var aws_secret_key=AWS_SECRET_KEY -var 
> version=10.0 windows-2012-r2-base.json{code}
> Note:  Is fixed by downgrading to 0.10.8 of Chocolatey, but probably not best 
> solution



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-4956) Windows packer errors after chocolatey install

2018-04-13 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-4956:
--
Labels: pull-request-available  (was: )

> Windows packer errors after chocolatey install
> --
>
> Key: GEODE-4956
> URL: https://issues.apache.org/jira/browse/GEODE-4956
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Michael Oleske
>Priority: Major
>  Labels: pull-request-available
>
> *Current Behavior:* Installs latest Chocolatey (0.10.9), then errors out with 
> non zero exit status
> *Expected Behavior:* No non zero exit
> *Steps to reproduce it:*
> {code:bash}
> packer build -var-file=default.json -var source_ami=LATEST_AMI_ID -var 
> aws_access_key=AWS_ACCESS_KEY -var aws_secret_key=AWS_SECRET_KEY -var 
> version=10.0 windows-2012-r2-base.json{code}
> Note:  Is fixed by downgrading to 0.10.8 of Chocolatey, but probably not best 
> solution



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-5046) RemotePutMessage.distribute should handle RegionDestoryedException

2018-04-13 Thread Eric Shu (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Shu updated GEODE-5046:

Fix Version/s: (was: 1.6.0)
   1.7.0

> RemotePutMessage.distribute should handle RegionDestoryedException
> --
>
> Key: GEODE-5046
> URL: https://issues.apache.org/jira/browse/GEODE-5046
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.5.0, 1.6.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> RemotePutMessage.distribute() tries to get a version tag from a remote member 
> in a loop. It tries another member if one member failed. 
> It is possible that a region is destroyed on a member, and the method should 
> handle it and retry to another member instead of failing the operation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-5046) RemotePutMessage.distribute should handle RegionDestoryedException

2018-04-13 Thread Eric Shu (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Shu updated GEODE-5046:

Affects Version/s: 1.6.0

> RemotePutMessage.distribute should handle RegionDestoryedException
> --
>
> Key: GEODE-5046
> URL: https://issues.apache.org/jira/browse/GEODE-5046
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.5.0, 1.6.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> RemotePutMessage.distribute() tries to get a version tag from a remote member 
> in a loop. It tries another member if one member failed. 
> It is possible that a region is destroyed on a member, and the method should 
> handle it and retry to another member instead of failing the operation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-5039) EvictionAttributesMutator.setMaximum does not work

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-5039:


Commit e95a251be9cefbb8218f8642c033020ebda7d721 in geode's branch 
refs/heads/release/1.6.0 from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e95a251 ]

GEODE-5039: Change AbstractRegion to correctly construct 
EvictionAttributesMutator (#1766)

 git cherry-pick c62846d643d35c68945320dc8a0e85197b28b0f6


> EvictionAttributesMutator.setMaximum does not work
> --
>
> Key: GEODE-5039
> URL: https://issues.apache.org/jira/browse/GEODE-5039
> Project: Geode
>  Issue Type: Bug
>  Components: eviction
>Affects Versions: 1.5.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> EvictionAttributesMutator.setMaximum does not change the lru count.
>  
> Given I am configuring eviction
> When setting EvictionAttributesMutator.setMaximum
> Then the lru count should update accordingly



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-5068) Upgrade Jackson to 2.9.5

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-5068:


Commit 82092e83725bf9b879256dfd46de25fdbdc38266 in geode's branch 
refs/heads/develop from [~gosullivan]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=82092e8 ]

GEODE-5068: bump Jackson version. (#1796)

GEODE-5068: bump Jackson version to 2.9.5.


> Upgrade Jackson to 2.9.5
> 
>
> Key: GEODE-5068
> URL: https://issues.apache.org/jira/browse/GEODE-5068
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> We're a patch version behind, let's try to stay on the latest.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-5068) Upgrade Jackson to 2.9.5

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-5068:


Commit 82092e83725bf9b879256dfd46de25fdbdc38266 in geode's branch 
refs/heads/develop from [~gosullivan]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=82092e8 ]

GEODE-5068: bump Jackson version. (#1796)

GEODE-5068: bump Jackson version to 2.9.5.


> Upgrade Jackson to 2.9.5
> 
>
> Key: GEODE-5068
> URL: https://issues.apache.org/jira/browse/GEODE-5068
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> We're a patch version behind, let's try to stay on the latest.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-5048) Availability Indicator for "list jndi-bindings", "list jdbc-connections" and "list jdbc-mappings" are wrong

2018-04-13 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-5048:
--
Labels: pull-request-available  (was: )

> Availability Indicator for "list jndi-bindings", "list jdbc-connections" and 
> "list jdbc-mappings" are wrong
> ---
>
> Key: GEODE-5048
> URL: https://issues.apache.org/jira/browse/GEODE-5048
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
>
> those commands, when not connected to a locator, should be listed as "not 
> available" in gfsh help, but they are listed as "available".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-5047) Modify gfsh command 'list Lucene index' to list status of re-indexing.

2018-04-13 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-5047:
--
Labels: pull-request-available  (was: )

> Modify gfsh command 'list Lucene index' to list status of re-indexing.
> --
>
> Key: GEODE-5047
> URL: https://issues.apache.org/jira/browse/GEODE-5047
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: nabarun
>Priority: Major
>  Labels: pull-request-available
>
> As a GemFire developer, I want to use gfsh to check if the Lucene index 
> creation has completed successfully using the 'list lucene indexes' and 
> 'describe lucene index' commands.
> Acceptance criteria:
> When I use gfsh to add a new Lucene index to an existing region with data, I 
> can check its status using 'list lucene index':
>  * If indexing is in progress, the list command will display this
>  * If indexing is complete, the list command will display this and I can 
> execute a Lucene search.
> h2. Implementation ideas
> Check for completed file. If not present, status is 'initializing'. Once 
> re-indexing is complete, status changes to 'initialized'.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4384) gfsh command to destroy jndi binding

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4384:


Commit 30945b6f0048ea07cf39b4eb5d80fb1e384f6735 in geode's branch 
refs/heads/release/1.6.0 from Karen Miller
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=30945b6 ]

GEODE-4384 Add docs for gfsh destroy jndi-binding command (#1780)



> gfsh command to destroy jndi binding
> 
>
> Key: GEODE-4384
> URL: https://issues.apache.org/jira/browse/GEODE-4384
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Barbara Pruijn
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> In cache.xml user can specify jndi binding like so:
> {code:java}
>   
>  jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin"
>   password="changeme" 
> connection-url="jdbc:postgresql://localhost:5432/gemfire_db">
>   
>   
> {code}
> A user should be able to delete a datasource using the gfsh command {{destroy 
> jndi-binding --name=jndi-binding-name}}
>  Then the datasource will be deleted from the cluster and the binding will be 
> deleted without the user having to restart the existing server(s).
> Please look at Geode's schema for a list of attributes that can be set: 
> [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4955) Improve spotless -- Remove empty javadocs and block comments

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4955:


Commit 50573481dd71d40d9d441fb313906611b3605fb2 in geode's branch 
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5057348 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  
geode-core (#1786)



> Improve spotless -- Remove empty javadocs and block comments
> 
>
> Key: GEODE-4955
> URL: https://issues.apache.org/jira/browse/GEODE-4955
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> This should be executed after GEODE-4654, since the removal of javadoc stubs 
> may yield a now-empty javadoc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4954) Improve spotless -- remove trivial javadoc stubs

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4954:


Commit 50573481dd71d40d9d441fb313906611b3605fb2 in geode's branch 
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5057348 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  
geode-core (#1786)



> Improve spotless -- remove trivial javadoc stubs
> 
>
> Key: GEODE-4954
> URL: https://issues.apache.org/jira/browse/GEODE-4954
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> For instance, the block
> {noformat}
> @param myparam
> @param secondParam
> @throws Exception
> {noformat}
> is entirely implicit by the method's signature, which is included in the 
> javadoc itself.  Javadoc stubs that do not include description of a given 
> term is trivial, redundant, and should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4955) Improve spotless -- Remove empty javadocs and block comments

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4955:


Commit 5707de5e0edea1ae94b1f5c99d62b2fb6700f0d2 in geode's branch 
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5707de5 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  non 
geode-core module tests (#1788)



> Improve spotless -- Remove empty javadocs and block comments
> 
>
> Key: GEODE-4955
> URL: https://issues.apache.org/jira/browse/GEODE-4955
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> This should be executed after GEODE-4654, since the removal of javadoc stubs 
> may yield a now-empty javadoc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4954) Improve spotless -- remove trivial javadoc stubs

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4954:


Commit 5707de5e0edea1ae94b1f5c99d62b2fb6700f0d2 in geode's branch 
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5707de5 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  non 
geode-core module tests (#1788)



> Improve spotless -- remove trivial javadoc stubs
> 
>
> Key: GEODE-4954
> URL: https://issues.apache.org/jira/browse/GEODE-4954
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> For instance, the block
> {noformat}
> @param myparam
> @param secondParam
> @throws Exception
> {noformat}
> is entirely implicit by the method's signature, which is included in the 
> javadoc itself.  Javadoc stubs that do not include description of a given 
> term is trivial, redundant, and should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4384) gfsh command to destroy jndi binding

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4384:


Commit ac7db5b2950af134233c976b3f63f3e48e8d3fb9 in geode's branch 
refs/heads/develop from Karen Miller
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ac7db5b ]

GEODE-4384 Add docs for gfsh destroy jndi-binding command (#1780)



> gfsh command to destroy jndi binding
> 
>
> Key: GEODE-4384
> URL: https://issues.apache.org/jira/browse/GEODE-4384
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Barbara Pruijn
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> In cache.xml user can specify jndi binding like so:
> {code:java}
>   
>  jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin"
>   password="changeme" 
> connection-url="jdbc:postgresql://localhost:5432/gemfire_db">
>   
>   
> {code}
> A user should be able to delete a datasource using the gfsh command {{destroy 
> jndi-binding --name=jndi-binding-name}}
>  Then the datasource will be deleted from the cluster and the binding will be 
> deleted without the user having to restart the existing server(s).
> Please look at Geode's schema for a list of attributes that can be set: 
> [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GEODE-5079) Investigate why dynamic_cast fails when visibility is set to 'hidden' by default in Clang

2018-04-13 Thread Ryan McMahon (JIRA)
Ryan McMahon created GEODE-5079:
---

 Summary: Investigate why dynamic_cast fails when visibility is set 
to 'hidden' by default in Clang
 Key: GEODE-5079
 URL: https://issues.apache.org/jira/browse/GEODE-5079
 Project: Geode
  Issue Type: Bug
  Components: native client
Reporter: Ryan McMahon


We should investigate why symbols aren't fully exported when specifying 
'CXX_VISIBILITY_PRESET hidden' and aliasing with the 'using' keyword i.e.

```

using CacheableBytes = CacheableArray

```

The immediate fix was to set visibility to 'default' for Clang only 
(https://issues.apache.org/jira/browse/GEODE-5067), but it would be good to 
better understand 'hidden' visibility causes problems. 

The issue can be reproduced by reverting Clang back to 'default' visibility and 
running the testThinClientBigValue test.

We identified that if we do not alias with 'using' and explicitly define the 
class e.g. CacheableBytes and decorate that class with APACHE_GEODE_EXPORT, 
then this seems to resolve the issue when using 'hidden' by default on Clang.  
However, it seems cumbersome to explicitly define all these classes just to 
solve this particular issue.

Some potentially relevant stackoverflow posts include:

https://stackoverflow.com/questions/19496643/using-clang-fvisibility-hidden-and-typeinfo-and-type-erasure

[https://stackoverflow.com/questions/5116333/dynamic-cast-failed-when-hiding-symbol]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-3926) Lucene Query should throw an exception while lucene index is being built on existing region

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3926:


Commit 83c667b12c510f7a10aca57179b9e61f29cfddbb in geode's branch 
refs/heads/develop from [~huynhja]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=83c667b ]

GEODE-3926: Catching exception from lucene query computing thread (#1774)



> Lucene Query should throw an exception while lucene index is being built on 
> existing region
> ---
>
> Key: GEODE-3926
> URL: https://issues.apache.org/jira/browse/GEODE-3926
> Project: Geode
>  Issue Type: Sub-task
>  Components: lucene
>Reporter: Jason Huynh
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> When GEODE-3928 is complete, we will have a process to index existing data in 
> a region when a lucene index is added. That process may take some time. While 
> indexing is going on queries should not block for a long period of time or 
> return incorrect results. Instead the query should throw an exception 
> indicating that the index does not exist/is not built yet.
> Acceptance:
> Queries executed while indexing is going on throw an exception, rather than 
> blocking or returning incorrect results.
> Implementation Details:
> GEODE-3928 is about modifying computeRepository to actually do the indexing. 
> Queries also call compute repository, so they will block until 
> computeRepository is done.
> To avoid blocking, we can make  computeRepo to return an IndexRepository in 
> an "building" state. That index repo could contain an asynchronous task that 
> is actually indexing the data. Until the asynchronous task is complete, the 
> IndexRepostory could throw exceptions from query operations. This has the 
> advantage of making sure that whenever computeRepository is called, we always 
> at least start or make sure there is a task running to index the data.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-5070) Support --member option for describe & list jdbc connector commands

2018-04-13 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-5070:
--
Labels: pull-request-available  (was: )

> Support --member option for describe & list jdbc connector commands
> ---
>
> Key: GEODE-5070
> URL: https://issues.apache.org/jira/browse/GEODE-5070
> Project: Geode
>  Issue Type: New Feature
>  Components: gfsh
>Reporter: Sai Boorlagadda
>Priority: Major
>  Labels: pull-request-available
>
> When cluster configuration service is disabled user have to provide --member 
> option in-order to describe and list connections and mappings. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (GEODE-3981) Cache should not provide access to internal regions from public APIs

2018-04-13 Thread Darrel Schneider (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Darrel Schneider reassigned GEODE-3981:
---

Assignee: (was: Darrel Schneider)

> Cache should not provide access to internal regions from public APIs
> 
>
> Key: GEODE-3981
> URL: https://issues.apache.org/jira/browse/GEODE-3981
> Project: Geode
>  Issue Type: Improvement
>Reporter: Fred Krone
>Priority: Major
>
> We should protect the user from accidentally modifying an internal region.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (GEODE-5078) InternalCache should have a getApplicationRegion method

2018-04-13 Thread Darrel Schneider (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Darrel Schneider reassigned GEODE-5078:
---

Assignee: Darrel Schneider

> InternalCache should have a getApplicationRegion method
> ---
>
> Key: GEODE-5078
> URL: https://issues.apache.org/jira/browse/GEODE-5078
> Project: Geode
>  Issue Type: Sub-task
>  Components: regions
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
>
> To help servers not provide access to secret/internal regions to clients; 
> InternalCache should have a method named getApplicationRegion which behaves 
> just like getRegion except that if the given name finds a secret/internal 
> region then it will throw an exception.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-3981) Cache should not provide access to internal regions from public APIs

2018-04-13 Thread Darrel Schneider (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Darrel Schneider updated GEODE-3981:

Component/s: (was: regions)

> Cache should not provide access to internal regions from public APIs
> 
>
> Key: GEODE-3981
> URL: https://issues.apache.org/jira/browse/GEODE-3981
> Project: Geode
>  Issue Type: Improvement
>Reporter: Fred Krone
>Priority: Major
>
> We should protect the user from accidentally modifying an internal region.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (GEODE-5064) Remove unused code and if clause that does not get thrown

2018-04-13 Thread Jason Huynh (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Huynh resolved GEODE-5064.

Resolution: Fixed

> Remove unused code and if clause that does not get thrown
> -
>
> Key: GEODE-5064
> URL: https://issues.apache.org/jira/browse/GEODE-5064
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> There appears to be an exception that should be thrown, but upon futher 
> inspection, this clause can never be hit because the boolean it checks is 
> never set to true;
>  
> In LocalRegion:
> logger.info("Failed to create index {} on region {} with exception: {}",
>  icd.getIndexName(), this.getFullPath(), ex);
> // Check if the region index creation is from cache.xml, in that case throw 
> exception.
> // Other case is when bucket regions are created dynamically, in that case 
> ignore the
> // exception.
> if (internalRegionArgs.getDeclarativeIndexCreation()) {
>  throw new 
> InternalGemFireError(LocalizedStrings.GemFireCache_INDEX_CREATION_EXCEPTION_1
>  .toLocalizedString(icd.getIndexName(), this.getFullPath()), ex);
> }



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-3981) Cache should not provide access to internal regions from public APIs

2018-04-13 Thread Darrel Schneider (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Darrel Schneider updated GEODE-3981:

Labels:   (was: geode-150)

> Cache should not provide access to internal regions from public APIs
> 
>
> Key: GEODE-3981
> URL: https://issues.apache.org/jira/browse/GEODE-3981
> Project: Geode
>  Issue Type: Improvement
>  Components: regions
>Reporter: Fred Krone
>Assignee: Darrel Schneider
>Priority: Major
>
> We should protect the user from accidentally modifying an internal region.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-5077) Categorize refactored/newly added OQL tests

2018-04-13 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-5077:
--
Labels: pull-request-available  (was: )

> Categorize refactored/newly added OQL tests
> ---
>
> Key: GEODE-5077
> URL: https://issues.apache.org/jira/browse/GEODE-5077
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
>
> Following a refactor these tests were added and it would be nice to add the 
> OQLIndexTest or OQLQueryTest to the categories.
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithIndexAndPdxDistributedTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithIndexDistributedTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithOrderByDistributedTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithPdxDuringRebalanceRegressionTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRWithIndexAfterRebalanceRegressionTest.java



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GEODE-5078) InternalCache should have a getApplicationRegion method

2018-04-13 Thread Darrel Schneider (JIRA)
Darrel Schneider created GEODE-5078:
---

 Summary: InternalCache should have a getApplicationRegion method
 Key: GEODE-5078
 URL: https://issues.apache.org/jira/browse/GEODE-5078
 Project: Geode
  Issue Type: Sub-task
  Components: regions
Reporter: Darrel Schneider


To help servers not provide access to secret/internal regions to clients; 
InternalCache should have a method named getApplicationRegion which behaves 
just like getRegion except that if the given name finds a secret/internal 
region then it will throw an exception.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (GEODE-5077) Categorize refactored/newly added OQL tests

2018-04-13 Thread Jason Huynh (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Huynh reassigned GEODE-5077:
--

Assignee: Jason Huynh

> Categorize refactored/newly added OQL tests
> ---
>
> Key: GEODE-5077
> URL: https://issues.apache.org/jira/browse/GEODE-5077
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>
> Following a refactor these tests were added and it would be nice to add the 
> OQLIndexTest or OQLQueryTest to the categories.
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithIndexAndPdxDistributedTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithIndexDistributedTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithOrderByDistributedTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithPdxDuringRebalanceRegressionTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRWithIndexAfterRebalanceRegressionTest.java



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GEODE-5077) Categorize refactored/newly added OQL tests

2018-04-13 Thread Jason Huynh (JIRA)
Jason Huynh created GEODE-5077:
--

 Summary: Categorize refactored/newly added OQL tests
 Key: GEODE-5077
 URL: https://issues.apache.org/jira/browse/GEODE-5077
 Project: Geode
  Issue Type: Bug
  Components: querying
Reporter: Jason Huynh


Following a refactor these tests were added and it would be nice to add the 
OQLIndexTest or OQLQueryTest to the categories.

geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithIndexAndPdxDistributedTest.java
geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithIndexDistributedTest.java
geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithOrderByDistributedTest.java
geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithPdxDuringRebalanceRegressionTest.java
geode-core/src/test/java/org/apache/geode/internal/cache/PRWithIndexAfterRebalanceRegressionTest.java



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GEODE-5076) jmx client should not access or modify internal regions

2018-04-13 Thread Darrel Schneider (JIRA)
Darrel Schneider created GEODE-5076:
---

 Summary: jmx client should not access or modify internal regions
 Key: GEODE-5076
 URL: https://issues.apache.org/jira/browse/GEODE-5076
 Project: Geode
  Issue Type: Sub-task
  Components: jmx
Reporter: Darrel Schneider


When a request from a jmx client (including gfsh) is processed that contains a 
region name, then getApplicationRegion should be used instead of getRegion.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GEODE-5075) REST admin client should not access or modify internal regions

2018-04-13 Thread Darrel Schneider (JIRA)
Darrel Schneider created GEODE-5075:
---

 Summary: REST admin client should not access or modify internal 
regions
 Key: GEODE-5075
 URL: https://issues.apache.org/jira/browse/GEODE-5075
 Project: Geode
  Issue Type: Sub-task
  Components: rest (admin)
Reporter: Darrel Schneider


When a request is processed from a REST admin client that contains a region 
name, then getApplicationRegion should be called instead of getRegion



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-4874) Inconsistency in gfsh help for create jndi-binding

2018-04-13 Thread Barbara Pruijn (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barbara Pruijn updated GEODE-4874:
--
Fix Version/s: (was: 1.6.0)
   1.7.0

> Inconsistency in gfsh help for create jndi-binding 
> ---
>
> Key: GEODE-4874
> URL: https://issues.apache.org/jira/browse/GEODE-4874
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.5.0
>Reporter: Karen Smoler Miller
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> I see an error and an inconsistency when trying to use the gfsh help 
> functionality for create jndi-binding.
> Tab completion of
> create jndi-binding
> outputs
>  gfsh>create jndi-binding –
>  create jndi-binding --connection-url
>  create jndi-binding --jdbc-driver-class
>  create jndi-binding --name
>  create jndi-binding --type
> This is inconsistent with the output of other tab completions, which just 
> give the options, and do not repeat the "create jndi-binding" portion of the 
> command.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-4962) Fix typo and output format from 'list gateways' gfsh command

2018-04-13 Thread Barbara Pruijn (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barbara Pruijn updated GEODE-4962:
--
Fix Version/s: (was: 1.6.0)
   1.7.0

> Fix typo and output format from 'list gateways' gfsh command
> 
>
> Key: GEODE-4962
> URL: https://issues.apache.org/jira/browse/GEODE-4962
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, wan
>Reporter: Diane Hardman
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The output printed from `list gateways` command needs some TLC:
> Sample output:
> {noformat}
> Cluster-2 gfsh>list gateways
> Gateways
> GatewaySender
> GatewaySender Id |                  Member                  | Remote Cluster 
> Id |   Type   | Status  | Queued Events | Receiver Location
>  |  | 
> - |  | --- | - | -
> ny               | 10.118.19.46(server-ln-1:31527):1026 | 1               
>   | Parallel | Running | 0             | 10.118.19.46:5248
> ny               | 10.118.19.46(server-ln-2:31545):1027 | 1               
>   | Parallel | Running | 0             | 10.118.19.46:5269
> GatewayReceiver
>                   Member                  | Port | Sender Count | Sender's 
> Connected
>  |  |  | 
> 
> 10.118.19.46(server-ln-1:31527):1026 | 5407 | 7            | 
> [Ljava.lang.String;@7deec2d6
> 10.118.19.46(server-ln-2:31545):1027 | 5071 | 7            | 
> [Ljava.lang.String;@6baa580f
> {noformat}
> Note: 'Sender's Connected' should instead be 'Senders Connected'
> Also, need to pretty-print the String[] for Senders Connected.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GEODE-5074) REST dev client should not access or modify internal regions

2018-04-13 Thread Darrel Schneider (JIRA)
Darrel Schneider created GEODE-5074:
---

 Summary: REST dev client should not access or modify internal 
regions
 Key: GEODE-5074
 URL: https://issues.apache.org/jira/browse/GEODE-5074
 Project: Geode
  Issue Type: Sub-task
  Components: rest (dev)
Reporter: Darrel Schneider


When a request is processed from a REST dev client that contains a region name, 
then getApplicationRegion should be used instead of getRegion.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GEODE-5073) Native client should not access or modify internal regions

2018-04-13 Thread Darrel Schneider (JIRA)
Darrel Schneider created GEODE-5073:
---

 Summary: Native client should not access or modify internal regions
 Key: GEODE-5073
 URL: https://issues.apache.org/jira/browse/GEODE-5073
 Project: Geode
  Issue Type: Sub-task
  Components: native client
Reporter: Darrel Schneider


When the server processes a message from a native client that contains a region 
name, it should use getApplicationRegion instead of getRegion.

Note that fixing this for the java client may completely fix it for the native 
client.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (GEODE-4962) Fix typo and output format from 'list gateways' gfsh command

2018-04-13 Thread Barbara Pruijn (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barbara Pruijn resolved GEODE-4962.
---
Resolution: Fixed

> Fix typo and output format from 'list gateways' gfsh command
> 
>
> Key: GEODE-4962
> URL: https://issues.apache.org/jira/browse/GEODE-4962
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, wan
>Reporter: Diane Hardman
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The output printed from `list gateways` command needs some TLC:
> Sample output:
> {noformat}
> Cluster-2 gfsh>list gateways
> Gateways
> GatewaySender
> GatewaySender Id |                  Member                  | Remote Cluster 
> Id |   Type   | Status  | Queued Events | Receiver Location
>  |  | 
> - |  | --- | - | -
> ny               | 10.118.19.46(server-ln-1:31527):1026 | 1               
>   | Parallel | Running | 0             | 10.118.19.46:5248
> ny               | 10.118.19.46(server-ln-2:31545):1027 | 1               
>   | Parallel | Running | 0             | 10.118.19.46:5269
> GatewayReceiver
>                   Member                  | Port | Sender Count | Sender's 
> Connected
>  |  |  | 
> 
> 10.118.19.46(server-ln-1:31527):1026 | 5407 | 7            | 
> [Ljava.lang.String;@7deec2d6
> 10.118.19.46(server-ln-2:31545):1027 | 5071 | 7            | 
> [Ljava.lang.String;@6baa580f
> {noformat}
> Note: 'Sender's Connected' should instead be 'Senders Connected'
> Also, need to pretty-print the String[] for Senders Connected.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GEODE-5072) Java clients should not access or modify internal regions

2018-04-13 Thread Darrel Schneider (JIRA)
Darrel Schneider created GEODE-5072:
---

 Summary: Java clients should not access or modify internal regions
 Key: GEODE-5072
 URL: https://issues.apache.org/jira/browse/GEODE-5072
 Project: Geode
  Issue Type: Sub-task
  Components: client/server
Reporter: Darrel Schneider


When a server processes a client message that contains a region name, it should 
use getApplicationRegion instead of getRegion.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4955) Improve spotless -- Remove empty javadocs and block comments

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4955:


Commit ca98d86c12a3b3d28d859bbced8f7a5dd9730cc4 in geode's branch 
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ca98d86 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  non 
geode-core modules (#1787)



> Improve spotless -- Remove empty javadocs and block comments
> 
>
> Key: GEODE-4955
> URL: https://issues.apache.org/jira/browse/GEODE-4955
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> This should be executed after GEODE-4654, since the removal of javadoc stubs 
> may yield a now-empty javadoc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4954) Improve spotless -- remove trivial javadoc stubs

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4954:


Commit ca98d86c12a3b3d28d859bbced8f7a5dd9730cc4 in geode's branch 
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ca98d86 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  non 
geode-core modules (#1787)



> Improve spotless -- remove trivial javadoc stubs
> 
>
> Key: GEODE-4954
> URL: https://issues.apache.org/jira/browse/GEODE-4954
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> For instance, the block
> {noformat}
> @param myparam
> @param secondParam
> @throws Exception
> {noformat}
> is entirely implicit by the method's signature, which is included in the 
> javadoc itself.  Javadoc stubs that do not include description of a given 
> term is trivial, redundant, and should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-3981) Cache should not provide access to internal regions from public APIs

2018-04-13 Thread Darrel Schneider (JIRA)

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

Darrel Schneider commented on GEODE-3981:
-

Remote clients should never need to access or modify the secret/internal 
regions that exist to implement other features. I will add a new API named 
getApplicationRegion that will throw an exception if it is asked to get one of 
these internal regions.

I will also file other tickets for the remote protocols that need to be change 
to use this new API.

 

> Cache should not provide access to internal regions from public APIs
> 
>
> Key: GEODE-3981
> URL: https://issues.apache.org/jira/browse/GEODE-3981
> Project: Geode
>  Issue Type: Improvement
>  Components: regions
>Reporter: Fred Krone
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: geode-150
>
> We should protect the user from accidentally modifying an internal region.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4955) Improve spotless -- Remove empty javadocs and block comments

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4955:


Commit f280247a5dbbc3a1f26a581e35b7f7d8091b4bf3 in geode's branch 
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f280247 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks: 
geode-core:internal (#1784)



> Improve spotless -- Remove empty javadocs and block comments
> 
>
> Key: GEODE-4955
> URL: https://issues.apache.org/jira/browse/GEODE-4955
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> This should be executed after GEODE-4654, since the removal of javadoc stubs 
> may yield a now-empty javadoc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4954) Improve spotless -- remove trivial javadoc stubs

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4954:


Commit f280247a5dbbc3a1f26a581e35b7f7d8091b4bf3 in geode's branch 
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f280247 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks: 
geode-core:internal (#1784)



> Improve spotless -- remove trivial javadoc stubs
> 
>
> Key: GEODE-4954
> URL: https://issues.apache.org/jira/browse/GEODE-4954
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> For instance, the block
> {noformat}
> @param myparam
> @param secondParam
> @throws Exception
> {noformat}
> is entirely implicit by the method's signature, which is included in the 
> javadoc itself.  Javadoc stubs that do not include description of a given 
> term is trivial, redundant, and should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (GEODE-3981) Cache should not provide access to internal regions from public APIs

2018-04-13 Thread Darrel Schneider (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Darrel Schneider reassigned GEODE-3981:
---

Assignee: Darrel Schneider

> Cache should not provide access to internal regions from public APIs
> 
>
> Key: GEODE-3981
> URL: https://issues.apache.org/jira/browse/GEODE-3981
> Project: Geode
>  Issue Type: Improvement
>  Components: regions
>Reporter: Fred Krone
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: geode-150
>
> We should protect the user from accidentally modifying an internal region.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (GEODE-4874) Inconsistency in gfsh help for create jndi-binding

2018-04-13 Thread Barbara Pruijn (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barbara Pruijn resolved GEODE-4874.
---
Resolution: Fixed

> Inconsistency in gfsh help for create jndi-binding 
> ---
>
> Key: GEODE-4874
> URL: https://issues.apache.org/jira/browse/GEODE-4874
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.5.0
>Reporter: Karen Smoler Miller
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> I see an error and an inconsistency when trying to use the gfsh help 
> functionality for create jndi-binding.
> Tab completion of
> create jndi-binding
> outputs
>  gfsh>create jndi-binding –
>  create jndi-binding --connection-url
>  create jndi-binding --jdbc-driver-class
>  create jndi-binding --name
>  create jndi-binding --type
> This is inconsistent with the output of other tab completions, which just 
> give the options, and do not repeat the "create jndi-binding" portion of the 
> command.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (GEODE-5051) Improve gfsh destroy jndi-binding help prose

2018-04-13 Thread Barbara Pruijn (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barbara Pruijn resolved GEODE-5051.
---
Resolution: Fixed

> Improve gfsh destroy jndi-binding help prose
> 
>
> Key: GEODE-5051
> URL: https://issues.apache.org/jira/browse/GEODE-5051
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current help text output for gfsh destroy jndi-binding contains some 
> errors:
>  gfsh>help destroy jndi-binding
> NAME
> destroy jndi-binding
> IS AVAILABLE
> false
> SYNOPSIS
> Destroy a jndi binding that holds the configuration for the XA datasource.
> SYNTAX
> destroy jndi-binding --name=value [--if-exists(=value)?]
> PARAMETERS
> name
> Name of the binding to be destroyed.
> Required: true
> if-exists
> Skip the destroy operation when a jndi binding with the same name does
> not exists. Without specifying this option, this command execution
> results into an error.
> Required: false
> Default (if the parameter is specified without value): true
> Default (if the parameter is not specified): false
> We can improve this text by changing the underlined prose to:
> gfsh>help destroy jndi-binding
> NAME
> destroy jndi-binding
> IS AVAILABLE
> false
> SYNOPSIS
> Destroy a +JNDI+ binding that holds the configuration for +an+ XA 
> datasource.
> SYNTAX
> destroy jndi-binding --name=value [--if-exists(=value)?]
> PARAMETERS
> name
> Name of the binding to be destroyed.
> Required: true
> if-exists
> +Skip the destroy operation when the specified JNDI binding does+
> +not exist. Without this option, an error results from the 
> specification+
> +of a JNDI binding that does not exist.+
> Required: false
> Default (if the parameter is specified without value): true
> Default (if the parameter is not specified): false
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-4863) refactor jdbc commands to use this public api

2018-04-13 Thread Barbara Pruijn (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barbara Pruijn updated GEODE-4863:
--
Fix Version/s: 1.7.0

> refactor jdbc commands to use this public api
> -
>
> Key: GEODE-4863
> URL: https://issues.apache.org/jira/browse/GEODE-4863
> Project: Geode
>  Issue Type: Sub-task
>  Components: configuration
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> they will need to create a custom config object based on their own xsd.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-4728) Geode Native Documentation Improvements

2018-04-13 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-4728:
--
Labels: pull-request-available  (was: )

> Geode Native Documentation Improvements
> ---
>
> Key: GEODE-4728
> URL: https://issues.apache.org/jira/browse/GEODE-4728
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Addison
>Priority: Major
>  Labels: pull-request-available
>
> This ticket will capture a series of changes to the Geode Native docs to 
> bring them inline with the updated API.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4863) refactor jdbc commands to use this public api

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4863:


Commit 2ecb3725a315bf1b85436dc4c56b32e53ce3237a in geode's branch 
refs/heads/develop from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2ecb372 ]

GEODE-4863: refactor jdbc commands to use this public cluster configuration api 
(#1776)

   * refactored jdbc connector commands to use public cc service
   * removed JdbcConnectorServiceXmlGenerator
   * removed RegionMappingBuilder & ConnectionConfigBuilder
   * if cc service is running then user can only alter whats available in CC
   * describe & List commands now list entries from cc service
   * converted some integration tests to junits
   * removed unwanted functions, tests

Signed-off-by: Jinmei Liao 


> refactor jdbc commands to use this public api
> -
>
> Key: GEODE-4863
> URL: https://issues.apache.org/jira/browse/GEODE-4863
> Project: Geode
>  Issue Type: Sub-task
>  Components: configuration
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> they will need to create a custom config object based on their own xsd.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-5071) Update the gfsh limitations documentation

2018-04-13 Thread Barbara Pruijn (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barbara Pruijn updated GEODE-5071:
--
Description: 
The list of gfsh limitations should be updated on this page:
https://geode.apache.org/docs/guide/14/configuring/cluster_config/gfsh_persist.html#concept_r22_hyw_bl__section_bn3_23p_y4

Under the line: "You cannot directly modify the attributes of the following 
objects:"
Please remove:
cache-listener
cache-loader
cache-writer
custom-expiry
declarable

Further down, please remove:
Adding JNDI bindings



 

  was:
The list of gfsh limitations should be updated on this page:

Under the line: "You cannot directly modify the attributes of the following 
objects:"
Please remove:
cache-listener
cache-loader
cache-writer
custom-expiry
declarable

Further down, please remove:
Adding JNDI bindings



 


> Update the gfsh limitations documentation
> -
>
> Key: GEODE-5071
> URL: https://issues.apache.org/jira/browse/GEODE-5071
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Barbara Pruijn
>Priority: Major
>
> The list of gfsh limitations should be updated on this page:
> https://geode.apache.org/docs/guide/14/configuring/cluster_config/gfsh_persist.html#concept_r22_hyw_bl__section_bn3_23p_y4
> Under the line: "You cannot directly modify the attributes of the following 
> objects:"
> Please remove:
> cache-listener
> cache-loader
> cache-writer
> custom-expiry
> declarable
> Further down, please remove:
> Adding JNDI bindings
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-5071) Update the gfsh limitations documentation

2018-04-13 Thread Barbara Pruijn (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barbara Pruijn updated GEODE-5071:
--
Description: 
The list of gfsh limitations should be updated on this page:

Under the line: "You cannot directly modify the attributes of the following 
objects:"
Please remove:
cache-listener
cache-loader
cache-writer
custom-expiry
declarable

Further down, please remove:
Adding JNDI bindings



 

  was:
The list of gfsh limitations should be updated on this 
page:[https://gemfire.docs.pivotal.io/geode/configuring/cluster_config/gfsh_persist.html]

Under the line: "You cannot directly modify the attributes of the following 
objects:"
Please remove:
cache-listener
cache-loader
cache-writer
custom-expiry
declarable

Further down, please remove:
Adding JNDI bindings



 


> Update the gfsh limitations documentation
> -
>
> Key: GEODE-5071
> URL: https://issues.apache.org/jira/browse/GEODE-5071
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Barbara Pruijn
>Priority: Major
>
> The list of gfsh limitations should be updated on this page:
> Under the line: "You cannot directly modify the attributes of the following 
> objects:"
> Please remove:
> cache-listener
> cache-loader
> cache-writer
> custom-expiry
> declarable
> Further down, please remove:
> Adding JNDI bindings
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-5066) Race condition between stats init and cache close causes memory access exception

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-5066:


Commit 392b8901654304082f2a79237c6ba141a9339109 in geode-native's branch 
refs/heads/develop from [~mcmellawatt]
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=392b890 ]

GEODE-5066: Accessing cacheImpl directly to avoid access exception (#274)



> Race condition between stats init and cache close causes memory access 
> exception
> 
>
> Key: GEODE-5066
> URL: https://issues.apache.org/jira/browse/GEODE-5066
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Ryan McMahon
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> The cache can be accessed by the statistics manager thread after the cache 
> has been destroyed, which results in a memory access exception.  A quick fix 
> is to directly use the cacheImpl in the stats manager initialization logic, 
> though this object may be partially destroyed and potentially run into a 
> similar issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GEODE-5071) Update the gfsh limitations documentation

2018-04-13 Thread Barbara Pruijn (JIRA)
Barbara Pruijn created GEODE-5071:
-

 Summary: Update the gfsh limitations documentation
 Key: GEODE-5071
 URL: https://issues.apache.org/jira/browse/GEODE-5071
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Barbara Pruijn


The list of gfsh limitations should be updated on this 
page:[https://gemfire.docs.pivotal.io/geode/configuring/cluster_config/gfsh_persist.html]

Under the line: "You cannot directly modify the attributes of the following 
objects:"
Please remove:
cache-listener
cache-loader
cache-writer
custom-expiry
declarable

Further down, please remove:
Adding JNDI bindings



 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-5067) Failed dynamic_cast when visibility is set to hidden on Clang

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-5067:


Commit 3694801db067ebcf05a23c5bbe47d8dbdfac512c in geode-native's branch 
refs/heads/develop from [~mcmellawatt]
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=3694801 ]

GEODE-5067: Changing visibility preset to 'default' on Clang (#272)

- Changing visibility preset to 'default' on Clang to fix RTTI/dynamic_casting 
issues

Signed-off-by: Ryan McMahon 


> Failed dynamic_cast when visibility is set to hidden on Clang
> -
>
> Key: GEODE-5067
> URL: https://issues.apache.org/jira/browse/GEODE-5067
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Ryan McMahon
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The testThinClientBigValue test is failing due to issues with Clang and the 
> cmake 'CXX_VISIBILITY_PRESET hidden' setting.  It appears Clang does not 
> propagate visibility attributes through using statements i.e.
> ```
> using CacheableBytes = CacheableArray;
> ```
> Despite CacheableArray and its base class Serializable being decorated with 
> APACHE_GEODE_EXPORT, dynamic_casts appear to fail. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GEODE-5070) Support --member option for describe & list jdbc connector commands

2018-04-13 Thread Sai Boorlagadda (JIRA)
Sai Boorlagadda created GEODE-5070:
--

 Summary: Support --member option for describe & list jdbc 
connector commands
 Key: GEODE-5070
 URL: https://issues.apache.org/jira/browse/GEODE-5070
 Project: Geode
  Issue Type: New Feature
  Components: gfsh
Reporter: Sai Boorlagadda


When cluster configuration service is disabled user have to provide --member 
option in-order to describe and list connections and mappings. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4856) Public API for retrieving/persisting Cluster Configuration

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-4856:


Commit ad45baa5f4221b773797d4051ddd12f66c96aadc in geode's branch 
refs/heads/develop from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ad45baa ]

GEODE-4856: Public API for retrieving/persisting Cluster Configuration (#1791)

  fixed a bug in getCacheConfig and updateCacheConfig
  to support non-existing group

Signed-off-by: Jinmei Liao 



> Public API for retrieving/persisting Cluster Configuration
> --
>
> Key: GEODE-4856
> URL: https://issues.apache.org/jira/browse/GEODE-4856
> Project: Geode
>  Issue Type: New Feature
>  Components: configuration
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Public API for Cluster Configuration Service: 
> https://cwiki.apache.org/confluence/display/GEODE/Public+API+for+Cluster+Configuration
>  Add @experimental to all the public apis we exposed for this story.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-5066) Race condition between stats init and cache close causes memory access exception

2018-04-13 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-5066:
--
Labels: pull-request-available  (was: )

> Race condition between stats init and cache close causes memory access 
> exception
> 
>
> Key: GEODE-5066
> URL: https://issues.apache.org/jira/browse/GEODE-5066
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Ryan McMahon
>Priority: Major
>  Labels: pull-request-available
>
> The cache can be accessed by the statistics manager thread after the cache 
> has been destroyed, which results in a memory access exception.  A quick fix 
> is to directly use the cacheImpl in the stats manager initialization logic, 
> though this object may be partially destroyed and potentially run into a 
> similar issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-5064) Remove unused code and if clause that does not get thrown

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-5064:


Commit 6097e3d74713efba5e11f70921ed41347f7f6cb6 in geode's branch 
refs/heads/develop from [~huynhja]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6097e3d ]

GEODE-5064: Removed unused code in LocalRegion (#1790)



> Remove unused code and if clause that does not get thrown
> -
>
> Key: GEODE-5064
> URL: https://issues.apache.org/jira/browse/GEODE-5064
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> There appears to be an exception that should be thrown, but upon futher 
> inspection, this clause can never be hit because the boolean it checks is 
> never set to true;
>  
> In LocalRegion:
> logger.info("Failed to create index {} on region {} with exception: {}",
>  icd.getIndexName(), this.getFullPath(), ex);
> // Check if the region index creation is from cache.xml, in that case throw 
> exception.
> // Other case is when bucket regions are created dynamically, in that case 
> ignore the
> // exception.
> if (internalRegionArgs.getDeclarativeIndexCreation()) {
>  throw new 
> InternalGemFireError(LocalizedStrings.GemFireCache_INDEX_CREATION_EXCEPTION_1
>  .toLocalizedString(icd.getIndexName(), this.getFullPath()), ex);
> }



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (GEODE-5035) Some tests use incorrect temp directory

2018-04-13 Thread Michael Dodge (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Dodge resolved GEODE-5035.
--
   Resolution: Fixed
Fix Version/s: 1.7.0

> Some tests use incorrect temp directory
> ---
>
> Key: GEODE-5035
> URL: https://issues.apache.org/jira/browse/GEODE-5035
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Michael Dodge
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Some tests that use {{JUnit}}'s {{TemporaryFolder}} rule (e.g., 
> {{DiskSpaceLimitIntegrationTest}} {{FileProcessControllerIntegrationTest}}) 
> do not specify the temp directory to use as the parent folder for the 
> temporary folder. This can result in the default location being used, which 
> is different from what is specified by the pipeline. This can result in 
> strange behavior, such as a test writing contents to a temporary file without 
> exception but then failing an existence test on the same file.
> The {{TemporaryFolder}} rule should be synchronized with the 
> {{java.io.tmpdir}} system property.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-5035) Some tests use incorrect temp directory

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-5035:


Commit 130ed6e36bdb91a68b97a95db3c811f0abaad72c in geode's branch 
refs/heads/develop from [~PivotalSarge]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=130ed6e ]

GEODE-5035: Explicitly pass java.io.tmpdir to JVMs invoked by Gradle. (#1779)

- Exclude distributed tests from using java.io.tmpdir as they appear
  to need /tmp.

> Some tests use incorrect temp directory
> ---
>
> Key: GEODE-5035
> URL: https://issues.apache.org/jira/browse/GEODE-5035
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Michael Dodge
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Some tests that use {{JUnit}}'s {{TemporaryFolder}} rule (e.g., 
> {{DiskSpaceLimitIntegrationTest}} {{FileProcessControllerIntegrationTest}}) 
> do not specify the temp directory to use as the parent folder for the 
> temporary folder. This can result in the default location being used, which 
> is different from what is specified by the pipeline. This can result in 
> strange behavior, such as a test writing contents to a temporary file without 
> exception but then failing an existence test on the same file.
> The {{TemporaryFolder}} rule should be synchronized with the 
> {{java.io.tmpdir}} system property.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (GEODE-4902) Log markers filter some messages pathologically

2018-04-13 Thread Patrick Rhomberg (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Rhomberg resolved GEODE-4902.
-
Resolution: Fixed

> Log markers filter some messages pathologically
> ---
>
> Key: GEODE-4902
> URL: https://issues.apache.org/jira/browse/GEODE-4902
> Project: Geode
>  Issue Type: Bug
>  Components: docs, logging
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Many logging calls across all log levels are marked with 
> {{o.a.g.internal.logging.log4j.LogMarker}} markers for selective enabling and 
> debugging.  All these markers have a parent marker {{GEODE_VERBOSE}}.  
> However, per the default given in 
> {{geode-core/src/main/resources/log4j2.xml}}, this parent marker is set to 
> filter log messages.
> Many of these log messages are invoked at the {{info}} level, suggesting an 
> expectation that the message would be seen.
> These markers should be refactored to (a) include by default markers that 
> commonly or exclusively appear in coarse-grained logging levels, and (b) to 
> reorganize the markers' parent/child relationships so that they are not 
> blanket-disabled by default.  Only those markers attacked to more verbose 
> logging should be disabled by default.
> ---
> Additionally, the log classes {{FastLogger}} and {{LogWriterLogger}} are 
> themselves slightly pathological.  Notably, the former overrides some 
> {{isEnabled}} aliases but leaves exposed default many of the root method 
> signatures.  The latter pathologically includes a reference to itself as a 
> field unto itself in the lines:
> {noformat}
> private final ExtendedLoggerWrapper logWrapper;
> // ...
>   private LogWriterLogger(final Logger logger, final String connectionName,
>   final boolean isSecure) {
> super((AbstractLogger) logger, logger.getName(), 
> logger.getMessageFactory());
> this.logWrapper = this;
> // ...
>   }
> {noformat}
> These classes could use refactoring in their own right, perhaps as a separate 
> child ticket.
> -
> Docs: While only the top-level marker (formerly {{GEMFIRE_VERBOSE}}, now 
> {{GEODE_VERBOSE}}) is documented, it may be worth a release note that the 
> Log4J2 markers have changed, and anyone be using a custom log4j2.xml after 
> discovering these markers will have to update that XML to the new markers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (GEODE-4954) Improve spotless -- remove trivial javadoc stubs

2018-04-13 Thread Patrick Rhomberg (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Rhomberg reassigned GEODE-4954:
---

Assignee: Patrick Rhomberg

> Improve spotless -- remove trivial javadoc stubs
> 
>
> Key: GEODE-4954
> URL: https://issues.apache.org/jira/browse/GEODE-4954
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> For instance, the block
> {noformat}
> @param myparam
> @param secondParam
> @throws Exception
> {noformat}
> is entirely implicit by the method's signature, which is included in the 
> javadoc itself.  Javadoc stubs that do not include description of a given 
> term is trivial, redundant, and should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (GEODE-4955) Improve spotless -- Remove empty javadocs and block comments

2018-04-13 Thread Patrick Rhomberg (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Rhomberg reassigned GEODE-4955:
---

Assignee: Patrick Rhomberg

> Improve spotless -- Remove empty javadocs and block comments
> 
>
> Key: GEODE-4955
> URL: https://issues.apache.org/jira/browse/GEODE-4955
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> This should be executed after GEODE-4654, since the removal of javadoc stubs 
> may yield a now-empty javadoc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (GEODE-4952) Improve spotless -- automatically remove unused imports.

2018-04-13 Thread Patrick Rhomberg (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Rhomberg resolved GEODE-4952.
-
Resolution: Fixed

> Improve spotless -- automatically remove unused imports.
> 
>
> Key: GEODE-4952
> URL: https://issues.apache.org/jira/browse/GEODE-4952
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 3h 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-5056) ParallelGatewaySenderOperationsDUnitTest.testParallelPropagationSenderStartAfterStop_Scenario2 intermittently fail

2018-04-13 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-5056:


Commit f7bb77c89a3d19673e8929275fc6c407a4b382bd in geode's branch 
refs/heads/develop from Xiaojian Zhou
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f7bb77c ]

GEODE-5056: when found the dropped events at primary sender, send (#1794)

QueueRemovalMessage for it

> ParallelGatewaySenderOperationsDUnitTest.testParallelPropagationSenderStartAfterStop_Scenario2
>  intermittently fail 
> ---
>
> Key: GEODE-5056
> URL: https://issues.apache.org/jira/browse/GEODE-5056
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> After fixe GEODE-4942, I found there's at least one race condition is not 
> covered. 
>  
> [vm6] [debug 2018/04/11 16:47:35.189 PDT  Processor2> tid=110] WAN: On primary bucket 57, setting the seq number as 1357
>  
> [vm7] [info 2018/04/11 16:47:35.150 PDT  
> tid=19] Started  ParallelGatewaySender\{id=ln,remoteDsId=2,isRunning =true}
>  
> [vm7] [debug 2018/04/11 16:47:35.189 PDT  10.118.19.25(27489):32781 shared ordered uid=7 port=59148> tid=95] WAN: 
> On secondary bucket 57, setting the seq number as 1357
> [vm7] [debug 2018/04/11 16:47:35.190 PDT  10.118.19.25(27489):32781 shared ordered uid=7 port=59148> tid=95] Key : 
> > 1357
> [vm6] [debug 2018/04/11 16:47:35.190 PDT  Processor2> tid=110] register dropped event for primary queue. BucketId is 
> 57, shadowKey is 1357, prQ is /ln_PARALLEL_GATEWAY_SENDER_QUEUE
>  
> - Note: vm6's sender is restarted and cleanup the map, before the
> QueueRemvalMessage is sent out for the map.
> [vm6] [info 2018/04/11 16:47:35.249 PDT  
> tid=19] Started  ParallelGatewaySender\{id=ln,remoteDsId=2,isRunning =true}
> [vm6] [debug 2018/04/11 16:47:35.437 PDT  GatewaySender_ln_0> tid=118] BatchRemovalThread about to query the batch 
> removal map \{/ln_PARALLEL_GATEWAY_SENDER_QUEUE={96=[1396], 2=[1402], 
> 83=[1383], 6=[1406], 71=[1371], 87=[1387], 73=[1373], 90=[1390], 77=[1377], 
> 94=[1394]}}
> [vm6] [debug 2018/04/11 16:47:35.753 PDT  GatewaySender_ln_0> tid=118] BatchRemovalThread about to query the batch 
> removal map {/ln_PARALLEL_GATEWAY_SENDER_QUEUE={49=[1449], 65=[1465], 
> 83=[1483], 53=[1453], 71=[1471], 87=[1487], *57=[1457]*, 73=[1473], 
> 77=[1477], 62=[1462]}}
>  shadowKey 1457 was created after the sender is restarted
>  
> [vm6] [debug 2018/04/11 16:47:35.438 PDT  GatewaySender_ln_0> tid=118] Sending (ParallelQueueRemovalMessage@2344969b 
> processorId=0 sender=10.118.19.25(27489):32781) to 3 peers 
> ([10.118.19.25(27492):32783@4(GEODE 1.6.0), 
> 10.118.19.25(27485):32779@1(GEODE 1.6.0), 
> 10.118.19.25(27482):32778@2(GEODE 1.6.0)]) via tcp/ip
> [vm7] [debug 2018/04/11 16:47:35.439 PDT  10.118.19.25(27489):32781 shared unordered uid=4 port=59119> tid=52] 
> Received message 'ParallelQueueRemovalMessage@11583f5b processorId=0 
> sender=10.118.19.25(27489):32781' from <10.118.19.25(27489):32781>
>  
> i.e. the dropped key was in the map, but before sending a QueueRemovalMessage 
> the sender is closed and cleared the map. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-5068) Upgrade Jackson to 2.9.5

2018-04-13 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-5068:
--
Labels: pull-request-available  (was: )

> Upgrade Jackson to 2.9.5
> 
>
> Key: GEODE-5068
> URL: https://issues.apache.org/jira/browse/GEODE-5068
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
>  Labels: pull-request-available
>
> We're a patch version behind, let's try to stay on the latest.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-4410) DistributedSystem has public method to get internal class StatisticsManager

2018-04-13 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-4410:
--
Labels: pull-request-available  (was: )

> DistributedSystem has public method to get internal class StatisticsManager
> ---
>
> Key: GEODE-4410
> URL: https://issues.apache.org/jira/browse/GEODE-4410
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GEODE-5069) Reduce direct exposure of GfJsonObject from CommandResult

2018-04-13 Thread Jens Deppe (JIRA)
Jens Deppe created GEODE-5069:
-

 Summary: Reduce direct exposure of GfJsonObject from CommandResult
 Key: GEODE-5069
 URL: https://issues.apache.org/jira/browse/GEODE-5069
 Project: Geode
  Issue Type: Sub-task
  Components: gfsh
Reporter: Jens Deppe






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (GEODE-5009) Add unit tests for GfJsonObject

2018-04-13 Thread Jens Deppe (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jens Deppe resolved GEODE-5009.
---
   Resolution: Fixed
Fix Version/s: 1.7.0

> Add unit tests for GfJsonObject
> ---
>
> Key: GEODE-5009
> URL: https://issues.apache.org/jira/browse/GEODE-5009
> Project: Geode
>  Issue Type: Sub-task
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (GEODE-5008) Add unit tests for GfJsonArray

2018-04-13 Thread Jens Deppe (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jens Deppe resolved GEODE-5008.
---
   Resolution: Fixed
Fix Version/s: 1.7.0

> Add unit tests for GfJsonArray
> --
>
> Key: GEODE-5008
> URL: https://issues.apache.org/jira/browse/GEODE-5008
> Project: Geode
>  Issue Type: Sub-task
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)