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

Hitesh Shah commented on AMBARI-15679:
--------------------------------------

[~oleewere] There were a bunch of new files added for which there are different 
licenses in play. However, the top level license file has not been updated. 
Likewise does any of these new additions need an update to the NOTICE file? 

Additionally, 

ambari-logsearch/ambari-logsearch-portal/src/main/webapp/libs/bower/globalize/generator/HijriCalendar.js
ambari-logsearch/ambari-logsearch-portal/src/main/webapp/libs/bower/globalize/generator/UmAlQuraCalendar.js

Could you provide the original source for these? What license was the original 
source under? 

\cc [~sumitmohanty] 



> Initial commit for LogSearch
> ----------------------------
>
>                 Key: AMBARI-15679
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15679
>             Project: Ambari
>          Issue Type: Technical task
>          Components: stacks
>    Affects Versions: 2.4.0
>            Reporter: Sumit Mohanty
>            Assignee: Olivér Szabó
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15679.patch
>
>
> LogSearch service includes three major components:
> * A Solr cloud to store logs and query
> * Log collectors/feeders that consume log files being generated by the 
> services
> * Log search service that provides REST API and UI front end
> The above components are managed by Ambari through a stack definition. The 
> stack definition provides the mechanism to have the LogSearch service 
> configured to read log files created by other services, including Ambari 
> Server. This integration allows customizing log locations and letting 
> LogSearch service be aware of the locations.
> Final peace is to provide an integration from the Ambari UI to LogSearch 
> service so that the logs for a service is easily accessible from the service 
> dashboards.



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

Reply via email to