March 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HSEARCH-3846) Filtering for sorts on multi-valued fields in nested documents

by Yoann Rodière (JIRA)

4 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-2320) Add more specific sorts to the sort DSL

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *closed* an issue as *Out of Date* Closing because all the features mentioned here are either already implemented in Search 6, or have a dedicated ticket: * a withComparator() method for building a sort that will use a java.util.Comparator => Can be achieved through fromLuceneSortField(). * a treatMultiValuedAs(mode) method for instructions about how multi-valued fields should be sorted. => added mode() in HSEARCH-3103 ( https://hibernate.atlassian.net/browse/HSEARCH-3103 ) Resolved * a byNative() method for injecting implementation-dependent sorts inside a DSL-built sort (such as a JSON string for ElasticSearch, or a SortField for a local Lucene index) => Can be achieved through fromJson() / fromLuceneSortField(). * a onMissingValue() method for distance sort (at least first/last as for field sorts, or even substitue value if possible) => See HSEARCH-3863 ( https://hibernate.atlassian.net/browse/HSEARCH-3863 ) Open * a withComputeMethod() method for distance sort => Won't fix * a byDistanceFromSpatialQuery(Query) method for distance sort => Won't fix Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiOWY5YzYx... ) / New Feature ( https://hibernate.atlassian.net/browse/HSEARCH-2320?atlOrigin=eyJpIjoiOWY... ) HSEARCH-2320 ( https://hibernate.atlassian.net/browse/HSEARCH-2320?atlOrigin=eyJpIjoiOWY... ) Add more specific sorts to the sort DSL ( https://hibernate.atlassian.net/browse/HSEARCH-2320?atlOrigin=eyJpIjoiOWY... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Assignee: Yoann Rodière Fix versions: 6.x-backlog Resolution: Out of Date Status: Open Closed ( https://hibernate.atlassian.net/browse/HSEARCH-2320#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-2320#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#100122- sha1:52999ef )

4 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-1994) Improve usability for properties which should be sortable but not searchable

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *closed* an issue as *Out of Date* This was solved in Search 6, though differently. @GenericField now has a flag to specify whether the field is sortable or not: @GenericField(sortable = Sortable.YES). As a result, there is no need to duplicate the annotation anymore. Closing as out of date. Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiMzM4OTNl... ) / New Feature ( https://hibernate.atlassian.net/browse/HSEARCH-1994?atlOrigin=eyJpIjoiMzM... ) HSEARCH-1994 ( https://hibernate.atlassian.net/browse/HSEARCH-1994?atlOrigin=eyJpIjoiMzM... ) Improve usability for properties which should be sortable but not searchable ( https://hibernate.atlassian.net/browse/HSEARCH-1994?atlOrigin=eyJpIjoiMzM... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Assignee: Yoann Rodière Resolution: Out of Date Status: Open Closed ( https://hibernate.atlassian.net/browse/HSEARCH-1994#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-1994#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#100122- sha1:52999ef )

4 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-3866) Stop testing against JDK13 in the CI build

by Yoann Rodière (JIRA)

4 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-3866) Stop testing against JDK13 in the CI build

by Yoann Rodière (JIRA)

4 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-3866) Stop testing against JDK13 in the CI build

by Yoann Rodière (JIRA)

4 years, 3 months

1
0
0 / 0

[JIRA] (HBX-2004) Update freemarker version to 2.3.30

by Koen Aers (JIRA)

4 years, 3 months

1
0
0 / 0

[JIRA] (HBX-2003) Update eclipse-jdt-core dependency to version 3.20.0

by Koen Aers (JIRA)

4 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-3325) Search 6 groundwork - Restore support for full-text filters

by Waldemar Kłaczyński (JIRA)

Waldemar Kłaczyński ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-3325 ( https://hibernate.atlassian.net/browse/HSEARCH-3325?atlOrigin=eyJpIjoiMWV... ) Re: Search 6 groundwork - Restore support for full-text filters ( https://hibernate.atlassian.net/browse/HSEARCH-3325?atlOrigin=eyJpIjoiMWV... ) There is no magic about using the fields. I do not associate the filter with a given field. Only in context do I enable a set of tools to specify field names by the way the query was asked. Including additional parameters in annotations extend the definition possibilities. I just follow the use case in real conditions. As I presented the case. The filter works dynamically if the price is master or the price is a child of another entity. Practically, the proposed solutions are dictated by real needs. I showed here the entire use case in the product search engine, according to the price available to the user. Obviously, it is also aimed at coughing, but I see that it should not be associated with the filter only as an additional function in the predicate. If they work like that, they will only have some real usefulness, not for me. Otherwise it's just as you mentioned it will be a piece of code that is not useful to anyone. I am currently pulling several projects and I want to use hibernate-search in all of them, so I can define my real needs. Ultimately, I can handle patches, because hibernate cheeses are too valuable to give up, but not everyone can do patches. So I share my goals, keeping in mind that I'm improving your work. ( https://hibernate.atlassian.net/browse/HSEARCH-3325#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3325#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#100122- sha1:87fe5bb )

4 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-3325) Search 6 groundwork - Restore support for full-text filters

by Waldemar Kłaczyński (JIRA)

Waldemar Kłaczyński ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-3325 ( https://hibernate.atlassian.net/browse/HSEARCH-3325?atlOrigin=eyJpIjoiNDY... ) Re: Search 6 groundwork - Restore support for full-text filters ( https://hibernate.atlassian.net/browse/HSEARCH-3325?atlOrigin=eyJpIjoiNDY... ) I assume the use of filters as a solution to hide part of the code. Just like it is in JPA in native query. One part is useful for better code organization. Not useful to others at all, it can be replaced when creating queries. But whether or not something can be replaced by another method should be the responsibility of the user. For me, just such a system is necessary. I have to design each application and prepare a set of tools. That the team that is to perform the task and maintain the code was as simple as possible. They didn't understand how the equipment used by me worked. They just have to specifically address the primary purpose of the project, not really getting into the way hiternate-search or apache lucene work. So the proposed task only has a cosmetic impact on the code. But very important in the later use of your library in team work. ( https://hibernate.atlassian.net/browse/HSEARCH-3325#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3325#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#100122- sha1:87fe5bb )

4 years, 3 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 March 2020