[AMBARI-8379] Falcon lineage needs changes to startup.properties

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.7.0
• Fix Version/s: 1.7.0
• Component/s: ambari-server
• Assignee: Alejandro Fernandez
• Reporter: Alejandro Fernandez
• Created: 19/Nov/14 00:01
• Updated: 19/Nov/14 20:57
• Resolved: 19/Nov/14 19:59

Description

Summary of changes needed and implications

changes in falcon/conf/startup.properties:

1) For Falcon lineage to work below changes are needed on Ambari deployed configs for Falcon
Implications : Lineage feature of Falcon is blocked without these changes

MetadataMappingService is required for lineage:

*.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
                        org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
                        org.apache.falcon.service.ProcessSubscriberService,\
                        org.apache.falcon.entity.store.ConfigurationStore,\
                        org.apache.falcon.rerun.service.RetryService,\
			org.apache.falcon.rerun.service.LateRunService,\
		        org.apache.falcon.service.LogCleanupService,\
                        org.apache.falcon.metadata.MetadataMappingService

######### Graph Database Properties #########
# Graph implementation
*.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory

# Graph Storage
*.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
*.falcon.graph.storage.backend=berkeleyje
*.falcon.graph.serialize.path=/grid/0/data/lineage
*.falcon.graph.preserve.history=false

The properties that need a directory in the local file system should detect a mount point that is available on the Falcon server, and the python scripts need to crease these directories when the Falcon service is configured.

The folder permission are,
owner:falcon user
group:hadoop
permissions:775

Issue Links

• links to: Code Review for additional fix
• links to: Code Review patch