This is an automated email from the ASF dual-hosted git repository.
udo pushed a change to branch feature/GEODE-3637
in repository https://gitbox.apache.org/repos/asf/geode.git.
discard 849d2fd GEODE-3637: Revert changes to client queue initialization
add 01dc11f GEODE-3953: Incorrect use of .equals() for comparison of
fieldname arrays GEODE-3954: Misleading Exception message with mismatched
fieldAnalyzers
add f53bdf0 GEODE-3637: Revert changes to client queue initialization
new 0187e8c GEODE-3637: Reimplement client queue initialization. Adding
shutdown logic
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (849d2fd)
\
N -- N -- N refs/heads/feature/GEODE-3637 (0187e8c)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../internal/cache/tier/sockets/AcceptorImpl.java | 314 ++++++++++++---------
.../cache/tier/sockets/ServerConnection.java | 51 ++--
.../sockets/AcceptorImplClientQueueDUnitTest.java | 263 +++++++++++++++++
.../apache/geode/test/dunit/rules/CacheRule.java | 22 +-
.../internal/LuceneIndexCreationProfile.java | 9 +-
.../LuceneIndexCreationProfileJUnitTest.java | 7 +
6 files changed, 505 insertions(+), 161 deletions(-)
create mode 100644
geode-core/src/test/java/org/apache/geode/internal/cache/tier/sockets/AcceptorImplClientQueueDUnitTest.java
--
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].
