February 2020 - hibernate-issues - Jboss List Archives

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13879 ( https://hibernate.atlassian.net/browse/HHH-13879?atlOrigin=eyJpIjoiMWU0N2... ) Re: Slow query log should use System#nanoTime not System#currentTimeMillis ( https://hibernate.atlassian.net/browse/HHH-13879?atlOrigin=eyJpIjoiMWU0N2... ) no worries Vlad, I’m not expressing a concern over your patch. Just pointing out that it’s not straight forward - as I said in my first sentence. Regarding monotonic clocks - that’s precisely the problem, neither {{ currentTimeMillis }} nor {{ nanoTime }} guarantee that. It doesn’t matter that the OS supports it, the JDK is not exposing the same counter - however what it exactly does depends on the version of the JVM, its vendor, and the OS. I’m aware of NTP issues - it’s probably better to stick with nanoTime for short durations - just worth keeping in mind that even so, it’s not bulletproof. ( https://hibernate.atlassian.net/browse/HHH-13879#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13879#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:a269fed )

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=eyJpIjoiMTM... ) Re: Sorting by numeric value has an exception "(expected=NUMERIC). Use UninvertingReader or index with docvalues" ( https://hibernate.atlassian.net/browse/HSEARCH-3839?atlOrigin=eyJpIjoiMTM... ) Indeed we should use SortedNumericDocValuesField. This is planned for some future Beta of Hibernate Search 6, see HSEARCH-3103 ( https://hibernate.atlassian.net/browse/HSEARCH-3103 ) Open. At the moment we have internal metadata to let us know that a given field is multi-valued or not, but we don't use it. We should use the metadata to pick the correct field type at indexing time, and maybe to build sorts differently at query time (I suppose we have to pick between min/max/avg/etc. when there are multiple values for a single document). We'll get there eventually; if you need this soon and can spend some time on this, we will gladly accept a contribution! ( 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:a269fed )

4 years, 2 months

1
0
0 / 0

[JIRA] (HHH-13879) Slow query log should use System#nanoTime not System#currentTimeMillis

by Steve Ebersole (JIRA)

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