April 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-13973) OSGi integration tests should not rely on snapshots from the global maven cache

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=eyJpIjoiNGI1ZDg4Nzli... ) / Task ( https://hibernate.atlassian.net/browse/HHH-13973?atlOrigin=eyJpIjoiNGI1ZD... ) HHH-13973 ( https://hibernate.atlassian.net/browse/HHH-13973?atlOrigin=eyJpIjoiNGI1ZD... ) OSGi integration tests should not rely on snapshots from the global maven cache ( https://hibernate.atlassian.net/browse/HHH-13973?atlOrigin=eyJpIjoiNGI1ZD... ) Issue Type: Task Assignee: Unassigned Components: build Created: 23/Apr/2020 04:25 AM Fix Versions: 5.5.0.Beta2 Priority: Major Reporter: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Currently the Karaf integration tests are depending on the `publishToMavenLocal` tasks from the hibernate-core and the hibernate-envers modules. To avoid all problems related with the shared namespace of the snapshot in Maven, we could publish them into a temporary folder of the build directory; then reconfigure Karaf to use this alternative source for dependencies. An example of the Karaf configuration can be found in Hibernate Search: https://github.com/hibernate/hibernate-search/blob/5.11/integrationtest/o... ( https://hibernate.atlassian.net/browse/HHH-13973#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13973#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#100125- sha1:63ccdc5 )

4 years, 5 months

1
0
0 / 0

[JIRA] (HHH-13972) Disable the ForbiddenAPI classloader cache

by Sanne Grinovero (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HHH-13972) Disable the ForbiddenAPI classloader cache

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=eyJpIjoiZmNiYjA4Zjgz... ) / Task ( https://hibernate.atlassian.net/browse/HHH-13972?atlOrigin=eyJpIjoiZmNiYj... ) HHH-13972 ( https://hibernate.atlassian.net/browse/HHH-13972?atlOrigin=eyJpIjoiZmNiYj... ) Disable the ForbiddenAPI classloader cache ( https://hibernate.atlassian.net/browse/HHH-13972?atlOrigin=eyJpIjoiZmNiYj... ) Issue Type: Task Assignee: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: build Created: 23/Apr/2020 04:13 AM Fix Versions: 5.5.0.Beta1 Priority: Minor Reporter: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The ForbiddenAPI tool we use has a smart classloader cache, but it seems this interacts with the gradle daemon; in some situations this has shown to load snapshot builds from a previous build. I haven't fully understood why this happens; what I know is we're possibly loading the snapshots that the OSGi integration tests are needing to deploy into a Maven repository, so I'd guess this possibly bypasses some sanity checks from the Gradle tooling. Let's disable the cache: it solves the problem, probably avoids some future headaches and I've not seen any performance difference. ( https://hibernate.atlassian.net/browse/HHH-13972#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13972#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#100125- sha1:63ccdc5 )

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3888) How to query in "Hibernate Search" fuzzy mode with FuzzyContext.withEditDistanceUpTo() with more than 2 "changes"?

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-3888 ( https://hibernate.atlassian.net/browse/HSEARCH-3888?atlOrigin=eyJpIjoiMzU... ) Re: How to query in "Hibernate Search" fuzzy mode with FuzzyContext.withEditDistanceUpTo() with more than 2 "changes"? ( https://hibernate.atlassian.net/browse/HSEARCH-3888?atlOrigin=eyJpIjoiMzU... ) I don't think we will add this to the DSL, as I doubt we can rely on the stability and overall quality of "sandbox" code. We actually explicitly exclude this artifact from our transitive dependencies. That being said, if you want to rely on that code, you can still roll out your own "slow fuzzy query parser": public final class SlowFuzzyQueryBuilder extends QueryBuilder { private final int minimumSimilarity; public FuzzyQueryBuilder(Analyzer analyzer, int minimumSimilarity) { super ( analyzer ); this.minimumSimilarity = minimumSimilarity; } @Override protected Query newTermQuery(Term term) { return new SlowFuzzyQuery( term, minimumSimilarity ); } } And get the custom analyzer from Hibernate Search: Analyzer analyzer = fullTextSession.getSearchFactory().getAnalyzer( MyEntity.class ); (Or re-build the analyzer manually using org.apache.lucene.analysis.custom.CustomAnalyzer#builder() ) Then just do this to create the Lucene query: SlowFuzzyQueryBuilder builder = new SlowFuzzyQueryBuilder( analyzer, 4 ); Query luceneQuery = builder.createBooleanQuery( "field_name" , "search terms" ); ( https://hibernate.atlassian.net/browse/HSEARCH-3888#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3888#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#100125- sha1:63ccdc5 )

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3888) How to query in "Hibernate Search" fuzzy mode with FuzzyContext.withEditDistanceUpTo() with more than 2 "changes"?

by TNT2k (JIRA)

TNT2k ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e8ded4... ) *commented* on HSEARCH-3888 ( https://hibernate.atlassian.net/browse/HSEARCH-3888?atlOrigin=eyJpIjoiNjk... ) Re: How to query in "Hibernate Search" fuzzy mode with FuzzyContext.withEditDistanceUpTo() with more than 2 "changes"? ( https://hibernate.atlassian.net/browse/HSEARCH-3888?atlOrigin=eyJpIjoiNjk... ) I searched around a bit, and found a “SlowFuzzyQuery” in a sandbox version of lucene ( maven ( https://mvnrepository.com/artifact/org.apache.lucene/lucene-sandbox ) , javadoc ( https://lucene.apache.org/core/4_0_0/sandbox/org/apache/lucene/sandbox/qu... ) ). This SlowFuzzyQuery is able to do, what I need, but is a bit slower (which is not a factor for me). May you implement this class into your QueryBuilder ( org.hibernate.search.query.dsl.TermContext.QueryBuilder ). I would highly appreciate this, because it would give me the possibility to uses custom analyzers, what I can not do without the QueryBuilder. Example code for current usage: this.fullTextEntityManager.createFullTextQuery( new SlowFuzzyQuery( new Term( "NAME" , "SEARCH_TERM".toLowerCase()), minimumSimilarity), CLASS).getResultList() ( https://hibernate.atlassian.net/browse/HSEARCH-3888#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3888#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#100125- sha1:63ccdc5 )

4 years, 5 months

1
0
0 / 0

[JIRA] (HHH-9513) Cascading inserts are failing after upgrade

by Markus Döring (JIRA)

Markus Döring ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-9513 ( https://hibernate.atlassian.net/browse/HHH-9513?atlOrigin=eyJpIjoiNWIwOWY... ) Re: Cascading inserts are failing after upgrade ( https://hibernate.atlassian.net/browse/HHH-9513?atlOrigin=eyJpIjoiNWIwOWY... ) I had the same problem (with 4.1.11 and 5.1) and found that this is only occuring when using hbm.xml files. I changed some of my entites to annotations and the problem is solved. Parts of my hbm.xml file causing the problem: <hibernate-mapping package = "de.srs.pen.dao.base" default -access= "property" default -cascade= "none" default -lazy= " true " > < class name= "FormValue" table= "form_values" > <id name= "valueKey" type= "java.lang. Long " > <column name= "value_key" /> <generator class= " native " /> </id> <map name= "details" inverse= " true " cascade= "all" > <key> <column name= "value_key" not- null = " true " /> </key> <map-key type= "java.lang. Long " column= "detail_key" /> <one-to-many class= "FormValueDetail" /> </map> </ class& gt; </hibernate-mapping> <hibernate-mapping package = "de.srs.pen.dao.base" default -access= "property" default -cascade= "none" default -lazy= " true " > < class name= "FormValueDetail" table= "form_value_details" > <id name= "detailKey" type= "java.lang. Long " > <column name= "detail_key" /> <generator class= " native " /> </id> <many-to-one name= "value" class= "FormValue" fetch= "join" lazy= " false " foreign-key= "FK_018_value" > <column name= "value_key" not- null = " true " /> </many-to-one> </ class& gt; </hibernate-mapping> Annotated telations with problem solved: @Entity public class FormValue { @Id @Column(name = "value_key" ) @GeneratedValue(strategy = GenerationType.AUTO) private Long valueKey; @OneToMany(cascade = CascadeType.ALL, mappedBy = "value" ) @MapKey(name = "detailKey" ) private Map< Long , FormValueDetail> details = new HashMap< Long , FormValueDetail>(0); } @Entity public class FormValueDetail { @Id @Column(name = "detail_key") @GeneratedValue(strategy = GenerationType.AUTO) private Long detailKey; @ManyToOne @JoinColumn(name = "value_key") @ForeignKey(name = "FK_018_value") private FormValue value; } Maybe this helps finding the issue or someone else finding a workaround. Regards Markus Döring ( https://hibernate.atlassian.net/browse/HHH-9513#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-9513#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#100125- sha1:63ccdc5 )

4 years, 5 months

1
0
0 / 0

[JIRA] (HHH-7668) Wrong binding of @ManyToOne for non-PK associations

by Marco Bettiol (JIRA)

Marco Bettiol ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-7668 ( https://hibernate.atlassian.net/browse/HHH-7668?atlOrigin=eyJpIjoiOTAxYjE... ) Re: Wrong binding of @ManyToOne for non-PK associations ( https://hibernate.atlassian.net/browse/HHH-7668?atlOrigin=eyJpIjoiOTAxYjE... ) Hi, any update? ( https://hibernate.atlassian.net/browse/HHH-7668#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-7668#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#100125- sha1:63ccdc5 )

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)

4 years, 5 months

1
0
0 / 0

[JIRA] (HHH-13970) SQL Server needs special handling for Identity column inserts

by IT Support (JIRA)

IT Support ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTlhMTA4MGE2... ) / Sub-task ( https://hibernate.atlassian.net/browse/HHH-13970?atlOrigin=eyJpIjoiNTlhMT... ) HHH-13970 ( https://hibernate.atlassian.net/browse/HHH-13970?atlOrigin=eyJpIjoiNTlhMT... ) SQL Server needs special handling for Identity column inserts ( https://hibernate.atlassian.net/browse/HHH-13970?atlOrigin=eyJpIjoiNTlhMT... ) Change By: IT Support ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) SQL Server Identity inserts are different than in other databases, an error message is generated when the {{org.hibernate.dialect.SQLServerDialect}} is updated to return {{true}} from {{supportsCompositeNestedIdentityColumns()}}(examples from [sql-server-helper.com|http://www.sql-server-helper.com/error-messages/msg...]) {noformat}Server: Msg 339, Level 15, State 1, Line 1 DEFAULT or NULL are not allowed as explicit identity values.{noformat} The following INSERT statement will generate the error: {code:sql}INSERT INTO [dbo].[SuperHero] ( [SuperHeroID], [SuperHeroName], [FirstName], [LastName] ) VALUES ( DEFAULT, 'Superman', 'Clark', 'Kent' ) Msg 339, Level 16, State 1, Line 1 DEFAULT or NULL are not allowed as explicit identity values.{code} Similarly, the following INSERT statement will also generate the error: {code:sql}INSERT INTO [dbo].[SuperHero] ( [SuperHeroID], [SuperHeroName], [FirstName], [LastName] ) VALUES ( NULL, 'Spiderman', 'Peter', 'Parker' ) Msg 339, Level 16, State 1, Line 1 DEFAULT or NULL are not allowed as explicit identity values.{code} To avoid this error, when inserting into a table with an IDENTITY column, do not include the IDENTITY column in the INSERT statement and let SQL Server assign the value to this column for each row inserted to the table. {noformat}INSERT INTO [dbo].[SuperHero] ( [SuperHeroName], [FirstName], [LastName] ) VALUES ( 'Superman', 'Clark', 'Kent' ) INSERT INTO [dbo].[SuperHero] ( [SuperHeroName], [FirstName], [LastName] ) VALUES ( 'Spiderman', 'Peter', 'Parker' ){noformat} As such the Identity insert generation in the SQL Server Dialects remove the Identity column. [https://hibernate.atlassian.net/browse/HHH-9662|https://hibernate.atlassi...] reformulates how it all works and now the SQL Server Dialects need to be updated specially. ( https://hibernate.atlassian.net/browse/HHH-13970#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13970#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#100125- sha1:0a83519 )

4 years, 5 months

1
0
0 / 0

[JIRA] (HHH-13970) SQL Server needs special handling for Identity column inserts

by IT Support (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