[
https://issues.apache.org/jira/browse/GEODE-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17210549#comment-17210549
]
ASF GitHub Bot commented on GEODE-7845:
---------------------------------------
mhansonp commented on pull request #5577:
URL: https://github.com/apache/geode/pull/5577#issuecomment-705903342
@jujoramos @jinmeiliao
> @mhansonp: just FYI, I have an old
[PR](https://github.com/apache/geode/pull/5393) opened (draft as the feature is
not yet implemented) to test the backward compatibility of the `clear`
operation, it might be useful for your current work.
I looked at the Juan's code and it looked like the code I really needed (the
core of the tests) had not been implemented yet, so it was not as much help as
I hoped.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Rollingupgrade should not conflict with the new ClearPRMessage
> ---------------------------------------------------------------
>
> Key: GEODE-7845
> URL: https://issues.apache.org/jira/browse/GEODE-7845
> Project: Geode
> Issue Type: Improvement
> Components: core
> Reporter: Xiaojian Zhou
> Assignee: Mark Hanson
> Priority: Major
> Labels: GeodeCommons, pull-request-available
>
> PartitionedRegion clear introduced a new ClearPRMessage. In case of doing
> rolling upgrade, the user called PR.clear. The new ClearPRMessage should not
> fail. It should not be sent to the old members.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
