Skip to content

Take expiry from entity class annotation for getAndTouch. #1640

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

Merged
merged 1 commit into from
Jan 10, 2023

Conversation

mikereiche
Copy link
Collaborator

Closes #1634.

  • You have read the Spring Data contribution guidelines.
  • There is a ticket in the bug tracker for the project in our JIRA.
  • You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
  • You submit test cases (unit or integration tests) that back your changes.
  • You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

Copy link
Collaborator Author

@mikereiche mikereiche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mikereiche mikereiche force-pushed the datacouch_1634_take_expiry_from_entity_annotations branch from de7219a to fc48b86 Compare January 10, 2023 18:25
@@ -72,6 +72,8 @@ public <T> ReactiveFindById<T> findById(Class<T> domainType) {
private final ReactiveTemplateSupport support;
private final Duration expiry;

private Duration expiryToUse;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this need to be volatile?

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.

Never call getAndTouch in ReactiveFindByIdOperationSupport
2 participants