[FALCON-1145] Changing entity name if it exceeds defined length

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.6.1
• Component/s: merlin

Environment

QA

• Assignee: Pragya Mittal
• Reporter: Pragya Mittal
• Created: 08/Apr/15 13:49
• Updated: 18/Jun/15 14:49
• Resolved: 15/Apr/15 09:06

Description

If oozie uses embedded database then in some cases while entering a new row in database it may exceed the specified limit(255) for varchar. This is happening due to very long class name which is appended as part of entity name. So user can drop the class name from entity name, so that there is no truncation error.

Caused by: <openjpa-2.2.2-r422266:1468616 fatal general error> org.apache.openjpa.persistence.PersistenceException: A truncation error was encountered trying to shrink VARCHAR 'hdfs://192.168.138.200:8020/tmp/falcon-regression-staging/fa&' to length 255. {prepstmnt 505661111 INSERT INTO COORD_JOBS (id, app_name, app_namespace, app_path, bundle_id, concurrency, conf, created_time, done_materialization, end_time, execution, external_id, frequency, group_name, job_xml, last_action_number, last_action, last_modified_time, mat_throttling, next_matd_time, orig_job_xml, pause_time, pending, sla_xml, start_time, status, suspended_time, time_out, time_unit, time_zone, user_name) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)} [code=20000, state=22001]
FailedObject: org.apache.oozie.CoordinatorJobBean@1b9a4027

For this is_deprecate flag is introduced which is 'false' by default.

Issue Links

• breaks: FALCON-1284 Fix entity cleanup when is_depracate=true