Falcon uses Oozie as its workflow engine and Oozie has a 255 char limit on the length of path of workflow/coordinator/bundle files. This limit occurs because oozie stores the path in a OpenJPA database which has 255 char limit for this column.
Instead of failing with a hard to understand error during run time, it makes sense for Falcon to check the length of path and throw a more useful exception when an entity is scheduled.
I propose adding a property to runtime.properties. This way, when Oozie changes the limit, falcon can update limit without code changes