Hi there, I've a scripted lookup that returns a field which contains text data. What is really intriguing is that if the returned data contains "metadata" in it, then the text is html encoded (partially at least), and not if this keyword 'metadata' is not present. Any logical explanation to that? How can I remove this html encoding? | stats count | eval curious = "jambon: de -> bayonne" | fields curious This will result in a single field containing "jambon: de -> bayonne" as expected. | stats count | eval curious = "metadata: de -> bayonne" | fields curious This will result in a single field containing "metadata: de -> bayonne" which is not expected ; why is the ">" html encoded?! I thought it was related to the fact that "metadata" is also a Splunk command, but after a few tries with "search", "metasearch",  "mcollect", etc, none of those trigger this behaviour. Is this a weird bug? I'm on Splunk 8.2.3, can you guys reproduce and on which versions? Thanks, ... View more