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

Feature/record expiry #34

Closed

Conversation

arnkthr
Copy link

@arnkthr arnkthr commented Jun 22, 2021

Added configuration to allow the connector to send records which will expire from redis at a globally configured time.

@jcustenborder
Copy link
Owner

@arnkthr Can you help me understand why this change is needed?

@arnkthr
Copy link
Author

arnkthr commented Jul 7, 2021

@arnkthr Can you help me understand why this change is needed?

Hi @jcustenborder, sorry, the change aims to provide the functionality mentioned in this issue #26

@cch0
Copy link

cch0 commented Jul 9, 2022

Are we waiting on anything before we can approve and merge this other than resolving the merge conflict?

@lmeadors
Copy link

lmeadors commented Feb 8, 2023

Is there a reason that this isn't being merged?

Setting TTL on cache entries so they expire eventually seems like a complete no-brainer feature to add, but this has been sitting here for over 18 months.

@jcustenborder
Copy link
Owner

There is a 2.0 version of the connector which has this functionality. It's been in the works for a while. This also required some refactoring to support sentinel and cluster.

@lmeadors
Copy link

lmeadors commented Feb 9, 2023

A V2 of this is great news! Two questions:

  • what is the ETA on that?
  • what can I do to help accelerate that? :)

@arnkthr arnkthr closed this Mar 5, 2024
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.

4 participants