Skip to content

Commit

Permalink
Fix some links (#4733)
Browse files Browse the repository at this point in the history
  • Loading branch information
philrz authored Jul 28, 2023
1 parent a4a2b64 commit 16214e2
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
## v1.9.0
* The [Zed Language Overview docs](docs/language/overview.md) have been split into multiple sections (#4576)
* Add support for [user-defined operators](docs/language/statements.md#operator-statements) (#4417, #4635, #4646, #4644, #4663, #4674, #4698, #4702, #4716)
* Add experimental support to the [`get` operator](https://github.com/brimdata/zed/blob/main/docs/language/operators/get.md) for customized methods, headers, and body (#4572)
* Add experimental support to the [`get` operator](docs/language/operators/get.md) for customized methods, headers, and body (#4572)
* Allow float decorators on integers in [ZSON](docs/formats/zson.md) (#4654)
* The [shaping docs](docs/language/shaping.md) have been expanded with a new section on [error handling](docs/language/shaping.md#error-handling) (#4686)
* `zq` no longer attaches positional command line file inputs directly to [`join`](docs/language/operators/join.md) inputs (use [`file`](docs/language/operators/file.md) within a Zed program instead) (#4689)
Expand Down
2 changes: 1 addition & 1 deletion performance/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ in `jq`. If there's glaring functional omissions that are limiting your use of
`zq`, we welcome [contributions](../README.md#contributing).

* For the permutations with `ndjson` input the recommended approach for
[shaping Zeek NDJSON](https://zed.brimdata.io/docs/next/integrations/zeek/shaping-zeek-ndjson)
[shaping Zeek NDJSON](https://zed.brimdata.io/docs/integrations/zeek/shaping-zeek-ndjson)
was followed as the input data was being read. In addition to conforming to the
best practices as described in that article, this also avoids a problem
described in [a comment in zed/2123](https://github.com/brimdata/zed/pull/2123#issuecomment-859164320).
Expand Down

0 comments on commit 16214e2

Please sign in to comment.