February 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HSEARCH-3839) Sorting by numeric value has an exception "(expected=NUMERIC). Use UninvertingReader or index with docvalues"

by Waldemar Kłaczyński (JIRA)

Waldemar Kłaczyński ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-3839 ( https://hibernate.atlassian.net/browse/HSEARCH-3839?atlOrigin=eyJpIjoiYTl... ) Re: Sorting by numeric value has an exception "(expected=NUMERIC). Use UninvertingReader or index with docvalues" ( https://hibernate.atlassian.net/browse/HSEARCH-3839?atlOrigin=eyJpIjoiYTl... ) As suggested, I put the proposed solution on hibernate-search for git. I have improved the formatting to Eclipse. https://github.com/wklaczynski/hibernate-search/tree/multivalues-problem-... As for other aggregation and search problems, I also have to solve this. Unfortunately, I can't wait, problems are critical for me, I can't develop my assumptions for my project without it. So I can't wait. I will try to find a solution to the problems. Of course, I will propose the solution as an offer. ( https://hibernate.atlassian.net/browse/HSEARCH-3839#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3839#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#100121- sha1:0fbe7c1 )

4 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-3814) Mark experimental APIs/SPIs with an @Incubating annotation

by Fabio Massimo Ercoli (JIRA)

4 years, 2 months

1
0
0 / 0

[JIRA] (HBX-1999) Remove class 'org.hibernate.tool.internal.reveng.DefaultAssociationInfo' and implement factory method for AssociationInfo in RevengUtils

by Koen Aers (JIRA)

4 years, 2 months

1
0
0 / 0

[JIRA] (HHH-12414) Referential Integrity Constraint Violation - Unidirectional OneToOne with Cascade.ALL, optional false and @PrimaryKeyColumnJoin

by Sanne Grinovero (JIRA)

4 years, 2 months

1
0
0 / 0

[JIRA] (HHH-12414) Referential Integrity Constraint Violation - Unidirectional OneToOne with Cascade.ALL, optional false and @PrimaryKeyColumnJoin

by Sanne Grinovero (JIRA)

4 years, 2 months

1
0
0 / 0

[JIRA] (HHH-13632) Hibernate + JCache does not remove entites from cache when entity is removed

by Christian Scharmach (JIRA)

4 years, 2 months

1
0
0 / 0

[JIRA] (HHH-13322) Sequence increment is not correctly determined

by Russ Tokuyama (JIRA)

Russ Tokuyama ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5d7aabc... ) *commented* on HHH-13322 ( https://hibernate.atlassian.net/browse/HHH-13322?atlOrigin=eyJpIjoiNjgwZG... ) Re: Sequence increment is not correctly determined ( https://hibernate.atlassian.net/browse/HHH-13322?atlOrigin=eyJpIjoiNjgwZG... ) We’ve also encountered this issue. Our Spring Boot app fails to start up with this error (entity class name redacted: Caused by: org.hibernate.MappingException: Could not instantiate id generator [entity-name=<entity class>] at org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.createIdentifierGenerator(DefaultIdentifierGeneratorFactory.java:124) ~[hibernate-core-5.4.9.Final.jar:5.4.9.Final] at org.hibernate.mapping.SimpleValue.createIdentifierGenerator(SimpleValue.java:344) ~[hibernate-core-5.4.9.Final.jar:5.4.9.Final] hibernate-core: 5.4.9.Final JVM: Zulu 8.42.0.23-CA-macosx OS: Macos 10.14.6 DB: Oracle 12c I did some debugging with IntelliJ and traced things to the getSequenceIncrementValue() in SequenceStyleGenerator like Florian reported. Reverting to hibernate-core to 5.3.12.Final avoided the error and our app started up and worked with the Oracle sequence set to increment by 50 to match the default allocationSize of 50 for the @SequenceGenerator annotation. ( https://hibernate.atlassian.net/browse/HHH-13322#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13322#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#100121- sha1:cefda43 )

4 years, 2 months

1
0
0 / 0

[JIRA] (HHH-12104) @Where clause is ignored when eagerly loading ManyToOne association

by Stuart Purdie (JIRA)

Stuart Purdie ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e569e7... ) *commented* on HHH-12104 ( https://hibernate.atlassian.net/browse/HHH-12104?atlOrigin=eyJpIjoiM2I3Nj... ) Re: @Where clause is ignored when eagerly loading ManyToOne association ( https://hibernate.atlassian.net/browse/HHH-12104?atlOrigin=eyJpIjoiM2I3Nj... ) We’ve encountered a case which I believe is really an instance of this bug. We have a set of (~100) Entities (most with soft delete implemented), and a moderately interwoven set of dependancies with them. Whilst everything works fine with direct loading (as all the key relationships between soft deletable Entities are Lazy), if we use CriteriaBuilder and are doing a join between two soft deleted Entities, the @Where annotation is not utilised for the Entity that is the target of the join. I believe (although have not proven) that this is an instance of this problem, as the use of the explicit join through the CriteriaBuilder makes those joins explicitly eager; irrespective of what the ‘default’ specified on the Entity itself is. (This is with Hibernate 5.4.3). In order to work around this, we have to ensure we include the @Where condition in each query; which does somewhat reduce the value of the @Where, particularly when there’s 4-5 such joins in the query. ( https://hibernate.atlassian.net/browse/HHH-12104#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-12104#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#100121- sha1:cefda43 )

4 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-3841) Offline startup of the Elasticsearch backend

by Yoann Rodière (JIRA)

4 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-3839) Sorting by numeric value has an exception "(expected=NUMERIC). Use UninvertingReader or index with docvalues"

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-3839 ( https://hibernate.atlassian.net/browse/HSEARCH-3839?atlOrigin=eyJpIjoiNWQ... ) Re: Sorting by numeric value has an exception "(expected=NUMERIC). Use UninvertingReader or index with docvalues" ( https://hibernate.atlassian.net/browse/HSEARCH-3839?atlOrigin=eyJpIjoiNWQ... ) > This is also a critical problem, I will try to solve it. If the problem is just that too many values are considered during the sort, I'd recommend that you submit a PR first and that we create a follow-up ticket to address this as a separate issue. From what I understand, Elasticsearch has a dedicated feature for that ( https://www.elastic.co/guide/en/elasticsearch/reference/current/search-re... ) , and this will likely require extensive testing if we re-implement it in Hibernate Search. Let's address one problem at a time? ( https://hibernate.atlassian.net/browse/HSEARCH-3839#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3839#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#100121- sha1:cefda43 )

4 years, 2 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 February 2020