Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using redis local #1979

Merged
merged 1 commit into from
Jan 16, 2025
Merged

using redis local #1979

merged 1 commit into from
Jan 16, 2025

Conversation

ag060
Copy link
Contributor

@ag060 ag060 commented Jan 14, 2025

using local redis instead of centralized redis

Earlier we were using local caffine cache and syncing the changes to
centralized redis.
Now we are using local redis only
Assumption is now that we get all the data for particular user key on
one machine.
This will be handled by producer

@ag060 ag060 changed the base branch from master to threat-detection-v1 January 14, 2025 10:11
@ag060 ag060 force-pushed the threat-detection-v1 branch from 580c213 to 6fce807 Compare January 15, 2025 05:32
Earlier we were using local caffine cache and syncing the changes to
centralized redis.
Now we are using local redis only
Assumption is now that we get all the data for particular user key on
one machine.
This will be handled by producer
@ag060 ag060 force-pushed the using-redis-local branch from 7475062 to 2e20126 Compare January 15, 2025 05:41
@ag060 ag060 merged commit b95bed6 into threat-detection-v1 Jan 16, 2025
2 checks passed
ag060 added a commit that referenced this pull request Jan 16, 2025
Earlier we were using local caffine cache and syncing the changes to
centralized redis.
Now we are using local redis only
Assumption is now that we get all the data for particular user key on
one machine.
This will be handled by producer
ag060 added a commit that referenced this pull request Jan 16, 2025
Earlier we were using local caffine cache and syncing the changes to
centralized redis.
Now we are using local redis only
Assumption is now that we get all the data for particular user key on
one machine.
This will be handled by producer
ag060 added a commit that referenced this pull request Jan 16, 2025
Earlier we were using local caffine cache and syncing the changes to
centralized redis.
Now we are using local redis only
Assumption is now that we get all the data for particular user key on
one machine.
This will be handled by producer
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.

1 participant