Spring Boot3+Hibernate6迁移后,超类JpaRepository查询子类属性失败
问题:Spring Boot 3.0(Hibernate 6)继承策略下JpaRepository查询报错
问题背景
从Spring Boot 2.7迁移到3.0后,使用Joined继承策略的实体层级中,基于抽象超类JpaRequest定义的JpaRepository调用findByKey()方法时,集成测试抛出Hibernate异常,提示无法解析子类属性requestItemConfiguration。调试发现Hibernate尝试将子类属性映射到抽象超类的EntityMetamodel导致失败。
报错信息
Caused by: org.hibernate.HibernateException: Unable to resolve property: requestItemConfiguration at org.hibernate.tuple.entity.EntityMetamodel.getPropertyIndex(EntityMetamodel.java:872) at org.hibernate.persister.entity.AbstractEntityPersister.getPropertyIndex(AbstractEntityPersister.java:2781) at org.hibernate.sql.results.graph.entity.internal.BatchEntitySelectFetchInitializer.endLoading(BatchEntitySelectFetchInitializer.java:226) at org.hibernate.sql.results.internal.StandardRowReader.finishUp(StandardRowReader.java:161) at org.hibernate.sql.results.spi.ListResultsConsumer.consume(ListResultsConsumer.java:168) at org.hibernate.sql.results.spi.ListResultsConsumer.consume(ListResultsConsumer.java:32) at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.doExecuteQuery(JdbcSelectExecutorStandardImpl.java:443) at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.executeQuery(JdbcSelectExecutorStandardImpl.java:166) at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.list(JdbcSelectExecutorStandardImpl.java:91) at org.hibernate.sql.exec.spi.JdbcSelectExecutor.list(JdbcSelectExecutor.java:31) at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.lambda$new$0(ConcreteSqmSelectQueryPlan.java:102) at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.withCacheableSqmInterpretation(ConcreteSqmSelectQueryPlan.java:305) at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.performList(ConcreteSqmSelectQueryPlan.java:246) at org.hibernate.query.sqm.internal.QuerySqmImpl.doList(QuerySqmImpl.java:546) at org.hibernate.query.spi.AbstractSelectionQuery.list(AbstractSelectionQuery.java:363) at org.hibernate.query.sqm.internal.QuerySqmImpl.list(QuerySqmImpl.java:1032) at org.hibernate.query.spi.AbstractSelectionQuery.getSingleResult(AbstractSelectionQuery.java:457) at org.hibernate.query.sqm.internal.QuerySqmImpl.getSingleResult(QuerySqmImpl.java:1062) at org.springframework.data.jpa.repository.query.JpaQueryExecution$SingleEntityExecution.doExecute(JpaQueryExecution.java:193) at org.springframework.data.jpa.repository.query.JpaQueryExecution.execute(JpaQueryExecution.java:90) at org.springframework.data.jpa.repository.query.AbstractJpaQuery.doExecute(AbstractJpaQuery.java:148) at org.springframework.data.jpa.repository.query.AbstractJpaQuery.execute(AbstractJpaQuery.java:136) at org.springframework.data.repository.core.support.RepositoryMethodInvoker.doInvoke(RepositoryMethodInvoker.java:136) at org.springframework.data.repository.core.support.RepositoryMethodInvoker.invoke(RepositoryMethodInvoker.java:120) at org.springframework.data.repository.core.support.QueryExecutorMethodInterceptor.doInvoke(QueryExecutorMethodInterceptor.java:164) at org.springframework.data.repository.core.support.QueryExecutorMethodInterceptor.invoke(QueryExecutorMethodInterceptor.java:143) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184) at org.springframework.data.projection.DefaultMethodInvokingMethodInterceptor.invoke(DefaultMethodInvokingMethodInterceptor.java:77) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184) at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:123) at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:388) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:119) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184) at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.invoke(PersistenceExceptionTranslationInterceptor.java:137) ... 87 common frames omitted
实体层级结构
抽象超类JpaRequest
@Entity @Table(name = "request") @Inheritance(strategy = InheritanceType.JOINED) public abstract class JpaRequest { @Id @GeneratedValue(strategy = GenerationType.AUTO) private Long id; @Column(name = "kee", unique = true, nullable = false) private String key; // 其他属性和方法 }
中间抽象子类JpaAbstractRequestItem
@Entity @Table(name = "abstract_request_item") public abstract class JpaAbstractRequestItem extends JpaRequest { // 其他属性和方法 }
具体子类JpaRequestItem
@Entity @Table(name = "request_item") public class JpaRequestItem extends JpaAbstractRequestItem { @ManyToOne(optional = true, fetch = FetchType.EAGER, cascade = { CascadeType.PERSIST }) @JoinColumn(name = "config_id", nullable = true) private JpaRequestItemConfiguration requestItemConfiguration; // 其他属性和方法 }
JpaRepository定义
public interface JpaRequestRepository extends JpaRepository<JpaRequest, Long> { JpaRequest findByKey(String key); // 其他方法 }
解决方案
Hibernate 6对Joined继承策略的实体加载逻辑做了调整,针对该问题可尝试以下方案:
方案1:显式指定查询返回类型
- 如果业务允许,修改Repository方法返回具体子类:
public interface JpaRequestRepository extends JpaRepository<JpaRequest, Long> { JpaRequestItem findByKey(String key); }
- 或者通过
@Query明确指定查询范围:
@Query("SELECT r FROM JpaRequest r WHERE r.key = :key") JpaRequest findByKey(@Param("key") String key);
方案2:关闭批量抓取
在抽象超类JpaRequest上添加注解关闭批量抓取,避免Hibernate尝试加载子类属性到超类元模型:
@BatchSize(size = 0) @Entity @Table(name = "request") @Inheritance(strategy = InheritanceType.JOINED) public abstract class JpaRequest { // ... }
方案3:调整关联属性抓取策略
将子类的Eager关联改为Lazy,避免加载超类时初始化子类关联:
@ManyToOne(optional = true, fetch = FetchType.LAZY, cascade = { CascadeType.PERSIST }) @JoinColumn(name = "config_id", nullable = true) private JpaRequestItemConfiguration requestItemConfiguration;
若业务需要Eager加载,可通过JOIN FETCH显式加载关联:
@Query("SELECT r FROM JpaRequest r JOIN FETCH ((JpaRequestItem)r).requestItemConfiguration WHERE r.key = :key") JpaRequest findByKeyWithConfig(@Param("key") String key);
方案4:升级Hibernate版本
该问题可能是Hibernate 6的已知bug,升级到最新的Hibernate 6.x补丁版本(如6.1.x或6.2.x最新版),很多继承相关问题已在后续版本修复。
内容的提问来源于stack exchange,提问作者randomprogrammer1
相关产品推荐
相关产品推荐

