[
https://issues.apache.org/jira/browse/METRON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15705350#comment-15705350
]
ASF GitHub Bot commented on METRON-576:
---------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/366
+1 by inspection
On Tue, Nov 29, 2016 at 08:49 Nick Allen <[email protected]> wrote:
> Any other feedback guys? Just waiting on +1s if you guys are happy with
> the change.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
>
<https://github.com/apache/incubator-metron/pull/366#issuecomment-263574416>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/AAg-xxUOaGFmpdUv4VZbMpuBckyeAf1bks5rDC1jgaJpZM4K41zJ>
> .
>
> 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)
