August 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HSEARCH-3979) Rename @IndexedEmbedded.maxDepth to includeDepth

by Yoann Rodière (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3975) Expose scrolling operations through JPA/ORM queries

by Yoann Rodière (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3269) Restore support for JSR-352 integration

by Yoann Rodière (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-2505) Lower the default read timeout with Elasticsearch

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiYzc3NWU2... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-2505?atlOrigin=eyJpIjoiYzc... ) HSEARCH-2505 ( https://hibernate.atlassian.net/browse/HSEARCH-2505?atlOrigin=eyJpIjoiYzc... ) Lower the default read timeout with Elasticsearch ( https://hibernate.atlassian.net/browse/HSEARCH-2505?atlOrigin=eyJpIjoiYzc... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We currently have a very high value of 60s, due to calls to the health API where we indeed may have to wait this long. -If per-request timeouts are added to Jest (https://github.com/searchbox-io/Jest/issues/411), we could use that instead and avoid this high default read timeout.- -We asked for per-request timeouts to be added to the official Elasticsearch client, so let's wait for that first.- It looks like it's not going to happen. Let's try another way: use a lower read timeout by default, but implement health checks in Hibernate Search so that we try again on read timeout, until the health check timeout is reached. For an idea of how to do this, see how we used to trigger a refresh after a flush; the code was removed, but you will probably need to reintroduce it: https://github.com/hibernate/hibernate-search/commit/cefff76cca94f1aa9417... Also, I've read somewhere that the health check after creating an index is no longer necessary in Elasticsearch 5 onwards; let's investigate that? ( https://hibernate.atlassian.net/browse/HSEARCH-2505#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-2505#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#100141- sha1:76df2fe )

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3979) Rename @IndexedEmbedded.maxDepth to includeDepth

by Yoann Rodière (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3308) Check Search 6 log/exception messages and use Search 5 messages instead (with Search 5 ID) where possible

by Yoann Rodière (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3356) Use consistent phrasing in log messages and exceptions

by Yoann Rodière (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-2505) Lower the default read timeout with Elasticsearch

by Yoann Rodière (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-2505) Lower the default read timeout with Elasticsearch

by Yoann Rodière (JIRA)

4 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3785) Support soft timeout ( limiting fetching ) on Elasticsearch

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiOGZkZGM1... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-3785?atlOrigin=eyJpIjoiOGZ... ) HSEARCH-3785 ( https://hibernate.atlassian.net/browse/HSEARCH-3785?atlOrigin=eyJpIjoiOGZ... ) Support soft timeout ( limiting fetching ) on Elasticsearch ( https://hibernate.atlassian.net/browse/HSEARCH-3785?atlOrigin=eyJpIjoiOGZ... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Hard timeout is implemented by us client side. For the soft Soft timeout we need to rely on Elasticsearch is implemented too , but it seems that there is an issue related to the fact that currently not tested because : {quote}Timeout resolution is very low, so it's uneffective unless the query takes a really long time to execute.{quote} We should find a way to test it regardless, for example by configuring Elasticsearch to use a higher time resolution (is it even possible?), or by crafting a query that we know will take forever to execute (how?). See full discussion here: [https://github.com/hibernate/hibernate-search/pull/2158#commitcomment-363...] See {{org.hibernate.search.integrationtest.backend.elasticsearch.testsupport.util.ElasticsearchTckBackendFeatures#fastTimeoutResolution}}. ( https://hibernate.atlassian.net/browse/HSEARCH-3785#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3785#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#100141- sha1:76df2fe )

4 years, 5 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 August 2020