Storm's transaction and caching semantics rely on a database which is providing SERIALIZABLE isolation. Setting it to something else (or allowing the default to be something else) can invalidate the basic recommended way that Storm is used, and should only be done by people who really know what they're doing. Therefore, I don't think this should be merged.
Storm's transaction and caching semantics rely on a database which is providing SERIALIZABLE isolation. Setting it to something else (or allowing the default to be something else) can invalidate the basic recommended way that Storm is used, and should only be done by people who really know what they're doing. Therefore, I don't think this should be merged.