February 2020 - hibernate-issues - Jboss List Archives

[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 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=eyJpIjoiYTN... ) Re: Sorting by numeric value has an exception "(expected=NUMERIC). Use UninvertingReader or index with docvalues" ( https://hibernate.atlassian.net/browse/HSEARCH-3839?atlOrigin=eyJpIjoiYTN... ) All in all, the solution completely exhausts the problem of many fields. There is still a problem of aggregation of many values. Report a new aggregation problem. The problem is similar, you must specify how the filter should behave for multiple values. In storage Storage.FLATTENED works but you cannot specify the logic, in Storage.NESTED all values for the filter disappear. PredicateFinalStep filter = scope.predicate() .match().field("prices.active").matching(true); SearchQuery<Assortment> query = session.search(scope) .where((f) -> f.bool().must(select) .filter(filter)) This is also a critical problem, I will try to solve it. I think that the multi parameter from AND, OR, XOR etc. could be similarly vy .... ( 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

[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=eyJpIjoiZWE... ) Re: Sorting by numeric value has an exception "(expected=NUMERIC). Use UninvertingReader or index with docvalues" ( https://hibernate.atlassian.net/browse/HSEARCH-3839?atlOrigin=eyJpIjoiZWE... ) I will leave it as a standard license. I just saw that someone had previously used the same source and also changed the license. I did the same. ( 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

[JIRA] (HHH-13735) 'A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance' when persisting, flushing, detaching and merging an Entity in the same Session (using Bytecode enhancement)

by Alexander Bittermann (JIRA)

Alexander Bittermann ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e5691d... ) *commented* on HHH-13735 ( https://hibernate.atlassian.net/browse/HHH-13735?atlOrigin=eyJpIjoiOGFiNT... ) Re: 'A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance' when persisting, flushing, detaching and merging an Entity in the same Session (using Bytecode enhancement) ( https://hibernate.atlassian.net/browse/HHH-13735?atlOrigin=eyJpIjoiOGFiNT... ) Still experiencing the same problem in version 5.4.12. What’s the status on this? ( https://hibernate.atlassian.net/browse/HHH-13735#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13735#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-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=eyJpIjoiNGY... ) Re: Sorting by numeric value has an exception "(expected=NUMERIC). Use UninvertingReader or index with docvalues" ( https://hibernate.atlassian.net/browse/HSEARCH-3839?atlOrigin=eyJpIjoiNGY... ) > > > > Elasticsearch's has already solved this problem. It would be a shame not > to use it > > Definitely. We will for sure keep this code, I was just asking for comments that specify where this code comes from, so as not to violate the Apache 2 License. I'll be waiting for your pull request on GitHub then Thanks! ( 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

[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=eyJpIjoiNGI... ) Re: Sorting by numeric value has an exception "(expected=NUMERIC). Use UninvertingReader or index with docvalues" ( https://hibernate.atlassian.net/browse/HSEARCH-3839?atlOrigin=eyJpIjoiNGI... ) Elasticsearch's has already solved this problem. It would be a shame not to use it. Many changes are necessary, but many can be accelerated by adopting their solutions. It's even better here because you can then ensure backward compatibility with Elasticsearch. It tests it and the solution works. I can choose how to choose the value. There is a min and max search fix, Elasticsearch's was a bug in these functions when it comes to Storage.FLATTENED, I corrected that these functions would work the same as for Storage.NESTED. But the solution turns out to be effective and solves my problem. This can be supplemented with the option of defining a comparator when using native LuceneSearch sort predicates. Extend native instructions with the ability to download a multi value comparator. ( 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

[JIRA] (HHH-13880) Allow to delegate the clearing of JDBC warnings on Connection close to the Connection Pool implementor

by Sanne Grinovero (JIRA)

4 years, 2 months

1
0
0 / 0

[JIRA] (HHH-13880) Allow to delegate the clearing of JDBC warnings on Connection close to the Connection Pool implementor

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYzdlNmNhNzFm... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-13880?atlOrigin=eyJpIjoiYzdlNm... ) HHH-13880 ( https://hibernate.atlassian.net/browse/HHH-13880?atlOrigin=eyJpIjoiYzdlNm... ) Allow to delegate the clearing of JDBC warnings on Connection close to the Connection Pool implementor ( https://hibernate.atlassian.net/browse/HHH-13880?atlOrigin=eyJpIjoiYzdlNm... ) Change By: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We noticed that: * Invoking {{ java.sql.Connection#clearWarnings }} is not very efficient on several JDBC drivers * Hibernate ORM clears such warnings before closing each connection and returning it to the connection pool * Some connection pool implementations such as Agroal (and likely most others too?) will also clear such warnings when the connection is returned to the pool. It seems sensible to allow this _clearWarnings_ operation to happen once at most; since this capability depends on the Connection Pool I will introduce a new flag on the pool: at this stage I don't expect to make this a configurable user property, but allow the implementors of {{ ConnectionProvider }} to hint about this capability: similarly to \ { \ {org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.ConnectionProviderJdbcConnectionAccess#supportsAggressiveRelease }} ( https://hibernate.atlassian.net/browse/HHH-13880#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13880#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-13880) Allow to delegate the clearing of JDBC warnings on Connection close to the Connection Pool implementor

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMDlmMDAyZGNl... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-13880?atlOrigin=eyJpIjoiMDlmMD... ) HHH-13880 ( https://hibernate.atlassian.net/browse/HHH-13880?atlOrigin=eyJpIjoiMDlmMD... ) Allow to delegate the clearing of JDBC warnings on Connection close to the Connection Pool implementor ( https://hibernate.atlassian.net/browse/HHH-13880?atlOrigin=eyJpIjoiMDlmMD... ) Change By: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We noticed that: * Invoking {{ java.sql.Connection#clearWarnings }} is not very efficient on several JDBC drivers * Hibernate ORM clears such warnings before closing each connection and returning it to the connection pool * Some connection pool implementations such as Agroal (and likely most others too?) will also clear such warnings when the connection is returned to the pool. It seems sensible to allow this _clearWarnings_ operation to happen once at most; since this capability depends on the Connection Pool I will introduce a new flag on the pool: at this stage I don't expect to make this a configurable user property, but allow the implementors of {{ ConnectionProvider }} to hint about this capability : similarly to \{\{org. hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.ConnectionProviderJdbcConnectionAccess#supportsAggressiveRelease }} ( https://hibernate.atlassian.net/browse/HHH-13880#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13880#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-13880) Allow to delegate the clearing of JDBC warnings on Connection close to the Connection Pool implementor

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYTgzMWVjN2Mw... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-13880?atlOrigin=eyJpIjoiYTgzMW... ) HHH-13880 ( https://hibernate.atlassian.net/browse/HHH-13880?atlOrigin=eyJpIjoiYTgzMW... ) Allow to delegate the clearing of JDBC warnings on Connection close to the Connection Pool implementor ( https://hibernate.atlassian.net/browse/HHH-13880?atlOrigin=eyJpIjoiYTgzMW... ) Change By: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We noticed that: * Invoking {{ java.sql.Connection#clearWarnings }} is not very efficient on several JDBC drivers * Hibernate ORM clears such warnings before closing each connection and returning it to the connection pool * Some connection pool implementations such as Agroal (and likely most others too?) will also clear such warnings when the connection is returned to the pool. It seems sensible to allow this clearWarnings _clearWarnings_ operation to happen once at most; since this capability depends on the Connection Pool I will introduce a new flag on the pool: at this stage I don't expect to make this a configurable user property, but allow the implementors of {{ ConnectionProvider }} to hint about this capability. ( https://hibernate.atlassian.net/browse/HHH-13880#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13880#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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2020