[ https://issues.apache.org/jira/browse/SLIDER-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492312#comment-14492312 ]
Ted Yu commented on SLIDER-773: ------------------------------- Went through the above attachment - looks fine to me. > Add co-processor support for app packages > ----------------------------------------- > > Key: SLIDER-773 > URL: https://issues.apache.org/jira/browse/SLIDER-773 > Project: Slider > Issue Type: Bug > Components: app-package, client > Affects Versions: Slider 0.60 > Reporter: Sumit Mohanty > Assignee: thomas liu > Priority: Critical > Fix For: Slider 0.80 > > Attachments: 773-suggest.txt, Co-processorSupport.pdf, > coprocessor-after.patch, coprocessor-apri-4th.patch, coprocessor.patch, > coprocessor.patch > > > It is typical for applications to allow plugins/co-processors that are > essentially a set of additional jar files in the classpath and optionally a > set of config files or config changes. > Current, slider app packages can handle additional config changes/entries > very well. Additional configs files can be added as well but it is not easy > if the config files include parameters that need to be resolved by the agent. > This requires app package changes. Dropping additional jar files into the > class path is not easy and requires app package changes. > It is not efficient to modify the app package to support such plugins. App > packaging and create command should be modified such that the user can > dynamically specify additional jars, config files, configs etc. > Specific scenarios are modifying HBase to add support for Phoenix or Ranger. -- This message was sent by Atlassian JIRA (v6.3.4#6332)