Skip to content

v0.11.0

Choose a tag to compare

@kirkrodrigues kirkrodrigues released this 14 Apr 18:29
· 221 commits to main since this release
12f80c7

A release that includes several convenience features, bug fixes, and improvements like additional support for AWS authentication methods and minor improvements to query performance.

Note

This release includes some changes that are incompatible with previous releases. If this affects you, reach out and we may be able to help with version migration. These changes are marked with "Breaking".

This release includes two tars for CLP as a distributed system:

  • clp-json for compressing and searching JSON logs
  • clp-text for compressing and searching unstructured text logs

This release also includes installable packages for CLP’s core.

Docs

The docs for this release are available here.

New features

  • log-ingestor/helm: Add support for automatically retrieving AWS credentials via the default credentials provider chain. (#1962)
    • Breaking:
      • In CLP’s configuration file, aws_authentication.type: "ec2" has been renamed to "default" , broadening its scope from EC2 instance metadata to the full AWS SDK default credential provider chain.
      • The Helm chart renames the <clp-deployment-name>-job-watcher to <clp-deployment-name>-service-account.
      • The Helm chart now uses the ServiceAccount (<clp-deployment-name>-service-account) and exposes OIDC annotations in values.yaml for S3 access.
  • log-ingestor: Switch buffer submission from soft timeout to hard timeout; Move buffer config from package config to job config. (#2150)
    • Breaking:
      • buffer_flush_timeout, buffer_flush_threshold, and channel_capacity have been removed from the package-level config (and Helm values). They are now per-job settings specified via the ingestion API's buffer_config field.
      • The buffer flush timer now uses a hard timeout (starts when the first entry is buffered and is not reset by subsequent entries), replacing the previous soft timeout (which reset on every new entry).
  • helm: Add support for deploying Presto in CLP's Helm chart. (#2004)
    • Breaking:
      • The query_engine config has moved from clpConfig.package.query_engine to clpConfig.webui.query_engine.
      • The query-scheduler, query-worker, and reducer components are now conditionally deployed; they are skipped when their respective config sections are set to null.
  • packaging: Add support for building deb, rpm, and apk packages containing CLP's core binaries. (#1996)

Bug fixes & improvements

  • clp-json: Accept empty files as valid inputs (fixes #1993, #2063). (#2138)
  • clp-json: Make timezone offset optional in timezone regex, allowing bare "UTC" and trailing "Z" formats (fixes #1952). (#2134)
  • presto-clp: Fix AWS S3 endpoint URL format so that Presto queries for archives on S3 no longer return zero rows (fixes #2107, fixes #2108). (#2109)
  • clp-json/clp-text: Improve performance for S3 ingestion jobs submitted through log-ingestor by eliminating redundant queries for S3 object metadata. (#2082, #2087)
  • clp-json: Improve query performance when using the API server by not uploading empty query result files to S3. (#2135)
  • deployment: Improve robustness of webui health checks by switching from TCP to HTTP to detect failures like trashing (fixes #2172). (#2186)
  • helm!: Rename mcp-server port from "mcp" to "mcp-server" for consistency (fixes #2021). (#2022)
    • Breaking: Any name-based references (e.g., kubectl port-forward, Ingress or Gateway) to mcp will need to be updated to mcp-server. Usage of the port number is unaffected.
  • clp-package: Only create a new dataset after paths to compress are validated in a compression job (fixes #2091). (#2092)
  • deployment: Pin Presto container image tags to versioned defaults and allow overrides via env vars (fixes #2072). (#2073)

View the full changelog for more details.

Thanks to @Bill-hbrhbr, @davidlion, @gibber9809, @hoophalab, @jackluo923, @jonathan-imanu, @junhaoliao, @LinZhihao-723, @Nathan903, @quinntaylormitchell, and @ShangDanLuXian for their contributions.