opentelemetry-collector-contrib
opentelemetry-collector-contrib copied to clipboard
[receiver/fluentforward] Add case to handle uint64 timestamp
Link to tracking Issue: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/11435
The committers listed above are authorized under a signed CLA.
- :white_check_mark: login: bhogayatakb / name: Keval Bhogayata (78a501305a2b82eb860f1ecc31aebc379dc0232c)
Lint errors, please fix
@bogdandrutu Linting applied & Commit Ammended
Let me know if there is anything I can do for the failing checks, @bogdandrutu @dmitryax
@bhogayatakb can you please add a changelog entry and a test case?
There was a testcase expecting uint to be an invalid type. As we are considering uint as a valid type for timestamp - this testcase should no longer be relevant, right ? [Refer the file changes - receiver/fluentforwardreceiver/conversion_test.go]
@dmitryax added changelog entry and made changes in test cases, there is a failing check regarding integration test for rabbitmq, should I be making any changes to pass that test ?
@dmitryax @bogdandrutu checks passed, is it good to go ?