Skip to content

v1.6.0
Compare
Choose a tag to compare
@brim-bot brim-bot released this 03 Mar 18:33
· 703 commits to main since this release
v1.6.0
6e15e99
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Note: Changes to the Zed lake storage format

This release includes a change to the Zed lake storage format that is not backward compatible. To migrate your pools to the new format there is a Zed lake migration kit and specific guidance for users of the Zed CLI tools.

Quick Start

Visit the Brim Data download page to find the package for your platform.

Zed is distributed as a TGZ/ZIP file of command line executables for each supported platform. To install, unpack with with the appropriate utility for your platform. For example, on Linux:

curl -OL https://github.com/brimdata/zed/releases/download/v1.6.0/zed-v1.6.0.linux-amd64.tar.gz
tar xzvf zed-v1.6.0.linux-amd64.tar.gz

If you've installed the Zui desktop app and want to work with its Zed lake from the command line, we recommend using the Zed executables included with the app to ensure compatibility. See this Zui docs article for their location.

Release Notes

  • Zed lake storage format is now at version 3 (#4386, #4415)
  • Allow loading and responses in VNG format over the lake API (#4345)
  • Fix an issue where record spread expressions could cause a crash (#4359)
  • Fix an issue where the Zed service /version endpoint returned "unknown" if it had been built via go install (#4371)
  • Branch-level meta-queries on the main branch no longer require an explicit @main reference (#4377, #4394)
  • Add -defaultfmt flag to zed serve to specify the lake API's default response format (#4379, #4396)
  • Zed queries now appear in the lake log when zed serve is run at -log.level debug (#4385)
  • Fix an issue where elements of complex named types could not be accessed (#4391)
  • Add docs for the pass operator and an example of join on more than two inputs (#4403)
  • When the result of summarize is a single value and there is no field name specified, the output is now that single value rather than a single-field record containing that value (#4420)
Assets 9
Loading