May 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HSEARCH-3275) Search 6 groundwork - Move to a stable implementation of Lucene spatial support

by Yoann Rodière (JIRA)

5 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-3902) Expose addOrUpdate/delete/purge on IndexIndexer/PojoIndexer

by Yoann Rodière (JIRA)

5 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-3275) Search 6 groundwork - Move to a stable implementation of Lucene spatial support

by Yoann Rodière (JIRA)

5 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-3275) Search 6 groundwork - Move to a stable implementation of Lucene spatial support

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-3275 ( https://hibernate.atlassian.net/browse/HSEARCH-3275?atlOrigin=eyJpIjoiMjN... ) Re: Search 6 groundwork - Move to a stable implementation of Lucene spatial support ( https://hibernate.atlassian.net/browse/HSEARCH-3275?atlOrigin=eyJpIjoiMjN... ) The context has changed and made most of this ticket obsolete. First, LatLonPoint and related classes in Lucene are now in the core, not in the sandbox ( https://issues.apache.org/jira/browse/LUCENE-7314 ). They are thus supported to the same extent as other core features. Second, the precision of LatLonPoint seems largely sufficient for most use cases. From the javadoc of org.apache.lucene.document.LatLonPoint : > > > > Values are indexed with some loss of precision from the > > > > > > original double values (4.190951585769653E-8 for the latitude component > > > > > > and 8.381903171539307E-8 for longitude). > > In the worst case, for latitude, this gives a precision near the equator of 40,075.017/360*8.381903171539307*10^-8 = 9.33 cm, or around 3.7 inches. I'd say this is enough to find the location of a pizza joint or a rental bike, or for most use cases we're likely to encounter. So, let's just add some documentation about the precision, that should be enough. ( https://hibernate.atlassian.net/browse/HSEARCH-3275#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3275#add-comment?atlOrigin... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126- sha1:dd08494 )

5 years, 11 months

1
0
0 / 0

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

by Yoann Rodière (JIRA)

5 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14011) JoinTable referencedColumn in base class is not recognized

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14011 ( https://hibernate.atlassian.net/browse/HHH-14011?atlOrigin=eyJpIjoiMGYxMm... ) Re: JoinTable referencedColumn in base class is not recognized ( https://hibernate.atlassian.net/browse/HHH-14011?atlOrigin=eyJpIjoiMGYxMm... ) Yeah, I have that on my todo list. I’ll look into it when I have some time. ( https://hibernate.atlassian.net/browse/HHH-14011#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14011#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126- sha1:dd08494 )

5 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14017) Adding PK proxy using field access to non-pk mapped collection results in NULL constraint violation

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMzI0NTFjYjg4... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14017?atlOrigin=eyJpIjoiMzI0NT... ) HHH-14017 ( https://hibernate.atlassian.net/browse/HHH-14017?atlOrigin=eyJpIjoiMzI0NT... ) Adding PK proxy using field access to non-pk mapped collection results in NULL constraint violation ( https://hibernate.atlassian.net/browse/HHH-14017?atlOrigin=eyJpIjoiMzI0NT... ) Change By: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) A simple model that maps a collection through a unique column {code:java} @Entity @Table(name = "base_object") public class BaseObject implements Serializable { @Id @Column(name = "id") @GeneratedValue(strategy = GenerationType.AUTO) private Integer id; @Column(name = "name", nullable = false, unique = true) private String name; @ManyToMany @JoinTable( name = "related_objects", joinColumns = @JoinColumn(name = "base_name", referencedColumnName = "name"), inverseJoinColumns = @JoinColumn(name = "related_name", referencedColumnName = "name") ) private Set<RelatedObject> related = new HashSet<>(); } @Entity @Table(name = "related_object") public class RelatedObject { @Id @Column(name = "id") @GeneratedValue(strategy = GenerationType.AUTO) private Integer id; @Column(name = "name", nullable = false, unique = true) private String name; } {code} When trying to add a {{RelatedObject}} reference to the collection, the flushing fails with a NULL constraint violation, although the proxy is lazily initialized. {code:java} BaseObject b = entityManager.find(BaseObject.class, bId); RelatedObject r = entityManager.getReference(RelatedObject.class, rId); b.getRelated().add(r); entityManager.flush(); {code} Note that it works when using property mapping instead, so this seems to be related to the proxy not being narrowed before being accessed. ( https://hibernate.atlassian.net/browse/HHH-14017#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14017#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126- sha1:dd08494 )

5 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14017) Adding PK proxy using field access to non-pk mapped collection results in NULL constraint violation

by Christian Beikov (JIRA)

5 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14017) Adding PK proxy using field access to non-pk mapped collection results in NULL constraint violation

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=eyJpIjoiN2ZjY2MxOTY5... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14017?atlOrigin=eyJpIjoiN2ZjY2... ) HHH-14017 ( https://hibernate.atlassian.net/browse/HHH-14017?atlOrigin=eyJpIjoiN2ZjY2... ) Adding PK proxy using field access to non-pk mapped collection results in NULL constraint violation ( https://hibernate.atlassian.net/browse/HHH-14017?atlOrigin=eyJpIjoiN2ZjY2... ) Issue Type: Bug Affects Versions: 5.4.14 Assignee: Unassigned Components: hibernate-core Created: 12/May/2020 13:00 PM Priority: Major Reporter: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) A simple model that maps a collection through a unique column @Entity @Table(name = "base_object" ) public class BaseObject implements Serializable { @Id @Column(name = "id" ) @GeneratedValue(strategy = GenerationType.AUTO) private Integer id; @Column(name = "name" , nullable = false , unique = true ) private String name; @ManyToMany @JoinTable( name = "related_objects" , joinColumns = @JoinColumn(name = "base_name" , referencedColumnName = "name" ), inverseJoinColumns = @JoinColumn(name = "related_name" , referencedColumnName = "name" ) ) private Set<RelatedObject> related = new HashSet<>(); } @Entity @Table(name = "related_object" ) public class RelatedObject { @Id @Column(name = "id" ) @GeneratedValue(strategy = GenerationType.AUTO) private Integer id; @Column(name = "name" , nullable = false , unique = true ) private String name; } When trying to add a RelatedObject reference to the collection, the flushing fails with a NULL constraint violation, although the proxy is lazily initialized. BaseObject b = entityManager.find(BaseObject.class, bId); RelatedObject r = entityManager.getReference(RelatedObject.class, rId); b.getRelated().add(r); entityManager.flush(); ( https://hibernate.atlassian.net/browse/HHH-14017#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14017#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126- sha1:dd08494 )

5 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14016) Can not prevent cache region from being cleared from second level cache on bulk update

by Erik (JIRA)

Erik ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMWJiOWMxZTdm... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-14016?atlOrigin=eyJpIjoiMWJiOW... ) HHH-14016 ( https://hibernate.atlassian.net/browse/HHH-14016?atlOrigin=eyJpIjoiMWJiOW... ) Can not prevent cache region from being cleared from second level cache on bulk update ( https://hibernate.atlassian.net/browse/HHH-14016?atlOrigin=eyJpIjoiMWJiOW... ) Issue Type: Improvement Affects Versions: 5.4.15 Assignee: Unassigned Created: 12/May/2020 10:57 AM Priority: Minor Reporter: Erik ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Bulk updates using queries or the criteria API can be used to avoid fetching an entity before executing the update. For example: UPDATE User u SET u.deleted = true WHERE u.id = :id In this case, the only modified entity is known, and the entity in question could be manually evicted from the second level cache. Instead, the whole cache region is evicted through a BulkOperationCleanupAction , and I have not been able to find a workaround for this. Currently it seems like it'd require modifying the EntityPersister itself, as this is where the affected regions are taken from. ( https://hibernate.atlassian.net/browse/HHH-14016#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14016#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126- sha1:dd08494 )

5 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2020