Hi, I was looking at the new sharelib stuff, and I’m wondering what the story is when switching from the old version to the new timestamped version. If I had an existing sharelib from an older Oozie, then when I run the oozie-setup.sh sharelib create tool, it results in this:
# sudo -u oozie hadoop fs -ls share/lib Found 10 items drwxr-xr-x - oozie oozie 0 2013-11-18 17:32 share/lib/distcp drwxr-xr-x - oozie oozie 0 2013-11-18 17:32 share/lib/hcatalog drwxr-xr-x - oozie oozie 0 2013-11-18 17:32 share/lib/hive drwxr-xr-x - oozie oozie 0 2013-11-18 17:35 share/lib/lib_20131118173502 drwxr-xr-x - oozie oozie 0 2013-11-18 17:33 share/lib/mapreduce-streaming drwxr-xr-x - oozie oozie 0 2013-11-18 17:33 share/lib/oozie drwxr-xr-x - oozie oozie 0 2013-11-18 17:33 share/lib/pig -rw-r--r-- 3 oozie oozie 1365 2013-11-18 17:33 share/lib/sharelib.properties drwxr-xr-x - oozie oozie 0 2013-11-18 17:33 share/lib/sqoop I haven’t tested it, but I assume that the old directories (e.g. share/lib/pig), will never get cleaned up by Oozie because its only looking for the prefixes when purging, right? Would it make sense to simply delete anything that doesn’t have the “lib_” or “launcher_” prefix? The only issues I see with that are that (a) someone could have put other files/dirs in share/lib and (b) it won’t catch files/dirs that happen to have those prefixes (e.g. “share/lib/lib_mystuff”). I think those two cases are ok because the user shouldn’t be putting other stuff in /user/oozie/share/lib anyway. Thoughts? thanks - Robert
