[
https://issues.apache.org/jira/browse/METRON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687048#comment-15687048
]
ASF GitHub Bot commented on METRON-576:
---------------------------------------
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/366
Instead of using the global properties, there is now a capability called
`STELLAR_CONFIG`. The includes/excludes are pulled from this.
In the context of the REPL, it attempts to load a file called
`stellar.properties` from the classpath. The values in this file become the
`STELLAR_CONFIG`.
If none exists, it uses a default set of properties. The default
properties only include`org.apache.metron.*`. This hopefully provides a better
experience for casual users, but provides advanced users the ability to easily
include additional packages in the function resolution process.
> Stellar function resolution takes too long on running cluster
> -------------------------------------------------------------
>
> Key: METRON-576
> URL: https://issues.apache.org/jira/browse/METRON-576
> Project: Metron
> Issue Type: Improvement
> Reporter: Nick Allen
> Assignee: Nick Allen
>
> When running the Stellar REPL in a cluster on AWS, function resolution takes
> 50-60 seconds. The user is not able to execute any functions in the REPL
> until this process completes.
> The default function resolver searches the classpath for Stellar functions.
> The delay may be because there are just too many classes in the classpath to
> search on a running cluster. As more libraries are added as dependencies
> under /usr/metron/<version>/lib this problem just gets worse.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)