heesung-sn commented on code in PR #15264:
URL: https://github.com/apache/pulsar/pull/15264#discussion_r858929007
##########
tests/integration/src/test/java/org/apache/pulsar/tests/integration/io/sinks/KinesisSinkTester.java:
##########
@@ -189,38 +194,56 @@ private void internalValidateSinkResult(Map<String,
String> kvs) {
Map<String, String> actualKvs = new LinkedHashMap<>();
- // millisBehindLatest equals zero when record processing is caught up,
- // and there are no new records to process at this moment.
- // See
https://docs.aws.amazon.com/kinesis/latest/APIReference/API_GetRecords.html#Streams-GetRecords-response-MillisBehindLatest
- Awaitility.await().until(() ->
addMoreRecordsAndGetMillisBehindLatest(actualKvs, iterator) == 0);
+ addMoreRecords(actualKvs, iterator);
Review Comment:
I think this is related to this pull.
It seems like the java17 compiled KinesisSink code saves more cpu cycles
than before and changed the initial KPL behavior - now we can see the KPL
default record aggregation in this test, which was not covered in the original
test.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
