March 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HV-1760) @Negative*/@Positive* do not support CharSequence as documented

by PhilC (JIRA)

PhilC ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HV-1760 ( https://hibernate.atlassian.net/browse/HV-1760?atlOrigin=eyJpIjoiMzZlN2Rj... ) Re: @Negative*/@Positive* do not support CharSequence as documented ( https://hibernate.atlassian.net/browse/HV-1760?atlOrigin=eyJpIjoiMzZlN2Rj... ) I have no immediate need for them. Simply updating the documentation would be fine with me. ( https://hibernate.atlassian.net/browse/HV-1760#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1760#add-comment?atlOrigin=eyJp... ) 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:db27712 )

4 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-3103) Sorts on multi-valued fields

by Waldemar Kłaczyński (JIRA)

Waldemar Kłaczyński ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-3103 ( https://hibernate.atlassian.net/browse/HSEARCH-3103?atlOrigin=eyJpIjoiMzg... ) Re: Sorts on multi-valued fields ( https://hibernate.atlassian.net/browse/HSEARCH-3103?atlOrigin=eyJpIjoiMzg... ) Maybe to speed up sorting, you can save in the field definition how it should behave when storing values. So eventually he would remember only one field, max, min, avg, etc ... Later sorting would consist of reading only one field. It would be a good solution in a flat model. This would speed up document search. Indexing the field in such a way would prevent you from choosing a different aggregation method, but it is not always necessary for everyone. So the user would decide between search performance and subsequent dynamic search capability. @GenericField(name = "bruttoPrice_sort" , sortable = Sortable.YES, mode = MultiValue.AVG) The user would have to choose whether to remember the calculated value or to calculate it during sorting. As for calculating values, median counting for nested multiple values is inefficient. This requires creating an array with the number of nested value elements in order to sort it. So calculating values when creating an index would be the solution here. Some functions, especially those that pull values up to aggregation, can be simplified for multiple nested values. So that he doesn't use ArrayList. ( https://hibernate.atlassian.net/browse/HSEARCH-3103#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3103#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:db27712 )

4 years, 4 months

1
0
0 / 0

[JIRA] (HV-1760) @Negative*/@Positive* do not support CharSequence as documented

by Guillaume Smet (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (HV-1760) @Negative*/@Positive* do not support CharSequence as documented

by Guillaume Smet (JIRA)

Guillaume Smet ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HV-1760 ( https://hibernate.atlassian.net/browse/HV-1760?atlOrigin=eyJpIjoiNGMxOTY1... ) Re: @Negative*/@Positive* do not support CharSequence as documented ( https://hibernate.atlassian.net/browse/HV-1760?atlOrigin=eyJpIjoiNGMxOTY1... ) You're right, the validators are missing. Did you have any use for them? Maybe you would be interested in contributing? It shouldn't be too hard to add them if you need them. ( https://hibernate.atlassian.net/browse/HV-1760#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1760#add-comment?atlOrigin=eyJp... ) 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:db27712 )

4 years, 4 months

1
0
0 / 0

[JIRA] (HV-1760) @Negative*/@Positive* do not support CharSequence as documented

by PhilC (JIRA)

PhilC ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Validator ( https://hibernate.atlassian.net/browse/HV?atlOrigin=eyJpIjoiZmU3NDdhY2RiM... ) / Bug ( https://hibernate.atlassian.net/browse/HV-1760?atlOrigin=eyJpIjoiZmU3NDdh... ) HV-1760 ( https://hibernate.atlassian.net/browse/HV-1760?atlOrigin=eyJpIjoiZmU3NDdh... ) @Negative*/@Positive* do not support CharSequence as documented ( https://hibernate.atlassian.net/browse/HV-1760?atlOrigin=eyJpIjoiZmU3NDdh... ) Issue Type: Bug Affects Versions: 6.1.2.Final Assignee: Unassigned Components: validators Created: 09/Mar/2020 12:58 PM Priority: Minor Reporter: PhilC ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The hibernate validator documentation ( https://docs.jboss.org/hibernate/stable/validator/reference/en-US/html_si... ) for @Negative , @NegativeOrZero , @Positive , and @PositiveOrZero states that hibernate validator supports validating any subtype of CharSequence : > > > > additionally supported by HV: any sub-type of CharSequence (the numeric > value represented by the character sequence is evaluated) > > However, when attempting to validate a String field with any of those constraints, hibernate validator throws the following exception: javax.validation.UnexpectedTypeException: HV000030: No validator could be found for constraint 'javax.validation.constraints.Negative' validating type 'java.lang. String '. Check configuration for 'string' at org.hibernate.validator.internal.engine.constraintvalidation.ConstraintTree.getExceptionForNullValidator(ConstraintTree.java:116) at org.hibernate.validator.internal.engine.constraintvalidation.ConstraintTree.getInitializedConstraintValidator(ConstraintTree.java:162) at org.hibernate.validator.internal.engine.constraintvalidation.SimpleConstraintTree.validateConstraints(SimpleConstraintTree.java:54) at org.hibernate.validator.internal.engine.constraintvalidation.ConstraintTree.validateConstraints(ConstraintTree.java:75) at org.hibernate.validator.internal.metadata.core.MetaConstraint.doValidateConstraint(MetaConstraint.java:130) at org.hibernate.validator.internal.metadata.core.MetaConstraint.validateConstraint(MetaConstraint.java:123) at org.hibernate.validator.internal.engine.ValidatorImpl.validateMetaConstraint(ValidatorImpl.java:555) at org.hibernate.validator.internal.engine.ValidatorImpl.validateConstraintsForSingleDefaultGroupElement(ValidatorImpl.java:518) at org.hibernate.validator.internal.engine.ValidatorImpl.validateConstraintsForDefaultGroup(ValidatorImpl.java:488) at org.hibernate.validator.internal.engine.ValidatorImpl.validateConstraintsForCurrentGroup(ValidatorImpl.java:450) at org.hibernate.validator.internal.engine.ValidatorImpl.validateInContext(ValidatorImpl.java:400) at org.hibernate.validator.internal.engine.ValidatorImpl.validate(ValidatorImpl.java:172) at NegativeConstraintTest.test(NegativeConstraintTest.java:25) Here is a unit test that demonstrates the problem: import org.junit.jupiter.api.Test; import javax.validation.Validation; import javax.validation.Validator; import javax.validation.constraints.Negative; public class NegativeConstraintTest { public static class Target { private final String string; public Target( String string) { this.string = string; } @Negative public String getString() { return string; } } @Test public void test() { Validator validator = Validation.buildDefaultValidatorFactory().getValidator(); validator.validate( new Target( "1.0" )); } } Please either update the documentation, or add support for CharSequences to these constraints. ( https://hibernate.atlassian.net/browse/HV-1760#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1760#add-comment?atlOrigin=eyJp... ) 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:db27712 )

4 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-3860) Refactor FieldSearchSortIT to enable testing more complex cases

by Yoann Rodière (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-3860) Refactor FieldSearchSortIT to enable testing more complex cases

by Yoann Rodière (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-3860) Refactor FieldSearchSortIT to enable testing more complex cases

by Yoann Rodière (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-3859) .desc().missing().last() / .asc().missing().first() places documents around 0 instead of last/first

by Yoann Rodière (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-3859) .desc().missing().last() / .asc().missing().first() places documents around 0 instead of last/first

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiZGY4ZmI3... ) / Bug ( https://hibernate.atlassian.net/browse/HSEARCH-3859?atlOrigin=eyJpIjoiZGY... ) HSEARCH-3859 ( https://hibernate.atlassian.net/browse/HSEARCH-3859?atlOrigin=eyJpIjoiZGY... ).desc().missing().last() / .asc().missing().first() places documents around 0 instead of last/first ( https://hibernate.atlassian.net/browse/HSEARCH-3859?atlOrigin=eyJpIjoiZGY... ) Issue Type: Bug Affects Versions: 6.0.0.Beta5 Assignee: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Created: 09/Mar/2020 09:45 AM Fix Versions: 6.0.0.Beta6 Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We use Double.MIN_VALUE / Float.MIN_VALUE as the default value for these cases, but that value is not the minimum value: it's just the lowest positive value. We should use -Double.MAX_VALUE instead. ( https://hibernate.atlassian.net/browse/HSEARCH-3859#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3859#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:db27712 )

4 years, 4 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