August 2022 - hibernate-issues - Jboss List Archives

[JIRA] (HSEARCH-2366) Add an Elasticsearch mapping export tool

by Yoann Rodière (JIRA)

3 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4675) Use .and()/.or() rather than .bool() where possible in documentation and tests

by Yoann Rodière (JIRA)

3 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4591) Allow object projections on single-valued, flattened object fields with the Lucene backend

by Yoann Rodière (JIRA)

3 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4675) Use .and()/.or() rather than .bool() where possible in documentation and tests

by Yoann Rodière (JIRA)

3 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4616) Rename automatic indexing to something more explicit

by Yoann Rodière (JIRA)

3 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4676) Use .and() syntax by default with .where(BiFunction) and .nested() predicate?

by Yoann Rodière (JIRA)

3 years, 10 months

1
0
0 / 0

[JIRA] (HHH-15459) OPTIMISTIC_FORCE_INCREMENT and PESSIMISTIC_FORCE_INCREMENT update version more then once

by Fabian Köntopp (JIRA)

Fabian Köntopp ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6278292... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYzFhY2FjYTY2... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15459?atlOrigin=eyJpIjoiYzFhY2... ) HHH-15459 ( https://hibernate.atlassian.net/browse/HHH-15459?atlOrigin=eyJpIjoiYzFhY2... ) OPTIMISTIC_FORCE_INCREMENT and PESSIMISTIC_FORCE_INCREMENT update version more then once ( https://hibernate.atlassian.net/browse/HHH-15459?atlOrigin=eyJpIjoiYzFhY2... ) Issue Type: Bug Affects Versions: 5.6.10 Assignee: Unassigned Components: hibernate-core Created: 22/Aug/2022 05:05 AM Priority: Major Reporter: Fabian Köntopp ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6278292... ) When using this ( https://vladmihalcea.com/how-to-increment-the-parent-entity-version-whene... ) proposal from @Vlad Mihalcea, updating multiple fields from multiple childs in one transaction increases the version number not by one but by the number of changed child entities. My understanding is, that the version number should be updated only once for one transaction even if the OPTIMISTIC_FORCE_INCREMENT or PESSIMISTIC_FORCE_INCREMENT lock modes are used multiple times in it. ( https://hibernate.atlassian.net/browse/HHH-15459#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15459#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#100205- sha1:59a7aeb )

3 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4677) Rename .add(...) to .and(...)/.or(...) in "simple" boolean predicates

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiY2MxMzdj... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-4677?atlOrigin=eyJpIjoiY2M... ) HSEARCH-4677 ( https://hibernate.atlassian.net/browse/HSEARCH-4677?atlOrigin=eyJpIjoiY2M... ) Rename .add(...) to .and(...)/.or(...) in "simple" boolean predicates ( https://hibernate.atlassian.net/browse/HSEARCH-4677?atlOrigin=eyJpIjoiY2M... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Follows up on [https://hibernate.atlassian.net/browse/HSEARCH-4601|https://hibernate.atl...]. See the discussion [starting here|https://github.com/hibernate/hibernate-search/pull/3152#issuecomment...]: {quote}> And now, by reading the examples with lambdas, i.e. when the operator instantiation and the add operations are distant from one another, I'm wondering if such syntax isn't requiring an excessive cognitive load for casual readers to figure out what kind of operation this add is performing. I'd say the cognitive load would be reduced if the methods were to be more explicitly named {{and}} and {{or}}. That means getting back to the situation before you de-duplicated all the interfaces, then :) That might be clearer for long chains of {{.add()}}, but I find it strange to use {{and}}/{{or}} for the very first clause, and that would also feel very redundant, e.g. {{f.and().and( e1 ).and( e2 )}}. It would also prevent developers from writing "generic" functions that simply add multiple clauses to a boolean predicate, without knowing whether it's an {{and}} or an {{or}}; not a big deal, but worth mentioning. {quote} {quote} > In addition to making code more self-explanatory, having specific "{{add}}" methods would be less error-prone when different predicates are used in different {{with(...)}} constructs, as in "Example 228. Easily adding clauses dynamically using with(…) and the lambda syntax". That wouldn't make things less error-prone for {{and}}/{{and}} nesting though, e.g. {{f.and().and( ... ).and( f.nested().and( ... ).and( ... ) )}}. > For the forthcoming {{not}} predicate (HSEARCH-4645), renaming {{add}} to something like {{andNot}} may also be more explicit. To me that's one more reason to _not_ introduce and {{add}} syntax for {{not}}: make that predicate accept a _single_ inner clause and leave it at that. People can still nest an {{and}} predicate if they want to, and we can always try to "flatten" expressions under the hood with some tricks (which we'll probably need for the {{not()}} predicate anyway).{quote} ( https://hibernate.atlassian.net/browse/HSEARCH-4677#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4677#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#100205- sha1:59a7aeb )

3 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4677) Rename .add(...) to .and(...)/.or(...) in "simple" boolean predicates

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiOWMwOGM3... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-4677?atlOrigin=eyJpIjoiOWM... ) HSEARCH-4677 ( https://hibernate.atlassian.net/browse/HSEARCH-4677?atlOrigin=eyJpIjoiOWM... ) Rename .add(...) to .and(...)/.or(...) in "simple" boolean predicates ( https://hibernate.atlassian.net/browse/HSEARCH-4677?atlOrigin=eyJpIjoiOWM... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Follows up on [https://hibernate.atlassian.net/browse/HSEARCH-4601|https://hibernate.atl...]. See the discussion [starting here|https://github.com/hibernate/hibernate-search/pull/3152#issuecomment...]: {quote}> And now, by reading the examples with lambdas, i.e. when the operator instantiation and the add operations are distant from one another, I'm wondering if such syntax isn't requiring an excessive cognitive load for casual readers to figure out what kind of operation this add is performing. I'd say the cognitive load would be reduced if the methods were to be more explicitly named {{and}} and {{or}}. That means getting back to the situation before you de-duplicated all the interfaces, then :) That might be clearer for long chains of {{.add()}}, but I find it strange to use {{and}}/{{or}} for the very first clause, and that would also feel very redundant, e.g. {{f.and().and( e1 ).and( e2 )}}. It would also prevent developers from writing "generic" functions that simply add multiple clauses to a boolean predicate, without knowing whether it's an {{and}} or an {{or}}; not a big deal, but worth mentioning. {quote} Another solution {quote}> In addition to making code more self-explanatory, having specific "{{add}}" methods would be to alter conventions less error-prone when different predicates are used in different {{with(...)}} constructs , i as in "Example 228. e Easily adding clauses dynamically using with(…) and the lambda syntax". to use That wouldn't make things less error-prone for {{and}}/{{ or and }} as the name of the lambda parameter ( nesting though, e.g. {{f.and(). with( and -> (... ) }}). That would reduce the cognitive load when using {{with}}, at least, but obviously not when using the fluent syntax {{ and( f. and nested (). add and (...). add and (...) ) }}. That being said, I'd argue > For the fluent syntax is more suited forthcoming {{not}} predicate (HSEARCH-4645), renaming {{add}} to short chains; I’d use something like {{.with andNot }} for longer chains spanning many lines of code may also be more explicit. For now, I To me that ' ll use s one more reason to _not_ introduce and {{ and add }} / syntax for {{ or not }} as the name of the lambda parameter in tests : make that predicate accept a _single_ inner clause and examples leave it at that. People can still nest an {{and}} predicate if they want to , and I'll open another ticket we can always try to re-evaluate "flatten" expressions under the problem before hood with some tricks (which we release 6 'll probably need for the {{not()}} predicate anyway). 2.0.Final. {quote} ( https://hibernate.atlassian.net/browse/HSEARCH-4677#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4677#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#100205- sha1:59a7aeb )

3 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4677) Rename .add(...) to .and(...)/.or(...) in "simple" boolean predicates

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=eyJpIjoiMDdhZjY1... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-4677?atlOrigin=eyJpIjoiMDd... ) HSEARCH-4677 ( https://hibernate.atlassian.net/browse/HSEARCH-4677?atlOrigin=eyJpIjoiMDd... ) Rename .add(...) to .and(...)/.or(...) in "simple" boolean predicates ( https://hibernate.atlassian.net/browse/HSEARCH-4677?atlOrigin=eyJpIjoiMDd... ) Issue Type: Task Assignee: Unassigned Components: engine Created: 22/Aug/2022 04:48 AM Fix Versions: 6.2-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Follows up on https://hibernate.atlassian.net/browse/HSEARCH-4601 ( https://hibernate.atlassian.net/browse/HSEARCH-4601 ). See the discussion starting here ( https://github.com/hibernate/hibernate-search/pull/3152#issuecomment-1220... ) : > > > > > And now, by reading the examples with lambdas, i.e. when the operator > instantiation and the add operations are distant from one another, I'm > wondering if such syntax isn't requiring an excessive cognitive load for > casual readers to figure out what kind of operation this add is > performing. I'd say the cognitive load would be reduced if the methods > were to be more explicitly named and and or. > > > > That means getting back to the situation before you de-duplicated all the > interfaces, then That might be clearer for long chains of.add() , but I > find it strange to use and / or for the very first clause, and that would > also feel very redundant, e.g. f.and().and( e1 ).and( e2 ). It would also > prevent developers from writing "generic" functions that simply add > multiple clauses to a boolean predicate, without knowing whether it's an and > or an or ; not a big deal, but worth mentioning. > > > > Another solution would be to alter conventions, i.e. to use and / or as the > name of the lambda parameter (e.g. f.and().with( and -> ... ) ). That would > reduce the cognitive load when using with , at least, but obviously not > when using the fluent syntax f.and().add(...).add(...). That being said, > I'd argue the fluent syntax is more suited to short chains; I’d use.with for > longer chains spanning many lines of code. > > > > For now, I'll use and / or as the name of the lambda parameter in tests and > examples, and I'll open another ticket to re-evaluate the problem before > we release 6.2.0.Final. > > ( https://hibernate.atlassian.net/browse/HSEARCH-4677#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4677#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#100205- sha1:59a7aeb )

3 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4642) Upgrade build dependencies to the latest version

by Yoann Rodière (JIRA)

3 years, 10 months

1
0
0 / 0

[JIRA] (HHH-15455) User Guide Contains a reference to hibernate-ehcache, no longer supported

by Andrea Boriero (JIRA)

3 years, 10 months

1
0
0 / 0

[JIRA] (HHH-15156) The param names auto-generated when build the JPAQuery are duplicated.

by Andrea Boriero (JIRA)

Andrea Boriero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15156 ( https://hibernate.atlassian.net/browse/HHH-15156?atlOrigin=eyJpIjoiOTMxMD... ) Re: The param names auto-generated when build the JPAQuery are duplicated. ( https://hibernate.atlassian.net/browse/HHH-15156?atlOrigin=eyJpIjoiOTMxMD... ) Hi Chen Wei ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) , can you check if this has been resolved in 5.6.9.Final? Thanks a lot! ( https://hibernate.atlassian.net/browse/HHH-15156#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15156#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#100205- sha1:59a7aeb )

3 years, 10 months

1
0
0 / 0

[JIRA] (HHH-15453) java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null

by Andrea Boriero (JIRA)

3 years, 10 months

1
0
0 / 0

[JIRA] (HHH-15458) Interpret String with JSON type code as plain JSON

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiN2EzYjk0OGQ4... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15458?atlOrigin=eyJpIjoiN2EzYj... ) HHH-15458 ( https://hibernate.atlassian.net/browse/HHH-15458?atlOrigin=eyJpIjoiN2EzYj... ) Interpret String with JSON type code as plain JSON ( https://hibernate.atlassian.net/browse/HHH-15458?atlOrigin=eyJpIjoiN2EzYj... ) Issue Type: Improvement Affects Versions: 6.1.2 Assignee: Unassigned Components: hibernate-core Created: 22/Aug/2022 02:05 AM Priority: Major Reporter: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) When annotating a String field with @JdbcTypeCode(SqlTypes.JSON) we currently serialize the string to JSON i.e. when given {{ {"abc": "def"} }} we persist {{ {\"abc\": \"def\"} }}which is a JSON serialized string. We should interpret a String field with this type code as plain JSON and skip serialization/deserialization. ( https://hibernate.atlassian.net/browse/HHH-15458#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15458#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#100205- sha1:59a7aeb )

3 years, 10 months

1
0
0 / 0

[JIRA] (HHH-15457) Could not resolve attribute "xx" of generic mapped superclass in criteria queries

by Çağatay Kalan (JIRA)

Çağatay Kalan ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15457 ( https://hibernate.atlassian.net/browse/HHH-15457?atlOrigin=eyJpIjoiYmQxOD... ) Re: Could not resolve attribute "xx" of generic mapped superclass in criteria queries ( https://hibernate.atlassian.net/browse/HHH-15457?atlOrigin=eyJpIjoiYmQxOD... ) With further investigation, I understood that this is due to type erasure so I found another way where I use abstract getter/setters on the mapped superclass and declare the fields on the derived entity class. Sorry for bothering. ( https://hibernate.atlassian.net/browse/HHH-15457#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15457#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#100205- sha1:5460ff5 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15457) Could not resolve attribute "xx" of generic mapped superclass in criteria queries

by Çağatay Kalan (JIRA)

Çağatay Kalan ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMWQ5ZmNmZmFi... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15457?atlOrigin=eyJpIjoiMWQ5Zm... ) HHH-15457 ( https://hibernate.atlassian.net/browse/HHH-15457?atlOrigin=eyJpIjoiMWQ5Zm... ) Could not resolve attribute "xx" of generic mapped superclass in criteria queries ( https://hibernate.atlassian.net/browse/HHH-15457?atlOrigin=eyJpIjoiMWQ5Zm... ) Issue Type: Bug Affects Versions: 6.1.1 Assignee: Unassigned Components: hibernate-core, metamodel Created: 20/Aug/2022 22:24 PM Environment: Mac OS, JDK 17, Hibernate Core 6.1.1 Final Priority: Major Reporter: Çağatay Kalan ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I have the following generic entity setup. @Entity open class User : DefaultJpaUser<TestUser, TestUserRole>() { @NotBlank override fun getUsername(): String? { return super.getUsername() } } @Entity @Getter @Setter open class TestUserRole : DefaultJpaUserRole<TestUser, TestUserRole>() { var modified: Instant? = null} public abstract class DefaultJpaUser< U extends DefaultJpaUser<U, UR>, UR extends DefaultJpaUserRole<U, UR>> extends JpaUser<Long, Long, DefaultJpaRole, UR, U> { } public abstract class DefaultJpaUserRole< U extends DefaultJpaUser<U, UR>, UR extends DefaultJpaUserRole<U, UR>> extends JpaUserRole<Long, Long, DefaultJpaRole, U, UR> { } @Getter @Setter @NoArgsConstructorpublic class JpaUserRole< UID, RID, R extends JpaRole<RID>, U extends JpaUser<UID, RID, R, UR, U>, UR extends JpaUserRole<UID, RID, R, U, UR>> { private UserRoleId<UID, RID> id = new UserRoleId<>(); @NotNull @ManyToOne @MapsId("userId") private U user; @NotNull @ManyToOne @MapsId("roleId") private R role; public JpaUserRole(UserRoleId<UID, RID> id) { this.id = id; } @Embeddable @Getter @Setter @NoArgsConstructor @AllArgsConstructor public static class UserRoleId<UID, RID> implements Serializable { @Serial private static final long serialVersionUID = 4710225845169939700L; private UID userId; private RID roleId; } } public class JpaUser<UID, RID, R extends JpaRole<RID>, UR extends JpaUserRole<UID, RID, R, U, UR>, U extends JpaUser<UID, RID, R, UR, U>> implements User<UID> { UID id; String username; String password; String email; Boolean emailConfirmed; Set<UR> roles = new HashSet<>(); public Set<UR> getRoles() { return roles; } } And I am trying to execute this criteria query: var cb = entityManager.getCriteriaBuilder(); var q = cb.createQuery(Tuple.class); var root = q.from(userRoleClass); var userJoin = root.join("user"); q.where(cb.equal(userJoin.get("id"), user.getId())); q.select(root.get("id")); return entityManager.createQuery(q).getResultList() .stream().map(row -> row.get(0, Long.class).toString()).collect(Collectors.toList()); I get “could not resolve attribute id on JpaUserRole” error. Same issue occurs if I join with “role” and query a role field. I am not sure but this may be due to Hibernate resolving members from the declaring type (JpaUserRole) instead of the persistent type (TestUserRole) I traced the issue until “ org.hibernate.metamodel.internal. normalMemberResolver where the member is resolved from the declaring type but could not go further. Maybe there is no solution due to type erasure. I just wanted to learn if what I am trying to do is possible. Sorry that I have both Kotlin and Java code in the same issue 🙂 ( https://hibernate.atlassian.net/browse/HHH-15457#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15457#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#100205- sha1:5460ff5 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15456) SQLiteDialect - supportsInsertSelectIdentity

by Gwenael Treguier (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HBX-2387) Update version identifier to 6.1.2-SNAPSHOT

by Koen Aers (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HBX-2391) Update version identifier to 6.1.2.Final

by Koen Aers (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HBX-2391) Update version identifier to 6.1.2.Final

by Koen Aers (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HBX-2389) Update Hibernate ORM Dependency to Version 6.1.2.Final

by Koen Aers (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14948) Metamodel imports cache increases indefinitely for dynamically generated HQL aliases eventually leading to an OOM

by Réda Housni Alaoui (JIRA)

Réda Housni Alaoui ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14948 ( https://hibernate.atlassian.net/browse/HHH-14948?atlOrigin=eyJpIjoiNGQ4ND... ) Re: Metamodel imports cache increases indefinitely for dynamically generated HQL aliases eventually leading to an OOM ( https://hibernate.atlassian.net/browse/HHH-14948?atlOrigin=eyJpIjoiNGQ4ND... ) I was already aware of the explanation of https://github.com/hibernate/hibernate-orm/pull/4411#issuecomment-989304639 ( https://github.com/hibernate/hibernate-orm/pull/4411#issuecomment-989304639 ). It still did not make sense to me. What was the cost of adding at least a configuration? Why not keep the default value for 5.6.x ? Why not adding this to the release note as a breaking change with all the blinking lights? I am sure, the use case reported here is only representative of a small minority of Hibernate users. > > > > And if people ask nicely > > If I appeared not nice, it is probably because I think the decision derived from the explanation is a mistake. https://hibernate.atlassian.net/browse/HHH-15100 ( https://hibernate.atlassian.net/browse/HHH-15100 ) was created by someone else on march and received zero answer. Moreover, I am not among the kind of people who asks OSS maintainers then wait. I immediatly created a pull request yesterday for https://hibernate.atlassian.net/browse/HHH-15100 ( https://hibernate.atlassian.net/browse/HHH-15100 ). > > > > Generally speaking, I would suggest that if your map is growing so much, > it would be interesting to try to avoid the root cause. Are you generating > many queries dynamicaly via string manipulation? Why are all these tokens > different? Or are you able to trigger this in another way? > > The map contains 1318 entries on application startup before any query. The keys are either JPA entities simple name (like “product” for “Product”) or full qualified name (like “org.example.Product”). We don’t use any query string. But we have a massive usage of JPA CriteriaQuery generating tokens like “from” or “generatedAlias0.product”. Since the current fix, those false positives never make it to the map because of the 1000 entries limit. So each false positive generate one call to Class.forName(). Given the knowledge we had on December 2021 and potential performance implication on huge applications (the ones precisely needing performance optimization), I will keep saying that this ticket was very badly managed. This happens to everybody so please do not hold a grudge against me if you don’t agree. ( https://hibernate.atlassian.net/browse/HHH-14948#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14948#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#100205- sha1:5460ff5 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14948) Metamodel imports cache increases indefinitely for dynamically generated HQL aliases eventually leading to an OOM

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14948 ( https://hibernate.atlassian.net/browse/HHH-14948?atlOrigin=eyJpIjoiOGFjOW... ) Re: Metamodel imports cache increases indefinitely for dynamically generated HQL aliases eventually leading to an OOM ( https://hibernate.atlassian.net/browse/HHH-14948?atlOrigin=eyJpIjoiOGFjOW... ) The explanation is here: https://github.com/hibernate/hibernate-orm/pull/4411#issuecomment-989304639 ( https://github.com/hibernate/hibernate-orm/pull/4411#issuecomment-989304639 ). As mentioned, we could introduce a configurable threshold, if there’s evidence of this being necessary. And if people ask nicely. Generally speaking, I would suggest that if your map is growing so much, it would be interesting to try to avoid the root cause. Are you generating many queries dynamicaly via string manipulation? Why are all these tokens different? Or are you able to trigger this in another way? ( https://hibernate.atlassian.net/browse/HHH-14948#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14948#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#100205- sha1:5460ff5 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4380) Upgrade to maven-assembly-plugin 3.4.2

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4380) Upgrade to maven-assembly-plugin 3.3+

by Automation for Jira (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15453) java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null

by Andrea Boriero (JIRA)

Andrea Boriero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15453 ( https://hibernate.atlassian.net/browse/HHH-15453?atlOrigin=eyJpIjoiOTM3Yj... ) Re: java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null ( https://hibernate.atlassian.net/browse/HHH-15453?atlOrigin=eyJpIjoiOTM3Yj... ) Thanks Puhong You ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) , I managed to reproduce the issue,working on a solution! ( https://hibernate.atlassian.net/browse/HHH-15453#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15453#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#100205- sha1:5460ff5 )

3 years, 11 months

1
0
0 / 0

[JIRA] (WEBSITE-630) Remove a.mazurov@indexatum.com from hibernate JIRA

by Sanne Grinovero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15453) java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null

by Puhong You (JIRA)

Puhong You ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15453 ( https://hibernate.atlassian.net/browse/HHH-15453?atlOrigin=eyJpIjoiY2MyMW... ) Re: java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null ( https://hibernate.atlassian.net/browse/HHH-15453?atlOrigin=eyJpIjoiY2MyMW... ) Hi, Andrea, I oversimplified the test case when I initially reported this bug. I apologize for my mistake. The missing piece is the Agency object. The object hierarchy is like this: each Agency can have 0 or more Users, and each User must belong to an Agency and each user can have 0 or more roles. Here is the Agency table: AGENCY table: Columns: AGENCY_ID integer not null primary key, AGENCY_NAME varchar(256) not null, Rows: (100, 'Test Agency'); USER table (add the AGENCY_ID column): Columns: USER_ID integer not null primary key, USER_NAME varchar(256) not null, AGENCY_ID integer not null, Rows: (1, 'Ann', 100); (2, 'Bob', 100); Here is the Agency entity bean: @Entity@Table(name = "AGENCY" , schema = "TEST" ) public class Agency { private Integer agencyId = null ; private String agencyName = null ; private Set<User> users; @Id @Column(name = "AGENCY_ID" ) public Integer getAgencyId() { return agencyId; } public void setAgencyId( Integer roleId) { this.agencyId = roleId; } @Column(name = "AGENCY_NAME" ) public String getAgencyName() { return agencyName; } public void setAgencyName( String roleName) { this.agencyName = roleName; } @OneToMany(cascade = CascadeType.ALL, fetch = FetchType.EAGER, mappedBy = "agency" ) @Fetch(FetchMode.SELECT) public Set<User> getUsers() { return users; } public void setUsers(Set<User> users) { this.users = users; } @Override public boolean equals( Object o) { if ( this == o) { return true ; } if (o == null || getClass() != o.getClass()) { return false ; } Agency that = (Agency) o; return Objects.equals(agencyId, that.agencyId) && Objects.equals(agencyName, that.agencyName); } @Override public int hashCode() { return Objects.hash(agencyId, agencyName); } Here are the updated User entity bean: @Entity@Table(name = "USER" , schema = "TEST" ) public class User { private Integer userId = null ; private String userName = null ; private Agency agency = null ; private Set<Role> roles = null ; @Id @Column(name = "CRIS_USER_ID" ) public Integer getUserId() { return userId; } public void setUserId( Integer userId) { this.userId = userId; } @Column(name = "IDP_USER_ID" ) public String getUserName() { return userName; } public void setUserName( String userName) { this.userName = userName; } @ManyToOne @JoinColumn(name = "AGENCY_ID" ) public Agency getAgency() { return agency; } public void setAgency(Agency agency) { this.agency = agency; } @ManyToMany(cascade = CascadeType.PERSIST, fetch = FetchType.EAGER) @JoinTable( name = "UM_USER_ROLE" , joinColumns = @JoinColumn(name = "CRIS_USER_ID" ), inverseJoinColumns = @JoinColumn(name = "ROLE_ID" )) @Fetch(FetchMode.SUBSELECT) public Set<Role> getRoles() { return roles; } public void setRoles(Set<Role> roles) { this.roles = roles; } I am able to reproduce the reported java.lang.NullPointerException. ( https://hibernate.atlassian.net/browse/HHH-15453#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15453#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#100205- sha1:6417f3f )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15100) Limitation of metamodel imports cache causes severe performance drops in large projects

by Réda Housni Alaoui (JIRA)

Réda Housni Alaoui ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15100 ( https://hibernate.atlassian.net/browse/HHH-15100?atlOrigin=eyJpIjoiZmM0Mz... ) Re: Limitation of metamodel imports cache causes severe performance drops in large projects ( https://hibernate.atlassian.net/browse/HHH-15100?atlOrigin=eyJpIjoiZmM0Mz... ) Pull request opened at https://github.com/hibernate/hibernate-orm/pull/5219 ( https://github.com/hibernate/hibernate-orm/pull/5219 ) ( https://hibernate.atlassian.net/browse/HHH-15100#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15100#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#100205- sha1:6417f3f )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14948) Metamodel imports cache increases indefinitely for dynamically generated HQL aliases eventually leading to an OOM

by Réda Housni Alaoui (JIRA)

Réda Housni Alaoui ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14948 ( https://hibernate.atlassian.net/browse/HHH-14948?atlOrigin=eyJpIjoiYzkzMm... ) Re: Metamodel imports cache increases indefinitely for dynamically generated HQL aliases eventually leading to an OOM ( https://hibernate.atlassian.net/browse/HHH-14948?atlOrigin=eyJpIjoiYzkzMm... ) For information our imports map contains 1318 entries without any negative entry. So this fix pretty much disabled the negative cache. ( https://hibernate.atlassian.net/browse/HHH-14948#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14948#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#100205- sha1:6417f3f )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14948) Metamodel imports cache increases indefinitely for dynamically generated HQL aliases eventually leading to an OOM

by Réda Housni Alaoui (JIRA)

Réda Housni Alaoui ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14948 ( https://hibernate.atlassian.net/browse/HHH-14948?atlOrigin=eyJpIjoiMjEwOT... ) Re: Metamodel imports cache increases indefinitely for dynamically generated HQL aliases eventually leading to an OOM ( https://hibernate.atlassian.net/browse/HHH-14948?atlOrigin=eyJpIjoiMjEwOT... ) The added limit caused a critical and hard to trace performance issue on our major application. I can’t fathom how this kind of breaking change could have been added without a configurable limit and without waiting for a major version … ( https://hibernate.atlassian.net/browse/HHH-14948#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14948#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#100205- sha1:6417f3f )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15455) User Guide Contains a reference to hibernate-ehcache, no longer supported

by Andrea Boriero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15455) User Guide Contains a reference to hibernate-ehcache, no longer supported

by Mike Conner (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (WEBSITE-630) Remove a.mazurov@indexatum.com from hibernate JIRA

by Alexander Mazurov (JIRA)

Alexander Mazurov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Websites ( https://hibernate.atlassian.net/browse/WEBSITE?atlOrigin=eyJpIjoiNDc5YTg0... ) / Task ( https://hibernate.atlassian.net/browse/WEBSITE-630?atlOrigin=eyJpIjoiNDc5... ) WEBSITE-630 ( https://hibernate.atlassian.net/browse/WEBSITE-630?atlOrigin=eyJpIjoiNDc5... ) Remove a.mazurov(a)indexatum.com from hibernate JIRA ( https://hibernate.atlassian.net/browse/WEBSITE-630?atlOrigin=eyJpIjoiNDc5... ) Issue Type: Task Assignee: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: JIRA Created: 18/Aug/2022 04:50 AM Priority: Trivial Reporter: Alexander Mazurov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Dear administrators of the Hibernate’s JIRA. Could you, please, remove my account from Hibernate JIRA? To remove a user: * From your site's *Administration* , select *Users*. * From the user you want to remove, select *Show details* from the *Actions* column. You may need to click the dropdown to see this option. * On the user details screen, select the *3 dot icon* and then select *Remove* user. ( https://hibernate.atlassian.net/browse/WEBSITE-630#add-comment?atlOrigin=... ) Add Comment ( https://hibernate.atlassian.net/browse/WEBSITE-630#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#100205- sha1:6417f3f )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15452) Predicate add expression results in UnsupportedOperationException

by Andrea Boriero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15454) Primitive type requested from tuple throws exception

by Tassilo Karge (JIRA)

Tassilo Karge ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f50ce4... ) *commented* on HHH-15454 ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiNmVjMz... ) Re: Primitive type requested from tuple throws exception ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiNmVjMz... ) Would be solved for 5.6 with this PR: https://github.com/hibernate/hibernate-orm/pull/5218 ( https://github.com/hibernate/hibernate-orm/pull/5218 ) ( https://hibernate.atlassian.net/browse/HHH-15454#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15454#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#100205- sha1:6417f3f )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15440) @OneToOne and @OptimisticLock(excluded = true) not working correctly

by Andrea Boriero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4500) Provide more context in error messages about fields with invalid type (value vs. object)

by Automation for Jira (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4656) Provide more guidance in error messages when calling "retrieve-by-name" methods

by Automation for Jira (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15454) Primitive type requested from tuple throws exception

by Tassilo Karge (JIRA)

Tassilo Karge ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f50ce4... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNjIyNTA5Y2Jj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiNjIyNT... ) HHH-15454 ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiNjIyNT... ) Primitive type requested from tuple throws exception ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiNjIyNT... ) Change By: Tassilo Karge ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f50ce4... ) The Tuple subclasses seem to be incapable of returning primitive types. That manifests in an exception, for example in the usecase described below: The function getJavaType() on Attribute returns the type of the field it represents in the entity. This may be a primitive type. However, that leads to inconsistencies, for example when selecting that attribute in a tuple query. See the related test case for an example. Judging from the changes in this PR; [https://github.com/hibernate/hibernate-orm/pull/4784|https://github.com/h...] the metamodel is intended to return primitive types. Therefore, the tuple is what needs to be fixed. ( https://hibernate.atlassian.net/browse/HHH-15454#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15454#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#100205- sha1:6417f3f )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15454) Primitive type requested from tuple throws exception

by Tassilo Karge (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-9087) Version increment on joined-subclass uses incorrect column names

by Dylan Koby (JIRA)

Dylan Koby ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c7e3f0... ) *commented* on HHH-9087 ( https://hibernate.atlassian.net/browse/HHH-9087?atlOrigin=eyJpIjoiMjA2ZjI... ) Re: Version increment on joined-subclass uses incorrect column names ( https://hibernate.atlassian.net/browse/HHH-9087?atlOrigin=eyJpIjoiMjA2ZjI... ) Hi, HHH-5237 ( https://hibernate.atlassian.net/browse/HHH-5237 ) Closed proposed a one line patch. Any chance that it will be considered ? Thank you. ( https://hibernate.atlassian.net/browse/HHH-9087#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-9087#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#100205- sha1:6417f3f )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15454) Primitive type returned by metamodel in combination with tuple query leads to exceptions

by Tassilo Karge (JIRA)

Tassilo Karge ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f50ce4... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNjMyZWJmNzc1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiNjMyZW... ) HHH-15454 ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiNjMyZW... ) Primitive type returned by metamodel in combination with tuple query leads to exceptions ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiNjMyZW... ) Change By: Tassilo Karge ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f50ce4... ) The function getJavaType() on Attribute returns the type of the field it represents in the entity. This may be a primitive type. However, that leads to inconsistencies, for example when selecting that attribute in a tuple query. See the related test case for an example. Reading Judging from the title, changes in this issue might have been fixed on the master by the following PR : ; [https://github.com/hibernate/hibernate-orm/pull/4784|https://github.com/h...] If that is the case metamodel is intended to return primitive types. Therefore , it just the tuple is what needs to be backported to the current 5 fixed. x version. ( https://hibernate.atlassian.net/browse/HHH-15454#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15454#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#100205- sha1:6417f3f )

3 years, 11 months

1
0
0 / 0

[JIRA] (WEBSITE-629) Broken link: https://hibernate.org/hib_docs/reference/html/components.html#components-s2-4

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15454) Primitive type returned by metamodel in combination with tuple query leads to exceptions

by Tassilo Karge (JIRA)

Tassilo Karge ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f50ce4... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMGY5MmU1NTM4... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiMGY5Mm... ) HHH-15454 ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiMGY5Mm... ) Primitive type returned by metamodel in combination with tuple query leads to exceptions ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiMGY5Mm... ) Change By: Tassilo Karge ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f50ce4... ) The function getJavaType() on Attribute returns the type of the field it represents in the entity. This may be a primitive type. However, that leads to inconsistencies, for example when selecting that attribute in a tuple query. See the related test case for an example. I believe Reading the title, this issue might have been fixed on the master by the following PR: [https://github.com/hibernate/hibernate-orm/pull/4784|https://github.com/h...] If that is the case, it just needs to be backported to the current 5.x version. ( https://hibernate.atlassian.net/browse/HHH-15454#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15454#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#100205- sha1:6417f3f )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15454) Primitive type returned by metamodel in combination with tuple query leads to exceptions

by Tassilo Karge (JIRA)

Tassilo Karge ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f50ce4... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiN2ZmMGEzMzMz... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiN2ZmMG... ) HHH-15454 ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiN2ZmMG... ) Primitive type returned by metamodel in combination with tuple query leads to exceptions ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiN2ZmMG... ) Issue Type: Bug Affects Versions: 5.6.8 Assignee: Unassigned Components: hibernate-core, metamodel Created: 18/Aug/2022 01:28 AM Priority: Major Reporter: Tassilo Karge ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f50ce4... ) The function getJavaType() on Attribute returns the type of the field it represents in the entity. This may be a primitive type. However, that leads to inconsistencies, for example when selecting that attribute in a tuple query. See the related test case for an example. I believe this issue might have been fixed on the master by the following PR: https://github.com/hibernate/hibernate-orm/pull/4784 ( https://github.com/hibernate/hibernate-orm/pull/4784 ) If that is the case, it just needs to be backported to the current 5.x version. ( https://hibernate.atlassian.net/browse/HHH-15454#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15454#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#100205- sha1:6417f3f )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15440) @OneToOne and @OptimisticLock(excluded = true) not working correctly

by Andrea Boriero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (WEBSITE-629) Broken link: https://hibernate.org/hib_docs/reference/html/components.html#components-s2-4

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on WEBSITE-629 ( https://hibernate.atlassian.net/browse/WEBSITE-629?atlOrigin=eyJpIjoiZjgz... ) Re: Broken link: https://hibernate.org/hib_docs/reference/html/components.html#components-... ( https://hibernate.atlassian.net/browse/WEBSITE-629?atlOrigin=eyJpIjoiZjgz... ) Unfortunately there’s no archive/equivalent in the current website. I’ll just have this URL redirect to https://hibernate.org/orm/documentation/obsolete ( https://hibernate.org/orm/documentation/obsolete ) ( https://hibernate.atlassian.net/browse/WEBSITE-629#add-comment?atlOrigin=... ) Add Comment ( https://hibernate.atlassian.net/browse/WEBSITE-629#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#100205- sha1:6417f3f )

3 years, 11 months

1
0
0 / 0

[JIRA] (WEBSITE-629) Broken link: https://hibernate.org/hib_docs/reference/html/components.html#components-s2-4

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on WEBSITE-629 ( https://hibernate.atlassian.net/browse/WEBSITE-629?atlOrigin=eyJpIjoiMTI0... ) Re: Broken link: https://hibernate.org/hib_docs/reference/html/components.html#components-... ( https://hibernate.atlassian.net/browse/WEBSITE-629?atlOrigin=eyJpIjoiMTI0... ) Found on the wayback machine: http://web.archive.org/web/20031113041621/http://www.hibernate.org/hib_do... ( http://web.archive.org/web/20031113041621/http://www.hibernate.org/hib_do... ) ( https://hibernate.atlassian.net/browse/WEBSITE-629#add-comment?atlOrigin=... ) Add Comment ( https://hibernate.atlassian.net/browse/WEBSITE-629#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#100205- sha1:6417f3f )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15453) java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null

by Andrea Boriero (JIRA)

Andrea Boriero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15453 ( https://hibernate.atlassian.net/browse/HHH-15453?atlOrigin=eyJpIjoiZjU4ND... ) Re: java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null ( https://hibernate.atlassian.net/browse/HHH-15453?atlOrigin=eyJpIjoiZjU4ND... ) Hi Puhong You ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) , tried also inserting directly the values in the db but still not able to reproduce the problem 😞 Can you please share your reproducer (on github or as a zip file) so I can investigate it? Thanks a lot ( https://hibernate.atlassian.net/browse/HHH-15453#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15453#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#100205- sha1:6417f3f )

3 years, 11 months

1
0
0 / 0

[JIRA] (WEBSITE-629) Broken link: https://hibernate.org/hib_docs/reference/html/components.html#components-s2-4

by Website Form collector (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15453) java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null

by Puhong You (JIRA)

Puhong You ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15453 ( https://hibernate.atlassian.net/browse/HHH-15453?atlOrigin=eyJpIjoiZWY1NW... ) Re: java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null ( https://hibernate.atlassian.net/browse/HHH-15453?atlOrigin=eyJpIjoiZWY1NW... ) Hi, Andrea, thanks for looking into this. Your setup looks almost identical to mine. The only difference I can think of is that in my case I did not create the User and Role instances in the my test, so when I query for the user, the user object does not exist in session cache and Hibernate has to construct the user object from the database. Could it be that since you create the users in the test so the user objects are served from the session cache in your test? ( https://hibernate.atlassian.net/browse/HHH-15453#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15453#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15453) java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null

by Andrea Boriero (JIRA)

Andrea Boriero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15453 ( https://hibernate.atlassian.net/browse/HHH-15453?atlOrigin=eyJpIjoiN2NmMT... ) Re: java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null ( https://hibernate.atlassian.net/browse/HHH-15453?atlOrigin=eyJpIjoiN2NmMT... ) Hi Puhong You ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) , I tried to reproduce your error with the code you provided but without any success. This is the test i created @DomainModel( annotatedClasses = { FetchModeSubselectTest.User.class, FetchModeSubselectTest.Role.class } ) @SessionFactory @TestForIssue(jiraKey = "HHH-15453" ) public class FetchModeSubselectTest { @BeforeEach public void setUp(SessionFactoryScope scope) { scope.inTransaction( session -> { User user = new User(); user.setUserId( 1 ); user.setUserName( "Ann" ); User user2 = new User(); user2.setUserId( 2 ); user2.setUserName( "Bob" ); Role manager = new Role(); manager.setRoleId( 1 ); manager.setRoleName( "manager" ); Role developer = new Role(); developer.setRoleId( 2 ); developer.setRoleName( "developer" ); session.persist( user ); session.persist( user2 ); session.persist( manager ); session.persist( developer ); user.addRole( manager ); } ); } @Test public void testSelect(SessionFactoryScope scope) { scope.inSession( session -> { List<User> userList = session.createQuery( "FROM User WHERE userId = 2" , User.class ).list(); assertThat( userList.size() ).isEqualTo( 1 ); assertThat( userList.get( 0 ).getRoles().size() ).isEqualTo( 0 ); } ); } @Entity(name = "User" ) @Table(name = "USER_TABLE" ) public static class User { private Integer userId = null ; private String userName = null ; private Set<Role> roles = null ; @Id @Column(name = "USER_ID" ) public Integer getUserId() { return userId; } public void setUserId( Integer userId) { this.userId = userId; } @Column(name = "USER_NAME" ) public String getUserName() { return userName; } public void setUserName( String userName) { this.userName = userName; } @ManyToMany(cascade = CascadeType.PERSIST, fetch = FetchType.EAGER) @JoinTable( name = "USER_ROLE" , joinColumns = @JoinColumn(name = "USER_ID" ), inverseJoinColumns = @JoinColumn(name = "ROLE_ID" )) @Fetch(FetchMode.SUBSELECT) public Set<Role> getRoles() { return roles; } public void setRoles(Set<Role> roles) { this.roles = roles; } public void addRole(Role role) { if ( roles == null ) { roles = new HashSet<>(); } roles.add( role ); } @Override public boolean equals( Object o) { if ( this == o ) { return true ; } if ( o == null || getClass() != o.getClass() ) { return false ; } User user = (User) o; return Objects.equals( userId, user.userId ) && Objects.equals( userName, user.userName ) && Objects.equals( roles, user.roles ); } @Override public int hashCode() { return Objects.hash( userId, userName, roles ); } } @Entity(name = "Role" ) @Table(name = "ROLE_TABLE" ) public static class Role { private Integer roleId = null ; private String roleName = null ; @Id @Column(name = "ROLE_ID" ) public Integer getRoleId() { return roleId; } public void setRoleId( Integer roleId) { this.roleId = roleId; } @Column(name = "ROLE_NAME" ) public String getRoleName() { return roleName; } public void setRoleName( String roleName) { this.roleName = roleName; } @Override public boolean equals( Object o) { if ( this == o ) { return true ; } if ( o == null || getClass() != o.getClass() ) { return false ; } Role role = (Role) o; return Objects.equals( roleId, role.roleId ) && Objects.equals( roleName, role.roleName ); } @Override public int hashCode() { return Objects.hash( roleId, roleName ); } } } am I missing something? ( https://hibernate.atlassian.net/browse/HHH-15453#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15453#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15453) java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null

by Andrea Boriero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15452) Predicate add expression results in UnsupportedOperationException

by Andrea Boriero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-13170) GORM: Challenges migrating away from deprecated Criteria API

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13170 ( https://hibernate.atlassian.net/browse/HHH-13170?atlOrigin=eyJpIjoiNzdjNj... ) Re: GORM: Challenges migrating away from deprecated Criteria API ( https://hibernate.atlassian.net/browse/HHH-13170?atlOrigin=eyJpIjoiNzdjNj... ) So let me point you to APIs through which you can implement the following: * Use jakarta.persistence.criteria.CriteriaBuilder#between}}and {{jakarta.persistence.criteria.CriteriaBuilder#coalesce * Use jakarta.persistence.criteria.CriteriaBuilder#lessThanOrEqualTo and jakarta.persistence.criteria.CriteriaBuilder#sum with unsafe casts (please create an issue for improving this by adding new methods to HibernateCriteriaBuilder ) * This is just a regular subquery. Unless you don’t have entities mapped for the tables, you can just use the regular CriteriaQuery#subquery and jakarta.persistence.criteria.CriteriaBuilder#in as well as jakarta.persistence.criteria.CriteriaBuilder#not APIs For the other examples, follow the same advice as in 3. and just use the subquery APIs. I know the JPA Criteria API is not as nice as simply writing a String, but overall, the end result will be easily portable, not only across JPA providers, but also across databases. ( https://hibernate.atlassian.net/browse/HHH-13170#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13170#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15449) @ManyToOne associations not loaded correctly with default EAGER and batch fetch property set when using TypedQuery.resultStream

by Andrea Boriero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-13170) GORM: Challenges migrating away from deprecated Criteria API

by Eduardo Simioni (JIRA)

Eduardo Simioni ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13170 ( https://hibernate.atlassian.net/browse/HHH-13170?atlOrigin=eyJpIjoiMzhhMz... ) Re: GORM: Challenges migrating away from deprecated Criteria API ( https://hibernate.atlassian.net/browse/HHH-13170?atlOrigin=eyJpIjoiMzhhMz... ) Some examples: 1) criteria.add(Restrictions.sqlRestriction( " ? between starts_on and IFNULL(ends_on, current_date)" , getTodayNoTime(), CalendarType.INSTANCE)); 2) criteria.add(Restrictions.sqlRestriction( "CAST(TIMESTAMPADD(SQL_TSI_DAY, -({alias}.days_before_send), {alias}.next_on) as DATE) <= ?" , getTodayNoTime(), CalendarDateType.INSTANCE)); 3) criteria.add(Restrictions.sqlRestriction( "this_.id not in(select cgc.customer_id from customer_group cg inner join customer_group_customer cgc on(cg.id = gc.customer_group_id) where cg.account_id = this_.account_id)" )); 4) Criteria criteria = createEntityCriteriaBypassAccount(); criteria.add(Restrictions.sqlRestriction( "this_.id NOT IN (SELECT daa.digital_account_id FROM digital_account_attribute daa WHERE daa.name " + "= ?) AND this_.id IN (SELECT DISTINCT p.payee_id FROM payment p WHERE p.release_date > ? AND p.type IN( 'CREDIT_CARD' , " + " 'INSTALLMENT_CREDIT_CARD' ))" , new Object []{DigitalAccountAttributeName.HAS_CREDIT_CARD_PAYMENT.name(), getCalendar()}, new Type[]{StringType.INSTANCE, CalendarType.INSTANCE})); return criteria.list(); 5) criteria.add(Restrictions.sqlRestriction( "this_.id in(select max(pns.id) from payment_notification_status pns where pns.payment_id = ?)" , paymentId, LongType.INSTANCE)); 6) Calendar last24Hours = CalendarUtils.addDays(getCalendar(), -1); Criteria criteria = createEntityCriteriaBypassAccount(); criteria.add(Restrictions.gt( "createdOn" , last24Hours)); Type[] types = {IntegerType.INSTANCE, IntegerType.INSTANCE, CalendarType.INSTANCE}; Object [] values = {ResponseStatus.OK, PaymentNotificationStatus.MAX_NOTIFICATION_ATTEMPTS, last24Hours}; String subQuery1 = "this_.payment_id NOT IN (SELECT pns.payment_id FROM payment_notification_status pns " + "WHERE (pns.status_code = ? OR pns.attempt_number=?) AND pns.created_on > ?)" ; criteria.add(Restrictions.sqlRestriction(subQuery1, values, types)); String subQuery2 = "this_.id IN (SELECT max(pns2.id) FROM payment_notification_status pns2 " + "WHERE pns2.status_code <> ? AND pns2.attempt_number < ? AND pns2.created_on > ? GROUP BY pns2.payment_id)" ; criteria.add(Restrictions.sqlRestriction(subQuery2, values, types)); 7) Type[] types = {CalendarType.INSTANCE, CalendarType.INSTANCE, StringType.INSTANCE, CalendarType.INSTANCE, CalendarType.INSTANCE}; Calendar start = sanitizeStartDate(filter); Calendar end = sanitizeEndDate(filter); Object [] values = {start, end, PaymentStatus.CONFIRMED.name(), start, end}; String subQuery = "select max(payment_.id) from payment payment_ inner join charge charge1_ on payment_.charge_id=charge1_.id where payment_.type in ('" + PaymentType.CREDIT_CARD + " ', ' " + PaymentType.INSTALLMENT_CREDIT_CARD + "') and ((payment_.date >= ? and payment_.date < ? and payment_.status = ? and payment_.partial_refund = 0" + ") or (payment_.updated_on >= ? and payment_.updated_on < ? and payment_.status in( '" + PaymentStatus.CUSTOMER_PAID_BACK + "' , '" + PaymentStatus.BANK_PAID_BACK + "'))) group by charge1_.charge_group_id" ; criteria.add(sqlRestriction( "this_.id in (" + subQuery + ")" , values, types)); ( https://hibernate.atlassian.net/browse/HHH-13170#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13170#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4676) Use .and() syntax by default with .where(BiFunction) and .nested() predicate?

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=eyJpIjoiMDNmM2Fh... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-4676?atlOrigin=eyJpIjoiMDN... ) HSEARCH-4676 ( https://hibernate.atlassian.net/browse/HSEARCH-4676?atlOrigin=eyJpIjoiMDN... ) Use .and() syntax by default with .where(BiFunction) and .nested() predicate? ( https://hibernate.atlassian.net/browse/HSEARCH-4676?atlOrigin=eyJpIjoiMDN... ) Issue Type: Improvement Assignee: Unassigned Components: engine Created: 17/Aug/2022 06:45 AM Fix Versions: 6.2-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Follows up on https://hibernate.atlassian.net/browse/HSEARCH-4601 ( https://hibernate.atlassian.net/browse/HSEARCH-4601 ) The .where(BiFunction) syntax uses a bool predicate: MySearchParameters searchParameters = getSearchParameters(); List<Book> hits = searchSession.search( Book.class ) .where( (f, b) -> { b.must( f.matchAll() ); if ( searchParameters.getGenreFilter() != null ) { b.must( f.match().field( "genre" ) .matching( searchParameters.getGenreFilter() ) ); } if ( searchParameters.getFullTextFilter() != null ) { b.must( f.match().fields( "title", "description" ) .matching( searchParameters.getFullTextFilter() ) ); } if ( searchParameters.getPageCountMaxFilter() != null ) { b.must( f.range().field( "pageCount" ) .atMost( searchParameters.getPageCountMaxFilter() ) ); } } ) .fetchHits( 20 ); But most of the time, I expect people will want an and , and we just introduced a simpler syntax for and predicates ( https://hibernate.atlassian.net/browse/HSEARCH-4601 ( https://hibernate.atlassian.net/browse/HSEARCH-4601 ) ). It would probably be better to use the and syntax there: MySearchParameters searchParameters = getSearchParameters(); List<Book> hits = searchSession.search( Book.class ) .where( (f, b) -> { b.add( f.matchAll() ); if ( searchParameters.getGenreFilter() != null ) { b.add( f.match().field( "genre" ) .matching( searchParameters.getGenreFilter() ) ); } if ( searchParameters.getFullTextFilter() != null ) { b.add( f.match().fields( "title", "description" ) .matching( searchParameters.getFullTextFilter() ) ); } if ( searchParameters.getPageCountMaxFilter() != null ) { b.add( f.range().field( "pageCount" ) .atMost( searchParameters.getPageCountMaxFilter() ) ); } } ) .fetchHits( 20 ); Similarly, the current syntax for adding clauses to a nested predicate is that of the bool predicate: .where( f -> f.and() .add( f.range().field( "summary.total" ) .atLeast( new BigDecimal( "20.0" ) ) ) .add( f.range().field( "summary.shipping" ) .atMost( new BigDecimal( "10.0" ) ) ) .add( f.nested( "lineItems" ) .must( f.range().field( "lineItems.amount" ) .between( new BigDecimal( "7.0" ), new BigDecimal( "9.0" ) ) ) .must( f.match().field( "lineItems.category" ) .matching( "BOOK" ) ) )) However, most of the time one will simply want an and inside the nested predicate: an or would be equivalent to not using the nested predicate to begin with, and advanced features of the bool predicate are… well, for advanced users. We should probably use an (implicit) and there as well: .where( f -> f.and() .add( f.range().field( "summary.total" ) .atLeast( new BigDecimal( "20.0" ) ) ) .add( f.range().field( "summary.shipping" ) .atMost( new BigDecimal( "10.0" ) ) ) .add( f.nested( "lineItems" ) .add( f.range().field( "lineItems.amount" ) .between( new BigDecimal( "7.0" ), new BigDecimal( "9.0" ) ) ) .add( f.match().field( "lineItems.category" ) .matching( "BOOK" ) ) )) ( https://hibernate.atlassian.net/browse/HSEARCH-4676#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4676#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4675) Use .and()/.or() rather than .bool() where possible in documentation and tests

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4675) Use .and()/.or() rather than .bool() where possible in documentation and tests

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4674) Move to Testcontainers to start Elasticsearch/OpenSearch/databases/etc.

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=eyJpIjoiMjlkMWY1... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-4674?atlOrigin=eyJpIjoiMjl... ) HSEARCH-4674 ( https://hibernate.atlassian.net/browse/HSEARCH-4674?atlOrigin=eyJpIjoiMjl... ) Move to Testcontainers to start Elasticsearch/OpenSearch/databases/etc. ( https://hibernate.atlassian.net/browse/HSEARCH-4674?atlOrigin=eyJpIjoiMjl... ) Issue Type: Task Assignee: Unassigned Components: build, integration, tests Created: 17/Aug/2022 05:23 AM Fix Versions: 6.3-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We would probably be able to integrate a TestContainers rule into our various SetupHelpers, making sure that the appropriate containers (database, Elasticsearch, …) are started before tests start. org.hibernate.search.util.impl.integrationtest.common.rule.BackendConfiguration#testRule would be particularly relevant when it comes to Elasticsearch. This would also have the advantage of speeding up the build, as there’s a way to have TestContainers start each container only once for the whole build (using Ryuk). See also this comment ( https://hibernate.atlassian.net/browse/HSEARCH-4643?focusedCommentId=109767 ) : testcontainers could help with dependency upgrades (though no certainty here). There might be a few blockers, mainly support for the databases we need in TestContainers; I know that TestContainers' Elasticsearch support wasn’t compatible with OpenSearch (it rejected any image that’s not the official Elasticsearch one) last time I checked. ( https://hibernate.atlassian.net/browse/HSEARCH-4674#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4674#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15452) Predicate add expression results in UnsupportedOperationException

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15452 ( https://hibernate.atlassian.net/browse/HHH-15452?atlOrigin=eyJpIjoiMmI3ND... ) Re: Predicate add expression results in UnsupportedOperationException ( https://hibernate.atlassian.net/browse/HHH-15452?atlOrigin=eyJpIjoiMmI3ND... ) You do understand that the JPA specification requires that, and I cite from the Javadoc of Predicate#getExpressions : > > > > Modifications to the list do not affect the query. > > So your code is broken and only worked by accident in previous Hibernate versions. The proper way to do this is: Predicate conjuncion = builder.conjunction(); Predicate expr = builder.equal(rootClaseGrid.get( "documento" ), "AAAA" ); cq.where(builder.and(conjunction, expr)); Since the Javadoc seem to imply that modifications are allowed, I agree that this is a bug. The bug is, that we should return mutable lists, possibly copies of the original list. ( https://hibernate.atlassian.net/browse/HHH-15452#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15452#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4612) Disable purgeAllOnStart by default in MassIndexer when dropAndCreateSchemaOnStart is enabled

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4612) Disable purgeAllOnStart by default in MassIndexer when dropAndCreateSchemaOnStart is enabled

by Automation for Jira (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-13170) GORM: Challenges migrating away from deprecated Criteria API

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13170 ( https://hibernate.atlassian.net/browse/HHH-13170?atlOrigin=eyJpIjoiOTMwY2... ) Re: GORM: Challenges migrating away from deprecated Criteria API ( https://hibernate.atlassian.net/browse/HHH-13170?atlOrigin=eyJpIjoiOTMwY2... ) Please share with us what kind of sql restrictions you think are impossible to model in HQL/Criteria. We added support for so many SQL constructs that I am really curious what you can’t model yet. ( https://hibernate.atlassian.net/browse/HHH-13170#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13170#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15452) Predicate add expression results in UnsupportedOperationException

by Andrea Boriero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15453) java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null

by Puhong You (JIRA)

Puhong You ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15453 ( https://hibernate.atlassian.net/browse/HHH-15453?atlOrigin=eyJpIjoiN2JlM2... ) Re: java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null ( https://hibernate.atlassian.net/browse/HHH-15453?atlOrigin=eyJpIjoiN2JlM2... ) Notes: 1. the User with userId = 1 has a row in the USER_ROLE association table, and the query works. The user with userId = 2 has no row in the USER_ROLE association table, and the query throws java.lang.NullPointerException. 2. In the User.java entity bean, if I change the FetchMode for the roles collection from @Fetch(FetchMode.SUBSELECT)to @Fetch(FetchMode.JOIN), both queries work. ( https://hibernate.atlassian.net/browse/HHH-15453#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15453#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15453) java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null

by Puhong You (JIRA)

Puhong You ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYTQ5NzY0YzVk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15453?atlOrigin=eyJpIjoiYTQ5Nz... ) HHH-15453 ( https://hibernate.atlassian.net/browse/HHH-15453?atlOrigin=eyJpIjoiYTQ5Nz... ) java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null ( https://hibernate.atlassian.net/browse/HHH-15453?atlOrigin=eyJpIjoiYTQ5Nz... ) Issue Type: Bug Affects Versions: 6.1.2 Assignee: Unassigned Components: hibernate-core Created: 16/Aug/2022 11:54 AM Environment: Hibernate 6.1.2.Final, Java 17 and 18, MacOS/Windows, DB2 Priority: Major Reporter: Puhong You ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Setup: ** *DataBase Tables* ** 1. USER table: Columns: USER_ID integer not null primary key, USER_NAME varchar(256) not null, Rows: (1, 'Ann'); (2, 'Bob'); 2. ROLE table Columns: ROLE_ID integer not null primary key, ROLE_NAME varchar(256) not null, Rows: (1, 'Manager'); (2, 'Developer'); 3. USER_ROLE table Columns: USER_ID integer not null, ROLE_ID integer not null, Composite key: (USER_ID, ROLE_ID) Rows: (1,1); ** *EntityBeans* ** 4. User.java import jakarta.persistence.CascadeType; import jakarta.persistence.Column; import jakarta.persistence.Entity; import jakarta.persistence.FetchType; import jakarta.persistence.Id; import jakarta.persistence.JoinColumn; import jakarta.persistence.JoinTable; import jakarta.persistence.ManyToMany; import jakarta.persistence.Table; import java.util.Objects; import java.util.Set; import org.hibernate.annotations.Fetch; import org.hibernate.annotations.FetchMode; @Entity @Table(name = "USER", schema = "TEST") public class User { private Integer userId = null; private String userName = null; private Set<Role> roles = null; @Id @Column(name = "USER_ID") public Integer getUserId() { return userId; } public void setUserId(Integer userId) { this.userId = userId; } @Column(name = "USER_NAME") public String getUserName() { return userName; } public void setUserName(String userName) { this.userName = userName; } @ManyToMany(cascade = CascadeType.PERSIST, fetch = FetchType.EAGER) @JoinTable( name = "USER_ROLE", schema = "TEST", joinColumns = @JoinColumn(name = "USER_ID"), inverseJoinColumns = @JoinColumn(name = "ROLE_ID")) @Fetch(FetchMode.SUBSELECT) public Set<Role> getRoles() { return roles; } public void setRoles(Set<Role> roles) { this.roles = roles; } @Override public boolean equals(Object o) { if (this == o) { return true; } if (o == null || getClass() != o.getClass()) { return false; } User user = (User) o; return Objects.equals(userId, user.userId) && Objects.equals(userName, user.userName) && Objects.equals(roles, user.roles); } @Override public int hashCode() { return Objects.hash(userId, userName, roles); } } 5. Role.java import jakarta.persistence.Column; import jakarta.persistence.Entity; import jakarta.persistence.Id; import jakarta.persistence.Table; import java.util.Objects; @Entity @Table(name = "ROLE", schema = "TEST") public class Role { private Integer roleId = null; private String roleName = null; @Id @Column(name = "ROLE_ID") public Integer getRoleId() { return roleId; } public void setRoleId(Integer roleId) { this.roleId = roleId; } @Column(name = "ROLE_NAME") public String getRoleName() { return roleName; } public void setRoleName(String roleName) { this.roleName = roleName; } @Override public boolean equals(Object o) { if (this == o) { return true; } if (o == null || getClass() != o.getClass()) { return false; } Role role = (Role) o; return Objects.equals(roleId, role.roleId) && Objects.equals(roleName, role.roleName); } @Override public int hashCode() { return Objects.hash(roleId, roleName); } } ** *Query and Error* ** 6. This query works: String query1 = "FROM User WHERE userId = 1"; // Obtain Hibernate session Session session = getSession(); List<User> userList = session.createQuery(query1, User.class).list(); 7. This query threw java.lang.NullPointerException: String query2 = "FROM User WHERE userId = 2"; // Obtain Hibernate session Session session = getSession(); List<User> userList = session.createQuery(query2, User.class).list(); The full stack traces – Original Exception: java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is null at org.hibernate.loader.ast.internal.CollectionLoaderSubSelectFetch.load(CollectionLoaderSubSelectFetch.java:91) at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:815) at org.hibernate.event.internal.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:75) at org.hibernate.event.service.internal.EventListenerGroupImpl.fireEventOnEachListener(EventListenerGroupImpl.java:107) at org.hibernate.internal.SessionImpl.initializeCollection(SessionImpl.java:1706) at org.hibernate.collection.spi.AbstractPersistentCollection.lambda$initialize$3(AbstractPersistentCollection.java:609) at org.hibernate.collection.spi.AbstractPersistentCollection.withTemporarySessionIfNeeded(AbstractPersistentCollection.java:265) at org.hibernate.collection.spi.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:607) at org.hibernate.collection.spi.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:805) at org.hibernate.engine.internal.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java:991) at org.hibernate.engine.internal.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java:977) at org.hibernate.sql.results.spi.ListResultsConsumer.consume(ListResultsConsumer.java:170) at org.hibernate.sql.results.spi.ListResultsConsumer.consume(ListResultsConsumer.java:32) at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.doExecuteQuery(JdbcSelectExecutorStandardImpl.java:437) at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.executeQuery(JdbcSelectExecutorStandardImpl.java:166) at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.list(JdbcSelectExecutorStandardImpl.java:91) at org.hibernate.sql.exec.spi.JdbcSelectExecutor.list(JdbcSelectExecutor.java:31) at org.hibernate.loader.ast.internal.SingleIdLoadPlan.load(SingleIdLoadPlan.java:140) at org.hibernate.loader.ast.internal.SingleIdLoadPlan.load(SingleIdLoadPlan.java:110) at org.hibernate.loader.ast.internal.SingleIdEntityLoaderStandardImpl.load(SingleIdEntityLoaderStandardImpl.java:72) at org.hibernate.persister.entity.AbstractEntityPersister.doLoad(AbstractEntityPersister.java:4313) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:4303) at org.hibernate.event.internal.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:598) at org.hibernate.event.internal.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:571) at org.hibernate.event.internal.DefaultLoadEventListener.load(DefaultLoadEventListener.java:223) at org.hibernate.event.internal.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:362) at org.hibernate.event.internal.DefaultLoadEventListener.doOnLoad(DefaultLoadEventListener.java:112) at org.hibernate.event.internal.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:74) at org.hibernate.event.service.internal.EventListenerGroupImpl.fireEventOnEachListener(EventListenerGroupImpl.java:118) at org.hibernate.internal.SessionImpl.fireLoadNoChecks(SessionImpl.java:1237) at org.hibernate.internal.SessionImpl.internalLoad(SessionImpl.java:1090) at org.hibernate.sql.results.graph.entity.internal.EntitySelectFetchInitializer.initializeInstance(EntitySelectFetchInitializer.java:197) at org.hibernate.sql.results.internal.StandardRowReader.coordinateInitializers(StandardRowReader.java:153) at org.hibernate.sql.results.internal.StandardRowReader.readRow(StandardRowReader.java:98) at org.hibernate.sql.results.spi.ListResultsConsumer.consume(ListResultsConsumer.java:143) at org.hibernate.sql.results.spi.ListResultsConsumer.consume(ListResultsConsumer.java:32) at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.doExecuteQuery(JdbcSelectExecutorStandardImpl.java:437) at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.executeQuery(JdbcSelectExecutorStandardImpl.java:166) at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.list(JdbcSelectExecutorStandardImpl.java:91) at org.hibernate.sql.exec.spi.JdbcSelectExecutor.list(JdbcSelectExecutor.java:31) at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.lambda$new$0(ConcreteSqmSelectQueryPlan.java:102) at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.withCacheableSqmInterpretation(ConcreteSqmSelectQueryPlan.java:305) at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.performList(ConcreteSqmSelectQueryPlan.java:246) at org.hibernate.query.sqm.internal.QuerySqmImpl.doList(QuerySqmImpl.java:537) at org.hibernate.query.spi.AbstractSelectionQuery.list(AbstractSelectionQuery.java:363) at org.hibernate.query.sqm.internal.QuerySqmImpl.list(QuerySqmImpl.java:987) ( https://hibernate.atlassian.net/browse/HHH-15453#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15453#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-13170) GORM: Challenges migrating away from deprecated Criteria API

by Eduardo Simioni (JIRA)

Eduardo Simioni ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13170 ( https://hibernate.atlassian.net/browse/HHH-13170?atlOrigin=eyJpIjoiNjA5YT... ) Re: GORM: Challenges migrating away from deprecated Criteria API ( https://hibernate.atlassian.net/browse/HHH-13170?atlOrigin=eyJpIjoiNjA5YT... ) What about the criteria.add(Restrictions.sqlRestriction()) option? I’ve started a branch to migrate my company’s code to Hibernate 6 (Hibernate Criteria to JPA basically), but I can’t complete this migration without an sql restriction alternative. We are using only criteria, no HQL. I’ve got very far and thought of possible alternative solutions, but in the end, although we have just 31 usages in a very large project, I could only migrate a few of them to other solutions, for all the rest, a replacement to SQL Restriction is absolutely needed. ( https://hibernate.atlassian.net/browse/HHH-13170#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13170#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15452) Predicate add expression results in UnsupportedOperationException

by Hernan (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15452) Predicate add expresion results in UnsupportedOperationException

by Hernan (JIRA)

Hernan ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=62fba63... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZmZkMWJlYzcw... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15452?atlOrigin=eyJpIjoiZmZkMW... ) HHH-15452 ( https://hibernate.atlassian.net/browse/HHH-15452?atlOrigin=eyJpIjoiZmZkMW... ) Predicate add expresion results in UnsupportedOperationException ( https://hibernate.atlassian.net/browse/HHH-15452?atlOrigin=eyJpIjoiZmZkMW... ) Issue Type: Bug Affects Versions: 6.1.1 Assignee: Unassigned Components: hibernate-core Created: 16/Aug/2022 07:55 AM Environment: Hibernate ORM core version 6.1.1.Final, openjdk version "11" 2018-09-25, Ubuntu 20.04.4 LTS, SQL Server 2008 R2 (SP3) Priority: Major Reporter: Hernan ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=62fba63... ) While upgrating Hibernate version from 4.3.7 to 6.1.1 I'm getting an Exception running a piece of code that used to work and is found in several tutorials and examples The simplest code I can build to show the behavior is: CriteriaBuilder builder = em4.getCriteriaBuilder(); CriteriaQuery<Persona> cq = builder.createQuery(Persona.class); Root<Persona> rootClaseGrid = cq.from(Persona.class); cq.select(rootClaseGrid); Predicate conjuncion = builder.conjunction(); Predicate expr = builder.equal(rootClaseGrid.get( "documento" ), "AAAA" ); conjuncion.getExpressions().add(expr); Last line throws: Exception in thread "main" java.lang.UnsupportedOperationException at java.base/java.util.AbstractList.add(AbstractList.java:153) at java.base/java.util.AbstractList.add(AbstractList.java:111) at pruebas.PruebaHM.main(PruebaHM.java:181) Debugging Hibernate code shows that method "getExpressions" resolves in class "org.hibernate.query.sqm.tree.predicate.AbstractSqmPredicate", with code: @Override public List<Expression< Boolean >> getExpressions() { /// most predicates do not have sub-predicates return Collections.emptyList(); } in fact returning always an emptyList of java.util.AbstractList, trying to add elements always throws UnsupportedOperationException: public void add( int index, E element) { throw new UnsupportedOperationException(); } Older versions (for instance 4.3.7) manage a list of Expression<Boolean>, the last line in the code above resolves in class "org.hibernate.jpa.criteria.predicate.CompoundPredicate" : @Override public List<Expression< Boolean >> getExpressions() { return expressions; } Thanks in advance ( https://hibernate.atlassian.net/browse/HHH-15452#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15452#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15451) Upgrade PostgreSQL JDBC driver to 42.4.1

by Sanne Grinovero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15449) @ManyToOne associations not loaded correctly with default EAGER and batch fetch property set when using TypedQuery.resultStream

by Andrea Boriero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15450) Add fluent style access type

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15450 ( https://hibernate.atlassian.net/browse/HHH-15450?atlOrigin=eyJpIjoiNTc2NG... ) Re: Add fluent style access type ( https://hibernate.atlassian.net/browse/HHH-15450?atlOrigin=eyJpIjoiNTc2NG... ) We might want to consider how to make that the default, as well. We could have a configuration property (“use the FLUENT access type instead of PROPERTY by default” = true, “). We could also try to emulate the current mechanism based on @Id : on an entity, if the @Id annotation is found on a method that doesn’t follow the JavaBeans naming conventions (e.g. Long id() ), then we would default to the FLUENT access type. There are multiple challenges, though: * No idea how this would work on mapped superclasses that don’t include an ID, but I suspect we have the same problem with the current access type (no way to decide on a default). * What if I have a property in the fluent style that happens to also match JavaBeans conventions, e.g.`getDoneFast`? ( boolean getDoneFast; public boolean getDoneFast(); public boolean getDoneFast(boolean value); ) ( https://hibernate.atlassian.net/browse/HHH-15450#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15450#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15440) @OneToOne and @OptimisticLock(excluded = true) not working correctly

by Andrea Boriero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15450) Add fluent style access type

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNGJhZGZjNWVi... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15450?atlOrigin=eyJpIjoiNGJhZG... ) HHH-15450 ( https://hibernate.atlassian.net/browse/HHH-15450?atlOrigin=eyJpIjoiNGJhZG... ) Add fluent style access type ( https://hibernate.atlassian.net/browse/HHH-15450?atlOrigin=eyJpIjoiNGJhZG... ) Issue Type: Improvement Assignee: Unassigned Components: hibernate-core Created: 16/Aug/2022 05:54 AM Priority: Major Reporter: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The “fluent” style is to not have prefixes for method names. Every no-arg non-void method is considered a property. A single arg void method with the same name and argument type matching the read accessor type, is considered to be the write accessor. For example: @Entity @Access(FLUENT) public class Blog { ... public String title() {...} public void title( String title) {...} } It might be worth considering same named single argument methods also as write accessors, regardless of the return type, to support use cases where the write accessor returns the “this” object for chained method invocation. ( https://hibernate.atlassian.net/browse/HHH-15450#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15450#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4500) Provide more context in error messages about fields with invalid type (value vs. object)

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4656) Provide more guidance in error messages when calling "retrieve-by-name" methods

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4552) Simplify some mapper SPIs

by Automation for Jira (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4552) Simplify some mapper SPIs

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4646) Document that Spring Boot may create a (wrong) Elasticsearch client just because Hibernate Search adds the Elasticsearch client to the classpath

by Automation for Jira (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4551) Make the mapping requirements of sorts/projections/aggregations more visible in the documentation

by Automation for Jira (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4653) Document built-in analyzers and how to override them

by Automation for Jira (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4554) Update documentation of default credentials provider chain for Elasticsearch AWS

by Automation for Jira (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4658) Document the syntax of conditions passed to the mass indexer

by Automation for Jira (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15449) @ManyToOne associations not loaded correctly with default EAGER and batch fetch property set when using TypedQuery.resultStream

by Frode Carlsen (JIRA)

Frode Carlsen ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15449 ( https://hibernate.atlassian.net/browse/HHH-15449?atlOrigin=eyJpIjoiMjlkZG... ) Re: @ManyToOne associations not loaded correctly with default EAGER and batch fetch property set when using TypedQuery.resultStream ( https://hibernate.atlassian.net/browse/HHH-15449?atlOrigin=eyJpIjoiMjlkZG... ) It would seem BatchEntitySelectFetchInitalizer#endLoading ( https://github.com/hibernate/hibernate-orm/blob/9ecb4484a40ef37a362bb095b... ( https://github.com/hibernate/hibernate-orm/blob/9ecb4484a40ef37a362bb095b... ) ) method is not called when invoking TypedQuery#getResultStream(). Thus the associated @ManyToOne entities are not set. When invoking TypedQuery#getResultList() this works as expected. ( https://hibernate.atlassian.net/browse/HHH-15449#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15449#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15449) @ManyToOne associations not loaded correctly with default EAGER and batch fetch property set when using TypedQuery.resultStream

by ekun (JIRA)

ekun ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c2a7fd... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMjQ1MTY4MzBi... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15449?atlOrigin=eyJpIjoiMjQ1MT... ) HHH-15449 ( https://hibernate.atlassian.net/browse/HHH-15449?atlOrigin=eyJpIjoiMjQ1MT... ) @ManyToOne associations not loaded correctly with default EAGER and batch fetch property set when using TypedQuery.resultStream ( https://hibernate.atlassian.net/browse/HHH-15449?atlOrigin=eyJpIjoiMjQ1MT... ) Issue Type: Bug Affects Versions: 6.1.2 Assignee: Unassigned Attachments: hibernate-test-case-eager-regression.zip Components: hibernate-core Created: 16/Aug/2022 04:00 AM Environment: As per hibernate test case template attached Hibernate 5.6.9, 6.1.2 Labels: regression Priority: Major Reporter: ekun ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c2a7fd... ) When the following propert is set in persistence.xml to a value greater than 1 <property name="hibernate.default_batch_fetch_size" value="2" /> Then, In a graph with a Parent-Child relationship, where the Child has a @ManyToOne to Parent entity, with default fetch EAGER. Then when hibernate-test-case-eager-regression.zip ( https://hibernate.atlassian.net/secure/attachment/50044/50044_hibernate-t... ) Child entities are loaded by an HQL query using the resultStream method, the parent entity is not mapped on any of the elements returned to the stream. See attached test case proving the way it worked in Hibernate 5, and the subsequent fault in 6. Workaround 1: Switch to @ManyToOne(fetch=FetchType.LAZY) ( https://hibernate.atlassian.net/browse/HHH-15449#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15449#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4653) Document built-in analyzers and how to override them

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4551) Make the mapping requirements of sorts/projections/aggregations more visible in the documentation

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4646) Document that Spring Boot may create a (wrong) Elasticsearch client just because Hibernate Search adds the Elasticsearch client to the classpath

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4658) Document the syntax of conditions passed to the mass indexer

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4665) Fix Asciidoc formatting of the migration guide

by Automation for Jira (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4579) Default to constructor projection when possible if .select() is not called during query definition and loading is not configured

by Automation for Jira (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4673) Remove the need for the `-parameters` compiler flag when using the default constructor of records as projection constructor

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=eyJpIjoiMDBlOGY3... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-4673?atlOrigin=eyJpIjoiMDB... ) HSEARCH-4673 ( https://hibernate.atlassian.net/browse/HSEARCH-4673?atlOrigin=eyJpIjoiMDB... ) Remove the need for the `-parameters` compiler flag when using the default constructor of records as projection constructor ( https://hibernate.atlassian.net/browse/HSEARCH-4673?atlOrigin=eyJpIjoiMDB... ) Issue Type: Improvement Assignee: Unassigned Components: mapper-pojo-base Created: 16/Aug/2022 01:43 AM Fix Versions: 6.2-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) When using @ProjectionConstructor at the type level on a record type, we know we will be using the canonical constructor. In that case, there is a dedicted, records-specific API to retrieve the name of “record components”, which happen to also be the name of parameters to the canonical constructors. We could leverage that as a source of information for the name of constructor parameters, thereby making projection constructors work (at least in this specific case) even when -parameters was not used during compilation. See https://hibernate.zulipchat.com/#narrow/stream/132094-hibernate-orm-dev/t... ( https://hibernate.zulipchat.com/#narrow/stream/132094-hibernate-orm-dev/t... ) , https://github.com/hibernate/hibernate-orm/pull/5202/files ( https://github.com/hibernate/hibernate-orm/pull/5202/files ) , https://github.com/hibernate/hibernate-commons-annotations/pull/21 ( https://github.com/hibernate/hibernate-commons-annotations/pull/21 ) ( https://hibernate.atlassian.net/browse/HSEARCH-4673#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4673#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15448) Upgrade MSSQL JDBC and container image versions used for testing

by Sanne Grinovero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15448) Upgrade MSSQL JDBC and container image versions used for testing

by Sanne Grinovero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14387) A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance with hibernate-enhance-maven-plugin

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14387 ( https://hibernate.atlassian.net/browse/HHH-14387?atlOrigin=eyJpIjoiNjUxZT... ) Re: A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance with hibernate-enhance-maven-plugin ( https://hibernate.atlassian.net/browse/HHH-14387?atlOrigin=eyJpIjoiNjUxZT... ) Totally missed that there was a profile. Now I can see the error, thanks. ( https://hibernate.atlassian.net/browse/HHH-14387#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14387#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14387) A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance with hibernate-enhance-maven-plugin

by Christian Beikov (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4672) Upgrade -orm6 artifacts to hibernate-commons-annotations 6.0.3.Final

by Automation for Jira (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4672) Upgrade -orm6 artifacts to hibernate-commons-annotations 6.0.3.Final

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4671) Upgrade to Hibernate ORM 5.3.28.Final

by Automation for Jira (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4642) Upgrade build dependencies to the latest version

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4656) Provide more guidance in error messages when calling "retrieve-by-name" methods

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4646) Document that Spring Boot may create a (wrong) Elasticsearch client just because Hibernate Search adds the Elasticsearch client to the classpath

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4552) Simplify some mapper SPIs

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4551) Make the mapping requirements of sorts/projections/aggregations more visible in the documentation

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4554) Update documentation of default credentials provider chain for Elasticsearch AWS

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4500) Provide more context in error messages about fields with invalid type (value vs. object)

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4380) Upgrade to maven-assembly-plugin 3.3+

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4653) Document built-in analyzers and how to override them

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4579) Default to constructor projection when possible if .select() is not called during query definition and loading is not configured

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4658) Document the syntax of conditions passed to the mass indexer

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4672) Upgrade -orm6 artifacts to hibernate-commons-annotations 6.0.3.Final

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4672) Upgrade -orm6 artifacts to hibernate-commons-annotations 6.0.3.Final

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4671) Upgrade to Hibernate ORM 5.3.28.Final

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4671) Upgrade to Hibernate ORM 5.3.28.Final

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14387) A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance with hibernate-enhance-maven-plugin

by Andrzej (JIRA)

Andrzej ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5fe8586... ) *commented* on HHH-14387 ( https://hibernate.atlassian.net/browse/HHH-14387?atlOrigin=eyJpIjoiMDZlYj... ) Re: A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance with hibernate-enhance-maven-plugin ( https://hibernate.atlassian.net/browse/HHH-14387?atlOrigin=eyJpIjoiMDZlYj... ) Yes it should throw exception. Did you run mvn clean compile exec:java -Penhance ? Because the problem occurs when it is used hibernate-enhance-maven-plugin and this is activated in enhance profile if you just run appliaction without enhancing entities it works fine. ( https://hibernate.atlassian.net/browse/HHH-14387#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14387#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#100204- sha1:f005d5a )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15448) Upgrade MSSQL JDBC and container image versions used for testing

by Sanne Grinovero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HCANN-123) Support accessing record components as XProperty

by Christian Beikov (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HCANN-122) Make java.lang.reflect.Type implementations compatible with standard Java versions

by Christian Beikov (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HCANN-122) Make java.lang.reflect.Type implementations compatible with standard Java versions

by Christian Beikov (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14387) A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance with hibernate-enhance-maven-plugin

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14387 ( https://hibernate.atlassian.net/browse/HHH-14387?atlOrigin=eyJpIjoiNmQ2MG... ) Re: A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance with hibernate-enhance-maven-plugin ( https://hibernate.atlassian.net/browse/HHH-14387?atlOrigin=eyJpIjoiNmQ2MG... ) I just ran the test case as provided in *Hibernateenhancetest_6.zip* and it works fine for me. I should see an exception, right? ( https://hibernate.atlassian.net/browse/HHH-14387#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14387#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#100204- sha1:948b370 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14258) Hibernate 6.0.0.Alpha6 NativeQuery setResultTransformer not working

by 张路权 (JIRA)

张路权 ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14258 ( https://hibernate.atlassian.net/browse/HHH-14258?atlOrigin=eyJpIjoiZmMzMz... ) Re: Hibernate 6.0.0.Alpha6 NativeQuery setResultTransformer not working ( https://hibernate.atlassian.net/browse/HHH-14258?atlOrigin=eyJpIjoiZmMzMz... ) Sorry for getting back to you so late, but I haven't tried anything yet. I'll get back to you after the test. Thank you very much. ( https://hibernate.atlassian.net/browse/HHH-14258#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14258#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#100204- sha1:948b370 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-13794) JPA Metamodelgen on JDK 11+ can fail with ClassCastException on JAXBContext due to classloading conflict

by Hack Kampbjørn (JIRA)

Hack Kampbjørn ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13794 ( https://hibernate.atlassian.net/browse/HHH-13794?atlOrigin=eyJpIjoiMjVkN2... ) Re: JPA Metamodelgen on JDK 11+ can fail with ClassCastException on JAXBContext due to classloading conflict ( https://hibernate.atlassian.net/browse/HHH-13794?atlOrigin=eyJpIjoiMjVkN2... ) That project exposes the problem: [INFO] --- maven-processor-plugin:4.0-rc1:process (process) @ hhh-13794-testcase --- [INFO] diagnostic: Note: Hibernate JPA 2 Static-Metamodel Generator 5.6.10.Final [WARNING] diagnostic: warning: Unable to parse persistence.xml: Unable to perform unmarshalling at line number 0 and column 0. Message: null It does not have any details in the XML files so it generates the model on annotations alone. I’ve updated the test case so it fails when XML files are not parsed https://github.com/worldticket/hhh-13794-testcase ( https://github.com/worldticket/hhh-13794-testcase ) With the fix in PR, XML files are parsed and the generated JPA model includes all details ( https://hibernate.atlassian.net/browse/HHH-13794#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13794#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#100204- sha1:948b370 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-13794) JPA Metamodelgen on JDK 11+ can fail with ClassCastException on JAXBContext due to classloading conflict

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13794 ( https://hibernate.atlassian.net/browse/HHH-13794?atlOrigin=eyJpIjoiOTRkNj... ) Re: JPA Metamodelgen on JDK 11+ can fail with ClassCastException on JAXBContext due to classloading conflict ( https://hibernate.atlassian.net/browse/HHH-13794?atlOrigin=eyJpIjoiOTRkNj... ) I just tried the reproducer you provided with {{Maven version: 3.6.3, Java version: 11.0.9, vendor: AdoptOpenJDK}}and it worked fine. Please provide more context. Maybe this was fixed in newer Maven versions? ( https://hibernate.atlassian.net/browse/HHH-13794#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13794#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#100204- sha1:948b370 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15425) org.hibernate.QueryException: could not resolve property is thrown when Hibernate criteria tries to select the id of an association annotated with @NotFound

by Andrea Boriero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HBX-2390) Create a JBoss Tools adaptation layer

by Koen Aers (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15447) Remove references to deprecated dialects (where possible)

by Jan Schatteman (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15072) Default EmbeddableInstantiator for records

by Christian Beikov (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HCANN-123) Support accessing record components as XProperty

by Christian Beikov (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HCANN-123) Support accessing record components as XProperty

by Christian Beikov (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15445) Envers inserts erroneous audit entries for many-to-many relation if using `global_with_modified_flag`

by Chris Cranford (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15445) Envers inserts erroneous audit entries for many-to-many relation if using `global_with_modified_flag`

by Chris Cranford (JIRA)

Chris Cranford ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15445 ( https://hibernate.atlassian.net/browse/HHH-15445?atlOrigin=eyJpIjoiMjhiZG... ) Re: Envers inserts erroneous audit entries for many-to-many relation if using `global_with_modified_flag` ( https://hibernate.atlassian.net/browse/HHH-15445?atlOrigin=eyJpIjoiMjhiZG... ) As explained on Zulip, the issue in this situation is the use of getReference() versus find(). In order for Envers to perform proper diff analysis on entity state, the entity must be loaded fully into the PersistenceContext. When using getReference() , the entity’s full state isn’t loaded by ORM and therefore only the primary key fields are available. Envers also does not lazily load this state because this can create other cascading concerns during the listener invocation. So we ultimately rely on the user to guarantee the entity’s state is loaded so the right audit state gets persisted. You can workaround and avoid this by using EntityManager#find() rather than EntityManager#getReference(). ( https://hibernate.atlassian.net/browse/HHH-15445#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15445#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#100204- sha1:2e7ea99 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15425) org.hibernate.QueryException: could not resolve property is thrown when Hibernate criteria tries to select the id of an association annotated with @NotFound

by Andrea Boriero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15446) Allow Dialect version to be specified separately from the dialect class name

by Jan Schatteman (JIRA)

Jan Schatteman ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZjE0ZWI2YjQ2... ) / Task ( https://hibernate.atlassian.net/browse/HHH-15446?atlOrigin=eyJpIjoiZjE0ZW... ) HHH-15446 ( https://hibernate.atlassian.net/browse/HHH-15446?atlOrigin=eyJpIjoiZjE0ZW... ) Allow Dialect version to be specified separately from the dialect class name ( https://hibernate.atlassian.net/browse/HHH-15446?atlOrigin=eyJpIjoiZjE0ZW... ) Change By: Jan Schatteman ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We need to be able to specify the dialect version by using the environment settings {{JAKARTA_HBM2DDL_DB_VERSION}}, {{JAKARTA_HBM2DDL_DB_MAJOR_VERSION}}, {{JAKARTA_HBM2DDL_DB_MINOR_VERSION.}} Right now, if the version is specified like this, it is not taken into account. This would allow replacing something such as {code:java}cfg.setProperty( AvailableSettings.DIALECT, Oracle10gDialect.class.getName() );{code} with {code:java}cfg.setProperty( AvailableSettings.DIALECT, OracleDialect.class.getName() ); cfg.setProperty( AvailableSettings.JAKARTA_HBM2DDL_DB_MAJOR_VERSION, "10" );{code} NB: once the above is implemented, tests that used these deprecated Dialects, should take special care in assuring that they actually get the requested dialect. (e.g. {{BatchVersionedDataConfigTest.testBatchVersionedDataForOracle10gDialect() }} may pass, even with a version different from the one specified{{ }} ) ( https://hibernate.atlassian.net/browse/HHH-15446#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15446#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#100204- sha1:2e7ea99 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15446) Allow Dialect version to be specified separately from the dialect class name

by Jan Schatteman (JIRA)

Jan Schatteman ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYzdkMGVkNWZi... ) / Task ( https://hibernate.atlassian.net/browse/HHH-15446?atlOrigin=eyJpIjoiYzdkMG... ) HHH-15446 ( https://hibernate.atlassian.net/browse/HHH-15446?atlOrigin=eyJpIjoiYzdkMG... ) Allow Dialect version to be specified separately from the dialect class name ( https://hibernate.atlassian.net/browse/HHH-15446?atlOrigin=eyJpIjoiYzdkMG... ) Change By: Jan Schatteman ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We need to be able to specify the dialect version by using the environment settings {{JAKARTA_HBM2DDL_DB_VERSION}}, {{JAKARTA_HBM2DDL_DB_MAJOR_VERSION}}, {{JAKARTA_HBM2DDL_DB_MINOR_VERSION.}} Right now, if the version is specified like this, it is not taken into account. This would allow replacing something such as { { code:java} cfg.setProperty( AvailableSettings.DIALECT, Oracle10gDialect.class.getName() ); {code } } with {code:java}cfg.setProperty( AvailableSettings.DIALECT, OracleDialect.class.getName() ); cfg.setProperty( AvailableSettings.JAKARTA_HBM2DDL_DB_MAJOR_VERSION, "10" );{code} NB: once the above is implemented, tests that used these deprecated Dialects, should take special care in assuring that they actually get the requested dialect. (e.g. {{BatchVersionedDataConfigTest }}) ( https://hibernate.atlassian.net/browse/HHH-15446#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15446#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#100204- sha1:2e7ea99 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15446) Allow Dialect version to be specified separately from the dialect class name

by Jan Schatteman (JIRA)

Jan Schatteman ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYmFiODZjMmYx... ) / Task ( https://hibernate.atlassian.net/browse/HHH-15446?atlOrigin=eyJpIjoiYmFiOD... ) HHH-15446 ( https://hibernate.atlassian.net/browse/HHH-15446?atlOrigin=eyJpIjoiYmFiOD... ) Allow Dialect version to be specified separately from the dialect class name ( https://hibernate.atlassian.net/browse/HHH-15446?atlOrigin=eyJpIjoiYmFiOD... ) Change By: Jan Schatteman ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We need to be able to specify the dialect version by using the environment settings {{JAKARTA_HBM2DDL_DB_VERSION}}, {{JAKARTA_HBM2DDL_DB_MAJOR_VERSION}}, {{JAKARTA_HBM2DDL_DB_MINOR_VERSION.}} Right now, if the version is specified like this, it is not taken into account. This would allow replacing something such as {{cfg.setProperty( AvailableSettings.DIALECT, Oracle10gDialect.class.getName() );}} with {code:java}cfg.setProperty( AvailableSettings.DIALECT, OracleDialect.class.getName() ); cfg.setProperty( AvailableSettings.JAKARTA_HBM2DDL_DB_MAJOR_VERSION, "10" );{code} NB: once the above is implemented, tests that used these deprecated Dialects, should take special care in assuring that they actually get the requested dialect. (e.g. {{BatchVersionedDataConfigTest }}) ( https://hibernate.atlassian.net/browse/HHH-15446#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15446#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#100204- sha1:2e7ea99 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15446) Allow Dialect version to be specified separately from the dialect class name

by Jan Schatteman (JIRA)

Jan Schatteman ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMmJjMmJiZjc3... ) / Task ( https://hibernate.atlassian.net/browse/HHH-15446?atlOrigin=eyJpIjoiMmJjMm... ) HHH-15446 ( https://hibernate.atlassian.net/browse/HHH-15446?atlOrigin=eyJpIjoiMmJjMm... ) Allow Dialect version to be specified separately from the dialect class name ( https://hibernate.atlassian.net/browse/HHH-15446?atlOrigin=eyJpIjoiMmJjMm... ) Issue Type: Task Affects Versions: 6.1.2 Assignee: Unassigned Components: hibernate-core Created: 10/Aug/2022 07:52 AM Priority: Major Reporter: Jan Schatteman ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We need to be able to specify the dialect version by using the environment settings JAKARTA_HBM2DDL_DB_VERSION , JAKARTA_HBM2DDL_DB_MAJOR_VERSION , JAKARTA_HBM2DDL_DB_MINOR_VERSION. Right now, if the version is specified like this, it is not taken into account. ( https://hibernate.atlassian.net/browse/HHH-15446#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15446#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#100204- sha1:2e7ea99 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15442) Allow for setParameter usage with a queries for a specific type in an Any-discriminated relationship

by Andrea Boriero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15445) Envers inserts erroneous audit entries for many-to-many relation if using `global_with_modified_flag`

by Simon Seyock (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15445) Envers inserts erronous audit entries for many-to-many relation if using `global_with_modified_flag`

by Simon Seyock (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15445) Envers inserts erronous revision entries for many-to-many relation if using `global_with_modified_flag`

by Simon Seyock (JIRA)

Simon Seyock ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=62f3875... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZmY2MmIyNDU4... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15445?atlOrigin=eyJpIjoiZmY2Mm... ) HHH-15445 ( https://hibernate.atlassian.net/browse/HHH-15445?atlOrigin=eyJpIjoiZmY2Mm... ) Envers inserts erronous revision entries for many-to-many relation if using `global_with_modified_flag` ( https://hibernate.atlassian.net/browse/HHH-15445?atlOrigin=eyJpIjoiZmY2Mm... ) Issue Type: Bug Affects Versions: 5.6.9 Assignee: Chris Cranford ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: hibernate-envers Created: 10/Aug/2022 03:45 AM Priority: Major Reporter: Simon Seyock ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=62f3875... ) If using the config option global_with_modified_flag , envers creates erronous audit entries for ManyToMany relations in certain cases. Suppose EntityA and EntityB are related via a ManyToMany relation and EntityA is the owning side of the relation. In this case I can remove an EntityB from the relation, persist the EntityA and the relation is updated correctly. If envers is configured with ` global_with_modified_flag , it creates 3 audit entries, one for the relation, one for the owning and one for the owned side. The audit entry for the owned side does not contain any data except for id , rev , revtype and the *_mod fields. The _mod field that corresponds to the relation is set to true like it is expected. All other fields are null. I would expect that all other fields are filled with the current values. I wrote a reproducer for this problem, the last assert fails: https://github.com/simonseyock/hibernate-test-case-templates/blob/many-to... ( https://github.com/simonseyock/hibernate-test-case-templates/blob/many-to... ) If anyone can help me with a workaround for this, I would be very thankful. ( https://hibernate.atlassian.net/browse/HHH-15445#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15445#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#100204- sha1:2e7ea99 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4670) Fix flaky test org.hibernate.search.integrationtest.mapper.orm.massindexing.MassIndexingErrorCustomBackgroundFailureHandlerIT(default-default-database-oracle)

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=eyJpIjoiMTRiZWZm... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-4670?atlOrigin=eyJpIjoiMTR... ) HSEARCH-4670 ( https://hibernate.atlassian.net/browse/HSEARCH-4670?atlOrigin=eyJpIjoiMTR... ) Fix flaky test org.hibernate.search.integrationtest.mapper.orm.massindexing.MassIndexingErrorCustomBackgroundFailureHandlerIT(default-default-database-oracle) ( https://hibernate.atlassian.net/browse/HSEARCH-4670?atlOrigin=eyJpIjoiMTR... ) Issue Type: Task Assignee: Unassigned Components: tests Created: 10/Aug/2022 02:59 AM Fix Versions: 6.2-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) See https://ci.hibernate.org/blue/organizations/jenkins/hibernate-search/deta... ( https://ci.hibernate.org/blue/organizations/jenkins/hibernate-search/deta... ) Error No interactions wanted here: -> at org.hibernate.search.integrationtest.mapper.orm.massindexing.MassIndexingErrorCustomBackgroundFailureHandlerIT.assertNoFailureHandling(MassIndexingErrorCustomBackgroundFailureHandlerIT.java:46) But found these interactions on mock 'failureHandler': -> at org.hibernate.search.engine.reporting.impl.FailSafeFailureHandlerWrapper.handle(FailSafeFailureHandlerWrapper.java:30) Actually, above is the only interaction with this mock. Stacktrace org.mockito.exceptions.verification.NoInteractionsWanted: No interactions wanted here: -> at org.hibernate.search.integrationtest.mapper.orm.massindexing.MassIndexingErrorCustomBackgroundFailureHandlerIT.assertNoFailureHandling(MassIndexingErrorCustomBackgroundFailureHandlerIT.java:46) But found these interactions on mock 'failureHandler': -> at org.hibernate.search.engine.reporting.impl.FailSafeFailureHandlerWrapper.handle(FailSafeFailureHandlerWrapper.java:30) Actually, above is the only interaction with this mock. at org.hibernate.search.integrationtest.mapper.orm.massindexing.MassIndexingErrorCustomBackgroundFailureHandlerIT.assertNoFailureHandling(MassIndexingErrorCustomBackgroundFailureHandlerIT.java:46) at org.hibernate.search.integrationtest.mapper.orm.massindexing.AbstractMassIndexingErrorIT.entityLoading(AbstractMassIndexingErrorIT.java:122) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.hibernate.search.util.impl.integrationtest.common.rule.BackendMock$1.evaluate(BackendMock.java:52) at org.hibernate.search.util.impl.integrationtest.common.rule.MappingSetupHelper$1.evaluate(MappingSetupHelper.java:74) at org.hibernate.search.util.impl.integrationtest.common.TestConfigurationProvider$1.evaluate(TestConfigurationProvider.java:45) at org.hibernate.search.util.impl.integrationtest.common.rule.ThreadSpy$1.evaluate(ThreadSpy.java:42) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at org.junit.runners.ParentRunner.run(ParentRunner.java:413) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at org.junit.runners.ParentRunner.run(ParentRunner.java:413) at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:456) at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:169) at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:595) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:581) Standard Output 09:51:13,050 (main) INFO SimpleSessionFactoryBuilder:47 - Not setting the property with key 'hibernate.search.coordination.strategy' because value is null. 09:51:13,050 (main) WARN CachingRegionFactory:48 - org.hibernate.testing.cache.CachingRegionFactory should be only used for testing. 09:51:13,051 (main) WARN pooling:75 - HHH10001002: Using Hibernate built-in connection pool (not for production use!) 09:51:13,051 (main) INFO pooling:119 - HHH10001005: using driver [oracle.jdbc.OracleDriver] at URL [jdbc:oracle:thin:@localhost:1521/XE] 09:51:13,051 (main) INFO pooling:128 - HHH10001001: Connection properties: {password=****, user=SYSTEM} 09:51:13,051 (main) INFO pooling:132 - HHH10001003: Autocommit mode: false 09:51:13,051 (main) INFO DriverManagerConnectionProviderImpl:322 - HHH000115: Hibernate connection pool size: 31 (min=1) 09:51:13,066 (main) INFO Dialect:175 - HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect 09:51:13,069 (main) INFO HibernateSearchPreIntegrationService:91 - HSEARCH000034: Hibernate Search version 6.2.0-SNAPSHOT 09:51:13,074 (main) INFO access:48 - HHH10001501: Connection obtained from JdbcConnectionAccess [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator$ConnectionProviderJdbcConnectionAccess@1a049419] for (non-JTA) DDL execution was not in auto-commit mode; the Connection 'local transaction' will be committed and the Connection will be set into auto-commit mode. 09:51:13,075 (main) WARN ExceptionHandlerLoggedImpl:27 - GenerationTarget encountered exception accepting command : Error executing DDL "drop table Book cascade constraints" via JDBC Statement org.hibernate.tool.schema.spi.CommandAcceptanceException: Error executing DDL "drop table Book cascade constraints" via JDBC Statement at org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase.accept(GenerationTargetToDatabase.java:67) ~[hibernate-core-5.6.10.Final.jar:5.6.10.Final] at org.hibernate.tool.schema.internal.SchemaDropperImpl.applySqlString(SchemaDropperImpl.java:387) ~[hibernate-core-5.6.10.Final.jar:5.6.10.Final] at org.hibernate.tool.schema.internal.SchemaDropperImpl.applySqlStrings(SchemaDropperImpl.java:371) ~[hibernate-core-5.6.10.Final.jar:5.6.10.Final] at org.hibernate.tool.schema.internal.SchemaDropperImpl.dropFromMetadata(SchemaDropperImpl.java:246) ~[hibernate-core-5.6.10.Final.jar:5.6.10.Final] at org.hibernate.tool.schema.internal.SchemaDropperImpl.performDrop(SchemaDropperImpl.java:156) ~[hibernate-core-5.6.10.Final.jar:5.6.10.Final] at org.hibernate.tool.schema.internal.SchemaDropperImpl.doDrop(SchemaDropperImpl.java:128) ~[hibernate-core-5.6.10.Final.jar:5.6.10.Final] at org.hibernate.tool.schema.internal.SchemaDropperImpl.doDrop(SchemaDropperImpl.java:114) ~[hibernate-core-5.6.10.Final.jar:5.6.10.Final] at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:157) ~[hibernate-core-5.6.10.Final.jar:5.6.10.Final] at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:85) ~[hibernate-core-5.6.10.Final.jar:5.6.10.Final] at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:335) ~[hibernate-core-5.6.10.Final.jar:5.6.10.Final] at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:471) ~[hibernate-core-5.6.10.Final.jar:5.6.10.Final] at org.hibernate.search.util.impl.integrationtest.mapper.orm.SimpleSessionFactoryBuilder.build(SimpleSessionFactoryBuilder.java:124) ~[hibernate-search-util-internal-integrationtest-mapper-orm-6.2.0-SNAPSHOT.jar:?] at org.hibernate.search.util.impl.integrationtest.mapper.orm.OrmSetupHelper$SetupContext.build(OrmSetupHelper.java:204) ~[hibernate-search-util-internal-integrationtest-mapper-orm-6.2.0-SNAPSHOT.jar:?] at org.hibernate.search.util.impl.integrationtest.mapper.orm.OrmSetupHelper$SetupContext.build(OrmSetupHelper.java:138) ~[hibernate-search-util-internal-integrationtest-mapper-orm-6.2.0-SNAPSHOT.jar:?] at org.hibernate.search.util.impl.integrationtest.common.rule.MappingSetupHelper$AbstractSetupContext.setup(MappingSetupHelper.java:174) ~[hibernate-search-util-internal-integrationtest-common-6.2.0-SNAPSHOT.jar:?] at org.hibernate.search.util.impl.integrationtest.mapper.orm.OrmSetupHelper$SetupContext.setup(OrmSetupHelper.java:194) ~[hibernate-search-util-internal-integrationtest-mapper-orm-6.2.0-SNAPSHOT.jar:?] at org.hibernate.search.integrationtest.mapper.orm.massindexing.AbstractMassIndexingErrorIT.setup(AbstractMassIndexingErrorIT.java:500) ~[test-classes/:?] at org.hibernate.search.integrationtest.mapper.orm.massindexing.AbstractMassIndexingErrorIT.entityLoading(AbstractMassIndexingErrorIT.java:93) ~[test-classes/:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?] at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) ~[junit-4.13.2.jar:4.13.2] at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) ~[junit-4.13.2.jar:4.13.2] at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) ~[junit-4.13.2.jar:4.13.2] at org.mockito.internal.junit.JUnitSessionStore$1.evaluateSafely(JUnitSessionStore.java:55) ~[mockito-core-4.6.1.jar:?] at org.mockito.internal.junit.JUnitSessionStore$1.evaluate(JUnitSessionStore.java:43) ~[mockito-core-4.6.1.jar:?] at org.hibernate.search.util.impl.integrationtest.common.rule.BackendMock$1.evaluate(BackendMock.java:52) ~[hibernate-search-util-internal-integrationtest-common-6.2.0-SNAPSHOT.jar:?] at org.hibernate.search.util.impl.integrationtest.common.rule.MappingSetupHelper$1.evaluate(MappingSetupHelper.java:74) ~[hibernate-search-util-internal-integrationtest-common-6.2.0-SNAPSHOT.jar:?] at org.hibernate.search.util.impl.integrationtest.common.TestConfigurationProvider$1.evaluate(TestConfigurationProvider.java:45) ~[hibernate-search-util-internal-integrationtest-common-6.2.0-SNAPSHOT.jar:?] at org.hibernate.search.util.impl.integrationtest.common.rule.ThreadSpy$1.evaluate(ThreadSpy.java:42) ~[hibernate-search-util-internal-integrationtest-common-6.2.0-SNAPSHOT.jar:?] at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.ParentRunner.run(ParentRunner.java:413) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.Suite.runChild(Suite.java:128) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.Suite.runChild(Suite.java:27) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) ~[junit-4.13.2.jar:4.13.2] at org.junit.runners.ParentRunner.run(ParentRunner.java:413) ~[junit-4.13.2.jar:4.13.2] at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) ~[surefire-junit47-3.0.0-M7.jar:3.0.0-M7] at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) ~[surefire-junit47-3.0.0-M7.jar:3.0.0-M7] at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) ~[surefire-junit47-3.0.0-M7.jar:3.0.0-M7] at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) ~[surefire-junit47-3.0.0-M7.jar:3.0.0-M7] at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) ~[surefire-junit47-3.0.0-M7.jar:3.0.0-M7] at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) ~[surefire-junit47-3.0.0-M7.jar:3.0.0-M7] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:456) ~[surefire-booter-3.0.0-M7.jar:3.0.0-M7] at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:169) ~[surefire-booter-3.0.0-M7.jar:3.0.0-M7] at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:595) ~[surefire-booter-3.0.0-M7.jar:3.0.0-M7] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:581) ~[surefire-booter-3.0.0-M7.jar:3.0.0-M7] Caused by: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:629) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:563) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1150) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:770) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:298) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:497) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:111) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1010) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.OracleStatement.executeSQLStatement(OracleStatement.java:1530) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1310) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:2162) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:2117) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:327) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase.accept(GenerationTargetToDatabase.java:54) ~[hibernate-core-5.6.10.Final.jar:5.6.10.Final] ... 62 more Caused by: oracle.jdbc.OracleDatabaseException: ORA-00942: table or view does not exist at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:636) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:563) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1150) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:770) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:298) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:497) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:111) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1010) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.OracleStatement.executeSQLStatement(OracleStatement.java:1530) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1310) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:2162) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:2117) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:327) ~[ojdbc8-21.6.0.0.1.jar:21.6.0.0.1] at org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase.accept(GenerationTargetToDatabase.java:54) ~[hibernate-core-5.6.10.Final.jar:5.6.10.Final] ... 62 more 09:51:13,076 (main) INFO access:48 - HHH10001501: Connection obtained from JdbcConnectionAccess [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator$ConnectionProviderJdbcConnectionAccess@4f87b2e0] for (non-JTA) DDL execution was not in auto-commit mode; the Connection 'local transaction' will be committed and the Connection will be set into auto-commit mode. 09:51:13,083 (main) INFO JtaPlatformInitiator:52 - HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.JBossStandAloneJtaPlatform] 09:51:13,085 (main) DEBUG PojoMapper:179 - HSEARCH700018: Detected entity types: [HibernateOrmClassRawTypeModel[org.hibernate.search.integrationtest.mapper.orm.massindexing.AbstractMassIndexingErrorIT$Book]], indexed types: [HibernateOrmClassRawTypeModel[org.hibernate.search.integrationtest.mapper.orm.massindexing.AbstractMassIndexingErrorIT$Book]], initial mapped types: [HibernateOrmClassRawTypeModel[org.hibernate.search.integrationtest.mapper.orm.massindexing.AbstractMassIndexingErrorIT$Book]]. 09:51:13,085 (main) DEBUG PojoIndexedTypeManagerBuilder:159 - HSEARCH700017: Type manager for indexed type 'org.hibernate.search.integrationtest.mapper.orm.massindexing.AbstractMassIndexingErrorIT$Book': entityName: Book typeIdentifier: org.hibernate.search.integrationtest.mapper.orm.massindexing.AbstractMassIndexingErrorIT$Book indexManager: MappedIndexManagerImpl[implementor=StubIndexManager[Book]] identifierMapping: PropertyIdentifierMapping[handle=MethodHandleValueReadHandle[public java.lang.Integer org.hibernate.search.integrationtest.mapper.orm.massindexing.AbstractMassIndexingErrorIT$Book.getId()], bridgeHolder=SimpleBeanHolder[instance=DefaultIntegerBridge]] documentRouter: org.hibernate.search.mapper.pojo.bridge.runtime.impl.NoOpDocumentRouter@5a466dd processor: operation: process type objectFieldsToCreate: nested: - operation: process property handle: MethodHandleValueReadHandle[public java.lang.String org.hibernate.search.integrationtest.mapper.orm.massindexing.AbstractMassIndexingErrorIT$Book.getAuthor()] nested: operation: apply value bridge bridge: SimpleBeanHolder[instance=DefaultStringBridge] indexField: StubIndexFieldReference[author] - operation: process property handle: MethodHandleValueReadHandle[public java.lang.String org.hibernate.search.integrationtest.mapper.orm.massindexing.AbstractMassIndexingErrorIT$Book.getTitle()] nested: operation: apply value bridge bridge: SimpleBeanHolder[instance=DefaultStringBridge] indexField: StubIndexFieldReference[title] isEntityType: true reindexingResolver: operation: root dirtyPathsTriggeringSelfReindexing: [author, title] containingEntitiesResolverRoot: operation: no op 09:51:13,086 (main) DEBUG ConfiguredAutomaticIndexingStrategy:119 - Hibernate Search event listeners deactivated 09:51:13,568 (Hibernate Search - Mass indexing - Book - ID loading - 0) DEBUG HibernateOrmMassIdentifierLoader:444 - going to fetch 1499 primary keys 09:51:13,571 (Hibernate Search - Mass indexing - Book - ID loading - 0) INFO PojoMassIndexingLoggingMonitor:92 - HSEARCH000027: Mass indexing is going to index 1499 entities. 09:51:13,591 (Hibernate Search - Mass indexing - Workspace - 0) DEBUG CancellableExecutionCompletableFuture:45 - Could not cancel Future java.util.concurrent.FutureTask@8a185d3[Completed normally] (mayInterruptIfRunning = true) 09:51:13,594 (Hibernate Search - Mass indexing - Book - ID loading - 0) WARN SqlExceptionHelper:137 - SQL Error: 17002, SQLState: 08006 09:51:13,594 (Hibernate Search - Mass indexing - Book - ID loading - 0) ERROR SqlExceptionHelper:142 - IO Error: Socket read interrupted 09:51:13,696 (main) INFO SchemaDropperImpl$DelayedDropActionImpl:538 - HHH000477: Starting delayed evictData of schema as part of SessionFactory shut-down' 09:51:13,697 (main) INFO access:48 - HHH10001501: Connection obtained from JdbcConnectionAccess [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator$ConnectionProviderJdbcConnectionAccess@4111a657] for (non-JTA) DDL execution was not in auto-commit mode; the Connection 'local transaction' will be committed and the Connection will be set into auto-commit mode. 09:51:13,717 (main) INFO pooling:550 - HHH10001008: Cleaning up connection pool [jdbc:oracle:thin:@localhost:1521/XE] ( https://hibernate.atlassian.net/browse/HSEARCH-4670#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4670#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#100204- sha1:2e7ea99 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4669) Provide contextual information about the projection definition when it cannot be applied to an index

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=eyJpIjoiNGQ2NGM2... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-4669?atlOrigin=eyJpIjoiNGQ... ) HSEARCH-4669 ( https://hibernate.atlassian.net/browse/HSEARCH-4669?atlOrigin=eyJpIjoiNGQ... ) Provide contextual information about the projection definition when it cannot be applied to an index ( https://hibernate.atlassian.net/browse/HSEARCH-4669?atlOrigin=eyJpIjoiNGQ... ) Issue Type: Improvement Assignee: Unassigned Components: mapper-pojo-base Created: 10/Aug/2022 02:56 AM Fix Versions: 6.2-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) When, in a search query definition, someone calls.select(MyProjectionClass.class) , it’s possible that this class’s @ProjectionConstructor references fields that don’t exist, or are not projectable, and that will lead to an exception being thrown. That exception includes all the necessary information about the problem to fix (field name, why it cannot be targeted, etc.), but it lacks information about why that problem occurred, i.e. which projection definition could not be applied exactly. That information would be especially useful in the case of nested {{@ProjectionConstructor}}s. Concretely, this would mean catching SearchException in org.hibernate.search.mapper.pojo.search.definition.impl.PojoConstructorProjectionDefinition#apply and throwing another SearchException with a message such as “Could not apply projection constructor <name>: <message from the cause>”, (of course we’d also use the caught exception as the cause). We may have to tune this a bit to avoid very complicated messages when there are multiple levels of projection constructor nesting. ( https://hibernate.atlassian.net/browse/HSEARCH-4669#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4669#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#100204- sha1:2e7ea99 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4668) Avoid error logs when logging compiler/VM version during the build

by Automation for Jira (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4668) Avoid error logs when logging compiler/VM version during the build

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4668) Use info level instead of error level when logging compiler/VM version during the build

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4668) Use info level instead of error level when logging compiler/VM version during the build

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=eyJpIjoiYzRhMzBl... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-4668?atlOrigin=eyJpIjoiYzR... ) HSEARCH-4668 ( https://hibernate.atlassian.net/browse/HSEARCH-4668?atlOrigin=eyJpIjoiYzR... ) Use info level instead of error level when logging compiler/VM version during the build ( https://hibernate.atlassian.net/browse/HSEARCH-4668?atlOrigin=eyJpIjoiYzR... ) Issue Type: Task Assignee: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: build Created: 10/Aug/2022 01:26 AM Fix Versions: 6.2-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Currently we get things like this: [INFO] --- exec-maven-plugin:3.1.0:exec (print-java-main-compiler-version) @ hibernate-search-build-config --- [ERROR] [main] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/var/lib/jenkins/workspace/arch-personal-yoann_HSEARCH-4579(a)tmp/withMavenc623f12d/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/var/lib/jenkins/workspace/arch-personal-yoann_HSEARCH-4579@tmp/withMavenc623f12d" [INFO] [main] javac 17.0.2 [INFO] [INFO] --- exec-maven-plugin:3.1.0:exec (print-java-main-compiler-java-version) @ hibernate-search-build-config --- [ERROR] [main] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/var/lib/jenkins/workspace/arch-personal-yoann_HSEARCH-4579(a)tmp/withMavenc623f12d/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/var/lib/jenkins/workspace/arch-personal-yoann_HSEARCH-4579@tmp/withMavenc623f12d" [ERROR] [main] openjdk version "17.0.2" 2022-01-18 [ERROR] [main] OpenJDK Runtime Environment Temurin-17.0.2+8 (build 17.0.2+8) [ERROR] [main] OpenJDK 64-Bit Server VM Temurin-17.0.2+8 (build 17.0.2+8, mixed mode, sharing) [INFO] [INFO] --- exec-maven-plugin:3.1.0:exec (print-java-main-release-version) @ hibernate-search-build-config --- [INFO] [main] Main code compiled with -release 8 [INFO] [INFO] --- exec-maven-plugin:3.1.0:exec (print-java-test-compiler-version) @ hibernate-search-build-config --- [ERROR] [main] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/var/lib/jenkins/workspace/arch-personal-yoann_HSEARCH-4579(a)tmp/withMavenc623f12d/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/var/lib/jenkins/workspace/arch-personal-yoann_HSEARCH-4579@tmp/withMavenc623f12d" [INFO] [main] javac 17.0.2 [INFO] [INFO] --- exec-maven-plugin:3.1.0:exec (print-java-test-compiler-java-version) @ hibernate-search-build-config --- [ERROR] [main] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/var/lib/jenkins/workspace/arch-personal-yoann_HSEARCH-4579(a)tmp/withMavenc623f12d/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/var/lib/jenkins/workspace/arch-personal-yoann_HSEARCH-4579@tmp/withMavenc623f12d" [ERROR] [main] openjdk version "17.0.2" 2022-01-18 [ERROR] [main] OpenJDK Runtime Environment Temurin-17.0.2+8 (build 17.0.2+8) [ERROR] [main] OpenJDK 64-Bit Server VM Temurin-17.0.2+8 (build 17.0.2+8, mixed mode, sharing) [INFO] [INFO] --- exec-maven-plugin:3.1.0:exec (print-java-test-launcher-version) @ hibernate-search-build-config --- [ERROR] [main] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/var/lib/jenkins/workspace/arch-personal-yoann_HSEARCH-4579(a)tmp/withMavenc623f12d/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/var/lib/jenkins/workspace/arch-personal-yoann_HSEARCH-4579@tmp/withMavenc623f12d" [ERROR] [main] openjdk version "17.0.2" 2022-01-18 [ERROR] [main] OpenJDK Runtime Environment Temurin-17.0.2+8 (build 17.0.2+8) [ERROR] [main] OpenJDK 64-Bit Server VM Temurin-17.0.2+8 (build 17.0.2+8, mixed mode, sharing) [INFO] What we’re logging is obviously not errors, but it’s displayed as such because the version is displayed on stderr. Maybe we can do something about that, at least for recent JDKs? ( https://hibernate.atlassian.net/browse/HSEARCH-4668#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4668#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#100204- sha1:2e7ea99 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HV-1925) Switch to WildFly 27 for testing and remove the remaining javax stuff

by Guillaume Smet (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HV-1925) Switch to WildFly 27 for testing and remove the remaining javax stuff

by Guillaume Smet (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4667) Add a configuration properties reference to the reference documentation

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=eyJpIjoiMDZhNTRk... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-4667?atlOrigin=eyJpIjoiMDZ... ) HSEARCH-4667 ( https://hibernate.atlassian.net/browse/HSEARCH-4667?atlOrigin=eyJpIjoiMDZ... ) Add a configuration properties reference to the reference documentation ( https://hibernate.atlassian.net/browse/HSEARCH-4667?atlOrigin=eyJpIjoiMDZ... ) Issue Type: Task Assignee: Unassigned Components: documentation Created: 09/Aug/2022 06:12 AM Fix Versions: 6.x-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We do document all configuration properties in the reference documentation already, but they’re spread all over the documentation. It’s sometimes useful to simply have an index, a list of configuration properties with a short explanation; it seems it would have helped this user ( https://stackoverflow.com/q/73016660/6692043 ) , at least. Javadoc is supposed to serve this purpose, especially since we have *Settings classes listing all configuration properties. However, there many *Settings classes spread over all modules, which makes it hard to quickly get a view of all possible configuration properties. We should probably work on a tool that inspects source code or .class files, then generates a list of all configuration properties, with: * The full property key, which is a prefix followed by the value of a Java constant in a *Settings class. Generating all possible prefixes might be a bit complex, especially for backend/index properties (see https://docs.jboss.org/hibernate/stable/search/reference/en-US/html_singl... ( https://docs.jboss.org/hibernate/stable/search/reference/en-US/html_singl... ) ) * The description of the property, which is the javadoc on the Java constant in a *Settings class. * If possible, the default value of the property, which is the value of a Java constant with the same name as the one holding the property key, but in the *Settings.Defaults class. There is not always a default value. Which tool to use for generating this configuration property reference? That’s an open question. Ideally it should offer great customization (to build the property keys) and also support extracting formatted javadoc. An ad-hoc tool based on some source/bytecode processing tool (annotation processor, …) might work, but the simpler the better, and we definitely don’t want to parse/render javadoc ourselves, so we’ll need an external tool for that, at least. ( https://hibernate.atlassian.net/browse/HSEARCH-4667#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4667#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#100204- sha1:86bebeb )

3 years, 11 months

1
0
0 / 0

[JIRA] (HV-1924) Bump expressly from 5.0.0-M2 to 5.0.0

by Guillaume Smet (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HV-1924) Bump expressly from 5.0.0-M2 to 5.0.0

by Guillaume Smet (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15444) Implicit conversion due to varchar(8000)

by Andrea Boriero (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15444) Implicit conversion due to varchar(8000)

by Andrea Boriero (JIRA)

Andrea Boriero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15444 ( https://hibernate.atlassian.net/browse/HHH-15444?atlOrigin=eyJpIjoiYWFjNz... ) Re: Implicit conversion due to varchar(8000) ( https://hibernate.atlassian.net/browse/HHH-15444?atlOrigin=eyJpIjoiYWFjNz... ) Hi Shina Amin ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=62f1864... ) , This is not a forum for question, but an issue tracker to track feature requests, bug reports etc. Please use https://discourse.hibernate.org/c/hibernate-orm/5 ( https://discourse.hibernate.org/c/hibernate-orm/5 ) or https://hibernate.zulipchat.com/#narrow/stream/132096-hibernate-user ( https://hibernate.zulipchat.com/#narrow/stream/132096-hibernate-user ) Thanks ( https://hibernate.atlassian.net/browse/HHH-15444#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15444#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#100204- sha1:86bebeb )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14387) A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance with hibernate-enhance-maven-plugin

by Andrzej (JIRA)

Andrzej ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5fe8586... ) *commented* on HHH-14387 ( https://hibernate.atlassian.net/browse/HHH-14387?atlOrigin=eyJpIjoiMmQzZD... ) Re: A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance with hibernate-enhance-maven-plugin ( https://hibernate.atlassian.net/browse/HHH-14387?atlOrigin=eyJpIjoiMmQzZD... ) On Hibernate 6.2.1 error is still present. I’ve attached hibernateenhancetest_6.zip with test case. ( https://hibernate.atlassian.net/browse/HHH-14387#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14387#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#100204- sha1:86bebeb )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14387) A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance with hibernate-enhance-maven-plugin

by Andrzej (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14387) A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance with hibernate-enhance-maven-plugin

by Andrzej (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15444) Implicit conversion due to varchar(8000)

by Shina Amin (JIRA)

Shina Amin ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=62f1864... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMDIyNmEwNjI2... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15444?atlOrigin=eyJpIjoiMDIyNm... ) HHH-15444 ( https://hibernate.atlassian.net/browse/HHH-15444?atlOrigin=eyJpIjoiMDIyNm... ) Implicit conversion due to varchar(8000) ( https://hibernate.atlassian.net/browse/HHH-15444?atlOrigin=eyJpIjoiMDIyNm... ) Issue Type: Bug Affects Versions: 5.4.27 Assignee: Unassigned Components: hibernate-core Created: 08/Aug/2022 15:06 PM Priority: Major Reporter: Shina Amin ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=62f1864... ) For mssql db, I have columns with datatypes char(5), varchar(100), varchar(255). All these columns are getting converted into varchar(8000) by hibernate causing implicit conversion. How can I fix this? I am already sending sendStringParametersAsUnicode=false in connection string. ( https://hibernate.atlassian.net/browse/HHH-15444#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15444#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#100204- sha1:3bd651e )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15441) Improve error message if SqlTypes type code can't be interpreted

by Christian Beikov (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15438) PostgreSQL integration classes shouldn't throw ClassNotFoundException on org.postgresql driver classes that we try loading

by Christian Beikov (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15443) Support custom DDL types also if JDBC driver classes are invisible

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYWNlOTc1YzYx... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15443?atlOrigin=eyJpIjoiYWNlOT... ) HHH-15443 ( https://hibernate.atlassian.net/browse/HHH-15443?atlOrigin=eyJpIjoiYWNlOT... ) Support custom DDL types also if JDBC driver classes are invisible ( https://hibernate.atlassian.net/browse/HHH-15443?atlOrigin=eyJpIjoiYWNlOT... ) Issue Type: Improvement Affects Versions: 6.1.2 Assignee: Unassigned Components: hibernate-core Created: 08/Aug/2022 10:37 AM Fix Versions: 6.1.3 Priority: Major Reporter: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) After https://hibernate.atlassian.net/browse/HHH-15438 ( https://hibernate.atlassian.net/browse/HHH-15438 ) we will not register certain JdbcType and DdlType entries anymore if the JDBC driver classes for reading/writing data are not visible. Very often, we can handle this by introducing casts for expressions that infer this type e.g. parameter markers for insert etc. I suggest we introduce the following default methods in JdbcType : default String wrapReadExpression( String readExpression) { return readExpression; } default String wrapWriteExpression( String writeExpression) { return writeExpression; } We can then register custom JdbcType implementations that bind/extract e.g. JSON as plain String. For geometry , geography , interval and inet we will probably also have to encode the data as String and hence also wrap the readExpression with a cast to String. ( https://hibernate.atlassian.net/browse/HHH-15443#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15443#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#100204- sha1:3bd651e )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-7510) LazyInitializationException thrown when deleting an entity while global_with_modified_flag turned on

by Luís Alves (JIRA)

Luís Alves ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-7510 ( https://hibernate.atlassian.net/browse/HHH-7510?atlOrigin=eyJpIjoiZWJlMGF... ) Re: LazyInitializationException thrown when deleting an entity while global_with_modified_flag turned on ( https://hibernate.atlassian.net/browse/HHH-7510?atlOrigin=eyJpIjoiZWJlMGF... ) I’m running version 5.6.10.Final and it seems that I have similar problem to the one reported here. Here is the stacktrace: Caused by: org.hibernate.LazyInitializationException: failed to lazily initialize a collection, could not initialize proxy - no Session at org.hibernate.collection.internal.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:614) at org.hibernate.collection.internal.AbstractPersistentCollection.withTemporarySessionIfNeeded(AbstractPersistentCollection.java:218) at org.hibernate.collection.internal.AbstractPersistentCollection.readSize(AbstractPersistentCollection.java:162) at org.hibernate.collection.internal.PersistentBag.isEmpty(PersistentBag.java:376) at org.hibernate.envers.internal.entities.mapper.relation.AbstractCollectionMapper.isFromNullToEmptyOrFromEmptyToNull(AbstractCollectionMapper.java:206) at org.hibernate.envers.internal.entities.mapper.relation.AbstractCollectionMapper.mapModifiedFlagsToMapFromEntity(AbstractCollectionMapper.java:172) at org.hibernate.envers.internal.entities.mapper.MultiPropertyMapper.map(MultiPropertyMapper.java:91) at org.hibernate.envers.internal.synchronization.work.DelWorkUnit.generateData(DelWorkUnit.java:62) 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:175) 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:2426) at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.beforeTransactionCompletion(JdbcCoordinatorImpl.java:449) 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) at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl$TransactionDriverControlImpl.commit(JdbcResourceLocalTransactionCoordinatorImpl.java:281) at org.hibernate.engine.transaction.internal.TransactionImpl.commit(TransactionImpl.java:101) at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:562) This happens when I delete a OneToMany relationship that has children after running a test. When empty the cleanup after test runs successfully. The only difference is that I don’t have the global flag, but instead @Audited(withModifiedFlag = true. Enabling enable_lazy_load_no_trans: true cause a NPE instead. Might the bug still exist? ( https://hibernate.atlassian.net/browse/HHH-7510#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-7510#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#100204- sha1:3bd651e )

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4642) Upgrade build dependencies to the latest version

by Yoann Rodière (JIRA)

3 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 August 2022