September 2022 - hibernate-issues

[JIRA] (HSEARCH-2799) DeleteByQueryMultiTenancyIT.deleteByQueryOnlyAffectsEntitiesOfCurrentTenant fails on MS SQL Server

by Yoann Rodière (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-2378) Indexed resolution (truncation) for date/time types

by Yoann Rodière (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-2378) Indexed resolution (truncation) for date/time types

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=eyJpIjoiMTNhMmYx... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-2378?atlOrigin=eyJpIjoiMTN... ) HSEARCH-2378 ( https://hibernate.atlassian.net/browse/HSEARCH-2378?atlOrigin=eyJpIjoiMTN... ) Indexed resolution (truncation) for date/time types ( https://hibernate.atlassian.net/browse/HSEARCH-2378?atlOrigin=eyJpIjoiMTN... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) {{@DateBridge}} resolution used to be supported for {{java.util.Date}} and {{java.util.Calendar}}, but not {{java.time}} types. It’s no longer supported at all in Hibernate Search 6, because truncating a {{java.util.Date}} requires us to pick a timezone, and there’s no way to be sure that’s the timezone the user expected. However, we could restore support for resolution in very specific cases: * For date/time types where the timezone is not necessary in order to truncate a value (e.g. {{LocalDateTime}}, {{LocalDate}}) * For date/time types where the timezone is included in the value to truncate (e.g. {{ZonedDateTime}}, {{OffsetDateTime}}) * Optionally, for date/time types where an external timezone must be provided, in which case it could be part of the mapping ({{@TemporalField(resolution = ..., timeZone = "UTC+2")}} / {{@TemporalField(resolution = ..., timeZoneProvider = @BeanReference(name = "myBean" ) }}) ( https://hibernate.atlassian.net/browse/HSEARCH-2378#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-2378#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#100207- sha1:ee9e30a )

1 year, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-1766) Verify correctness of interaction between Filters and Faceting

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *closed* an issue as *Out of Date* Filters are just predicates in Hibernate Search 6, and we do test interaction between aggregations and predicates (e.g. org.hibernate.search.integrationtest.backend.tck.search.aggregation.SingleFieldAggregationBaseIT#noMatch) Closing as out of date. Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiYmVhM2Rj... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-1766?atlOrigin=eyJpIjoiYmV... ) HSEARCH-1766 ( https://hibernate.atlassian.net/browse/HSEARCH-1766?atlOrigin=eyJpIjoiYmV... ) Verify correctness of interaction between Filters and Faceting ( https://hibernate.atlassian.net/browse/HSEARCH-1766?atlOrigin=eyJpIjoiYmV... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Assignee: Unassigned Yoann Rodière Fix versions: 7.x-backlog Resolution: Out of Date Status: Open Closed ( https://hibernate.atlassian.net/browse/HSEARCH-1766#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-1766#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#100207- sha1:ee9e30a )

1 year, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-4454) 'hibernate.search.backend.uris' recognized as an invalid property

by Ivan Kotev (JIRA)

Ivan Kotev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) *commented* on HSEARCH-4454 ( https://hibernate.atlassian.net/browse/HSEARCH-4454?atlOrigin=eyJpIjoiOTE... ) Re: 'hibernate.search.backend.uris' recognized as an invalid property ( https://hibernate.atlassian.net/browse/HSEARCH-4454?atlOrigin=eyJpIjoiOTE... ) Hey Yoann, Sorry I wasn’t able to work on a reproducer though I have a theory why this warning might show up. In my project we connect to 2 different databases (hence multiple entity managers) and for only one of them we have enabled Hibernate Search. I’ll try to confirm if this really is the case. ( https://hibernate.atlassian.net/browse/HSEARCH-4454#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4454#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#100207- sha1:ee9e30a )

1 year, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-3081) Configuration of index-level compression

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=eyJpIjoiZmUzMjBh... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-3081?atlOrigin=eyJpIjoiZmU... ) HSEARCH-3081 ( https://hibernate.atlassian.net/browse/HSEARCH-3081?atlOrigin=eyJpIjoiZmU... ) Configuration of index-level compression ( https://hibernate.atlassian.net/browse/HSEARCH-3081?atlOrigin=eyJpIjoiZmU... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Field-level compression ({{Store.COMPRESS}}) is not possible anymore. We should use index-level compression codecs instead. In Elasticsearch, those are part of the index settings, so they are none of our business (they should be configured by the user , e.g. through [custom index settings|https://docs.jboss.org/hibernate/stable/search/reference/en-US/h...] ). In Lucene, we should provide a sensible default (maybe align with Elasticsearch?) and offer configuration properties to configure it. ( https://hibernate.atlassian.net/browse/HSEARCH-3081#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3081#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#100207- sha1:ee9e30a )

1 year, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-4454) 'hibernate.search.backend.uris' recognized as an invalid property

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-4454 ( https://hibernate.atlassian.net/browse/HSEARCH-4454?atlOrigin=eyJpIjoiYjR... ) Re: 'hibernate.search.backend.uris' recognized as an invalid property ( https://hibernate.atlassian.net/browse/HSEARCH-4454?atlOrigin=eyJpIjoiYjR... ) Hey Ivan Kotev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) , did you manage to write a reproducer in the end? ( https://hibernate.atlassian.net/browse/HSEARCH-4454#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4454#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#100207- sha1:ee9e30a )

1 year, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-4199) Range fields and predicates for these fields

by Yoann Rodière (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-1182) implement excludePath on indexedEmbedded

by Yoann Rodière (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HSEARCH-4392) Simpler representation of paths in annotation mapping

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=eyJpIjoiMzEyM2I1... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-4392?atlOrigin=eyJpIjoiMzE... ) HSEARCH-4392 ( https://hibernate.atlassian.net/browse/HSEARCH-4392?atlOrigin=eyJpIjoiMzE... ) Simpler representation of paths in annotation mapping ( https://hibernate.atlassian.net/browse/HSEARCH-4392?atlOrigin=eyJpIjoiMzE... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) See [HSEARCH-4386] : the current syntax using {{@ObjectPath}}/{{@PropertyValue}} is far from clear and can lead to mistakes that yield confusing error messages. To prevent that kind of mistake in the first place, we could provide (and recommend) a more straightforward way to provide paths. h4. Solution 1: simply allow string representations Minimal changes; just allow passing paths as strings: {code:java}@IndexingDependency(derivedFrom = { @ObjectPath( asString fromString = "firstName"), @ObjectPath( asString fromString = "familyName") }){code} Such a syntax would need to handle references to value extractors too, however; maybe we'll pick the current syntax "foo<collection>.bar", or maybe we'll switch to something better. h4. Solution 2: string representations + new annotations with better names/structure Do the above, but *also* rethink the name and structure of the {{@IndexingDependency}}/{{@AssociationInverseSide}}/{{@ObjectPath}}/{{@PropertyValue}} annotations so that it's impossible to think "ah, {{@ObjectPath(value = ...)}} probably allows me to provide multiple paths". This is easier said than done, though... When thinking about this, we should probably take into account the changes suggested in [HSEARCH-4271] too. ( https://hibernate.atlassian.net/browse/HSEARCH-4392#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4392#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#100207- sha1:ee9e30a )

1 year, 7 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 September 2022