July 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-14129) Bidirectional relationship fails to save after upgrading to 5.4.17

by Eduardo Simioni (JIRA)

Eduardo Simioni ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14129 ( https://hibernate.atlassian.net/browse/HHH-14129?atlOrigin=eyJpIjoiZWJkMz... ) Re: Bidirectional relationship fails to save after upgrading to 5.4.17 ( https://hibernate.atlassian.net/browse/HHH-14129?atlOrigin=eyJpIjoiZWJkMz... ) Although removing the NotNull annotation makes the unit test pass, it is not a solution since in a production scenario the column wouldn’t be nullable. ( https://hibernate.atlassian.net/browse/HHH-14129#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14129#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#100140- sha1:5beb332 )

3 years, 9 months

1
0
0 / 0

[JIRA] (HHH-14129) Bidirectional relationship fails to save after upgrading to 5.4.17

by Eduardo Simioni (JIRA)

Eduardo Simioni ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNGJlZTUwOWU2... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14129?atlOrigin=eyJpIjoiNGJlZT... ) HHH-14129 ( https://hibernate.atlassian.net/browse/HHH-14129?atlOrigin=eyJpIjoiNGJlZT... ) Bidirectional relationship fails to save after upgrading to 5.4.17 ( https://hibernate.atlassian.net/browse/HHH-14129?atlOrigin=eyJpIjoiNGJlZT... ) Change By: Eduardo Simioni ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) After updating upgrading from 5.4.16 to 5.4.17 we had several unit tests failing in one of our projects. I did some investigation and came up with a minimum scenario and test case that reproduces the problem: {code:java} @Entity public class Child { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private Long id; @NotNull @ManyToOne private Parent parent; public void setParent(Parent parent) { this.parent = parent; } } @Entity public class Parent { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private Long id; @ManyToOne(cascade = CascadeType.ALL) private Child child; public Parent(Child child) { this.child = child; this.child.setParent(this); } public Child getChild() { return child; } } {code} And a test case: {code:java} @ExtendWith(SpringExtension.class) public class ParentChildTest { @Test @Transactional public void save() { Parent parent = new Parent(new Child()); sessionFactory.getCurrentSession().save(parent); sessionFactory.getCurrentSession().setHibernateFlushMode(FlushMode.MANUAL); sessionFactory.getCurrentSession().flush(); } @Resource private SessionFactory sessionFactory; } {code} With 5.4.16 the following statements are executed and the test completes successfully {code:sql} insert into parent (id, child_id) values (null, ?) insert into child (id, parent_id) values (null, ?) update parent set child_id=? where id=? {code} With 5.4.17 the result is {noformat} DEBUG [SQL] insert into child (id, parent_id) values (null, ?) WARN [SqlExceptionHelper] SQL Error: 23502, SQLState: 23502 ERROR [SqlExceptionHelper] NULL not allowed for column "PARENT_ID"; SQL statement: insert into child (id, parent_id) values (null, ?) [23502-200] {noformat} If the @NotNulll annotation is removed the entities are saved without any problem, only in a different order {code:sql} insert into child (id, parent_id) values (null, ?) insert into parent (id, child_id) values (null, ?) update child set parent_id=? where id=? {code} # It seems to be related with the fix provided by [ HHH-10956 ] * ( https://hibernate.atlassian.net/browse/HHH-14129#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14129#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#100140- sha1:5beb332 )

3 years, 9 months

1
0
0 / 0

[JIRA] (HHH-14129) Bidirectional relationship fails to save after upgrading to 5.4.17

by Eduardo Simioni (JIRA)

3 years, 9 months

1
0
0 / 0

[JIRA] (HHH-14129) Bidirectional relationship fails to save after updating to 5.4.17

by Eduardo Simioni (JIRA)

Eduardo Simioni ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOGE2OTQyYzAy... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14129?atlOrigin=eyJpIjoiOGE2OT... ) HHH-14129 ( https://hibernate.atlassian.net/browse/HHH-14129?atlOrigin=eyJpIjoiOGE2OT... ) Bidirectional relationship fails to save after updating to 5.4.17 ( https://hibernate.atlassian.net/browse/HHH-14129?atlOrigin=eyJpIjoiOGE2OT... ) Issue Type: Bug Affects Versions: 5.4.17 Assignee: Unassigned Components: hibernate-core Created: 30/Jul/2020 14:38 PM Environment: H2 Database in MySQL mode was used for the test Priority: Major Reporter: Eduardo Simioni ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) After updating from 5.4.16 to 5.4.17 we had several unit tests failing in one of our projects. I did some investigation and came up with a minimum scenario and test case that reproduces the problem: @Entity public class Child { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private Long id; @NotNull @ManyToOne private Parent parent; public void setParent(Parent parent) { this.parent = parent; } } @Entity public class Parent { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private Long id; @ManyToOne(cascade = CascadeType.ALL) private Child child; public Parent(Child child) { this.child = child; this.child.setParent( this ); } public Child getChild() { return child; } } And a test case: @ExtendWith(SpringExtension.class) public class ParentChildTest { @Test @Transactional public void save() { Parent parent = new Parent( new Child()); sessionFactory.getCurrentSession().save(parent); sessionFactory.getCurrentSession().setHibernateFlushMode(FlushMode.MANUAL); sessionFactory.getCurrentSession().flush(); } @Resource private SessionFactory sessionFactory; } With 5.4.16 the following statements are executed and the test completes successfully insert into parent (id, child_id) values ( null , ?) insert into child (id, parent_id) values ( null , ?) update parent set child_id=? where id=? With 5.4.17 the result is DEBUG [SQL] insert into child (id, parent_id) values (null, ?) WARN [SqlExceptionHelper] SQL Error: 23502, SQLState: 23502 ERROR [SqlExceptionHelper] NULL not allowed for column "PARENT_ID"; SQL statement: insert into child (id, parent_id) values (null, ?) [23502-200] If the @NotNulll annotation is removed the entities are saved without any problem, only in a different order insert into child (id, parent_id) values ( null , ?) insert into parent (id, child_id) values ( null , ?) update child set parent_id=? where id=? It seems to be related with the fix provided by HHH-10956 ( https://hibernate.atlassian.net/browse/HHH-10956 ) Closed ( https://hibernate.atlassian.net/browse/HHH-14129#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14129#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#100140- sha1:5beb332 )

3 years, 9 months

1
0
0 / 0

[JIRA] (HSEARCH-3976) Document scrolling

by Yoann Rodière (JIRA)

3 years, 9 months

1
0
0 / 0

[JIRA] (HSEARCH-3976) Document scrolling

by Yoann Rodière (JIRA)

3 years, 9 months

1
0
0 / 0

[JIRA] (HSEARCH-3975) Expose scrolling operations through JPA/ORM queries

by Yoann Rodière (JIRA)

3 years, 9 months

1
0
0 / 0

[JIRA] (HSEARCH-3975) Expose scrolling operations through JPA/ORM queries

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=eyJpIjoiMzgzZTIx... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-3975?atlOrigin=eyJpIjoiMzg... ) HSEARCH-3975 ( https://hibernate.atlassian.net/browse/HSEARCH-3975?atlOrigin=eyJpIjoiMzg... ) Expose scrolling operations through JPA/ORM queries ( https://hibernate.atlassian.net/browse/HSEARCH-3975?atlOrigin=eyJpIjoiMzg... ) Issue Type: Task Assignee: Unassigned Components: mapper-orm Created: 30/Jul/2020 09:04 AM Fix Versions: 6.0.0.Beta-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) > > * Implement scroll() and scroll(ScrollMode) in HibernateOrmSearchQueryAdapter > , relying on SearchQuery#scroll(int) under the scene. * Only ScrollMode.FORWARD_ONLY > will be supported. > * We will need to decide on a page size. Let's use the same size as the > loading fetch size, which should be accessible from org.hibernate.search.mapper.orm.search.loading.impl.MutableEntityLoadingOptions#getFetchSize > . > * Some internal windowing will probably be necessary. Just copy/paste the org.hibernate.search.elasticsearch.util.impl.Window > class from Search 5 and adapt it. Do not forget to also copy the unit > test, org.hibernate.search.elasticsearch.test.WindowTest. > * See org.hibernate.search.query.hibernate.impl.ScrollableResultsImpl for > an example of how it was done in Search 5 (may or may not be helpful). > > * Add tests for scroll() and scroll(ScrollMode) in org.hibernate.search.integrationtest.mapper.orm.hibernateormapis.ToHibernateOrmIT > : * Nominal case (create scroll, fetch some hits until all hits have been > consumed, close). > * Edge cases: not fetching any result (should work fine), fetching some > results but not all of them (should work fine), trying to fetch more than > the total hit count (should throw an exception). > * Error cases: trying to scroll back, trying to call the get*(int) methods... > > * Check that using any scroll mode other than ScrollMode.FORWARD_ONLY > fails. > * Test query.stream() too (it's based on scroll() ). > > * Add tests for getResultStream() in org.hibernate.search.integrationtest.mapper.orm.hibernateormapis.ToJpaIT > . > ( https://hibernate.atlassian.net/browse/HSEARCH-3975#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3975#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#100140- sha1:5beb332 )

3 years, 9 months

1
0
0 / 0

[JIRA] (HSEARCH-3974) Backend-specific extensions for scroll

by Yoann Rodière (JIRA)

3 years, 9 months

1
0
0 / 0

[JIRA] (HSEARCH-3974) Backend-specific extensions for scroll

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=eyJpIjoiNzA2MDQ5... ) / New Feature ( https://hibernate.atlassian.net/browse/HSEARCH-3974?atlOrigin=eyJpIjoiNzA... ) HSEARCH-3974 ( https://hibernate.atlassian.net/browse/HSEARCH-3974?atlOrigin=eyJpIjoiNzA... ) Backend-specific extensions for scroll ( https://hibernate.atlassian.net/browse/HSEARCH-3974?atlOrigin=eyJpIjoiNzA... ) Issue Type: New Feature Assignee: Unassigned Components: backend-elasticsearch, backend-lucene Created: 30/Jul/2020 09:03 AM Fix Versions: 6.0.0.Beta-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) See item 12 in HSEARCH-3323: > > > > Allow backends to extend the SearchScroll interfaces, like they currently > do with SearchQuery ( ElasticsearchSearchQuery , LuceneSearchQuery ): > > * Add a generic parameter S extends SearchScroll<H> to ExtendedSearchFetchable > and override its scroll methods to return that type. > * Adapt the interfaces that extend ExtendedSearchFetchable as necessary. > * Create a new ExtendedSearchScroll<H> interface using the same principle. > > * Create specific interfaces for Elasticsearch and Lucene: ElasticsearchSearchScroll > and LuceneSearchScroll. > * Implement these interfaces where appropriate. > * Test extensions for Lucene and Elasticsearch. Mainly, check that the > scroll has the correct type. See how it's done for SearchResult in org.hibernate.search.integrationtest.backend.elasticsearch.ElasticsearchExtensionIT#query > . > Optionally, we may also handle item 8, but let's discuss it together on Zulip first: > > > > Add Lucene-specific extensions to Scrolling > > * This is mainly necessary for Infinispan > * Expose a way to force Lucene to extract TopDocs up to a specific index > and retrieve them: LuceneSearchScroll#preloadTopDocsUpTo(), returns TopDocs > > * Expose a way to load a specific document specified by its index: LuceneSearchScroll#loadHitByIndex(), > returns H > * Maybe we can improve on that later; ideally Infinispan should load > multiple hits in one call ( LuceneSearchScroll#loadHitsByIndex(int ...), > returns List<H> ) otherwise the cost of creating collectors for each > retrieved hit will be a bit too much. > ( https://hibernate.atlassian.net/browse/HSEARCH-3974#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3974#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#100140- sha1:5beb332 )

3 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2020