February 2020 - hibernate-issues - Jboss List Archives

[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%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYTFkNDE4NDky... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-13880?atlOrigin=eyJpIjoiYTFkND... ) HHH-13880 ( https://hibernate.atlassian.net/browse/HHH-13880?atlOrigin=eyJpIjoiYTFkND... ) Allow to delegate the clearing of JDBC warnings on Connection close to the Connection Pool implementor ( https://hibernate.atlassian.net/browse/HHH-13880?atlOrigin=eyJpIjoiYTFkND... ) Issue Type: Improvement Assignee: Unassigned Components: hibernate-core Created: 26/Feb/2020 05:19 AM Fix Versions: 5.4.13 Priority: Major Reporter: 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. ( 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 )

5 years, 7 months

1
0
0 / 0

[JIRA] (HHH-13876) Fix an obvious bug in StandardStack implementation

by Sanne Grinovero (JIRA)

5 years, 7 months

1
0
0 / 0

[JIRA] (HHH-13876) Fix an obvious bug in StandardStack implementation

by Sanne Grinovero (JIRA)

5 years, 7 months

1
0
0 / 0

[JIRA] (HHH-13878) Increase the scope of some methods to make them accessible outside of Hibernate ORM

by Sanne Grinovero (JIRA)

5 years, 7 months

1
0
0 / 0

[JIRA] (HHH-13878) Increase the scope of some methods to make them accessible outside of Hibernate ORM

by Sanne Grinovero (JIRA)

5 years, 7 months

1
0
0 / 0

[JIRA] (HHH-13878) Increase the scope of some methods to make them accessible outside of Hibernate ORM

by Sanne Grinovero (JIRA)

5 years, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-3843) Test Hibernate Search with JDK15 regularly

by Yoann Rodière (JIRA)

5 years, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-3843) Test Hibernate Search with JDK15 regularly

by Yoann Rodière (JIRA)

5 years, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-3843) Test Hibernate Search with JDK15 regularly

by Yoann Rodière (JIRA)

5 years, 7 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=eyJpIjoiMTQ... ) Re: Sorting by numeric value has an exception "(expected=NUMERIC). Use UninvertingReader or index with docvalues" ( https://hibernate.atlassian.net/browse/HSEARCH-3839?atlOrigin=eyJpIjoiMTQ... ) That was... fast! Thank you for taking the time to work on this. The code looks a lot like Elasticsearch's code, so I suppose you took it from there and adapted it to our codebase? That's perfectly fine since their code is Apache 2 licensed, but we'll need to add notices to files that were copied from there, to preserve a "copyright trail". See for example org.hibernate.search.backend.lucene.lowlevel.docvalues.impl.NumericDoubleValues. There are a few other things to iron out, like the code style and the tests that we need to add. I suspect we should also change the implementation of aggregations to use the sorted doc values instead of the old ones. Would you mind sending this patch as a pull request on Github so that we can discuss this and iterate? You can find a guide to sending pull requests in the CONTRIBUTING.md file ( https://github.com/hibernate/hibernate-search/blob/master/CONTRIBUTING.md ) ; don't hesitate to drop by the developer chat ( https://hibernate.zulipchat.com/#narrow/stream/132092-hibernate-search-dev ) if you need help. ( 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 )

5 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2020