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

Add support for Amazon Timestream Write API #1857

Open
wants to merge 10 commits into
base: master
Choose a base branch
from

Conversation

alex-berger
Copy link
Contributor

This PR adds support for Amazon Timestream Write API enabling rusoto clients to write metrics data to Amazon Timestream and to manage Amazon Timestream databases and tables. In order to add Timestream service I also had to bump botocore to version 1.19.12.

Note, I failed to also add support for Amazon Timestream Query API, because that API's generated code will not compile due to recursive types.

alex-berger and others added 9 commits November 6, 2020 10:51
…ithout this fix newest botocore service code did not compile for "json" and "rest-json" protocol based services with timestamp headers as it correctly generated f64 fields in the structs, but tried to parse them as String.
…Note, I had to skip the Timestream query service as it fails to compile due to recursive types in the generated code.
…Why are those single space characters in the generated code as generated on the test system but not in the one generated on my machine. I am using the same version for Rust stable and rustfmt as the test does (rustfmt 1.4.20-stable (48f6c32e 2020-08-09)).
Rollup Timestream Query API support into existing PR
@johansmitsnl
Copy link

Any chance that this PR will get accepted?

@johansmitsnl johansmitsnl mentioned this pull request Mar 15, 2021
2 tasks
@johansmitsnl
Copy link

I have opened up a new PR #1918 that is based on the 0.46 release with new Tokio support.

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

Successfully merging this pull request may close these issues.

None yet

3 participants