From 698d763d134554e864089b79421b1d79bb5de1b1 Mon Sep 17 00:00:00 2001 From: Noah Treuhaft Date: Wed, 16 Oct 2024 13:43:33 -0400 Subject: [PATCH] Update docs/language/functions/grok.md Co-authored-by: Phil Rzewski --- docs/language/functions/grok.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/language/functions/grok.md b/docs/language/functions/grok.md index dc07147e39..181d2ee41e 100644 --- a/docs/language/functions/grok.md +++ b/docs/language/functions/grok.md @@ -58,7 +58,7 @@ issue describing your use case. string. Zed currently accepts this trailing `:type` syntax but effectively ignores it and stores all parsed values as strings. Downstream use of Zed's [`cast` function](cast.md) can be used instead for data type conversion. - ([zed/4928](https://github.com/brimdata/super/issues/4928)) + ([super/4928](https://github.com/brimdata/super/issues/4928)) 2. Some Logstash Grok examples use an optional square bracket syntax for storing a parsed value in a nested field, e.g.,