Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/508
+1 by inspection
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/508
None other than the fact that we might have an empty guava cache hanging
around in memory. At the moment, nobody uses the alternative cache.
---
If your project is set up for it, you
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/508
Any implications to having a static cache initialized and unused if an
alternate cache is passed in via the other constructors?
---
If your project is set up for it, you can reply to
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/508
+1 by inspection, although I'm inclined to think of a reason not to have a
static cache, but instead an instance based one, I can't think of a specific
case.
---
If your project
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/508
@ottobackwards It should not. When we start being able to handle people
dropping new jars in HDFS on a *running* topology, then we will need to prune
this cache. As of now, though, a
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/508
1 question -> does this require any relation to the VFS cache?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
