Closed weilu closed 7 years ago
Okay, this is due to my outdated version of botocore==1.4.62. Upgrading to 1.5.26 fixed it. Apparently that version of botocore is horribly broken in many ways. Can the bad version be unpublished or marked bad on pypi?
I'm glad that you were able to get this to work! We don't remove releases from PyPI because that would break people who are currently using that version successfully despite its flaws.
I'm using boto3 (version 1.4.4) to talk to Kinesis:
When I test it with any data without the
\x
escape I'm able to get back the record as expected. boto3's doc says that "The data blob can be any type of data; for example, a segment from a log file, geographic/location data, website clickstream data, and so on." then why is the message with\x
escaped characters dropped? Am I expected to'\x08'.encode('string_escape')
before sending the data to kinesis?I have characters like
\x08
in the message data because I'm trying to write a serialized protocol buffer message to a Kinesis stream.