This is an automated email from the ASF dual-hosted git repository.

vvcephei pushed a change to branch kafka-10866-consumerrecords-metadata
in repository https://gitbox.apache.org/repos/asf/kafka.git.


 discard bb23614  guard against early long-poll return due to metadata-only 
response
 discard 2b5152c  CR feedback
 discard 5a24339  drop beginningOffset from the metadata
 discard 61bcf71  Rollback consumer-side metadata caching
 discard a94e635  Consumer changes to cope with cached metadata response
 discard 0b61ece  spotbugs
 discard 9e91dc5  fix test
 discard 2df2bf2  fix core integration test failures
 discard 57ede1a  tests
 discard b6aba4d  KAFKA-10866: Add fetched metadata to ConsumerRecords
     add 35b1e76  KAFKA-10793: move handling of FindCoordinatorFuture to fix 
race condition (#9671)
     add c830bce  MINOR: Fix meaningless message in assertNull validation 
(#9965)
     add 4075a5c  MINOR: Call logSegments.toBuffer only when required (#9971)
     add 91c504c  KAFKA-12233: Align the length passed to FileChannel by 
`FileRecords.writeTo` (#9970)
     add fc68c0f  MINOR: Remove redundant apostrophe in doc (#9976)
     add 8bdab2e  MINOR: Remove outdated comment in Connect's WorkerCoordinator 
(#9805)
     add fb6c7be  MINOR: Remove redundant casting and if condition from 
ConnectSchema (#9959)
     add 5cf9cfc  MINOR: Update zookeeper to 3.5.9 (#9977)
     add f4983f4  KAFKA-8930: MirrorMaker v2 documentation (#324) (#9983)
     add bd990ab  KAFKA-10866: Add fetched metadata to ConsumerRecords
     add 2b0f202  tests
     add c75b94e  fix core integration test failures
     add b0fde7c  fix test
     add b4d2b0d  spotbugs
     add 9502a9c  Consumer changes to cope with cached metadata response
     add cb61e58  Rollback consumer-side metadata caching
     add 3fd6831  drop beginningOffset from the metadata
     add fd952b8  CR feedback
     add fc3ec40  guard against early long-poll return due to metadata-only 
response

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   (bb23614)
            \
             N -- N -- N   refs/heads/kafka-10866-consumerrecords-metadata 
(fc3ec40)

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.

No new revisions were added by this update.

Summary of changes:
 .../kafka/clients/consumer/ConsumerConfig.java     |   2 +-
 .../consumer/internals/AbstractCoordinator.java    |  59 ++-
 .../apache/kafka/common/config/SaslConfigs.java    |   2 +-
 .../apache/kafka/common/record/FileRecords.java    |   2 +-
 .../kafka/common/record/FileRecordsTest.java       |  23 +
 .../apache/kafka/connect/data/ConnectSchema.java   |  46 +-
 .../runtime/distributed/WorkerCoordinator.java     |   3 -
 .../runtime/distributed/WorkerCoordinatorTest.java |  16 +-
 core/src/main/scala/kafka/log/Log.scala            |   6 +-
 docs/ops.html                                      | 583 ++++++++++++++++++++-
 docs/toc.html                                      |  20 +-
 gradle/dependencies.gradle                         |   2 +-
 .../state/internals/AbstractKeyValueStoreTest.java |   2 +-
 13 files changed, 673 insertions(+), 93 deletions(-)

Reply via email to