May 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-10881) hibernate.default_batch_fetch_size can create deadlocks

by Mirek Sz (JIRA)

Mirek Sz ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-10881 ( https://hibernate.atlassian.net/browse/HHH-10881?atlOrigin=eyJpIjoiYmYwMz... ) Re: hibernate.default_batch_fetch_size can create deadlocks ( https://hibernate.atlassian.net/browse/HHH-10881?atlOrigin=eyJpIjoiYmYwMz... ) Even in org.hibernate.persister.entity.AbstractEntityPersister.createEntityLoader(LockMode, LoadQueryInfluencers) there is comment about it protected UniqueEntityLoader createEntityLoader( LockMode lockMode, LoadQueryInfluencers loadQueryInfluencers) throws MappingException { //TODO: disable batch loading if lockMode > READ? return BatchingEntityLoaderBuilder.getBuilder( getFactory() ) .buildLoader( this , batchSize, lockMode, getFactory(), loadQueryInfluencers ); } ( https://hibernate.atlassian.net/browse/HHH-10881#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-10881#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#100126- sha1:a719cbc )

5 years, 11 months

1
0
0 / 0

[JIRA] (HHH-10881) hibernate.default_batch_fetch_size can create deadlocks

by Mirek Sz (JIRA)

5 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14002) Allow Hibernate to load multiple entities at once from cache

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14002 ( https://hibernate.atlassian.net/browse/HHH-14002?atlOrigin=eyJpIjoiNGUzOT... ) Re: Allow Hibernate to load multiple entities at once from cache ( https://hibernate.atlassian.net/browse/HHH-14002?atlOrigin=eyJpIjoiNGUzOT... ) This is a great idea! Thanks for raising it. ( https://hibernate.atlassian.net/browse/HHH-14002#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14002#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#100126- sha1:a719cbc )

5 years, 11 months

1
0
0 / 0

[JIRA] (BVAL-237) Expose validated bean via ConstraintValidatorContext

by l0coful (JIRA)

l0coful ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c8fa77... ) *commented* on BVAL-237 ( https://hibernate.atlassian.net/browse/BVAL-237?atlOrigin=eyJpIjoiYWM2ZmY... ) Re: Expose validated bean via ConstraintValidatorContext ( https://hibernate.atlassian.net/browse/BVAL-237?atlOrigin=eyJpIjoiYWM2ZmY... ) That’s really unfortunate that for 7 years such a simple fix hasn’t been added to hibernate validator, and that’s because “in some situations this bean would be null”. So what? Note that without this feature you cannot do any contextual validation with hibernate validator, like for example this: @Entity class User { protected Country country; @GovId protected String govId; } If you want to use this entity to represent users from different countries, and you want to implement @GovId validator so that it uses different validation for users from different countries, you currently cannot do it with hibernate validator because there’s no way to access country field of the User entity from the validation context. Fortunately there’s a way to do it using beans validation implementation from Micronaut framework which apparently doesn’t have a problem with injecting root bean into the validation context. ( https://hibernate.atlassian.net/browse/BVAL-237#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/BVAL-237#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#100126- sha1:a719cbc )

5 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-3842) Expose a global option to use ReindexOnUpdate.NO as a default

by Yoann Rodière (JIRA)

5 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-3920) Update tests to take advantage of the latest changes to test utils

by Yoann Rodière (JIRA)

5 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-3920) Update tests to take advantage of the latest changes to test utils

by Yoann Rodière (JIRA)

5 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-3917) Use TopScoreDocCollector when a descending score sort is requested explicitly

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *closed* an issue as *Won't Fix* It's actually not a good idea, as it results in inconsistent values being returned by LuceneSearchQuery.getLuceneSort() and LuceneSearchResult.getTopDocs()}: when the sort is non-null but contains only a sort by descending score, we end up returning top docs while "scoreDocs" are {{ScoreDoc instances instead of the expected FieldDoc instances. This in turn complicates the (user) implementation of merging top docs. Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiODMxZGRl... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-3917?atlOrigin=eyJpIjoiODM... ) HSEARCH-3917 ( https://hibernate.atlassian.net/browse/HSEARCH-3917?atlOrigin=eyJpIjoiODM... ) Use TopScoreDocCollector when a descending score sort is requested explicitly ( https://hibernate.atlassian.net/browse/HSEARCH-3917?atlOrigin=eyJpIjoiODM... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Fix versions: 6.0.0.Beta-backlog-high-priority Resolution: Won't Fix Status: In Progress Closed ( https://hibernate.atlassian.net/browse/HSEARCH-3917#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3917#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#100126- sha1:a719cbc )

5 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-3913) @FullTextField.aggregable doesn't do anything

by Yoann Rodière (JIRA)

5 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-3919) Add test configuration to test AWS Elasticsearch Service 7.4

by Yoann Rodière (JIRA)

5 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2020