mccraigmccraig of the clan mccraig

hi mat, i have some issues : - JSON serializing is client dependent : there are a whole bunch of different JSON libs, and cascading-cassandra shouldn't force any specific one...

tho maybe @ifesdjeen knows the cascading mechanics better than i do, and is happy with the change, in which case i'm happy to defer to his superior knowledge :)

sounds like a good deal to me :)

the special meaning of 0 for sources doesn't matter if we only set the value to 0 when sinking getSourceModified() does not appear to be called at all for me...

we can probably stop using a forked version of cassandra now... my fix was accepted into c_1.2 branch, and i think is in 1.2._ releases >= 1.2.10 i 'll check...

hmm... it def doesn't always prevent sinking to c\* ... i've sunk lots of data and never encountered this prob i wonder under which circs it skips and which it...

great ! so maybe cascalog is doing something which mitigates the prob, hence i never see it i'll look at a patch on monday On 6 Sep 2013, at 18:09,...

we ([yapster](https://yapster.info)) are using aleph via [juxt/yada](https://github.com/juxt/yada) we have an http rest/json api, and also use websockets quite a lot. we do multipart upload with the implementation that yada provides....

that would make sense... should an error not propagate though ?

tho i guess there is no way to propagate an error out if the stack has overflowed... could it log something ?