[
https://issues.apache.org/jira/browse/METRON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686725#comment-15686725
]
ASF GitHub Bot commented on METRON-576:
---------------------------------------
Github user nickwallen commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/366#discussion_r89112046
--- Diff:
metron-platform/metron-common/src/main/java/org/apache/metron/common/stellar/shell/StellarExecutor.java
---
@@ -143,11 +153,13 @@ public StellarExecutor(Console console) throws
Exception {
public StellarExecutor(String zookeeperUrl, Console console) throws
Exception {
this.variables = new HashMap<>();
- this.functionResolver = new StellarFunctions().FUNCTION_RESOLVER();
this.client = createClient(zookeeperUrl);
this.context = createContext();
+ StellarFunctions.initialize(this.context);
+ this.functionResolver = StellarFunctions.FUNCTION_RESOLVER();
--- End diff --
Yes, agreed. I think that makes sense. I'll hack on that a bit
> 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)
