[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4647:


Commit 44821a0c2ac277ce936c5e401d4e1db726d66233 in geode's branch 
refs/heads/feature/GEODE-4647 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=44821a0 ]

GEODE-4647: add a stats eventSecondaryQueueSizeId to track events in secondary
gateway sender queue


> Add a new stat for AyncEventQueue/GatewaySender to track 
> secondaryEventsQueueSize
> -
>
> Key: GEODE-4647
> URL: https://issues.apache.org/jira/browse/GEODE-4647
> Project: Geode
>  Issue Type: Bug
>  Components: docs, wan
>Reporter: Jason Huynh
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> Currently we have eventsQueueSize which tells us how big the queue is based 
> on how many primary events are in the queue.
> It would be nice to have the same type of stat for how many secondary events 
> are in the queue.



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

[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4647:


Commit ba9ea6e6da7fedb88a07884f44aae8f255c7a04c in geode's branch 
refs/heads/feature/GEODE-4647 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ba9ea6e ]

GEODE-4647: spotlessApply


> Add a new stat for AyncEventQueue/GatewaySender to track 
> secondaryEventsQueueSize
> -
>
> Key: GEODE-4647
> URL: https://issues.apache.org/jira/browse/GEODE-4647
> Project: Geode
>  Issue Type: Bug
>  Components: docs, wan
>Reporter: Jason Huynh
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> Currently we have eventsQueueSize which tells us how big the queue is based 
> on how many primary events are in the queue.
> It would be nice to have the same type of stat for how many secondary events 
> are in the queue.



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

[jira] [Commented] (GEODE-4791) Increase gradle version from 3.5.1 to 4.51

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4791:


Commit 78df32fe7a8bfe7be7595472377b660d899953fa in geode's branch 
refs/heads/feature/GEODE-4647 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=78df32f ]

GEODE-4791: Upgrading gradle from 3.5.1 to 4.5.1


> Increase gradle version from 3.5.1 to 4.51
> --
>
> Key: GEODE-4791
> URL: https://issues.apache.org/jira/browse/GEODE-4791
> Project: Geode
>  Issue Type: Improvement
>  Components: build, general
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4778) Code clean up and refactoring for Lucene

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4778:


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

GEODE-4778: Code clean up and refactor (#1553)

* code clean up
* Removed unused aeq lookup
* Removed/collapsed AbstractRepositoryManager
* Reduced references to LuceneIndexImpl into InternalLuceneIndex


> Code clean up and refactoring for Lucene
> 
>
> Key: GEODE-4778
> URL: https://issues.apache.org/jira/browse/GEODE-4778
> Project: Geode
>  Issue Type: Sub-task
>  Components: lucene
>Reporter: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> There are various areas that could be cleaned up in the Lucene module.
> This ticket is a general ticket to reduce method calls, condense classes and 
> remove unneeded variables, among other code clarity/clean up tasks



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

[jira] [Commented] (GEODE-4791) Increase gradle version from 3.5.1 to 4.51

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4791:


Commit 13b7364a7e3e09ba756ef68059acdfc6d0602e30 in geode's branch 
refs/heads/feature/GEODE-4647 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=13b7364 ]

GEODE-4791: turning off gradle parallel builds


> Increase gradle version from 3.5.1 to 4.51
> --
>
> Key: GEODE-4791
> URL: https://issues.apache.org/jira/browse/GEODE-4791
> Project: Geode
>  Issue Type: Improvement
>  Components: build, general
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




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

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

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4384:


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

GEODE-4384: gfsh command to destroy jndi binding (#1568)



> 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
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 2h 20m
>  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-4795) User Guide: Inequality queries return UNDEFINED entries

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4795:


Commit 3dfad345f292a3e71498d922c16372655ace49c6 in geode's branch 
refs/heads/feature/GEODE-4647 from [~dbarnes97]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3dfad34 ]

GEODE-4795: User Guide: Inequality queries return UNDEFINED entries


> User Guide: Inequality queries return UNDEFINED entries
> ---
>
> Key: GEODE-4795
> URL: https://issues.apache.org/jira/browse/GEODE-4795
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> The section describing OQL operators 
> [http://geode.apache.org/docs/guide/14/developing/query_additional/operators.html]
>  should state that inequality queries return results for which the search 
> field is UNDEFINED.



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

[jira] [Commented] (GEODE-4792) ArgumentRedactor regex should be rewritten to be more clear.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4792:


Commit 457f1c54f84d64378302a209c91242aca0bec570 in geode's branch 
refs/heads/feature/GEODE-4647 from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=457f1c5 ]

GEODE-4792: Expand ArgumentRedactor regular expression logic for better 
self-documentation.



> ArgumentRedactor regex should be rewritten to be more clear.
> 
>
> Key: GEODE-4792
> URL: https://issues.apache.org/jira/browse/GEODE-4792
> Project: Geode
>  Issue Type: Improvement
>  Components: security
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Even though I wrote it and it has a lot of comments, it's still hard to read 
> the ArgumentRedactor's regex.  It should be broken apart for better 
> readability.



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

[jira] [Commented] (GEODE-4797) Categorize all WAN tests as WANTest

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4797:


Commit c13886579a6075a5b2d52e60db668e9151b8a320 in geode's branch 
refs/heads/feature/GEODE-4647 from [~nabarunnag]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c138865 ]

GEODE-4797: Added WANTest category (#1580)



> Categorize all WAN tests as WANTest 
> 
>
> Key: GEODE-4797
> URL: https://issues.apache.org/jira/browse/GEODE-4797
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: nabarun
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4755) Jar deploy fails on Windows

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4755:


Commit d62173a1b8be41dbe22a79ce4fe9faa6cea30565 in geode's branch 
refs/heads/feature/GEODE-4647 from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d62173a ]

GEODE-4755: Use a more portable File permission API (#1573)

- This lets jar deployment work on Windows
- Unify creation of temporary staging directory

> Jar deploy fails on Windows
> ---
>
> Key: GEODE-4755
> URL: https://issues.apache.org/jira/browse/GEODE-4755
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Fails with this exception:
> {noformat}
> java.lang.UnsupportedOperationException: 'posix:permissions' not supported as 
> initial attribute
>at 
> sun.nio.fs.WindowsSecurityDescriptor.fromAttribute(WindowsSecurityDescriptor.java:358)
>at 
> sun.nio.fs.WindowsFileSystemProvider.createDirectory(WindowsFileSystemProvider.java:492)
>at java.nio.file.Files.createDirectory(Files.java:674)
>at java.nio.file.TempFileHelper.create(TempFileHelper.java:136)
>at 
> java.nio.file.TempFileHelper.createTempDirectory(TempFileHelper.java:173)
>at java.nio.file.Files.createTempDirectory(Files.java:991)
>at 
> org.apache.geode.management.internal.beans.FileUploader.uploadFile(FileUploader.java:77)
> {noformat}
> Potential classes affected:
> {noformat}
> org.apache.geode.distributed.internal.ClusterConfigurationService
> org.apache.geode.internal.cache.ClusterConfigurationLoader
> org.apache.geode.management.internal.beans.FileUploader
> org.apache.geode.management.internal.cli.functions.DeployFunction
> org.apache.geode.management.internal.web.controllers.AbstractCommandsController
> {noformat}
> Posixness can be checked with 
> {{FileSystems.getDefault().supportedFileAttributeViews().contains(“posix”);}}



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

[jira] [Commented] (GEODE-4791) Increase gradle version from 3.5.1 to 4.51

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4791:


Commit e09c4091382e1c6bfafbb77de86029bb08fcccea in geode's branch 
refs/heads/feature/GEODE-4647 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e09c409 ]

GEODE-4791: backing out upgrade to 4.5.1 due to an incompatibility with 
dockerized-test library, which only supports gradle 4.2


> Increase gradle version from 3.5.1 to 4.51
> --
>
> Key: GEODE-4791
> URL: https://issues.apache.org/jira/browse/GEODE-4791
> Project: Geode
>  Issue Type: Improvement
>  Components: build, general
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4647:


Commit 65a8f80a91306fd766b48769f42338e4f78f0533 in geode's branch 
refs/heads/feature/GEODE-4647 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=65a8f80 ]

GEODE-4647: add a stats eventSecondaryQueueSizeId to track events in secondary
gateway sender queue


> Add a new stat for AyncEventQueue/GatewaySender to track 
> secondaryEventsQueueSize
> -
>
> Key: GEODE-4647
> URL: https://issues.apache.org/jira/browse/GEODE-4647
> Project: Geode
>  Issue Type: Bug
>  Components: docs, wan
>Reporter: Jason Huynh
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> Currently we have eventsQueueSize which tells us how big the queue is based 
> on how many primary events are in the queue.
> It would be nice to have the same type of stat for how many secondary events 
> are in the queue.



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

[jira] [Commented] (GEODE-4791) Increase gradle version from 3.5.1 to 4.51

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4791:


Commit e09c4091382e1c6bfafbb77de86029bb08fcccea in geode's branch 
refs/heads/develop from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e09c409 ]

GEODE-4791: backing out upgrade to 4.5.1 due to an incompatibility with 
dockerized-test library, which only supports gradle 4.2


> Increase gradle version from 3.5.1 to 4.51
> --
>
> Key: GEODE-4791
> URL: https://issues.apache.org/jira/browse/GEODE-4791
> Project: Geode
>  Issue Type: Improvement
>  Components: build, general
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4791) Increase gradle version from 3.5.1 to 4.51

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4791:


Commit e09c4091382e1c6bfafbb77de86029bb08fcccea in geode's branch 
refs/heads/feature/GEODE-4791 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e09c409 ]

GEODE-4791: backing out upgrade to 4.5.1 due to an incompatibility with 
dockerized-test library, which only supports gradle 4.2


> Increase gradle version from 3.5.1 to 4.51
> --
>
> Key: GEODE-4791
> URL: https://issues.apache.org/jira/browse/GEODE-4791
> Project: Geode
>  Issue Type: Improvement
>  Components: build, general
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (GEODE-4811) Add a feature-flag annotation to gfsh commands

[ASF GitHub Bot (JIRA)]

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

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

> Add a feature-flag annotation to gfsh commands
> --
>
> Key: GEODE-4811
> URL: https://issues.apache.org/jira/browse/GEODE-4811
> Project: Geode
>  Issue Type: New Feature
>  Components: gfsh
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>
> Many gfsh commands are mutually required by each other for full 
> functionality.  For instance, {{destroy jndi-binding}} is meaningless without 
> the {{create jndi-binding}} command.
> As a developer, I would like to be able to coordinate release of multiple 
> related commands at once, across multiple commits.  A {{@FeatureFlag}} 
> annotation on gfsh command classes would be extremely useful.



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

[jira] [Updated] (GEODE-4814) Categorize FunctionService Tests

[Jason Huynh (JIRA)]

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

Jason Huynh updated GEODE-4814:
---
Issue Type: Task  (was: Bug)

> Categorize FunctionService Tests
> 
>
> Key: GEODE-4814
> URL: https://issues.apache.org/jira/browse/GEODE-4814
> Project: Geode
>  Issue Type: Task
>  Components: functions
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>
> add a new FunctionServiceTest interface and categorize all relevant dunit and 
> integration tests



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

[jira] [Created] (GEODE-4814) Categorize FunctionService Tests

[Jason Huynh (JIRA)]

Jason Huynh created GEODE-4814:
--

 Summary: Categorize FunctionService Tests
 Key: GEODE-4814
 URL: https://issues.apache.org/jira/browse/GEODE-4814
 Project: Geode
  Issue Type: Bug
  Components: functions
Reporter: Jason Huynh


add a new FunctionServiceTest interface and categorize all relevant dunit and 
integration tests



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

[jira] [Assigned] (GEODE-4814) Categorize FunctionService Tests

[Jason Huynh (JIRA)]

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

Jason Huynh reassigned GEODE-4814:
--

Assignee: Jason Huynh

> Categorize FunctionService Tests
> 
>
> Key: GEODE-4814
> URL: https://issues.apache.org/jira/browse/GEODE-4814
> Project: Geode
>  Issue Type: Bug
>  Components: functions
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>
> add a new FunctionServiceTest interface and categorize all relevant dunit and 
> integration tests



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

[jira] [Updated] (GEODE-4813) Categorize register interest tests

[ASF GitHub Bot (JIRA)]

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

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

> Categorize register interest tests
> --
>
> Key: GEODE-4813
> URL: https://issues.apache.org/jira/browse/GEODE-4813
> Project: Geode
>  Issue Type: Task
>  Components: client queues
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
>
> Add the ClientSubscription category to all register interest tests



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

[jira] [Assigned] (GEODE-4813) Categorize register interest tests

[Jason Huynh (JIRA)]

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

Jason Huynh reassigned GEODE-4813:
--

Assignee: Jason Huynh

> Categorize register interest tests
> --
>
> Key: GEODE-4813
> URL: https://issues.apache.org/jira/browse/GEODE-4813
> Project: Geode
>  Issue Type: Bug
>  Components: client queues
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>
> Add the ClientSubscription category to all register interest tests



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

[jira] [Updated] (GEODE-4813) Categorize register interest tests

[Jason Huynh (JIRA)]

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

Jason Huynh updated GEODE-4813:
---
Issue Type: Task  (was: Bug)

> Categorize register interest tests
> --
>
> Key: GEODE-4813
> URL: https://issues.apache.org/jira/browse/GEODE-4813
> Project: Geode
>  Issue Type: Task
>  Components: client queues
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>
> Add the ClientSubscription category to all register interest tests



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

[jira] [Assigned] (GEODE-4812) PartitionRegionConfig fails serialization via Externalizable

[Kirk Lund (JIRA)]

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

Kirk Lund reassigned GEODE-4812:


Assignee: Kirk Lund

> PartitionRegionConfig fails serialization via Externalizable
> 
>
> Key: GEODE-4812
> URL: https://issues.apache.org/jira/browse/GEODE-4812
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.0.0-incubating, 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 
> 1.4.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>
> PartitionRegionConfig extends ExternalizableDSFID which implements 
> Externalizable. It then mysteriously fails when attempting to serialize via 
> Externalizable.
> New test PartitionRegionConfigTest.externalizes() exposes this problem:
> {noformat}
> java.lang.NullPointerException
>   at 
> org.apache.geode.internal.cache.PartitionRegionConfig.toData(PartitionRegionConfig.java:246)
>   at 
> org.apache.geode.internal.ExternalizableDSFID.writeExternal(ExternalizableDSFID.java:35)
>   at 
> java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1459)
>   at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1430)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
>   at 
> org.apache.commons.lang.SerializationUtils.serialize(SerializationUtils.java:109)
>   at 
> org.apache.commons.lang.SerializationUtils.serialize(SerializationUtils.java:134)
>   at 
> org.apache.geode.internal.cache.PartitionRegionConfigTest.externalizes(PartitionRegionConfigTest.java:74)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
>   at 
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
>   at 
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
>   at 
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
>   at 
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> {noformat}



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

[jira] [Created] (GEODE-4812) PartitionRegionConfig fails serialization via Externalizable

[Kirk Lund (JIRA)]

Kirk Lund created GEODE-4812:


 Summary: PartitionRegionConfig fails serialization via 
Externalizable
 Key: GEODE-4812
 URL: https://issues.apache.org/jira/browse/GEODE-4812
 Project: Geode
  Issue Type: Bug
  Components: regions
Reporter: Kirk Lund


PartitionRegionConfig extends ExternalizableDSFID which implements 
Externalizable. It then mysteriously fails when attempting to serialize via 
Externalizable.

New test PartitionRegionConfigTest.externalizes() exposes this problem:
{noformat}
java.lang.NullPointerException
at 
org.apache.geode.internal.cache.PartitionRegionConfig.toData(PartitionRegionConfig.java:246)
at 
org.apache.geode.internal.ExternalizableDSFID.writeExternal(ExternalizableDSFID.java:35)
at 
java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1459)
at 
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1430)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
at 
org.apache.commons.lang.SerializationUtils.serialize(SerializationUtils.java:109)
at 
org.apache.commons.lang.SerializationUtils.serialize(SerializationUtils.java:134)
at 
org.apache.geode.internal.cache.PartitionRegionConfigTest.externalizes(PartitionRegionConfigTest.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at 
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
at 
com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
at 
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
at 
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
{noformat}




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

[jira] [Updated] (GEODE-4812) PartitionRegionConfig fails serialization via Externalizable

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-4812:
-
Affects Version/s: 1.0.0-incubating
   1.1.0
   1.1.1
   1.2.0
   1.3.0
   1.2.1
   1.4.0

> PartitionRegionConfig fails serialization via Externalizable
> 
>
> Key: GEODE-4812
> URL: https://issues.apache.org/jira/browse/GEODE-4812
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.0.0-incubating, 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 
> 1.4.0
>Reporter: Kirk Lund
>Priority: Major
>
> PartitionRegionConfig extends ExternalizableDSFID which implements 
> Externalizable. It then mysteriously fails when attempting to serialize via 
> Externalizable.
> New test PartitionRegionConfigTest.externalizes() exposes this problem:
> {noformat}
> java.lang.NullPointerException
>   at 
> org.apache.geode.internal.cache.PartitionRegionConfig.toData(PartitionRegionConfig.java:246)
>   at 
> org.apache.geode.internal.ExternalizableDSFID.writeExternal(ExternalizableDSFID.java:35)
>   at 
> java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1459)
>   at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1430)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
>   at 
> org.apache.commons.lang.SerializationUtils.serialize(SerializationUtils.java:109)
>   at 
> org.apache.commons.lang.SerializationUtils.serialize(SerializationUtils.java:134)
>   at 
> org.apache.geode.internal.cache.PartitionRegionConfigTest.externalizes(PartitionRegionConfigTest.java:74)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
>   at 
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
>   at 
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
>   at 
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
>   at 
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> {noformat}



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

[jira] [Commented] (GEODE-4797) Categorize all WAN tests as WANTest

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4797:


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

GEODE-4797: Added WANTest category (#1580)



> Categorize all WAN tests as WANTest 
> 
>
> Key: GEODE-4797
> URL: https://issues.apache.org/jira/browse/GEODE-4797
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: nabarun
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (GEODE-4812) PartitionRegionConfig fails serialization via Externalizable

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-4812:
-
Priority: Trivial  (was: Major)

> PartitionRegionConfig fails serialization via Externalizable
> 
>
> Key: GEODE-4812
> URL: https://issues.apache.org/jira/browse/GEODE-4812
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.0.0-incubating, 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 
> 1.4.0
>Reporter: Kirk Lund
>Priority: Trivial
>
> PartitionRegionConfig extends ExternalizableDSFID which implements 
> Externalizable. It then mysteriously fails when attempting to serialize via 
> Externalizable.
> New test PartitionRegionConfigTest.externalizes() exposes this problem:
> {noformat}
> java.lang.NullPointerException
>   at 
> org.apache.geode.internal.cache.PartitionRegionConfig.toData(PartitionRegionConfig.java:246)
>   at 
> org.apache.geode.internal.ExternalizableDSFID.writeExternal(ExternalizableDSFID.java:35)
>   at 
> java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1459)
>   at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1430)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
>   at 
> org.apache.commons.lang.SerializationUtils.serialize(SerializationUtils.java:109)
>   at 
> org.apache.commons.lang.SerializationUtils.serialize(SerializationUtils.java:134)
>   at 
> org.apache.geode.internal.cache.PartitionRegionConfigTest.externalizes(PartitionRegionConfigTest.java:74)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
>   at 
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
>   at 
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
>   at 
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
>   at 
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> {noformat}



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

[jira] [Resolved] (GEODE-4795) User Guide: Inequality queries return UNDEFINED entries

[Dave Barnes (JIRA)]

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

Dave Barnes resolved GEODE-4795.

   Resolution: Fixed
Fix Version/s: 1.6.0

> User Guide: Inequality queries return UNDEFINED entries
> ---
>
> Key: GEODE-4795
> URL: https://issues.apache.org/jira/browse/GEODE-4795
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> The section describing OQL operators 
> [http://geode.apache.org/docs/guide/14/developing/query_additional/operators.html]
>  should state that inequality queries return results for which the search 
> field is UNDEFINED.



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

[jira] [Commented] (GEODE-4795) User Guide: Inequality queries return UNDEFINED entries

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4795:


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

GEODE-4795: User Guide: Inequality queries return UNDEFINED entries


> User Guide: Inequality queries return UNDEFINED entries
> ---
>
> Key: GEODE-4795
> URL: https://issues.apache.org/jira/browse/GEODE-4795
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> The section describing OQL operators 
> [http://geode.apache.org/docs/guide/14/developing/query_additional/operators.html]
>  should state that inequality queries return results for which the search 
> field is UNDEFINED.



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

[jira] [Updated] (GEODE-4748) Geode put may result in inconsistent cache if network problem occurs or serialization of key or value class fails

[Fred Krone (JIRA)]

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

Fred Krone updated GEODE-4748:
--
Component/s: (was: regions)
 serialization

> Geode put may result in inconsistent cache if network problem occurs or 
> serialization of key or value class fails
> -
>
> Key: GEODE-4748
> URL: https://issues.apache.org/jira/browse/GEODE-4748
> Project: Geode
>  Issue Type: Bug
>  Components: membership, serialization
>Affects Versions: 1.0.0-incubating, 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 
> 1.4.0
>Reporter: Vadim Lotarev
>Priority: Critical
> Attachments: clumsy.jpg, geode-4748.log
>
>
> Geode cache became inconsistent in case if networking and serialization 
> problems occur at commit time. How to reproduce:
> # create any simple _replicated_ region
> # run two nodes
> # put some value in the region (within a transaction or not)
> # execute query on both nodes to check that the same value is returned (I 
> used JMX for that)
> # emulate somehow temporary networking or serialization error (throw 
> IOException from toData() or use [clumsy|https://jagt.github.io/clumsy/] to 
> emulate network interruption)
> # repeat [#3], exception should occur
> # repeat [#4] - you should see different values on different nodes
> It looks like errors occurred after {{TXState.applyChanges}} produce 
> inconsistency - it is impossible to rollback applied local changes what leads 
> to the state where local cache contains  changed data but other node(s) old 
> data (before changes made in transaction).
> To me, consistency is a key property for the systems like Geode so I would 
> consider this bug as a critical one.



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

[jira] [Updated] (GEODE-3968) Document how rebalance actually works

[Fred Krone (JIRA)]

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

Fred Krone updated GEODE-3968:
--
Component/s: (was: docs)

> Document how rebalance actually works
> -
>
> Key: GEODE-3968
> URL: https://issues.apache.org/jira/browse/GEODE-3968
> Project: Geode
>  Issue Type: Sub-task
>  Components: regions
>Reporter: Fred Krone
>Priority: Major
>  Labels: rebalance
>
> There are a lot of user questions around how rebalance works, configuration 
> etc.
> Example from Gideon: I still think we need to make important improvements to 
> the rebalancing documentation.  One "big picture" item is to explain the 
> resource manager's role in rebalancing activity (RM isn't mentioned in the 
> doc's in this context).  
> We should also add more detail explaining how to optimize multi-threaded 
> rebalancing.  
> What exactly happens with multi-threaded rebalancing, and what are the limits 
> and/or consequences?  For example, could too high a degree of parallelism 
> defeat the rebalancing algorithm (given the original design targets reaching 
> the right end-state by moving buckets one at-a-time)?  Or, is the reverse 
> true, and we might bet better final results with more threads ? Is there some 
> guideline we can devise based on the number of nodes in the cluster, the 
> number of cores per server, and the configured number of buckets for a PR?  
> Is multi-threaded applied on each host individually, or are the extra threads 
> only running on the rebalance "coordinator" node?  
> I wasn't able to explain any of the nuances of rebalancing based on our docs 
> and cursory review of the Geode codebase (although for the latter I'm sure I 
> could eventually . . .).  This actually screams for a dedicated section on 
> the Geode Wiki "Geode Internal Architecture" section . . . I would be happy 
> to help write this I can get get started with answers to the above questions.



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

[jira] [Closed] (GEODE-3968) Document how rebalance actually works

[Fred Krone (JIRA)]

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

Fred Krone closed GEODE-3968.
-

> Document how rebalance actually works
> -
>
> Key: GEODE-3968
> URL: https://issues.apache.org/jira/browse/GEODE-3968
> Project: Geode
>  Issue Type: Sub-task
>  Components: regions
>Reporter: Fred Krone
>Priority: Major
>  Labels: rebalance
>
> There are a lot of user questions around how rebalance works, configuration 
> etc.
> Example from Gideon: I still think we need to make important improvements to 
> the rebalancing documentation.  One "big picture" item is to explain the 
> resource manager's role in rebalancing activity (RM isn't mentioned in the 
> doc's in this context).  
> We should also add more detail explaining how to optimize multi-threaded 
> rebalancing.  
> What exactly happens with multi-threaded rebalancing, and what are the limits 
> and/or consequences?  For example, could too high a degree of parallelism 
> defeat the rebalancing algorithm (given the original design targets reaching 
> the right end-state by moving buckets one at-a-time)?  Or, is the reverse 
> true, and we might bet better final results with more threads ? Is there some 
> guideline we can devise based on the number of nodes in the cluster, the 
> number of cores per server, and the configured number of buckets for a PR?  
> Is multi-threaded applied on each host individually, or are the extra threads 
> only running on the rebalance "coordinator" node?  
> I wasn't able to explain any of the nuances of rebalancing based on our docs 
> and cursory review of the Geode codebase (although for the latter I'm sure I 
> could eventually . . .).  This actually screams for a dedicated section on 
> the Geode Wiki "Geode Internal Architecture" section . . . I would be happy 
> to help write this I can get get started with answers to the above questions.



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

[jira] [Resolved] (GEODE-3968) Document how rebalance actually works

[Fred Krone (JIRA)]

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

Fred Krone resolved GEODE-3968.
---
Resolution: Fixed

> Document how rebalance actually works
> -
>
> Key: GEODE-3968
> URL: https://issues.apache.org/jira/browse/GEODE-3968
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, regions
>Reporter: Fred Krone
>Priority: Major
>  Labels: rebalance
>
> There are a lot of user questions around how rebalance works, configuration 
> etc.
> Example from Gideon: I still think we need to make important improvements to 
> the rebalancing documentation.  One "big picture" item is to explain the 
> resource manager's role in rebalancing activity (RM isn't mentioned in the 
> doc's in this context).  
> We should also add more detail explaining how to optimize multi-threaded 
> rebalancing.  
> What exactly happens with multi-threaded rebalancing, and what are the limits 
> and/or consequences?  For example, could too high a degree of parallelism 
> defeat the rebalancing algorithm (given the original design targets reaching 
> the right end-state by moving buckets one at-a-time)?  Or, is the reverse 
> true, and we might bet better final results with more threads ? Is there some 
> guideline we can devise based on the number of nodes in the cluster, the 
> number of cores per server, and the configured number of buckets for a PR?  
> Is multi-threaded applied on each host individually, or are the extra threads 
> only running on the rebalance "coordinator" node?  
> I wasn't able to explain any of the nuances of rebalancing based on our docs 
> and cursory review of the Geode codebase (although for the latter I'm sure I 
> could eventually . . .).  This actually screams for a dedicated section on 
> the Geode Wiki "Geode Internal Architecture" section . . . I would be happy 
> to help write this I can get get started with answers to the above questions.



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

[jira] [Assigned] (GEODE-4721) Being invoked within JTA Region.values() (and all iteration related operations) does return empty collection

[Fred Krone (JIRA)]

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

Fred Krone reassigned GEODE-4721:
-

Assignee: (was: Eric Shu)

> Being invoked within JTA Region.values() (and all iteration related 
> operations) does return empty collection
> 
>
> Key: GEODE-4721
> URL: https://issues.apache.org/jira/browse/GEODE-4721
> Project: Geode
>  Issue Type: Bug
>  Components: regions, transactions
>Reporter: Vadim Lotarev
>Priority: Critical
>  Labels: pull-request-available
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> {{Region.values()}} returns empty collection being invoked within JTA. Other 
> operations returns data, for example this workaround works (though less 
> efficient): {{region.getAll(region.keySet()).values()}}, also 
> {{Region.size()}} returns correct value.



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

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

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn commented on GEODE-4384:
---

We should add the option --if-exists to the destroy command.
{code:java}
gfsh>help destroy jndi-binding
NAME
destroy jndi-binding
IS AVAILABLE
true
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
If true, the command will be a no-op if the entity does not exist.
Required: false
Default (if the parameter is specified without value): true
Default (if the parameter is not specified): false{code}

> 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
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 2h 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-4811) Add a feature-flag annotation to gfsh commands

[Patrick Rhomberg (JIRA)]

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

Patrick Rhomberg commented on GEODE-4811:
-

I guess it depends on whether or not you want it to be completely inaccessible, 
or just difficult to access.

I think there would be use in having them hidden behind a system property, and 
then being able to access them via {{JAVA_ARGS=-Dmy.feature.flag=true gfsh}}.  
Although I suppose an annotation {{@Disabled}} could also take a flag, like 
{{@Disabled(unless = "my.feature.flag")}}



> Add a feature-flag annotation to gfsh commands
> --
>
> Key: GEODE-4811
> URL: https://issues.apache.org/jira/browse/GEODE-4811
> Project: Geode
>  Issue Type: New Feature
>  Components: gfsh
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> Many gfsh commands are mutually required by each other for full 
> functionality.  For instance, {{destroy jndi-binding}} is meaningless without 
> the {{create jndi-binding}} command.
> As a developer, I would like to be able to coordinate release of multiple 
> related commands at once, across multiple commits.  A {{@FeatureFlag}} 
> annotation on gfsh command classes would be extremely useful.



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

[jira] [Commented] (GEODE-4811) Add a feature-flag annotation to gfsh commands

[Swapnil Bawaskar (JIRA)]

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

Swapnil Bawaskar commented on GEODE-4811:
-

Would it be more intuitive if we called the annotation {{@Disabled}}?

> Add a feature-flag annotation to gfsh commands
> --
>
> Key: GEODE-4811
> URL: https://issues.apache.org/jira/browse/GEODE-4811
> Project: Geode
>  Issue Type: New Feature
>  Components: gfsh
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> Many gfsh commands are mutually required by each other for full 
> functionality.  For instance, {{destroy jndi-binding}} is meaningless without 
> the {{create jndi-binding}} command.
> As a developer, I would like to be able to coordinate release of multiple 
> related commands at once, across multiple commits.  A {{@FeatureFlag}} 
> annotation on gfsh command classes would be extremely useful.



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

[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4685:


Commit 91235275cb8fb55006c82d3f85ec274b6cf1b7d3 in geode's branch 
refs/heads/feature/GEODE-4685 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9123527 ]

GEODE-4685: Moving of static DefaultQuery.setPdxReadSerialized to the 
TypeRegistry.
Cleaned up the overriding of readSerialized to reset to previous value.
Added cache to AbstractJdbcCallback.java so that children classes can access it.
Replaced AtomicLong with LongAdder.


> Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
> --
>
> Key: GEODE-4685
> URL: https://issues.apache.org/jira/browse/GEODE-4685
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: nabarun
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 5h 10m
>  Remaining Estimate: 0h
>
> Replace with the solution from GEODE-4679



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

[jira] [Commented] (GEODE-4778) Code clean up and refactoring for Lucene

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4778:


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

GEODE-4778: Code clean up and refactor (#1553)

* code clean up
* Removed unused aeq lookup
* Removed/collapsed AbstractRepositoryManager
* Reduced references to LuceneIndexImpl into InternalLuceneIndex


> Code clean up and refactoring for Lucene
> 
>
> Key: GEODE-4778
> URL: https://issues.apache.org/jira/browse/GEODE-4778
> Project: Geode
>  Issue Type: Sub-task
>  Components: lucene
>Reporter: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> There are various areas that could be cleaned up in the Lucene module.
> This ticket is a general ticket to reduce method calls, condense classes and 
> remove unneeded variables, among other code clarity/clean up tasks



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

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

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4384:


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

GEODE-4384: gfsh command to destroy jndi binding (#1568)



> 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
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 2h 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-4778) Code clean up and refactoring for Lucene

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4778:


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

GEODE-4778: Code clean up and refactor (#1553)

* code clean up
* Removed unused aeq lookup
* Removed/collapsed AbstractRepositoryManager
* Reduced references to LuceneIndexImpl into InternalLuceneIndex


> Code clean up and refactoring for Lucene
> 
>
> Key: GEODE-4778
> URL: https://issues.apache.org/jira/browse/GEODE-4778
> Project: Geode
>  Issue Type: Sub-task
>  Components: lucene
>Reporter: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> There are various areas that could be cleaned up in the Lucene module.
> This ticket is a general ticket to reduce method calls, condense classes and 
> remove unneeded variables, among other code clarity/clean up tasks



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

[jira] [Commented] (GEODE-4755) Jar deploy fails on Windows

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4755:


Commit d62173a1b8be41dbe22a79ce4fe9faa6cea30565 in geode's branch 
refs/heads/feature/GEODE-4685 from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d62173a ]

GEODE-4755: Use a more portable File permission API (#1573)

- This lets jar deployment work on Windows
- Unify creation of temporary staging directory

> Jar deploy fails on Windows
> ---
>
> Key: GEODE-4755
> URL: https://issues.apache.org/jira/browse/GEODE-4755
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Fails with this exception:
> {noformat}
> java.lang.UnsupportedOperationException: 'posix:permissions' not supported as 
> initial attribute
>at 
> sun.nio.fs.WindowsSecurityDescriptor.fromAttribute(WindowsSecurityDescriptor.java:358)
>at 
> sun.nio.fs.WindowsFileSystemProvider.createDirectory(WindowsFileSystemProvider.java:492)
>at java.nio.file.Files.createDirectory(Files.java:674)
>at java.nio.file.TempFileHelper.create(TempFileHelper.java:136)
>at 
> java.nio.file.TempFileHelper.createTempDirectory(TempFileHelper.java:173)
>at java.nio.file.Files.createTempDirectory(Files.java:991)
>at 
> org.apache.geode.management.internal.beans.FileUploader.uploadFile(FileUploader.java:77)
> {noformat}
> Potential classes affected:
> {noformat}
> org.apache.geode.distributed.internal.ClusterConfigurationService
> org.apache.geode.internal.cache.ClusterConfigurationLoader
> org.apache.geode.management.internal.beans.FileUploader
> org.apache.geode.management.internal.cli.functions.DeployFunction
> org.apache.geode.management.internal.web.controllers.AbstractCommandsController
> {noformat}
> Posixness can be checked with 
> {{FileSystems.getDefault().supportedFileAttributeViews().contains(“posix”);}}



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

[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4685:


Commit 39671f58c621b1d405a2cc929f56085ad339fb21 in geode's branch 
refs/heads/feature/GEODE-4685 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=39671f5 ]

GEODE-4685: Moving of static DefaultQuery.setPdxReadSerialized to the 
TypeRegistry.
Cleaned up the overriding of readSerialized to reset to previous value.
Added cache to AbstractJdbcCallback.java so that children classes can access it.
Replaced AtomicLong with LongAdder.


> Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
> --
>
> Key: GEODE-4685
> URL: https://issues.apache.org/jira/browse/GEODE-4685
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: nabarun
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 5h 10m
>  Remaining Estimate: 0h
>
> Replace with the solution from GEODE-4679



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

[jira] [Commented] (GEODE-4791) Increase gradle version from 3.5.1 to 4.51

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4791:


Commit 13b7364a7e3e09ba756ef68059acdfc6d0602e30 in geode's branch 
refs/heads/feature/GEODE-4685 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=13b7364 ]

GEODE-4791: turning off gradle parallel builds


> Increase gradle version from 3.5.1 to 4.51
> --
>
> Key: GEODE-4791
> URL: https://issues.apache.org/jira/browse/GEODE-4791
> Project: Geode
>  Issue Type: Improvement
>  Components: build, general
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4800) Handle relative paths for backup baseline directories

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4800:


Commit 9ac583970fae2ac115947af7b3e9b14755b71a25 in geode's branch 
refs/heads/feature/GEODE-4685 from [~nreich]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9ac5839 ]

GEODE-4800: Fix handling orf relative paths when providing backpu baseline dir 
(#1581)



> Handle relative paths for backup baseline directories
> -
>
> Key: GEODE-4800
> URL: https://issues.apache.org/jira/browse/GEODE-4800
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Nick Reich
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0, 1.6.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Backups that specify a relative path for the baseline directory for 
> incremental backups no longer function correctly: the restore script has 
> invalid paths for recovery.



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

[jira] [Commented] (GEODE-4791) Increase gradle version from 3.5.1 to 4.51

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4791:


Commit 78df32fe7a8bfe7be7595472377b660d899953fa in geode's branch 
refs/heads/feature/GEODE-4685 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=78df32f ]

GEODE-4791: Upgrading gradle from 3.5.1 to 4.5.1


> Increase gradle version from 3.5.1 to 4.51
> --
>
> Key: GEODE-4791
> URL: https://issues.apache.org/jira/browse/GEODE-4791
> Project: Geode
>  Issue Type: Improvement
>  Components: build, general
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (GEODE-4811) Add a feature-flag annotation to gfsh commands

[Patrick Rhomberg (JIRA)]

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

Patrick Rhomberg updated GEODE-4811:

Labels:   (was: pull-request-available)

> Add a feature-flag annotation to gfsh commands
> --
>
> Key: GEODE-4811
> URL: https://issues.apache.org/jira/browse/GEODE-4811
> Project: Geode
>  Issue Type: New Feature
>  Components: gfsh
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> Many gfsh commands are mutually required by each other for full 
> functionality.  For instance, {{destroy jndi-binding}} is meaningless without 
> the {{create jndi-binding}} command.
> As a developer, I would like to be able to coordinate release of multiple 
> related commands at once, across multiple commits.  A {{@FeatureFlag}} 
> annotation on gfsh command classes would be extremely useful.



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

[jira] [Updated] (GEODE-4811) Add a feature-flag annotation to gfsh commands

[Patrick Rhomberg (JIRA)]

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

Patrick Rhomberg updated GEODE-4811:

Labels: pull-request-available  (was: )

> Add a feature-flag annotation to gfsh commands
> --
>
> Key: GEODE-4811
> URL: https://issues.apache.org/jira/browse/GEODE-4811
> Project: Geode
>  Issue Type: New Feature
>  Components: gfsh
>Reporter: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>
> Many gfsh commands are mutually required by each other for full 
> functionality.  For instance, {{destroy jndi-binding}} is meaningless without 
> the {{create jndi-binding}} command.
> As a developer, I would like to be able to coordinate release of multiple 
> related commands at once, across multiple commits.  A {{@FeatureFlag}} 
> annotation on gfsh command classes would be extremely useful.



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

[jira] [Assigned] (GEODE-4811) Add a feature-flag annotation to gfsh commands

[Patrick Rhomberg (JIRA)]

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

Patrick Rhomberg reassigned GEODE-4811:
---

Assignee: Patrick Rhomberg

> Add a feature-flag annotation to gfsh commands
> --
>
> Key: GEODE-4811
> URL: https://issues.apache.org/jira/browse/GEODE-4811
> Project: Geode
>  Issue Type: New Feature
>  Components: gfsh
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>
> Many gfsh commands are mutually required by each other for full 
> functionality.  For instance, {{destroy jndi-binding}} is meaningless without 
> the {{create jndi-binding}} command.
> As a developer, I would like to be able to coordinate release of multiple 
> related commands at once, across multiple commits.  A {{@FeatureFlag}} 
> annotation on gfsh command classes would be extremely useful.



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

[jira] [Created] (GEODE-4811) Add a feature-flag annotation to gfsh commands

[Patrick Rhomberg (JIRA)]

Patrick Rhomberg created GEODE-4811:
---

 Summary: Add a feature-flag annotation to gfsh commands
 Key: GEODE-4811
 URL: https://issues.apache.org/jira/browse/GEODE-4811
 Project: Geode
  Issue Type: New Feature
  Components: gfsh
Reporter: Patrick Rhomberg


Many gfsh commands are mutually required by each other for full functionality.  
For instance, {{destroy jndi-binding}} is meaningless without the {{create 
jndi-binding}} command.

As a developer, I would like to be able to coordinate release of multiple 
related commands at once, across multiple commits.  A {{@FeatureFlag}} 
annotation on gfsh command classes would be extremely useful.



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

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

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4384:
--
Fix Version/s: 1.6.0

> 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
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 2h 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-4791) Increase gradle version from 3.5.1 to 4.51

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4791:


Commit 13b7364a7e3e09ba756ef68059acdfc6d0602e30 in geode's branch 
refs/heads/develop from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=13b7364 ]

GEODE-4791: turning off gradle parallel builds


> Increase gradle version from 3.5.1 to 4.51
> --
>
> Key: GEODE-4791
> URL: https://issues.apache.org/jira/browse/GEODE-4791
> Project: Geode
>  Issue Type: Improvement
>  Components: build, general
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




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

[jira] [Created] (GEODE-4809) Create performance test for rebalance action

[Nick Reich (JIRA)]

Nick Reich created GEODE-4809:
-

 Summary: Create performance test for rebalance action
 Key: GEODE-4809
 URL: https://issues.apache.org/jira/browse/GEODE-4809
 Project: Geode
  Issue Type: Sub-task
  Components: regions
Reporter: Nick Reich


Should allow for testing different scenarios (e.g. large cluster, disparate 
bucket sizes, level of imbalance, etc.). May wish to mock the actual actions of 
moving buckets, for example, by using sleeps based on bucket size to mimic 
network transfer of data.



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

[jira] [Created] (GEODE-4808) Add performance tests for rebalance simulation

[Nick Reich (JIRA)]

Nick Reich created GEODE-4808:
-

 Summary: Add performance tests for rebalance simulation
 Key: GEODE-4808
 URL: https://issues.apache.org/jira/browse/GEODE-4808
 Project: Geode
  Issue Type: Sub-task
  Components: regions
Reporter: Nick Reich


Create test to measure the computation overhead of rebalance.



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

[jira] [Updated] (GEODE-4772) Protobuf: add region clear message/operation

[ASF GitHub Bot (JIRA)]

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

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

> Protobuf: add region clear message/operation
> 
>
> Key: GEODE-4772
> URL: https://issues.apache.org/jira/browse/GEODE-4772
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
>
> As a dev using the new protocol, I want to be able to clear a region 
> completely.
> Add a region clear message/operation that clears a replicated region.
> GEODE-788 will implement .clear for partitioned regions - when that is 
> complete we can add support for clearing PRs.
>  
> Client should receive error if the region does not exist or the client does 
> not have authorization on the region.
>  



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

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

[Udo Kohlmeyer (JIRA)]

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

Udo Kohlmeyer reassigned GEODE-3926:


Assignee: Udo Kohlmeyer

> 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
>
> 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-4807) Pulse UI tests using locator/cluster rule.

[ASF GitHub Bot (JIRA)]

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

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

> Pulse UI tests using locator/cluster rule.
> --
>
> Key: GEODE-4807
> URL: https://issues.apache.org/jira/browse/GEODE-4807
> Project: Geode
>  Issue Type: Test
>  Components: pulse
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
>  Labels: pull-request-available
>




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

[jira] [Commented] (GEODE-4693) JDBCLoader on region with a pdx-class-name causes exception during deserialization when a get is done

[Anilkumar Gingade (JIRA)]

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

Anilkumar Gingade commented on GEODE-4693:
--

When a get is done from JDBC:
 * if the JDBC region mapping does not have a pdx-class-name, then a 
PdxInstance will be created with all object fields. This PdxInstance will never 
deserialize to a java class but will remain a PdxInstance.
 * if the JDBC region mapping does have a pdx-class-name, then the pdx type for 
that class name must exist and all the columns must have corresponding fields 
in the pdx type. If not a JdbcConnectorException will be thrown. The pdx field 
type is used to determine what JDBC ResultSet method will be called to get the 
column data as a Java object. The following shows the ResultSet method that 
corresponds to the pdx field type:
 ** boolean: getBoolean
 ** byte: getByte
 ** char: getString and then the first character of the string is used
 ** short: getShort
 ** int: getInt
 ** long: getLong
 ** float: getFloat
 ** double: getDouble
 ** Date: getTimestamp
 ** String: getString
 ** byte[]: getBytes
 ** Object: getObject
 ** boolean[]: getObject
 ** char[]: getObject
 ** short[]: getObject
 ** int[]: getObject
 ** long[]: getObject
 ** float[]: getObject
 ** double[]: getObject
 ** String[]: getObject
 ** Object[]: getObject
 ** byte[][]: getObject

When a put is done to JDBC if the pdx value has a "char" field or an "Object" 
field that contains an instance of "Character" then the actual data written to 
JDBC will be an instance of "String" that is created by calling 
"Character.toString". In previous releases the "Character" was passed directly 
to JDBC setObject which results in a SQLException. So any releases with this 
fix can now use pdx "char" fields and "Object" fields that contain an instance 
of "Character".

A new external API will be added that allows a pdx type to be registered 
without doing a region put.

 

 

> JDBCLoader on region with a pdx-class-name causes exception during 
> deserialization when a get is done
> -
>
> Key: GEODE-4693
> URL: https://issues.apache.org/jira/browse/GEODE-4693
> Project: Geode
>  Issue Type: Bug
>  Components: docs, extensions, regions
>Affects Versions: 1.4.0
>Reporter: Fred Krone
>Assignee: Anilkumar Gingade
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When Region.get() is performed with JDBCLoader and pdx-class-name, the 
> JDBCLoader always creates a PdxInstance whose fields are all of type object. 
> If the domain class has the fields as some other type, for example string or 
> int, then deserialization will fail.
> Workaround at this time is:
>  # Don't set the pdx-class-name on the jdbc region mapping. This will cause 
> deserialization to never happen since the data will remain a PdxInstance.
>  #  Have all your domain class fields serialized as pdx object fields. This 
> can be hard to do with the ReflectionBasedAutoSerializer so the 
> recommendation is to use PdxSerializable or your own PdxSerializer.
>  



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

[jira] [Updated] (GEODE-4693) JDBCLoader on region with a pdx-class-name causes exception during deserialization when a get is done

[Anilkumar Gingade (JIRA)]

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

Anilkumar Gingade updated GEODE-4693:
-
Component/s: docs

> JDBCLoader on region with a pdx-class-name causes exception during 
> deserialization when a get is done
> -
>
> Key: GEODE-4693
> URL: https://issues.apache.org/jira/browse/GEODE-4693
> Project: Geode
>  Issue Type: Bug
>  Components: docs, extensions, regions
>Affects Versions: 1.4.0
>Reporter: Fred Krone
>Assignee: Anilkumar Gingade
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When Region.get() is performed with JDBCLoader and pdx-class-name, the 
> JDBCLoader always creates a PdxInstance whose fields are all of type object. 
> If the domain class has the fields as some other type, for example string or 
> int, then deserialization will fail.
> Workaround at this time is:
>  # Don't set the pdx-class-name on the jdbc region mapping. This will cause 
> deserialization to never happen since the data will remain a PdxInstance.
>  #  Have all your domain class fields serialized as pdx object fields. This 
> can be hard to do with the ReflectionBasedAutoSerializer so the 
> recommendation is to use PdxSerializable or your own PdxSerializer.
>  



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

[jira] [Updated] (GEODE-4807) Pulse UI tests using locator/cluster rule.

[Sai Boorlagadda (JIRA)]

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

Sai Boorlagadda updated GEODE-4807:
---
Summary: Pulse UI tests using locator/cluster rule.  (was: Add pulse UI 
tests using locator/cluster rule.)

> Pulse UI tests using locator/cluster rule.
> --
>
> Key: GEODE-4807
> URL: https://issues.apache.org/jira/browse/GEODE-4807
> Project: Geode
>  Issue Type: Test
>  Components: pulse
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
>




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

[jira] [Created] (GEODE-4807) Add pulse UI tests using locator/cluster rule.

[Sai Boorlagadda (JIRA)]

Sai Boorlagadda created GEODE-4807:
--

 Summary: Add pulse UI tests using locator/cluster rule.
 Key: GEODE-4807
 URL: https://issues.apache.org/jira/browse/GEODE-4807
 Project: Geode
  Issue Type: Test
  Components: pulse
Reporter: Sai Boorlagadda






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

[jira] [Assigned] (GEODE-4807) Add pulse UI tests using locator/cluster rule.

[Sai Boorlagadda (JIRA)]

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

Sai Boorlagadda reassigned GEODE-4807:
--

Assignee: Sai Boorlagadda

> Add pulse UI tests using locator/cluster rule.
> --
>
> Key: GEODE-4807
> URL: https://issues.apache.org/jira/browse/GEODE-4807
> Project: Geode
>  Issue Type: Test
>  Components: pulse
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
>




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

[jira] [Updated] (GEODE-4806) Replace SimpleTestSecurityManager with SimpleSecurityManager

[Jens Deppe (JIRA)]

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

Jens Deppe updated GEODE-4806:
--
Labels: starter  (was: )

> Replace SimpleTestSecurityManager with SimpleSecurityManager
> 
>
> Key: GEODE-4806
> URL: https://issues.apache.org/jira/browse/GEODE-4806
> Project: Geode
>  Issue Type: Task
>  Components: security
>Reporter: Jens Deppe
>Priority: Major
>  Labels: starter
>
> These classes appear to be the same. 



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

[jira] [Created] (GEODE-4806) Replace SimpleTestSecurityManager with SimpleSecurityManager

[Jens Deppe (JIRA)]

Jens Deppe created GEODE-4806:
-

 Summary: Replace SimpleTestSecurityManager with 
SimpleSecurityManager
 Key: GEODE-4806
 URL: https://issues.apache.org/jira/browse/GEODE-4806
 Project: Geode
  Issue Type: Task
  Components: security
Reporter: Jens Deppe


These classes appear to be the same. 



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

[jira] [Resolved] (GEODE-4791) Increase gradle version from 3.5.1 to 4.51

[Udo Kohlmeyer (JIRA)]

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

Udo Kohlmeyer resolved GEODE-4791.
--
   Resolution: Fixed
Fix Version/s: 1.6.0

> Increase gradle version from 3.5.1 to 4.51
> --
>
> Key: GEODE-4791
> URL: https://issues.apache.org/jira/browse/GEODE-4791
> Project: Geode
>  Issue Type: Improvement
>  Components: build, general
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




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

[jira] [Assigned] (GEODE-4772) Protobuf: add region clear message/operation

[Michael Dodge (JIRA)]

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

Michael Dodge reassigned GEODE-4772:


Assignee: Michael Dodge

> Protobuf: add region clear message/operation
> 
>
> Key: GEODE-4772
> URL: https://issues.apache.org/jira/browse/GEODE-4772
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Michael Dodge
>Priority: Major
>
> As a dev using the new protocol, I want to be able to clear a region 
> completely.
> Add a region clear message/operation that clears a replicated region.
> GEODE-788 will implement .clear for partitioned regions - when that is 
> complete we can add support for clearing PRs.
>  
> Client should receive error if the region does not exist or the client does 
> not have authorization on the region.
>  



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

[jira] [Commented] (GEODE-4791) Increase gradle version from 3.5.1 to 4.51

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4791:


Commit 78df32fe7a8bfe7be7595472377b660d899953fa in geode's branch 
refs/heads/develop from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=78df32f ]

GEODE-4791: Upgrading gradle from 3.5.1 to 4.5.1


> Increase gradle version from 3.5.1 to 4.51
> --
>
> Key: GEODE-4791
> URL: https://issues.apache.org/jira/browse/GEODE-4791
> Project: Geode
>  Issue Type: Improvement
>  Components: build, general
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4685:


Commit f3d01827233987468bcd1f78d4aeeef3c53f88b8 in geode's branch 
refs/heads/feature/GEODE-4685 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f3d0182 ]

GEODE-4685: Moving of static DefaultQuery.setPdxReadSerialized to the 
TypeRegistry.
Cleaned up the overriding of readSerialized to reset to previous value.
Added cache to AbstractJdbcCallback.java so that children classes can access it.
Replaced AtomicLong with LongAdder.


> Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
> --
>
> Key: GEODE-4685
> URL: https://issues.apache.org/jira/browse/GEODE-4685
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: nabarun
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 5h 10m
>  Remaining Estimate: 0h
>
> Replace with the solution from GEODE-4679



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

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

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4384:


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

GEODE-4384: gfsh command to destroy jndi binding (#1568)



> 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
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 2h 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] [Resolved] (GEODE-4762) Code Cleanup: Remove dead code from o.a.g.admin, *.cache, and *.distributed.internal

[Patrick Rhomberg (JIRA)]

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

Patrick Rhomberg resolved GEODE-4762.
-
Resolution: Fixed

> Code Cleanup: Remove dead code from o.a.g.admin, *.cache, and 
> *.distributed.internal
> 
>
> Key: GEODE-4762
> URL: https://issues.apache.org/jira/browse/GEODE-4762
> Project: Geode
>  Issue Type: Improvement
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4685:


Commit 2ab498e7dd79bcf5ffe0a7df070cbc5c3b833eca in geode's branch 
refs/heads/feature/GEODE-4685 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2ab498e ]

GEODE-4685: Moving of static DefaultQuery.setPdxReadSerialized to the 
TypeRegistry.
Cleaned up the overriding of readSerialized to reset to previous value.
Added cache to AbstractJdbcCallback.java so that children classes can access it.
Replaced AtomicLong with LongAdder.


> Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
> --
>
> Key: GEODE-4685
> URL: https://issues.apache.org/jira/browse/GEODE-4685
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: nabarun
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 5h 10m
>  Remaining Estimate: 0h
>
> Replace with the solution from GEODE-4679



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

[jira] [Updated] (GEODE-4755) Jar deploy fails on Windows

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4755:
--
Fix Version/s: 1.6.0

> Jar deploy fails on Windows
> ---
>
> Key: GEODE-4755
> URL: https://issues.apache.org/jira/browse/GEODE-4755
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Fails with this exception:
> {noformat}
> java.lang.UnsupportedOperationException: 'posix:permissions' not supported as 
> initial attribute
>at 
> sun.nio.fs.WindowsSecurityDescriptor.fromAttribute(WindowsSecurityDescriptor.java:358)
>at 
> sun.nio.fs.WindowsFileSystemProvider.createDirectory(WindowsFileSystemProvider.java:492)
>at java.nio.file.Files.createDirectory(Files.java:674)
>at java.nio.file.TempFileHelper.create(TempFileHelper.java:136)
>at 
> java.nio.file.TempFileHelper.createTempDirectory(TempFileHelper.java:173)
>at java.nio.file.Files.createTempDirectory(Files.java:991)
>at 
> org.apache.geode.management.internal.beans.FileUploader.uploadFile(FileUploader.java:77)
> {noformat}
> Potential classes affected:
> {noformat}
> org.apache.geode.distributed.internal.ClusterConfigurationService
> org.apache.geode.internal.cache.ClusterConfigurationLoader
> org.apache.geode.management.internal.beans.FileUploader
> org.apache.geode.management.internal.cli.functions.DeployFunction
> org.apache.geode.management.internal.web.controllers.AbstractCommandsController
> {noformat}
> Posixness can be checked with 
> {{FileSystems.getDefault().supportedFileAttributeViews().contains(“posix”);}}



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

[jira] [Created] (GEODE-4805) Support a broad range of hostname port notations

[Swapnil Bawaskar (JIRA)]

Swapnil Bawaskar created GEODE-4805:
---

 Summary: Support a broad range of hostname port notations
 Key: GEODE-4805
 URL: https://issues.apache.org/jira/browse/GEODE-4805
 Project: Geode
  Issue Type: Bug
  Components: configuration
Reporter: Swapnil Bawaskar


In addition to hostname[port] notation, we should support hostname:port and a 
host of other notations commonly used. Here are a few commonly used examples: 
https://github.com/google/guava/blob/master/guava/src/com/google/common/net/HostAndPort.java



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

[jira] [Updated] (GEODE-4805) Support a broad range of hostname port notations

[Swapnil Bawaskar (JIRA)]

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

Swapnil Bawaskar updated GEODE-4805:

  Priority: Minor  (was: Major)
Issue Type: Improvement  (was: Bug)

> Support a broad range of hostname port notations
> 
>
> Key: GEODE-4805
> URL: https://issues.apache.org/jira/browse/GEODE-4805
> Project: Geode
>  Issue Type: Improvement
>  Components: configuration
>Reporter: Swapnil Bawaskar
>Priority: Minor
>
> In addition to hostname[port] notation, we should support hostname:port and a 
> host of other notations commonly used. Here are a few commonly used examples: 
> https://github.com/google/guava/blob/master/guava/src/com/google/common/net/HostAndPort.java



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

[jira] [Commented] (GEODE-4755) Jar deploy fails on Windows

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4755:


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

GEODE-4755: Use a more portable File permission API (#1573)

- This lets jar deployment work on Windows
- Unify creation of temporary staging directory

> Jar deploy fails on Windows
> ---
>
> Key: GEODE-4755
> URL: https://issues.apache.org/jira/browse/GEODE-4755
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Fails with this exception:
> {noformat}
> java.lang.UnsupportedOperationException: 'posix:permissions' not supported as 
> initial attribute
>at 
> sun.nio.fs.WindowsSecurityDescriptor.fromAttribute(WindowsSecurityDescriptor.java:358)
>at 
> sun.nio.fs.WindowsFileSystemProvider.createDirectory(WindowsFileSystemProvider.java:492)
>at java.nio.file.Files.createDirectory(Files.java:674)
>at java.nio.file.TempFileHelper.create(TempFileHelper.java:136)
>at 
> java.nio.file.TempFileHelper.createTempDirectory(TempFileHelper.java:173)
>at java.nio.file.Files.createTempDirectory(Files.java:991)
>at 
> org.apache.geode.management.internal.beans.FileUploader.uploadFile(FileUploader.java:77)
> {noformat}
> Potential classes affected:
> {noformat}
> org.apache.geode.distributed.internal.ClusterConfigurationService
> org.apache.geode.internal.cache.ClusterConfigurationLoader
> org.apache.geode.management.internal.beans.FileUploader
> org.apache.geode.management.internal.cli.functions.DeployFunction
> org.apache.geode.management.internal.web.controllers.AbstractCommandsController
> {noformat}
> Posixness can be checked with 
> {{FileSystems.getDefault().supportedFileAttributeViews().contains(“posix”);}}



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

[jira] [Resolved] (GEODE-4800) Handle relative paths for backup baseline directories

[Nick Reich (JIRA)]

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

Nick Reich resolved GEODE-4800.
---
   Resolution: Fixed
Fix Version/s: 1.6.0
   1.5.0

> Handle relative paths for backup baseline directories
> -
>
> Key: GEODE-4800
> URL: https://issues.apache.org/jira/browse/GEODE-4800
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Nick Reich
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0, 1.6.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Backups that specify a relative path for the baseline directory for 
> incremental backups no longer function correctly: the restore script has 
> invalid paths for recovery.



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

[jira] [Commented] (GEODE-4800) Handle relative paths for backup baseline directories

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4800:


Commit be18b0f49619070cb88befadcb0b267cbe0bcc95 in geode's branch 
refs/heads/release/1.5.0 from [~nreich]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=be18b0f ]

GEODE-4800: Fix handling orf relative paths when providing backpu baseline dir 
(#1581)

(cherry picked from commit 9ac583970fae2ac115947af7b3e9b14755b71a25)


> Handle relative paths for backup baseline directories
> -
>
> Key: GEODE-4800
> URL: https://issues.apache.org/jira/browse/GEODE-4800
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Nick Reich
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Backups that specify a relative path for the baseline directory for 
> incremental backups no longer function correctly: the restore script has 
> invalid paths for recovery.



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

[jira] [Commented] (GEODE-4800) Handle relative paths for backup baseline directories

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4800:


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

GEODE-4800: Fix handling orf relative paths when providing backpu baseline dir 
(#1581)



> Handle relative paths for backup baseline directories
> -
>
> Key: GEODE-4800
> URL: https://issues.apache.org/jira/browse/GEODE-4800
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Nick Reich
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Backups that specify a relative path for the baseline directory for 
> incremental backups no longer function correctly: the restore script has 
> invalid paths for recovery.



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

[jira] [Created] (GEODE-4804) How to install docs page

[Addison (JIRA)]

Addison created GEODE-4804:
--

 Summary: How to install docs page
 Key: GEODE-4804
 URL: https://issues.apache.org/jira/browse/GEODE-4804
 Project: Geode
  Issue Type: Sub-task
  Components: native client
Reporter: Addison


Users can see how to install the client on the following system configurations.

* Linux C++
* Solaris C++
* Windows C++
* Windows C#




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

[jira] [Commented] (GEODE-4385) gfsh command to list jndi binding

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4385:


Commit 7630dba4f75341c5658cc8dd0415fea91389bd06 in geode's branch 
refs/heads/feature/GEODE-4791 from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7630dba ]

GEODE-4385: Update help message for list jndi-binding (#1575)

- Also add ResourcePermission for the same command

> gfsh command to list jndi binding
> -
>
> Key: GEODE-4385
> URL: https://issues.apache.org/jira/browse/GEODE-4385
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Barbara Pruijn
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 50m
>  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 list a datasource using the gfsh command {{list 
> jndi-binding}}
>  Then all jndi-binding names will be displayed.
> 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-4781) Categorize Lucene tests

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4781:


Commit 1a69ddc4d1f49262570b1f2d727434bb7fc269d1 in geode's branch 
refs/heads/feature/GEODE-4791 from nabarunnag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1a69ddc ]

GEODE-4781: Converted LuceneTest to an interface


> Categorize Lucene tests
> ---
>
> Key: GEODE-4781
> URL: https://issues.apache.org/jira/browse/GEODE-4781
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: nabarun
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4787) Re-instate Management REST API endpoints for 'create index' and 'create region'

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4787:


Commit eb8f840a011f0236a94e8d5575d7401cdd654bc2 in geode's branch 
refs/heads/feature/GEODE-4791 from [~jblum]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=eb8f840 ]

GEODE-4787: Re-instate Management REST API endpoints for 'create index' and 
'create region'. (#1563)

Resolves PR #1563.

> Re-instate Management REST API endpoints for 'create index' and 'create 
> region'
> ---
>
> Key: GEODE-4787
> URL: https://issues.apache.org/jira/browse/GEODE-4787
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Affects Versions: 1.3.0, 1.4.0
>Reporter: John Blum
>Priority: Blocker
>  Labels: pull-request-available
> Attachments: ClusterConfigurationExampleIntegrationTests.java, 
> Customer.java, CustomerRepository.java
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> As of _Apache Geode_ *1.3*, Apache Geode no longer supports proper 
> (REST-like) Web service endpoints for the Geode's Management functionality.
> This primarily concerns the Management (REST-like) Web service API in 
> {{org.apache.geode.management.internal.web.controllers}}, which in Apache 
> Geode 1.2.1 and earlier, consisted of the following [Spring Web MVC 
> Cntrollers|https://github.com/apache/geode/tree/rel/v1.2.1/geode-core/src/main/java/org/apache/geode/management/internal/web/controllers].
> However, as Apache Geode 1.3 and later (i.e. 1.4 and beyond), the Apache 
> Geode community refactored and [reduced the 
> Controllers|https://github.com/apache/geode/tree/rel/v1.3.0/geode-core/src/main/java/org/apache/geode/management/internal/web/controllers],
>  and by extension, the Web service endpoints to, mostly, a [single Web 
> service 
> endpoint|https://github.com/apache/geode/blob/rel/v1.3.0/geode-core/src/main/java/org/apache/geode/management/internal/web/controllers/ShellCommandsController.java#L72-L79],
>  which essentially just accepts a _Gfsh_ command string, such as `{{create 
> region --name=Example --type=PARTITION}}`.
> This is an significant *anti-pattern* to be sure nor is it consistent with 
> good/proper Web service/general API design, much less REST-ful design.
> While this Management REST-like API was not a "complete" REST API design, as 
> measured against [Richardson Maturity 
> Model|https://martinfowler.com/articles/richardsonMaturityModel.html], it did 
> consist of elements in both Levels 1 and 2.
> For instance, it used proper URLs and URIs to identify and access resources 
> (e.g. Regions, Indexes, etc).  Additionally, it also used property Verbs to 
> affect (e.g. CRUD) the resources.
> Essentially, it only needed proper Resource abstractions representing the 
> different resources (e.g. Regions, Indexes, etc) along with Hypermedia 
> Controls to move beyond being a specific interface for _Gfsh_.
> The intent was never to make the Management REST API a specific extension for 
> _Gfsh_.  The initial purpose was to enable _Gfsh_ to connect to the Manager 
> via HTTP in order to transcend firewalls when a devops team wanted to manage 
> a remote cluster deployed in a cloud environment, such as AWS or GCP.  By 
> using HTTP over JMX/RMI, a user would not need to punch additional holes in 
> the firewall to expose the JMX/RMI port (1099) for instance.
> Still, the "intent" was never to stop at supporting just _Gfsh_, but to 
> become a true REST API that can be consumed by any client (not just _Gfsh_): 
> application, framework, tool, etc, regardless of language (e.g. Java, C++/C#, 
> Ruby, Python, etc).
> However, the team that modified this API failed to recognize the benefit of 
> this design and actually took a step backwards.  The HTTP Verbs are not 
> properly used.  The Web service API endpoints are not resourceful, and 
> imposing the _Gfsh_ DSL on clients is foolish and too restrictive.
> While, it might be argued that this was an "internal" API, technically, 
> speaking, guarding classes by putting them in an "internal" package is no 
> safe-guard or guarantee that could have been properly enforced using Java 
> access modifiers (e.g. {{private}}, {{package-protected}}, etc) and then only 
> exposing an SPI for consumption.
> The fact remains that this API was changed in an incompatible way before an 
> "alternative" solution was properly introduced.



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

[jira] [Commented] (GEODE-4788) change back the behavior of test code of getSomeKeys to ignore exceptions

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4788:


Commit cf5f83a2501877b5459c20f3ece6aafe1f6becf2 in geode's branch 
refs/heads/feature/GEODE-4791 from Xiaojian Zhou
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=cf5f83a ]

GEODE-4788: change back the behavior of test code of getSomeKeys to ignore 
exceptions. (#1564)



> change back the behavior of test code of getSomeKeys to ignore exceptions
> -
>
> Key: GEODE-4788
> URL: https://issues.apache.org/jira/browse/GEODE-4788
> Project: Geode
>  Issue Type: New Feature
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0, 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> In GEODE-2673, getSomeKeys' behavior was changed to throw exception when 
> detected some exceptions. 
> We need to change it back to ignore the exceptions as test code. 



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

[jira] [Commented] (GEODE-4766) PRCustomPartitioningDUnitTest should be in package org.apache.geode.internal.cache

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4766:


Commit 922ab8363510fea117c14376d90de765d4d5c556 in geode's branch 
refs/heads/feature/GEODE-4791 from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=922ab83 ]

GEODE-4766: move PRCustomPartitioningDUnitTest to internal.cache (#1542)



> PRCustomPartitioningDUnitTest should be in package 
> org.apache.geode.internal.cache
> --
>
> Key: GEODE-4766
> URL: https://issues.apache.org/jira/browse/GEODE-4766
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> PRCustomPartitioningDUnitTest should be in package 
> org.apache.geode.internal.cache



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

[jira] [Commented] (GEODE-4793) DUnit tests fail on Windows

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4793:


Commit 7becb7c2526b338b7cef5a73c2a3d96c1156208b in geode's branch 
refs/heads/feature/GEODE-4791 from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7becb7c ]

GEODE-4793: Ensure that Files.list() closes resources (#1572)

- This was causing some DUnits to fail on Windows.

> DUnit tests fail on Windows
> ---
>
> Key: GEODE-4793
> URL: https://issues.apache.org/jira/browse/GEODE-4793
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Various tests will fail on Windows with errors similar to the following:
> {noformat}
> [vm0] [error 2018/03/07 04:38:13.670 UTC  Connection(1)-10.32.110.121> tid=19] Error occurred while initializing 
> cluster configuration
> [vm0] java.lang.RuntimeException: Error occurred while initializing cluster 
> configuration
> [vm0] at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.getConfigurationRegion(ClusterConfigurationService.java:731)
> [vm0] at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.initSharedConfiguration(ClusterConfigurationService.java:459)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startSharedConfigurationService(InternalLocator.java:1332)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:668)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:647)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:309)
> [vm0] at 
> org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> [vm0] at 
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> [vm0] at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:78)
> [vm0] at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:59)
> [vm0] at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$1c67b668$1(ClusterStartupRule.java:157)
> [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm0] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm0] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm0] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm0] at hydra.MethExecutor.executeObject(MethExecutor.java:244)
> [vm0] at 
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
> [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm0] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm0] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm0] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm0] at 
> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:361)
> [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:200)
> [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:197)
> [vm0] at java.security.AccessController.doPrivileged(Native Method)
> [vm0] at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> [vm0] at java.security.AccessController.doPrivileged(Native Method)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> [vm0] at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm0] at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm0] at java.lang.Thread.run(Thread.java:748)
> [vm0] Caused by: java.io.IOException: Cannot create directory at 
> C:\Users\Administrator\geode\geode-core\dunit\vm0\ConfigDiskDir_locator-0
> [vm0] at 
> 

[jira] [Commented] (GEODE-4791) Increase gradle version from 3.5.1 to 4.51

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4791:


Commit 1a55a324d480bd7594e86d234660cc9a85c28470 in geode's branch 
refs/heads/feature/GEODE-4791 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1a55a32 ]

GEODE-4791: Upgrading gradle from 3.5.1 to 4.5.1


> Increase gradle version from 3.5.1 to 4.51
> --
>
> Key: GEODE-4791
> URL: https://issues.apache.org/jira/browse/GEODE-4791
> Project: Geode
>  Issue Type: Improvement
>  Components: build, general
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4777) Add UITest job to concourse develop pipeline

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4777:


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

GEODE-4777: Add UITest job to concourse develop pipeline (#1571)



> Add UITest job to concourse develop pipeline
> 
>
> Key: GEODE-4777
> URL: https://issues.apache.org/jira/browse/GEODE-4777
> Project: Geode
>  Issue Type: Task
>  Components: ci, pulse
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Add a UITest job to concourse develop pipeline to run `gradlew uiTest` to run 
> selenium tests as part of the CI pipeline.



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

[jira] [Commented] (GEODE-4217) gfsh create jdbc-connection command allows a password to be set without a user name

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4217:


Commit 18560c0c45f68601aa3cc6e6ddcaa7ba15f17be6 in geode's branch 
refs/heads/feature/GEODE-4791 from [~nreich]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=18560c0 ]

GEODE-4217: Add validation to CreateConnectionCommand (#1566)

* Do not allow creation of connection if user is null but password is not

> gfsh create jdbc-connection command  allows a password to be set without a 
> user name
> 
>
> Key: GEODE-4217
> URL: https://issues.apache.org/jira/browse/GEODE-4217
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Darrel Schneider
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The gfsh create jdbc-connection command  allows a password to be set without 
> a user name.
> If you configure a password you must also configure a user name and this 
> should be validated.



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

[jira] [Resolved] (GEODE-4793) DUnit tests fail on Windows

[Barbara Pruijn (JIRA)]

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

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

> DUnit tests fail on Windows
> ---
>
> Key: GEODE-4793
> URL: https://issues.apache.org/jira/browse/GEODE-4793
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Various tests will fail on Windows with errors similar to the following:
> {noformat}
> [vm0] [error 2018/03/07 04:38:13.670 UTC  Connection(1)-10.32.110.121> tid=19] Error occurred while initializing 
> cluster configuration
> [vm0] java.lang.RuntimeException: Error occurred while initializing cluster 
> configuration
> [vm0] at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.getConfigurationRegion(ClusterConfigurationService.java:731)
> [vm0] at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.initSharedConfiguration(ClusterConfigurationService.java:459)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startSharedConfigurationService(InternalLocator.java:1332)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:668)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:647)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:309)
> [vm0] at 
> org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> [vm0] at 
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> [vm0] at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:78)
> [vm0] at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:59)
> [vm0] at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$1c67b668$1(ClusterStartupRule.java:157)
> [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm0] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm0] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm0] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm0] at hydra.MethExecutor.executeObject(MethExecutor.java:244)
> [vm0] at 
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
> [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm0] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm0] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm0] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm0] at 
> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:361)
> [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:200)
> [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:197)
> [vm0] at java.security.AccessController.doPrivileged(Native Method)
> [vm0] at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> [vm0] at java.security.AccessController.doPrivileged(Native Method)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> [vm0] at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm0] at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm0] at java.lang.Thread.run(Thread.java:748)
> [vm0] Caused by: java.io.IOException: Cannot create directory at 
> C:\Users\Administrator\geode\geode-core\dunit\vm0\ConfigDiskDir_locator-0
> [vm0] at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.getConfigurationRegion(ClusterConfigurationService.java:699)
> [vm0] ... 33 more
> {noformat}
> The problem boils down to the use of `Files.list` which sometimes will hold 
> open a directory and prevent its cleanup between tests.



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

[jira] [Updated] (GEODE-4793) DUnit tests fail on Windows

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4793:
--
Fix Version/s: 1.6.0

> DUnit tests fail on Windows
> ---
>
> Key: GEODE-4793
> URL: https://issues.apache.org/jira/browse/GEODE-4793
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Various tests will fail on Windows with errors similar to the following:
> {noformat}
> [vm0] [error 2018/03/07 04:38:13.670 UTC  Connection(1)-10.32.110.121> tid=19] Error occurred while initializing 
> cluster configuration
> [vm0] java.lang.RuntimeException: Error occurred while initializing cluster 
> configuration
> [vm0] at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.getConfigurationRegion(ClusterConfigurationService.java:731)
> [vm0] at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.initSharedConfiguration(ClusterConfigurationService.java:459)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startSharedConfigurationService(InternalLocator.java:1332)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:668)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:647)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:309)
> [vm0] at 
> org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> [vm0] at 
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> [vm0] at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:78)
> [vm0] at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:59)
> [vm0] at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$1c67b668$1(ClusterStartupRule.java:157)
> [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm0] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm0] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm0] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm0] at hydra.MethExecutor.executeObject(MethExecutor.java:244)
> [vm0] at 
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
> [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm0] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm0] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm0] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm0] at 
> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:361)
> [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:200)
> [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:197)
> [vm0] at java.security.AccessController.doPrivileged(Native Method)
> [vm0] at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> [vm0] at java.security.AccessController.doPrivileged(Native Method)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> [vm0] at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm0] at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm0] at java.lang.Thread.run(Thread.java:748)
> [vm0] Caused by: java.io.IOException: Cannot create directory at 
> C:\Users\Administrator\geode\geode-core\dunit\vm0\ConfigDiskDir_locator-0
> [vm0] at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.getConfigurationRegion(ClusterConfigurationService.java:699)
> [vm0] ... 33 more
> {noformat}
> The problem boils down to the use of `Files.list` which sometimes will hold 
> open a directory and prevent its cleanup between tests.



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

[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4685:


Commit 10f56e3807ab5b69c4a96b972ba835ac806afdf5 in geode's branch 
refs/heads/feature/GEODE-4685 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=10f56e3 ]

GEODE-4685: Moving of static DefaultQuery.setPdxReadSerialized to the 
TypeRegistry.
Cleaned up the overriding of readSerialized to reset to previous value.
Added cache to AbstractJdbcCallback.java so that children classes can access it.
Replaced AtomicLong with LongAdder.


> Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
> --
>
> Key: GEODE-4685
> URL: https://issues.apache.org/jira/browse/GEODE-4685
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: nabarun
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 5h 10m
>  Remaining Estimate: 0h
>
> Replace with the solution from GEODE-4679



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

[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4685:


Commit 22ebbb17222ab05dd3bc707350e25acad4366ea4 in geode's branch 
refs/heads/feature/GEODE-4685 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=22ebbb1 ]

GEODE-4685: Moving of static DefaultQuery.setPdxReadSerialized to the 
TypeRegistry.
Cleaned up the overriding of readSerialized to reset to previous value.
Added cache to AbstractJdbcCallback.java so that children classes can access it.
Replaced AtomicLong with LongAdder.


> Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
> --
>
> Key: GEODE-4685
> URL: https://issues.apache.org/jira/browse/GEODE-4685
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: nabarun
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 5h 10m
>  Remaining Estimate: 0h
>
> Replace with the solution from GEODE-4679



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

[jira] [Commented] (GEODE-4385) gfsh command to list jndi binding

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4385:


Commit 7630dba4f75341c5658cc8dd0415fea91389bd06 in geode's branch 
refs/heads/feature/GEODE-4685 from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7630dba ]

GEODE-4385: Update help message for list jndi-binding (#1575)

- Also add ResourcePermission for the same command

> gfsh command to list jndi binding
> -
>
> Key: GEODE-4385
> URL: https://issues.apache.org/jira/browse/GEODE-4385
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Barbara Pruijn
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 50m
>  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 list a datasource using the gfsh command {{list 
> jndi-binding}}
>  Then all jndi-binding names will be displayed.
> 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] [Resolved] (GEODE-4786) Reconfigure sidenav and delete existing pages

[Addison (JIRA)]

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

Addison resolved GEODE-4786.

Resolution: Fixed

> Reconfigure sidenav and delete existing pages
> -
>
> Key: GEODE-4786
> URL: https://issues.apache.org/jira/browse/GEODE-4786
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Addison
>Assignee: Dave Barnes
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> I propose that we start refactoring the geode native docs from a blank 
> canvas.  This story is about deleting the existing pages and sidenav 
> structure and building out the docs, anew, one page at a time.



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

[jira] [Resolved] (GEODE-4729) Rearrange Geode Native Quickstarts and Examples

[Addison (JIRA)]

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

Addison resolved GEODE-4729.

Resolution: Fixed

> Rearrange Geode Native Quickstarts and Examples
> ---
>
> Key: GEODE-4729
> URL: https://issues.apache.org/jira/browse/GEODE-4729
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Addison
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> The goal of this ticket is to restructure the Geode Native docs to make the 
> addition of examples easier.



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

[jira] [Updated] (GEODE-4385) gfsh command to list jndi binding

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4385:
--
Component/s: docs

> gfsh command to list jndi binding
> -
>
> Key: GEODE-4385
> URL: https://issues.apache.org/jira/browse/GEODE-4385
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Barbara Pruijn
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 50m
>  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 list a datasource using the gfsh command {{list 
> jndi-binding}}
>  Then all jndi-binding names will be displayed.
> 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] [Resolved] (GEODE-4385) gfsh command to list jndi binding

[Barbara Pruijn (JIRA)]

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

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

> gfsh command to list jndi binding
> -
>
> Key: GEODE-4385
> URL: https://issues.apache.org/jira/browse/GEODE-4385
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Barbara Pruijn
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 50m
>  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 list a datasource using the gfsh command {{list 
> jndi-binding}}
>  Then all jndi-binding names will be displayed.
> 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] [Updated] (GEODE-4802) Geode cluster hung after network problems

[Eugene Nedzvetsky (JIRA)]

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

Eugene Nedzvetsky updated GEODE-4802:
-
Summary: Geode cluster hung after network problems  (was: Geode cluster 
hanged after network problems)

> Geode cluster hung after network problems
> -
>
> Key: GEODE-4802
> URL: https://issues.apache.org/jira/browse/GEODE-4802
> Project: Geode
>  Issue Type: Bug
>Reporter: Eugene Nedzvetsky
>Priority: Major
> Attachments: clumsy2.jpg, threaddump.log
>
>
> Test preparation:
>  # create file bin/server1/gemfire.properties with property 
> membership-port-range=2025-2030
>  # create file bin/server2/gemfire.propertieswith property 
> membership-port-range=2035-2040
>  # Download network problems emulator [https://jagt.github.io/clumsy]
>  # Fill field 'filtering' in Clumsy: tcp and (tcp.DstPort == 2025 or 
> tcp.DstPort == 2026 or tcp.DstPort == 2027 or tcp.DstPort == 2028 or 
> tcp.DstPort == 2029 or tcp.DstPort == 2030). Select function 'Drop' and set 
> Chance=100%. See clumsy2.jpg
> Steps to reproduce
>  # Start gfsh
>  # start locator --name=locator1
>  # start server --name=server1 --server-port=40411
>  # start server --name=server2 --server-port=40412
>  # create region --name=regionA --type=REPLICATE
>  # put --region=regionA --key="1" --value="one"
>  # Click on 'start' button in Clumsy
>  # put --region=regionA --key="1" --value="onev2"
>  # Wait *15s* and click on 'stop' in Clumsy
> Gfsh console has hung.
> bin\server1\server1.log:
> [warning 2018/03/07 18:02:50.360 PST server1  
> tid=0x4b] 15 seconds have elapsed while waiting for replies: 
>  replies from [192.168.100.109(server2:12804):2035]> on 
> 192.168.100.109(server1:14416):2045 whose current membership list is: 
> [[192.168.100.109(server2:12804):2035, 
> 192.168.100.109(locator1:15628:locator):1024, 
> 192.168.100.109(server1:14416):2045]]
> Pulse has shown 'normal' status for both servers.
> Gfsh works again if server1 process was killed.
> Also  i've reproduced another issue with the same scenario on my test 
> environment(see [^threaddump.log])
>  



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

[jira] [Updated] (GEODE-4385) gfsh command to list jndi binding

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4385:
--
Fix Version/s: 1.6.0

> gfsh command to list jndi binding
> -
>
> Key: GEODE-4385
> URL: https://issues.apache.org/jira/browse/GEODE-4385
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Barbara Pruijn
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 50m
>  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 list a datasource using the gfsh command {{list 
> jndi-binding}}
>  Then all jndi-binding names will be displayed.
> 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] [Updated] (GEODE-4803) CI: ConcurrentDeployDUnitTest needs tuning

[Kenneth Howe (JIRA)]

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

Kenneth Howe updated GEODE-4803:

Affects Version/s: 1.5.0
   Labels: ci  (was: )
  Description: 
The test concurrently runs iterations of gfsh commands to deploy and undeploy 
.jar's from 3 gfsh clients to the same server, then waits up to 5 minutes for 
the gfsh clients to finish. Sometimes in the CI pipelines one or more of the 
clients don't complete their iterations within the 5 minute wait.

Test timing and/or client iterations needs to be adjusted for variations in 
machine and network speed.

Also see GEODE-800.

  was:
The test concurrently runs iterations of gfsh commands to deploy and undeploy 
.jar's from 3 gfsh clients to the same server, then waits up to 5 minutes for 
the gfsh clients to finish. Sometimes in the CI pipelines one or more of the 
clients don't complete their iterations within the 5 minute wait.

Test timing and/or client iterations needs to be adjusted for variations in 
machine and network speed.


> CI: ConcurrentDeployDUnitTest needs tuning
> --
>
> Key: GEODE-4803
> URL: https://issues.apache.org/jira/browse/GEODE-4803
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.5.0
>Reporter: Kenneth Howe
>Priority: Major
>  Labels: ci
>
> The test concurrently runs iterations of gfsh commands to deploy and undeploy 
> .jar's from 3 gfsh clients to the same server, then waits up to 5 minutes for 
> the gfsh clients to finish. Sometimes in the CI pipelines one or more of the 
> clients don't complete their iterations within the 5 minute wait.
> Test timing and/or client iterations needs to be adjusted for variations in 
> machine and network speed.
> Also see GEODE-800.



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

[jira] [Created] (GEODE-4803) CI: ConcurrentDeployDUnitTest needs tuning

[Kenneth Howe (JIRA)]

Kenneth Howe created GEODE-4803:
---

 Summary: CI: ConcurrentDeployDUnitTest needs tuning
 Key: GEODE-4803
 URL: https://issues.apache.org/jira/browse/GEODE-4803
 Project: Geode
  Issue Type: Bug
  Components: gfsh
Reporter: Kenneth Howe


The test concurrently runs iterations of gfsh commands to deploy and undeploy 
.jar's from 3 gfsh clients to the same server, then waits up to 5 minutes for 
the gfsh clients to finish. Sometimes in the CI pipelines one or more of the 
clients don't complete their iterations within the 5 minute wait.

Test timing and/or client iterations needs to be adjusted for variations in 
machine and network speed.



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