[Systers-dev] Setting isolation level in storm

[kanika vats]

Hi Andy,
I got to know that there's a general expectation in Storm that you will be
using serializable isolation, so you'll probably want to be a bit careful if
you use something other than that.I do not have much knowledge about
isolation level but as far as i can see from the code at DlistUtils.py we
are setting the isolation level to autocommit when we create the database
and later restore it to old_isolation_level... what is the default isolation
level that is stored in old_iso_lvl??

Also please look into the matter as we can run into some strange unkown
cosequences while using other isolation level in storm.What I got to know
was :

 "You need to be aware that Storm does caching and invalidates the
cache on transaction boundaries (once you do commit() or rollback(),
for instance).  This works perfectly when using "serializable-style"
isolation levels, since the database and the cache will represent the
same data.  If you change the isolation level, the caching on the
Storm side will *still* happen, and will continue to be invalidated on
transaction boundaries by default, so it's very important to keep this
in mind when coding if you don't want to be surprised."

Please let me know on what you think about this.Can it create any
problems,if so how can we deal with them?

-- 
Best Regards
Kanika Vats