Update record timestamp in MockProducer

[gowthamgutha]

The timestamp in the callback is returning -1. It should rather return the timestamp in the ProducerRecord object if available or return NO_TIMESTAMP if not available.

More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.

Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.

Committer Checklist (excluded from commit message)

• Verify design and implementation
• Verify test coverage and CI build status
• Verify documentation (including upgrade notes)

[bbejeck]

Thanks, @gowthamgutha this change makes sense to me.
However, the ProducerRecord#timestamp field is a Long object and the check record.timestamp() == 0 is causing a NullPointerException in the MockProducerTest.
Maybe you can expand the check to something like (record.timestamp() == null || record.timestamp() == 0) ?

[gowthamgutha]

Thanks, @gowthamgutha this change makes sense to me.
However, the ProducerRecord#timestamp field is a Long object and the check record.timestamp() == 0 is causing a NullPointerException in the MockProducerTest.
Maybe you can expand the check to something like (record.timestamp() == null || record.timestamp() == 0) ?

Thanks for the reply. I updated the PR.