April 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HBX-2013) Update Hibernate core dependency to 5.4.14.Final

by Koen Aers (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HHH-13945) Envers cannot process deletion of child entity for ManyToOne relation

by Maxim Schelest (JIRA)

Maxim Schelest ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMmZkNDVmMTZl... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-13945?atlOrigin=eyJpIjoiMmZkND... ) HHH-13945 ( https://hibernate.atlassian.net/browse/HHH-13945?atlOrigin=eyJpIjoiMmZkND... ) Envers cannot process deletion of child entity for ManyToOne relation ( https://hibernate.atlassian.net/browse/HHH-13945?atlOrigin=eyJpIjoiMmZkND... ) Issue Type: Bug Affects Versions: 5.4.11 Assignee: Chris Cranford ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: hibernate-envers Created: 14/Apr/2020 03:03 AM Environment: JDK 8, Win, OracleDB Labels: Envers Priority: Blocker Reporter: Maxim Schelest ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) It worked fine till version 5.4.10.Final, but with beginning with 5.4.11.Final stopped working. Just for information: we found one change related to that in 5.4.11 is HHH-13760 ( https://hibernate.atlassian.net/browse/HHH-13760 ) Closed The problems happens in unit test. We delete data from parent and from child entities. Both uses Envers. The definition of relation to parent in child: @ManyToOne(fetch = FetchType.LAZY) @JoinColumn(name = "ORGANIZATION_ID" , referencedColumnName = "ID" ) @NotNull Hibernate deletes parent entity. Then Envers during processing of child entity tries to find the parent in database (it is also not in cache any more) and throws ObjectNotFoundException: org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [net.payback.lmsglobal.organization.core.db.entity.OrganizationEntity#2] at org.hibernate.boot.internal.StandardEntityNotFoundDelegate.handleEntityNotFound(StandardEntityNotFoundDelegate.java:28) at org.hibernate.proxy.AbstractLazyInitializer.checkTargetState(AbstractLazyInitializer.java:286) at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:181) at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:310) at org.hibernate.envers.internal.entities.mapper.relation.ToOneIdMapper.mapToMapFromEntity(ToOneIdMapper.java:62) at org.hibernate.envers.internal.entities.mapper.MultiPropertyMapper.map(MultiPropertyMapper.java:90) at org.hibernate.envers.internal.synchronization.work.DelWorkUnit.generateData(DelWorkUnit.java:53) at org.hibernate.envers.internal.synchronization.work.AbstractAuditWorkUnit.perform(AbstractAuditWorkUnit.java:66) at org.hibernate.envers.internal.synchronization.AuditProcess.executeInSession(AuditProcess.java:125) at org.hibernate.envers.internal.synchronization.AuditProcess.doBeforeTransactionCompletion(AuditProcess.java:174) at org.hibernate.envers.internal.synchronization.AuditProcessManager$1.doBeforeTransactionCompletion(AuditProcessManager.java:47) at org.hibernate.engine.spi.ActionQueue$BeforeTransactionCompletionProcessQueue.beforeTransactionCompletion(ActionQueue.java:954) at org.hibernate.engine.spi.ActionQueue.beforeTransactionCompletion(ActionQueue.java:525) at org.hibernate.internal.SessionImpl.beforeTransactionCompletion(SessionImpl.java:2371) at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.beforeTransactionCompletion(JdbcCoordinatorImpl.java:447) at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl.beforeCompletionCallback(JdbcResourceLocalTransactionCoordinatorImpl.java:183) at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl.access$300(JdbcResourceLocalTransactionCoordinatorImpl.java:40) It worked find for the last 5 years and stopped to work now. Following newly added in 5.4.10 lines of code from ToOneIdMapper causes a problem: Object entity = nonInsertableFake ? oldObj : newObj; if ( lazyMapping && entity instanceof HibernateProxy ) { entity = ( (HibernateProxy) entity ).getHibernateLazyInitializer().getImplementation(); } Thanks & best regards. ( https://hibernate.atlassian.net/browse/HHH-13945#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13945#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:185bad4 )

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3892) Aggregations on fields in nested documents

by Yoann Rodière (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3892) Aggregations on fields in nested documents

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiNmQxZmU1... ) / New Feature ( https://hibernate.atlassian.net/browse/HSEARCH-3892?atlOrigin=eyJpIjoiNmQ... ) HSEARCH-3892 ( https://hibernate.atlassian.net/browse/HSEARCH-3892?atlOrigin=eyJpIjoiNmQ... ) Aggregations on fields in nested documents ( https://hibernate.atlassian.net/browse/HSEARCH-3892?atlOrigin=eyJpIjoiNmQ... ) Issue Type: New Feature Assignee: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: backend-elasticsearch, backend-lucene Created: 14/Apr/2020 02:58 AM Fix Versions: 6.0.0.Beta-backlog-high-priority Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We don't have tests for this, and some testing I did locally revealed it just doesn't work yet: * For Lucene text fields, aggregations on fields in nested documents always return empty results. * For Lucene numeric fields, aggregations on fields in nested documents seem to ignore some values. * For Elasticsearch, aggregations on fields in nested documents always return empty results. ( https://hibernate.atlassian.net/browse/HSEARCH-3892#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3892#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:185bad4 )

4 years, 5 months

1
0
0 / 0

[JIRA] (HBX-2015) Allow custom reverse engineering strategy to enrich table/column metaattributes provided by hibernate.reveng.xml

by Koen Aers (JIRA)

Koen Aers ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HBX-2015 ( https://hibernate.atlassian.net/browse/HBX-2015?atlOrigin=eyJpIjoiNmMwNWR... ) Re: Allow custom reverse engineering strategy to enrich table/column metaattributes provided by hibernate.reveng.xml ( https://hibernate.atlassian.net/browse/HBX-2015?atlOrigin=eyJpIjoiNmMwNWR... ) hey jordi, would it be possible to attach an example of what you want to achieve? or better yet, a test that illustrates it… ( https://hibernate.atlassian.net/browse/HBX-2015#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/HBX-2015#add-comment?atlOrigin=eyJ... ) 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:185bad4 )

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3891) Allow POJO mapper implementations to pass explicit routing keys when indexing

by Yoann Rodière (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3891) Allow POJO mapper implementations to pass explicit routing keys when indexing

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiOTQxZDlh... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-3891?atlOrigin=eyJpIjoiOTQ... ) HSEARCH-3891 ( https://hibernate.atlassian.net/browse/HSEARCH-3891?atlOrigin=eyJpIjoiOTQ... ) Allow POJO mapper implementations to pass explicit routing keys when indexing ( https://hibernate.atlassian.net/browse/HSEARCH-3891?atlOrigin=eyJpIjoiOTQ... ) Issue Type: Task Assignee: Unassigned Components: mapper-pojo Created: 14/Apr/2020 02:03 AM Fix Versions: 6.0.0.Beta-backlog-low-priority Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We already allow it for the purge: org.hibernate.search.mapper.pojo.work.impl.PojoIndexedTypeIndexingPlan.IndexedEntityIndexingPlan#providedRoutingKey. Let's allow it for any kind of work: it will benefit to Infinispan, in particular. The idea would simply be to add a parameter String providedRoutingKey to every add / addOrUpdate / delete method in org.hibernate.search.mapper.pojo.work.spi.PojoIndexingPlan. ( https://hibernate.atlassian.net/browse/HSEARCH-3891#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3891#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:185bad4 )

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3889) Exception Predicate targets unexpected fields when use nested() in sort filter

by Yoann Rodière (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3889) Exception Predicate targets unexpected fields when use nested() in sort filter

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-3889 ( https://hibernate.atlassian.net/browse/HSEARCH-3889?atlOrigin=eyJpIjoiYWU... ) Re: Exception Predicate targets unexpected fields when use nested() in sort filter ( https://hibernate.atlassian.net/browse/HSEARCH-3889?atlOrigin=eyJpIjoiYWU... ) This exception is on purpose. The predicate passed as sort filter should only be referring to fields in the same nested document as the sort field, or a more deeply nested document; otherwise the filter just cannot work. See HSEARCH-3885 ( https://hibernate.atlassian.net/browse/HSEARCH-3885 ) Resolved. This code would work just fine: PermissionQuery allowQuery = new PermissionQuery( "prices.permissions" , operation, user, true ); PermissionQuery dannyQuery = new PermissionQuery( "prices.permissions" , operation, user, false ); BooleanQuery query = new BooleanQuery.Builder() .add(allowQuery, BooleanClause.Occur.MUST) .add(dannyQuery, BooleanClause.Occur.MUST_NOT) .build(); filter = predicate.extension(LuceneExtension.get()).fromLuceneQuery(query) .toPredicate(); sort.add(sorter.field( "prices.bruttoPrice_sort" ) .asc() .mode(SortMode.MIN) .filter(filter)); SearchQuery<Assortment> query = session.search(scope) .where((f) -> f.bool().must(select) .filter(f.nested().objectField( "prices" ).nest(filter)) .sort(sort.toSort()) .toQuery(); Note that's a bit complicated, but only because of the native query. Without it, we wouldn't have to use an explicit nested predicate to begin with. As to your patch, I'm a bit concerned it will allow "nesting" multiple nested predicates on the same object field, which I do not think will work correctly. Something like this: SearchQuery<Assortment> query = session.search(scope) .where(f -> f.nested().objectField( "prices" ).nest( f.nested().objectField( "prices" ).nest( f.nested().objectField( "prices" ).nest( f.match().field( "prices.thing" ).matching( "foo" ) ) ) )) .toQuery(); I will close this ticket for now, as I provided a solution to your problem. If that's not an acceptable solution, please feel free to re-open this ticket. ( https://hibernate.atlassian.net/browse/HSEARCH-3889#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3889#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:185bad4 )

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3889) Exception Predicate targets unexpected fields when use nested() in sort filter

by Yoann Rodière (JIRA)

4 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2020