April 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-13947) Switch the JPA Javadoc prefix URL to a build parameter

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13947 ( https://hibernate.atlassian.net/browse/HHH-13947?atlOrigin=eyJpIjoiMzlkOW... ) Re: Switch the JPA Javadoc prefix URL to a build parameter ( https://hibernate.atlassian.net/browse/HHH-13947?atlOrigin=eyJpIjoiMzlkOW... ) For reference, see the git commit’s description: * https://github.com/hibernate/hibernate-orm/commit/0b4bcce3fa2589f25b28d13... It inclues the script to run, should this need to be backported or otherwise be useful again. ( https://hibernate.atlassian.net/browse/HHH-13947#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13947#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] (HHH-13947) Switch the JPA Javadoc prefix URL to a build parameter

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *resolved* as *Fixed* While this one patch is meant to pave the road to make it easier to migrate to JPA 3 (Jakarta EE project), it doesn't actually change anything. It might be useful to backport this to older branches to keep the documentation sources more similar across maintained branches. Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZGE1MzNhZGZl... ) / Sub-task ( https://hibernate.atlassian.net/browse/HHH-13947?atlOrigin=eyJpIjoiZGE1Mz... ) HHH-13947 ( https://hibernate.atlassian.net/browse/HHH-13947?atlOrigin=eyJpIjoiZGE1Mz... ) Switch the JPA Javadoc prefix URL to a build parameter ( https://hibernate.atlassian.net/browse/HHH-13947?atlOrigin=eyJpIjoiZGE1Mz... ) Change By: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) backPortable: Backport? Fix versions: 5.5.0.Beta1 Resolution: Fixed Status: Open Resolved ( https://hibernate.atlassian.net/browse/HHH-13947#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13947#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] (HHH-13947) Switch the JPA Javadoc prefix URL to a build parameter

by Sanne Grinovero (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HHH-13947) Switch the JPA Javadoc prefix URL to a build parameter

by Sanne Grinovero (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HHH-13946) Compatibility with JPA 3.0 candidate release, Jakarta EE 9

by Sanne Grinovero (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HHH-13946) Compatibility with JPA 3.0 candidate release

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTNjNmQ4MjFj... ) / New Feature ( https://hibernate.atlassian.net/browse/HHH-13946?atlOrigin=eyJpIjoiNTNjNm... ) HHH-13946 ( https://hibernate.atlassian.net/browse/HHH-13946?atlOrigin=eyJpIjoiNTNjNm... ) Compatibility with JPA 3.0 candidate release ( https://hibernate.atlassian.net/browse/HHH-13946?atlOrigin=eyJpIjoiNTNjNm... ) Issue Type: New Feature Assignee: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Created: 14/Apr/2020 15:29 PM Fix Versions: 5.5.0.Beta1 Priority: Blocker Reporter: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) JPA 3.0 is coming as part of Jakarta EE 9 The main change is a full package rename: all "javax.persistence" packages (including public API and annotations) have been renamed to "jakarta.persistence"; this has obvious dramatic changes on backwards compatibility. On top of package names, we're also expected to change the keys of those configuration properties which used to start with "jakarta.persistence". More details can be found here: * https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee9/JakartaEE9Re... The main changing PR: * https://github.com/eclipse-ee4j/jpa-api/pull/231 The JPA project's new home can be found at * https://projects.eclipse.org/projects/ee4j.jpa/releases/3.0-jakarta-persi... An interesting aspect is that no other change whatsoever is allowed; the idea here is that while this is a breaking change, it should be straight forward to upgrade by simply running a replacement script. To keep our own work simpler, rather than working on a one-off big patch I'll work on testing a replacement script which we could run multiple times at minimal risk; this should make it simpler to forward-port further patches from before the big rename. ( https://hibernate.atlassian.net/browse/HHH-13946#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13946#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] (HHH-13916) Provide an alternative to SessionImpl for Infinispan Pending-put owner

by Gail Badner (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HHH-13916) Provide an alternative to SessionImpl for Infinispan Pending-put owner

by Gail Badner (JIRA)

Gail Badner ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMTBmMmMzMDQ2... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-13916?atlOrigin=eyJpIjoiMTBmMm... ) HHH-13916 ( https://hibernate.atlassian.net/browse/HHH-13916?atlOrigin=eyJpIjoiMTBmMm... ) Provide an alternative to SessionImpl for Infinispan Pending-put owner ( https://hibernate.atlassian.net/browse/HHH-13916?atlOrigin=eyJpIjoiMTBmMm... ) Change By: Gail Badner ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) As a last resort, {{ AbstractEntityPersister#isTransient }} calls {{ CacheHelper.fromSharedCache }} to determine if an entity is cached. If the return value is non-null, then the {{ AbstractEntityPersister#isTransient }} returns {{ false }} , and the return value is ignored. When Infinispan is the cache provider, {{ CacheHelper.fromSharedCache }} calls [ {{ InvalidationCacheAccessDelegate#get }} |https://github.com/infinispan/infinispan/blob/9.4.x/hibernate/cache-commons/src/main/java/org/infinispan/hibernate/cache/commons/access/InvalidationCacheAccessDelegate.java#L56-L65]. If the entity is not already cached, {{ InvalidationCacheAccessDelegate#get }} adds a pending-put for the entity as a side-effect. The entry in the pending-put map uses a {{ SessionImpl }} as the map key. If that entity really is transient, then the pending-put entry never gets cleared until it times out. Since the pending-put map contains {{ SessionImpl }} keys, those {{ SessionImpl }} objects cannot be garbage-collected until the entry times out. If lots of data is in the process of being imported, then an {{ OutOfMemoryError }} could be thrown. IIUC, it is not recommended to use the cache when importing data. That is why I am calling this issue an "improvement" rather than a "bug". {{ [WFLY-13259|https://issues.redhat.com/browse/WFLY-13259] }} contains a test that reproduces this issue. This improvement involves changing The original proposal was to change {{ AbstractEntityPersister#isTransient }} to call {{ CachedDomainDataAccess#get }} . Unfortunately , which calls that would not work consistently. For example, if an entity is deleted, and re-persisted while the deleted entity is still locked in the cache, {{ InvalidationCacheAccessDelegate CachedDomainDataAccess #get }} with a will return {{ null true }} , and {{ session AbstractEntityPersister#isTransient }} argument. Since will incorrectly return {{ session false }} is {{ null }} when re-persisting the new entity. Instead , {{ InvalidationCacheAccessDelegate#get }} does an improvement would be to not add store a pending-put SharedSessionContractImplementor in a PendingPut at all. There is already a way to get a UUID for the entity session by calling SharedSessionContractImplementor#getSessionIdentifier(). Unfortunately, the implementation in AbstractSharedSessionContract indicates that frequent "UUID generations will cause a significant amount of contention". Sanne has suggested returning a "token" that is just a new Object. I've created a [branch|https://github.com/gbadner/hibernate-core/tree/HHH-13916_token] that does this. Infinispan would need to be updated so that PendingPut#owner is set to SharedSessionContractImplementor#getSessionToken() (instead of the SharedSessionContractImplementor object). ( https://hibernate.atlassian.net/browse/HHH-13916#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13916#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] (HHH-13916) Provide an alternative to SessionImpl for Infinispan Pending-put owner

by Gail Badner (JIRA)

4 years, 5 months

1
0
0 / 0

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

by Waldemar Kłaczyński (JIRA)

Waldemar Kłaczyński ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-3889 ( https://hibernate.atlassian.net/browse/HSEARCH-3889?atlOrigin=eyJpIjoiNTc... ) Re: Exception Predicate targets unexpected fields when use nested() in sort filter ( https://hibernate.atlassian.net/browse/HSEARCH-3889?atlOrigin=eyJpIjoiNTc... ) The user could define filters as you presented. Maybe it is better to allow more if it is forbidden. Now the code is getting too complicated. Dividing queries later, submitting them according to the use case is inefficient and complicates the code. You can't prepare filtering patterns, querying dynamic models. Building separate filters for sorting and searching, and in the future and aggregation will be too complicated. After that, even if the user duplicated the predicates, they will be optimized. This is in my patch. But it will be possible to bus complex predicates in satatic methods as well as in native filters. Sometimes over-straining the nesting predicate as an indication that an element should be nested if the context requires it. ( 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2020