docs: v4.0.0 changelog

[chejinge]

Summary by CodeRabbit

• New Features

  • Added support for TCL tests for Pika Geo data type.
  • Enabled compilation and packaging on FreeBSD14 platform.
  • Introduced multi-key query caching for Mget.
  • New monitoring metrics for Codis-proxy (P99 and P95 response times).
  • Added master-slave replication monitoring (repl_connect_status).
  • Support for partition index filtering and the third-generation storage engine Floyd.

• Improvements

  • Updated Pika Docker Readme for easier deployment.
  • Enhanced query-caching and dynamic adjustment of RocksDB parameters.
  • Improved validation for PR titles to disallow Chinese characters at the end.
  • Refactored master-slave synchronization thread model for better performance.

• Bug Fixes

  • Resolved issues with ZREVRANK return values, data migration errors, and runtime crashes.
  • Fixed command anomalies, key TTL updates, data deletion problems, binlog writing issues, and error handling.

[coderabbitai[bot]]

Walkthrough

The v4.0.0 update for Pika introduces significant new features, including support for FreeBSD14, enhanced monitoring metrics, and improvements in storage engines. Bug fixes address issues like abnormal return values and data inconsistencies. Additionally, updates in deployment, testing, and query optimization enhance overall performance and stability.

Changes

Files	Change Summary
CHANGELOG.MD	Documented new features, improvements, and bug fixes in the Pika v4.0.0 release.
.github/workflows/pika.yml	Added a step to install the EPEL release before installing dependencies on CentOS 7.

Poem

A hop, a skip, the code does gleam,
In Pika’s world, a coder's dream.
Bugs squashed, new metrics soar,
With FreeBSD14, we've opened a door.
From caching tweaks to Docker's grace,
Version 4.0.0 takes its place.
🎉✨🚀

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.