[ 
https://issues.apache.org/jira/browse/APEXCORE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152342#comment-15152342
 ] 

Munagala V. Ramanath commented on APEXCORE-331:
-----------------------------------------------

Suggest replacing:
{quote}
      Apache  Apex  command line interface, can be used to launch, monitor, and 
manage Apache Apex
       applications. apex is a wrapper around the REST API provided by  
dtGatway,  and  provides  a
       developer  friendly  way  of  interacting  with Apache Apex platform. 
The CLI enables a much
       higher level of feature set by hiding deep details of REST API. Another  
advantage  of  apex
       CLI  is  to  provide  scope,  by  connecting and executing commands in a 
context of specific
       application. apex CLI enables easy integration with existing enterprise  
toolset  for  auto‐
       mated  application  monitoring and management.
{quote}
with:
{quote}
      Apache  Apex  command line interface can be used to launch, monitor, and 
manage Apache Apex
       applications. It enables easy integration with existing enterprise  
toolsets  for  automated   
      application  monitoring and management.
{quote}


> Add Apex as component to Apache Bigtop
> --------------------------------------
>
>                 Key: APEXCORE-331
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-331
>             Project: Apache Apex Core
>          Issue Type: Task
>            Reporter: Chinmay Kolhatkar
>            Assignee: Chinmay Kolhatkar
>         Attachments: apex.1
>
>
> Apache Bigtop is the packaging system for the Apache big data ecosystem. 
> Several Hadoop distros use it, most recently EMR. In the future this will be 
> a good foundation to create Docker containers and for deployment automation 
> overall. 
> There will also be a secondary objective to develop Apex smoke tests, which 
> we probably can leverage for our ODP contribution also.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to