April 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HSEARCH-3896) Verify multiple loading with the DefaultProjectionHitMapper on the same query instance

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-3896 ( https://hibernate.atlassian.net/browse/HSEARCH-3896?atlOrigin=eyJpIjoiNzd... ) Re: Verify multiple loading with the DefaultProjectionHitMapper on the same query instance ( https://hibernate.atlassian.net/browse/HSEARCH-3896?atlOrigin=eyJpIjoiNzd... ) Good catch, thanks. DefaultProjectionHitMapper can't be stateless because its purpose is to hold a mutable list of references to load. We need to turn getProjectionHitMapper into a factory method, or to make sure DefaultProjectionHitMapper clears it state after loading. I think the first solution is more robust as it will work even if a search query fails after having added references to the hit mapper but before loading entities. ( https://hibernate.atlassian.net/browse/HSEARCH-3896#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3896#add-comment?atlOrigin... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100124- sha1:93e2dd3 )

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3896) Verify multiple loading with the DefaultProjectionHitMapper on the same query instance

by Fabio Massimo Ercoli (JIRA)

Fabio Massimo Ercoli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiNzE3MDE2... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-3896?atlOrigin=eyJpIjoiNzE... ) HSEARCH-3896 ( https://hibernate.atlassian.net/browse/HSEARCH-3896?atlOrigin=eyJpIjoiNzE... ) Verify multiple loading with the DefaultProjectionHitMapper on the same query instance ( https://hibernate.atlassian.net/browse/HSEARCH-3896?atlOrigin=eyJpIjoiNzE... ) Issue Type: Task Affects Versions: 6.0.0.Beta6 Assignee: Unassigned Components: mapper-javabean, mapper-orm, mapper-pojo Created: 17/Apr/2020 02:01 AM Fix Versions: 6.0.0.Beta-backlog-high-priority Priority: Major Reporter: Fabio Massimo Ercoli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Trying to execute the same query instance, it seems that it carries some state from the previous executions. We have probably to inspect the DefaultProjectionHitMapper behavior. Probably it needs to be stateless or we need to change the method *.loading.context.spi.LoadingContext#getProjectionHitMapper into createProjectionHitMapper. We need a test case for it maybe on *.mapper.orm.search.loading.AbstractSearchQueryEntityLoadingIT. Having that working will allow us to reuse (to cache) the query instances within the same thread. ( https://hibernate.atlassian.net/browse/HSEARCH-3896#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3896#add-comment?atlOrigin... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100124- sha1:93e2dd3 )

4 years, 5 months

1
0
0 / 0

[JIRA] (HHH-13954) PostgreSQL - partitioned table: Schema-validation: missing table (when table exists)

by Paweł Pinkos (JIRA)

Paweł Pinkos ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c0e39f... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMzE3NjU1Y2E0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-13954?atlOrigin=eyJpIjoiMzE3Nj... ) HHH-13954 ( https://hibernate.atlassian.net/browse/HHH-13954?atlOrigin=eyJpIjoiMzE3Nj... ) PostgreSQL - partitioned table: Schema-validation: missing table (when table exists) ( https://hibernate.atlassian.net/browse/HHH-13954?atlOrigin=eyJpIjoiMzE3Nj... ) Issue Type: Bug Assignee: Unassigned Components: hibernate-core Created: 17/Apr/2020 00:35 AM Priority: Major Reporter: Paweł Pinkos ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c0e39f... ) Hibernate do not support partitioned tables in PostgreSQL 11 There is issue with supported metadata types. Under validation hibernate looking for ["TABLE","VIEW"] object type from database metadata. But postgresql in case of partirioned table return type "PARTITIONED TABLE". If ddl policy for hibernate is "validate" - then application failed under deploy. If "update" then hibernate trying create table but get error from database "Table already exists" Accepted types are hardcoded in (line number: 84,85): org.hibernate.tool.schema.extract.internal.InformationExtractorJdbcDatabaseMetaDataImpl https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src... Stacktrace below: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaConfiguration.class] : Invocation of init method failed; nested exception is javax.persistence.PersistenceException: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested exception is org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [xxx.xyz] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1796) ~ [spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:595) ~ [spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517) ~ [spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323) ~ [spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) ~ [spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:321) ~ [spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) ~ [spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1108) ~ [spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:868) ~ [spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:550) ~ [spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) ~ [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at com.orange.rms.dl.Application.main(Application.java:12) [classes/:na] Caused by: javax.persistence.PersistenceException: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested exception is org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [xxx.xyz] at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.buildNativeEntityManagerFactory(AbstractEntityManagerFactoryBean.java:403) ~ [spring-orm-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:378) ~ [spring-orm-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.afterPropertiesSet(LocalContainerEntityManagerFactoryBean.java:341) ~ [spring-orm-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1855) ~ [spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1792) ~ [spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE] ... 16 common frames omitted Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [xxx.xyz] at org.hibernate.tool.schema.internal.AbstractSchemaValidator.validateTable(AbstractSchemaValidator.java:121) ~ [hibernate-core-5.4.12.Final.jar:5.4.12.Final] at org.hibernate.tool.schema.internal.GroupedSchemaValidatorImpl.validateTables(GroupedSchemaValidatorImpl.java:42) ~ [hibernate-core-5.4.12.Final.jar:5.4.12.Final] at org.hibernate.tool.schema.internal.AbstractSchemaValidator.performValidation(AbstractSchemaValidator.java:89) ~ [hibernate-core-5.4.12.Final.jar:5.4.12.Final] at org.hibernate.tool.schema.internal.AbstractSchemaValidator.doValidation(AbstractSchemaValidator.java:68) ~ [hibernate-core-5.4.12.Final.jar:5.4.12.Final] at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:192) ~ [hibernate-core-5.4.12.Final.jar:5.4.12.Final] at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:73) ~ [hibernate-core-5.4.12.Final.jar:5.4.12.Final] at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:314) ~ [hibernate-core-5.4.12.Final.jar:5.4.12.Final] at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:468) ~ [hibernate-core-5.4.12.Final.jar:5.4.12.Final] at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1237) ~ [hibernate-core-5.4.12.Final.jar:5.4.12.Final] at org.springframework.orm.jpa.vendor.SpringHibernateJpaPersistenceProvider.createContainerEntityManagerFactory(SpringHibernateJpaPersistenceProvider.java:58) ~ [spring-orm-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:365) ~ [spring-orm-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.buildNativeEntityManagerFactory(AbstractEntityManagerFactoryBean.java:391) ~ [spring-orm-5.2.5.RELEASE.jar:5.2.5.RELEASE] ... 20 common frames omitted ( https://hibernate.atlassian.net/browse/HHH-13954#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13954#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100124- sha1:93e2dd3 )

4 years, 5 months

1
0
0 / 0

[JIRA] (HHH-12645) HQL left join fetch not working in inheritance scenario: org.hibernate.QueryException: could not resolve property

by Sai Surekha (JIRA)

Sai Surekha ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e99396... ) *commented* on HHH-12645 ( https://hibernate.atlassian.net/browse/HHH-12645?atlOrigin=eyJpIjoiODM1OG... ) Re: HQL left join fetch not working in inheritance scenario: org.hibernate.QueryException: could not resolve property ( https://hibernate.atlassian.net/browse/HHH-12645?atlOrigin=eyJpIjoiODM1OG... ) Hi All, I am upgrading hibernate from 5.1.17 to 5.4.11. I am also facing same issue and scenario is also same. I can not go for rename because it effects lot of files. @Entity public class BaseEntity { @Id private long id; } Child1: @Entity public class EntityA extends BaseEntity { @OneToMany(mappedBy = "entityA") private Set<EntityC> attributes; } Child2: @Entity public class EntityB extends BaseEntity { @OneToMany(mappedBy = "entityB") private Set<EntityC> attributes; } @Entity public class EntityC { @ManyToOne(fetch = FetchType.LAZY) @JoinColumn(name = "entityA_id") @NaturalId private EntityA entityA; @ManyToOne(fetch = FetchType.LAZY) @JoinColumn(name = "entityB_id") @NaturalId @XmlTransient @JsonProperty private EntityB entityB; } Can some one suggest solution for this? ( https://hibernate.atlassian.net/browse/HHH-12645#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-12645#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100124- sha1:93e2dd3 )

4 years, 5 months