Description
"oozie sla -len 10000000" caused OOM in Y! setting.
this jira to do following
1) use JDBCFetchPlan to reduce memory usage in SLAEventsGetJPAExecutor
-just like we are doing for "oozie jobs" command
2) enforce max cap(say, 1000) in -len parameter that user sets
-need documentation change to notify user