[
https://issues.apache.org/jira/browse/METRON-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16446016#comment-16446016
]
ASF GitHub Bot commented on METRON-1520:
----------------------------------------
Github user nickwallen commented on a diff in the pull request:
https://github.com/apache/metron/pull/990#discussion_r183109303
--- Diff: metron-platform/metron-parsers/README.md ---
@@ -174,6 +174,19 @@ then it is assumed to be a regex and will match any
topic matching the pattern (
* `spoutConfig` : A map representing a custom spout config (this is a
map). This can be overridden on the command line.
* `securityProtocol` : The security protocol to use for reading from kafka
(this is a string). This can be overridden on the command line and also
specified in the spout config via the `security.protocol` key. If both are
specified, then they are merged and the CLI will take precedence.
* `stormConfig` : The storm config to use (this is a map). This can be
overridden on the command line. If both are specified, they are merged with
CLI properties taking precedence.
+* `cacheConfig` : Cache config for stellar field transformations. This
configures a least frequently used cache. This is a map with the following
keys. If unconfigured, then no cache will be used.
--- End diff --
Is "unconfigured" == "default" behavior? I'd like to see mentioned
specifically that the default behavior is no cache (at least that's what I am
assuming).
> Add caching for stellar field transformations
> ---------------------------------------------
>
> Key: METRON-1520
> URL: https://issues.apache.org/jira/browse/METRON-1520
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
> Priority: Major
>
> Given how important caching is in the enrichment topology, we should have
> caching for stellar field transformations in the parsers as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
