Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Fields annotated with @Column(updatable=false) set null value in 2nd level cache

Description

I have two entity with 2nd level cache enable using caffeine:

@Entity @Table(name = "slide") @Cache(usage = CacheConcurrencyStrategy.READ_WRITE) public class Slide { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) @Column(name = "id") private Long id; @NotNull @Size(max = 64) @Column(name = "name", length = 64, nullable = false) private String name; @JoinColumn(updatable = false) @ManyToOne private Display display; @CreatedBy @Column(name = "created_by", updatable = false) private Long createdBy; @CreatedDate @Column(name = "created_at", updatable = false) private Instant createdAt; } @Entity @Table(name = "display") @Cache(usage = CacheConcurrencyStrategy.READ_WRITE) public class Display { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) @Column(name = "id") private Long id; @NotNull @Size(max = 64) @Column(name = "name", length = 64, nullable = false) private String name; @OneToMany(cascade = CascadeType.REMOVE, mappedBy = "display") @Cache(usage = CacheConcurrencyStrategy.READ_WRITE) private Set<Slide> slides = new HashSet<>(); @CreatedBy @Column(name = "created_by", updatable = false) private Long createdBy; @CreatedDate @Column(name = "created_at", updatable = false) private Instant createdAt; }

I saved Display, and then save Slide with the following code:

Slide slide = new Slide(); slide.setName("the name"); slide.setDisplay(display); slideRepository.save(slide);

It's ok when I get Slide by slide id from cache:

Slide slide = slideRepository.findById(1L).get(); System.out.println(slide.getName()); // the name System.out.println(slide.getDisplay().getId()); // 44(display id) System.out.println(slide.getCreatedBy()); // 10624(user id) System.out.println(slide.getCreatedAt()); // 2022-01-28T07:56:12Z

Then I update the slide without setting the value of Display and so on because I set updatable=false:

Slide slide = new Slide(); slide.setId(1L); slide.setName("change name"); slideRepository.save(slide);

Now when I get Slide by slide id again, it casue the problem:

Slide slide = slideRepository.findById(1L).get(); System.out.println(slide.getName()); // change name System.out.println(slide.getDisplay().getId()); // npe(display is null) System.out.println(slide.getCreatedBy()); // null System.out.println(slide.getCreatedAt()); // null

It return to peace after I clear 2nd level cache:

// clear the cache first em.getCache().unwrap(org.hibernate.Cache.class).evictAllRegions(); Slide slide = slideRepository.findById(1L).get(); System.out.println(slide.getName()); // change name System.out.println(slide.getDisplay().getId()); // 44(display id) System.out.println(slide.getCreatedBy()); // 10624(user id) System.out.println(slide.getCreatedAt()); // 2022-01-28T07:56:12Z

So the problem is I have to set the value of all columns though some of them have already annotated with updatable=false if I still want to use 2nd level cache:

Slide existSlide = slideRepository.findById(1L).get(); Slide slide = new Slide(); slide.setId(1L); slide.setName("change name"); slide.setDisplay(existSlide.getDisplay()); slide.setCreatedBy(existSlide.getCreatedBy()); slide.setCreatedAt(existSlide.getCreatedAt()); slideRepository.save(slide);

I think the cache can be more intellective to deal with this situation by keeping the value of these columns when updating the cache of the entity. I also understand the cache may be not exist when I update an entity directly so It doesn't know the original value. Maybe it shouldn't create the cache in this situation or getting the old value from db before transaction commited first?

The code above is just an example to show the issue and I'm annoyed by dealing with these problem in everywhere of my application.

By the way, the *Repository extends JpaRepository.

See also: Updating an entity with updatable=false set the field to null

Activity

Show:

Details

Assignee

Reporter

Components

Affects versions

Priority

Created January 28, 2022 at 8:27 AM
Updated January 28, 2022 at 8:28 AM

Flag notifications