Kinesis record reading: thawing non-nippy data about amazonica HOT 4 CLOSED

Yeah, I guess I assumed if you were using clojure to read from kinesis that you were putting the records into kinesis from clojure, in which case they'd be nippy frozen. Bad assumption. I'll parameterize the unwrap function.

from amazonica.

The fix version is on Clojars. If you want control over serialization and deserialization, you can pass a nio.ByteBuffer to calls to (put-record), in which case it won't be nippy/frozen, and supply a :deserializer function to (get-records) or (worker!) calls, which will the nio.ByteBuffer as their only arg and can return anything, which will be available under the :data key, same as before. I think that should work for your case, no?

from amazonica.

Michael, thank you. This sounds great! It is not likely I will have a chance to test it until Feb 3, but it does seem exactly what we needed in our scenario.

On Sat, Jan 25, 2014 at 1:36 PM, Michael Cohen [email protected]
wrote:

The fix version is on Clojars. If you want control over serialization and deserialization, you can pass a nio.ByteBuffer to calls to (put-record), in which case it won't be nippy/frozen, and supply a :deserializer function to (get-records) or (worker!) calls, which will the nio.ByteBuffer as their only arg and can return anything, which will be available under the :data key, same as before. I think that should work for your case, no?

Reply to this email directly or view it on GitHub:
#36 (comment)

from amazonica.

Thank you, @mcohen01

Fixed by c50213f.

from amazonica.