Skip to content
This repository has been archived by the owner. It is now read-only.
Permalink
Browse files
FALCON-2032 Update the extension documentation to add ExtensionServic…
…e before ConfigurationStore in startup properties

Author: Sowmya Ramesh <sramesh@hortonworks.com>

Reviewers: Balu Vellanki <balu@apache.org>

Closes #186 from sowmyaramesh/FALCON-2032

(cherry picked from commit df10d5a)
Signed-off-by: Sowmya Ramesh <sramesh@hortonworks.com>
  • Loading branch information
Sowmya Ramesh authored and sowmyaramesh committed Jun 16, 2016
1 parent 11ca2a0 commit b2e1296bdabdc58c104a2858aef483719cf5bc42
Show file tree
Hide file tree
Showing 4 changed files with 9 additions and 7 deletions.
@@ -34,6 +34,7 @@
*.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
org.apache.falcon.workflow.WorkflowJobEndNotificationService, \
org.apache.falcon.service.ProcessSubscriberService,\
org.apache.falcon.extensions.ExtensionService,\
org.apache.falcon.service.FeedSLAMonitoringService,\
org.apache.falcon.service.LifecyclePolicyMap,\
org.apache.falcon.entity.store.ConfigurationStore,\
@@ -43,8 +44,7 @@
org.apache.falcon.service.LogCleanupService,\
org.apache.falcon.service.GroupsService,\
org.apache.falcon.service.ProxyUserService,\
org.apache.falcon.service.FalconJPAService,\
org.apache.falcon.extensions.ExtensionService
org.apache.falcon.service.FalconJPAService
##Add if you want to send data to graphite
# org.apache.falcon.metrics.MetricNotificationService\
## Add if you want to use Falcon Azure integration ##
@@ -53,12 +53,13 @@ config name: *.application.services
config value: org.apache.falcon.extensions.ExtensionService
</verbatim>

ExtensionService should be added before ConfigurationStore in startup properties for application services configuration.
For manual installation user is expected to update "extension.store.uri" property defined in startup properties with
HDFS path where the extension artifacts will be copied to.
Extension artifacts in addons/extensions are packaged in falcon. For manual installation once the Falcon Server is setup user is expected to copy the extension artifacts under {falcon-server-dir}/extensions to HDFS at "extension.store.uri" path defined in startup properties and then restart Falcon.

---++ Migration
Recipes framework and HDFS mirroring capability was added in Apache Falcon 0.6.0 release and it was client side logic. With 0.10 release its moved to server side and renamed as server side extensions. Client side recipes only had CLI support and expected certain pre steps to get it working. This is no longer required in 0.10 release as new CLI and REST API support has been provided.

If user is migrating to 0.10 release and above then old Recipe setup and CLI's won't work. For manual installation user is expected to copy Extension artifacts to HDFS. Please refer "Packaging and installation" section above for more details.
Migrating to 0.10 release and above is not backward compatible for Recipes. If user is migrating to 0.10 release and above then old Recipe setup and CLI's won't work. For manual installation user is expected to copy Extension artifacts to HDFS. Please refer "Packaging and installation" section above for more details.
Please Refer to [[falconcli/FalconCLI][Falcon CLI]] and [[restapi/ResourceList][REST API]] for more details on usage of CLI and REST API's for extension jobs and instances management.
@@ -42,15 +42,16 @@
*.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
org.apache.falcon.workflow.WorkflowJobEndNotificationService, \
org.apache.falcon.service.ProcessSubscriberService,\
org.apache.falcon.extensions.ExtensionService,\
org.apache.falcon.service.LifecyclePolicyMap,\
org.apache.falcon.entity.store.ConfigurationStore,\
org.apache.falcon.rerun.service.RetryService,\
org.apache.falcon.rerun.service.LateRunService,\
org.apache.falcon.metadata.MetadataMappingService,\
org.apache.falcon.service.LogCleanupService,\
org.apache.falcon.service.GroupsService,\
org.apache.falcon.service.ProxyUserService,\
org.apache.falcon.extensions.ExtensionService
org.apache.falcon.service.ProxyUserService

##For feed SLA monitoring enable these two
# org.apache.falcon.service.FalconJPAService,\
# org.apache.falcon.service.FeedSLAMonitoringService,\
@@ -32,6 +32,7 @@
*.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
org.apache.falcon.workflow.WorkflowJobEndNotificationService, \
org.apache.falcon.service.ProcessSubscriberService,\
org.apache.falcon.extensions.ExtensionService,\
org.apache.falcon.service.FalconJPAService,\
org.apache.falcon.entity.store.ConfigurationStore,\
org.apache.falcon.rerun.service.RetryService,\
@@ -42,8 +43,7 @@
org.apache.falcon.notification.service.impl.SchedulerService,\
org.apache.falcon.notification.service.impl.AlarmService,\
org.apache.falcon.notification.service.impl.DataAvailabilityService,\
org.apache.falcon.execution.FalconExecutionService,\
org.apache.falcon.extensions.ExtensionService
org.apache.falcon.execution.FalconExecutionService

##### Falcon Configuration Store Change listeners #####
*.configstore.listeners=org.apache.falcon.entity.v0.EntityGraph,\

0 comments on commit b2e1296

Please sign in to comment.