[
https://issues.apache.org/jira/browse/METRON-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165583#comment-16165583
]
ASF GitHub Bot commented on METRON-1185:
----------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/755
ok, if and when we look at stellar archetypes and extensions we'll have to
keep this in mind
> Stellar REPL does not work on a kerberized cluster when calling functions
> interacting with HBase
> ------------------------------------------------------------------------------------------------
>
> Key: METRON-1185
> URL: https://issues.apache.org/jira/browse/METRON-1185
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
>
> Because we put all the jars on the classpath from $METRON_HOME/lib via a
> glob, if we get the wrong order, we get classpath issues around Stopwatch
> (i.e. more recent guava may sneak onto the classpath first). This is
> non-deterministic and can cause issues randomly. Instead of a glob, we
> should choose one of the uber jars with all the metron Stellar functions
> baked in and allow users to provide any extra directories we should include
> via an env variable. Also, we are not pulling the full hbase classpath, so
> in a kerberized cluster we do not get all of the configs on the classpath, so
> we can't find always find tgts.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
