You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "Edward Zhang (JIRA)" <ji...@apache.org> on 2015/12/03 20:25:11 UTC

[jira] [Commented] (EAGLE-72) Eagle should not enforce user app use org.apache.eagle as package prefix for providing storage

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

Edward Zhang commented on EAGLE-72:
-----------------------------------

That is very good point for EAGLE to integrate 3rd party logs. Also, do you think it is good to scan the packages or do we have better ways to recognize entities?

> Eagle should not enforce user app use org.apache.eagle as package prefix for providing storage
> ----------------------------------------------------------------------------------------------
>
>                 Key: EAGLE-72
>                 URL: https://issues.apache.org/jira/browse/EAGLE-72
>             Project: Eagle
>          Issue Type: Improvement
>    Affects Versions: 0.3.0
>            Reporter: Su Ralph
>
> Currently, eagle hbase repository scanner is hard coded to scan the prefix of 'org.apache.eagle' packages. Means user would need to have their class under this package prefix to use the storage framework. This is unreasonable. 
> Eagle should be able to read the config from api input or better from application config eagleProps.repositoryPackage.



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