Skip to content

Conversation

@gabsow
Copy link
Collaborator

@gabsow gabsow commented Nov 20, 2025

(cherry picked from commit 7211a07)


Note

Always enable the thread-safe shared string cache at init by calling ijson::init_shared_string_cache(true), removing the config-based toggle and updating logs.

  • Initialization behavior:
    • Always enable thread-safe shared string cache using ijson::init_shared_string_cache(true).
    • Remove CONFIG GET bigredis-enabled check and the conditional cache init.
    • Update initialization logs to reflect thread-safe cache is always enabled.
  • Imports:
    • Add ijson import; remove unused RedisValue import.

Written by Cursor Bugbot for commit d6a73e5. This will update automatically on new commits. Configure here.

@gabsow gabsow changed the title Always enable thread-safe cache for async flush support (#1446) MOD-12014 Always enable thread-safe cache for async flush support (#1446) Nov 20, 2025
…xistent $crate function

- Changed $crate::init_ijson_shared_string_cache to ijson::init_shared_string_cache
- Added ijson import to macro context
- Removed unused RedisValue import
@gabsow gabsow merged commit 791b3be into 2.8 Nov 23, 2025
18 of 19 checks passed
@gabsow gabsow deleted the cherry-pick-always-enable-thread-safe-cach-2.8 branch November 23, 2025 09:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants