JPA AttributeConverter 使 hibernate 在事务中对整个表生成更新语句

问题描述 投票：0回答：3

本文中的所有代码都可以在这里找到： https://github.com/cuipengfei/gs-accessing-data-jpa/tree/master/complete

您可以运行此测试来重现问题： https://github.com/cuipengfei/gs-accessing-data-jpa/blob/master/complete/src/test/java/hello/T1ServiceTest.java

我有一个领域模型：

@Entity
@Table(name = "t1", schema = "test")
public class T1 extends BaseEntity {

  @Column(nullable = false)
  private UUID someField;

  @Column()
  private ZonedDateTime date;

  public T1(UUID someField, ZonedDateTime date) {
    this.someField = someField;
    this.date = date;
  }
}

它有一个类型为 ZonedDateTime 的字段，所以我有一个转换器将其转换为 sql 时间戳：

@Converter(autoApply = true)
public class ZonedDateTimeAttributeConverter
    implements AttributeConverter<ZonedDateTime, Timestamp> {

  @Override
  public Timestamp convertToDatabaseColumn(ZonedDateTime entityValue) {
    return (entityValue == null) ? null :
        valueOf(entityValue.withZoneSameInstant(of("UTC")).toLocalDateTime());
  }

  @Override
  public ZonedDateTime convertToEntityAttribute(Timestamp databaseValue) {
    return (databaseValue == null) ? null : databaseValue.toLocalDateTime().atZone(
        of("UTC"));
  }
}

当我尝试在这样的交易中创建大量 T1 时：

@Service
public class T1Service {
  private static final Logger log = LoggerFactory.getLogger(T1Service.class);

  @Autowired
  T1Repository t1Repository;

  @Transactional
  public void insertMany() {
    for (int i = 0; i < 1000; i++) {
      log.info("!!! " + (i + 1) + "th item start");

      UUID randomUUID = UUID.randomUUID();
      T1 foundT1 = tryToFindExistingT1(randomUUID);//certainly won't find

      if (foundT1 == null) {
        log.info("t1 not found");
        ZonedDateTime date = now();
        //date = null;
        //if you enable the line above, there won't be any update statements anymore
        //and find will also become faster
        T1 t1 = new T1(randomUUID, date);
        saveT1(t1);
      }

      log.info("!!! " + (i + 1) + "th item finished");
      log.info("====================================");
    }
  }

  private T1 tryToFindExistingT1(UUID someField) {
    long start = currentTimeMillis();
    T1 t1Id = t1Repository.findBySomeField(someField);
    //as nth item increases, the line above will become very very slow
    //and also, there will be more and more update statements
    //but if you set date of t1 to null, update statement will disappear and it'll not be slow
    log.info("find took: " + (currentTimeMillis() - start) + " milliseconds");
    return t1Id;
  }

  private T1 saveT1(T1 t1) {
    long start = currentTimeMillis();
    T1 savedT1 = t1Repository.save(t1);
    log.info("save took: " + (currentTimeMillis() - start) + " milliseconds");
    return savedT1;
  }

}

hibernate将会生成整个t1表的更新语句。

这是 for 循环前几轮的日志：

2017-03-20 17:51:54.039  INFO 74789 --- [           main] hello.T1Service                          : !!! 1th item start
2017-03-20 17:51:54.052  INFO 74789 --- [           main] o.h.h.i.QueryTranslatorFactoryInitiator  : HHH000397: Using ASTQueryTranslatorFactory
Hibernate: select t1x0_.id as id1_0_, t1x0_.date as date2_0_, t1x0_.some_field as some_fie3_0_ from test.t1 t1x0_ where t1x0_.some_field=?
2017-03-20 17:51:54.154  INFO 74789 --- [           main] hello.T1Service                          : find took: 114 milliseconds
2017-03-20 17:51:54.154  INFO 74789 --- [           main] hello.T1Service                          : t1 not found
2017-03-20 17:51:54.177  INFO 74789 --- [           main] hello.T1Service                          : save took: 15 milliseconds
2017-03-20 17:51:54.177  INFO 74789 --- [           main] hello.T1Service                          : !!! 1th item finished
2017-03-20 17:51:54.177  INFO 74789 --- [           main] hello.T1Service                          : ====================================
2017-03-20 17:51:54.177  INFO 74789 --- [           main] hello.T1Service                          : !!! 2th item start
Hibernate: insert into test.t1 (date, some_field, id) values (?, ?, ?)
Hibernate: update test.t1 set date=?, some_field=? where id=?
Hibernate: select t1x0_.id as id1_0_, t1x0_.date as date2_0_, t1x0_.some_field as some_fie3_0_ from test.t1 t1x0_ where t1x0_.some_field=?
2017-03-20 17:51:54.194  INFO 74789 --- [           main] hello.T1Service                          : find took: 17 milliseconds
2017-03-20 17:51:54.194  INFO 74789 --- [           main] hello.T1Service                          : t1 not found
2017-03-20 17:51:54.195  INFO 74789 --- [           main] hello.T1Service                          : save took: 1 milliseconds
2017-03-20 17:51:54.195  INFO 74789 --- [           main] hello.T1Service                          : !!! 2th item finished
2017-03-20 17:51:54.195  INFO 74789 --- [           main] hello.T1Service                          : ====================================
2017-03-20 17:51:54.195  INFO 74789 --- [           main] hello.T1Service                          : !!! 3th item start
Hibernate: insert into test.t1 (date, some_field, id) values (?, ?, ?)
Hibernate: update test.t1 set date=?, some_field=? where id=?
Hibernate: update test.t1 set date=?, some_field=? where id=?
Hibernate: select t1x0_.id as id1_0_, t1x0_.date as date2_0_, t1x0_.some_field as some_fie3_0_ from test.t1 t1x0_ where t1x0_.some_field=?
2017-03-20 17:51:54.200  INFO 74789 --- [           main] hello.T1Service                          : find took: 4 milliseconds
2017-03-20 17:51:54.200  INFO 74789 --- [           main] hello.T1Service                          : t1 not found
2017-03-20 17:51:54.200  INFO 74789 --- [           main] hello.T1Service                          : save took: 0 milliseconds
2017-03-20 17:51:54.200  INFO 74789 --- [           main] hello.T1Service                          : !!! 3th item finished
2017-03-20 17:51:54.200  INFO 74789 --- [           main] hello.T1Service                          : ====================================
2017-03-20 17:51:54.200  INFO 74789 --- [           main] hello.T1Service                          : !!! 4th item start
Hibernate: insert into test.t1 (date, some_field, id) values (?, ?, ?)
Hibernate: update test.t1 set date=?, some_field=? where id=?
Hibernate: update test.t1 set date=?, some_field=? where id=?
Hibernate: update test.t1 set date=?, some_field=? where id=?
Hibernate: select t1x0_.id as id1_0_, t1x0_.date as date2_0_, t1x0_.some_field as some_fie3_0_ from test.t1 t1x0_ where t1x0_.some_field=?
2017-03-20 17:51:54.209  INFO 74789 --- [           main] hello.T1Service                          : find took: 9 milliseconds
2017-03-20 17:51:54.209  INFO 74789 --- [           main] hello.T1Service                          : t1 not found
2017-03-20 17:51:54.210  INFO 74789 --- [           main] hello.T1Service                          : save took: 1 milliseconds
2017-03-20 17:51:54.210  INFO 74789 --- [           main] hello.T1Service                          : !!! 4th item finished
2017-03-20 17:51:54.210  INFO 74789 --- [           main] hello.T1Service                          : ====================================

在日志中可以看到，hibernate会生成越来越多的update语句。

看起来更新语句的数量总是与 T1 等待提交的行数相同。

现在，如果我删除转换器，这个问题就会消失。

我可以使用 hibernate-java8 lib 代替这个转换器来达到相同的效果，但为什么会发生这种情况？

为什么 JPA AttributeConverter 让 hibernate 在事务中对整个表生成更新语句？

java spring hibernate jpa spring-data-jpa
3个回答
7
投票

我通过在 getter 和 setter 方法中应用转换器而不是作为注释来解决这个问题。像这样：

@Entity
@Table(name = "t1", schema = "test")
public class T1 extends BaseEntity {

  @Column(nullable = false)
  private UUID someField;

  @Column()
  private Timestamp date;

  public T1(UUID someField, ZonedDateTime date) {
    this.someField = someField;
    this.date = date;
  }

    public void setDate(ZonedDateTime date) {
        this.date = new ZonedDateTimeAttributeConverter().convertToDatabaseColumn(date);
    }

    public ZonedDateTime getDate() {
        return new ZonedDateTimeAttributeConverter().convertToEntityAttribute(date);
    }
}
0
投票

问题是从convertToEntityAttribute读取的属性与convertToDatabaseColumn生成的属性不完全相同。

Hibernate首先使用convertToEntityAttribute从数据库读取。然后，出于任何原因，再次使用 ConvertToDatabaseColumn 转换读取的对象，如果检测到对象不同，则进行更新。

0
投票

问题，正如 @Ruben 已经指出的那样，是转换器在转换为 

Timestamp
然后返回 
ZonedDateTime
时不会产生相等的对象。 Hibernate 特别是在深度复制过程中持久保存实体的过程中使用此代码路径。

这里的问题很可能与您居住并运行此代码的时区有关。您实体中的 

ZonedDatetime
实例将具有您的本地时区，但您的转换器将其转换为具有 
UTC
时区的实例。您最终会将此实例与本地时区中的 
ZonedDatetime
实例进行比较，后者不相等，并且会扰乱 Hibernate 的脏检查机制。

最新问题
© www.soinside.com 2019 - 2024. All rights reserved.