Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

please expose "ApproximateArrivalTimestamp" via JsonFriendlyRecord #85

Closed
zdjohn opened this issue Jul 1, 2016 · 5 comments
Closed

Comments

@zdjohn
Copy link
Contributor

zdjohn commented Jul 1, 2016

Even though ApproximateArrivalTimestamp is becoming available in Record. However it is not exposed in JsonFriendlyRecord.
This means "ApproximateArrivalTimestamp" is not exposed to anyone who uses KCL and use ProcessRecordsMessage to consume Kinesis Stream. (e.g. .Net developers like me)

The fix is relative simple, and I am happy to provide PR for it.

PS: https://github.com/awslabs/amazon-kinesis-client-net is over a year old, is there any plan on that regards?

@pfifer
Copy link
Contributor

pfifer commented Jul 8, 2016

Thanks for the feedback and the PR. We want to get all of the MultiLanguageDaemon clients up to date with the latest release of the Kinesis Client. We should be able to add the approximateArrivalTimestamp as part of the updates.

The PR looks pretty straight forward, and I will look into merging it. This will also require updating the other clients to expose the property as well.

@zdjohn
Copy link
Contributor Author

zdjohn commented Jul 11, 2016

@pfifer awesome thanks!

@pfifer
Copy link
Contributor

pfifer commented Aug 3, 2016

I've merged the PR. I'm looking into adding support for the other languages, but I don't have a timeline on that right now.

@pfifer
Copy link
Contributor

pfifer commented Jan 5, 2017

Support for the field is now available, but there are steps required to update the clients. Currently the Python client has been updated to use the new functionality, and we're investigating updating the remainder of the clients.

@pfifer
Copy link
Contributor

pfifer commented Jan 23, 2017

I created a issue to track adding the new features to the .NET client. I'm going to close this for now, please feel free to reopen if you have more questions.

@pfifer pfifer closed this as completed Jan 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants