October 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-12275) Restore support for @Field(analyzer = ...) and @Field(normalizer = ...)

by Yoann Rodière (Jira)

[ https://issues.redhat.com/browse/ISPN-12275?page=com.atlassian.jira.plugi... ] Yoann Rodière updated ISPN-12275: --------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8757 > Restore support for @Field(analyzer = ...) and @Field(normalizer = ...) > ----------------------------------------------------------------------- > > Key: ISPN-12275 > URL: https://issues.redhat.com/browse/ISPN-12275 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Reporter: Yoann Rodière > Priority: Major > Fix For: 12.0.0.Dev05 > > > In Infinispan 11 (Hibernate Search 5.10/5.11), it used to be possible to assign an analyzer or normalizer to a field with the following syntax: > {code} > @Field(analyzer = @Analyzer(definition = "myAnalyzer")) > private String myProperty; > @Field(analyzer = @Normalizer(definition = "myNormalizer")) > private String myProperty; > {code} > It seems that we made a mistake during the upgrade to Search 6, and support for this syntax was removed. All that's left is the property-scoped syntax, where the analyzer is defined next to the field: > {code} > @Field > @Analyzer(definition = "myAnalyzer") > private String myProperty; > {code} > If we want to provide at least partial backward compatibility in annotations, we should restore support for the former syntax (and keep the latter). > For the record, analyzer assigned using the former syntax take precedence over analyzers assigned using the latter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12279) Default value of @IndexedEmbedded.depth is not correctly interpreted

by Yoann Rodière (Jira)

[ https://issues.redhat.com/browse/ISPN-12279?page=com.atlassian.jira.plugi... ] Yoann Rodière updated ISPN-12279: --------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8757 > Default value of @IndexedEmbedded.depth is not correctly interpreted > -------------------------------------------------------------------- > > Key: ISPN-12279 > URL: https://issues.redhat.com/browse/ISPN-12279 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 12.0.0.Dev02 > Reporter: Yoann Rodière > Priority: Major > Fix For: 12.0.0.Dev05 > > > There was a problem during the migration to Search 6, and the processor for the annotation {{@IndexedEmbedded}} apparently does not correctly intepret {{@IndexedEmbedded()}} as "no depth defined". > As a result, {{@IndexedEmbedded(includePaths = { "foo" })}} will not set the depth to 0 as it should, but to {{Integer.MAX_VALUE}} (the default defined on the {{(a)IndexedEmbedded.depth()}} attribute) and will end up incorrectly including the whole embedded document. > The code to change is this (in {{org.hibernate.search.annotations.IndexedEmbedded}}): > {code} > Integer cleanedUpMaxDepth = annotation.depth(); > if ( cleanedUpMaxDepth.equals( -1 ) ) { > cleanedUpMaxDepth = null; > } > {code} > It should be instead: > {code} > Integer cleanedUpMaxDepth = annotation.depth(); > if ( cleanedUpMaxDepth.equals( Integer.MAX_VALUE ) ) { > cleanedUpMaxDepth = null; > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12407) Remove support for index-time boost

by Yoann Rodière (Jira)

[ https://issues.redhat.com/browse/ISPN-12407?page=com.atlassian.jira.plugi... ] Yoann Rodière updated ISPN-12407: --------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8757 > Remove support for index-time boost > ----------------------------------- > > Key: ISPN-12407 > URL: https://issues.redhat.com/browse/ISPN-12407 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Reporter: Yoann Rodière > Assignee: Yoann Rodière > Priority: Major > Fix For: 12.0.0.Dev05 > > > Index-time boost isn't supported anymore in Hibernate Search 6. > Instead, query-time boosting should be used. > The feature was deprecated in Infinispan 11: https://infinispan.org/docs/11.0.x/titles/upgrading/upgrading.html#entity... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12278) Restore support for @Field(norms = ...) and @Field(termVector = ...)

by Yoann Rodière (Jira)

[ https://issues.redhat.com/browse/ISPN-12278?page=com.atlassian.jira.plugi... ] Yoann Rodière updated ISPN-12278: --------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8757 > Restore support for @Field(norms = ...) and @Field(termVector = ...) > -------------------------------------------------------------------- > > Key: ISPN-12278 > URL: https://issues.redhat.com/browse/ISPN-12278 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 12.0.0.Dev02 > Reporter: Yoann Rodière > Priority: Major > Fix For: 12.0.0.Dev05 > > > It looks like these attributes of the {{@Field}} annotations were removed by mistake during the migration to Search 6. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12408) Remove support for the default null token on index fields

by Yoann Rodière (Jira)

[ https://issues.redhat.com/browse/ISPN-12408?page=com.atlassian.jira.plugi... ] Yoann Rodière updated ISPN-12408: --------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8757 > Remove support for the default null token on index fields > --------------------------------------------------------- > > Key: ISPN-12408 > URL: https://issues.redhat.com/browse/ISPN-12408 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Reporter: Yoann Rodière > Assignee: Yoann Rodière > Priority: Major > Fix For: 12.0.0.Dev05 > > > The default null token isn't supported anymore in Hibernate Search 6. Each field that takes advantage of the {{indexNullAs}} feature should define the null token explicitly. > The {{indexNullAs}} feature was deprecated in Infinispan 11: https://infinispan.org/docs/11.0.x/titles/upgrading/upgrading.html#entity... > Also, Hibernate Search 6 offers an {{exist}} predicate, which is used in Ickle for {{IS NOT NULL}} conditions; so {{indexNullAs}} is no longer as important as before. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12406) Upgrade to Hibernate Search 6.0.0.Beta11

by Yoann Rodière (Jira)

[ https://issues.redhat.com/browse/ISPN-12406?page=com.atlassian.jira.plugi... ] Yoann Rodière updated ISPN-12406: --------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8757 > Upgrade to Hibernate Search 6.0.0.Beta11 > ---------------------------------------- > > Key: ISPN-12406 > URL: https://issues.redhat.com/browse/ISPN-12406 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Reporter: Yoann Rodière > Assignee: Yoann Rodière > Priority: Major > Fix For: 12.0.0.Dev05 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12408) Remove support for the default null token on index fields

by Yoann Rodière (Jira)

[ https://issues.redhat.com/browse/ISPN-12408?page=com.atlassian.jira.plugi... ] Yoann Rodière updated ISPN-12408: --------------------------------- Description: The default null token isn't supported anymore in Hibernate Search 6. Each field that takes advantage of the {{indexNullAs}} feature should define the null token explicitly. The {{indexNullAs}} feature was deprecated in Infinispan 11: https://infinispan.org/docs/11.0.x/titles/upgrading/upgrading.html#entity... Also, Hibernate Search 6 offers an {{exist}} predicate, which is used in Ickle for {{IS NOT NULL}} conditions; so {{indexNullAs}} is no longer as important as before. was: The default null token isn't supported anymore in Hibernate Search 6. Each field that takes advantage of the {{indexNullAs}} feature should define the null token explicitly. The {{indexNullAs}} feature was deprecated in Infinispan 11: https://infinispan.org/docs/11.0.x/titles/upgrading/upgrading.html#entity... Also, Hibernate Search 6 offers an {{exist}} predicate, which is used in Ickly for {{IS NOT NULL}} conditions; so {{indexNullAs}} is no longer as important as before. > Remove support for the default null token on index fields > --------------------------------------------------------- > > Key: ISPN-12408 > URL: https://issues.redhat.com/browse/ISPN-12408 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Reporter: Yoann Rodière > Assignee: Yoann Rodière > Priority: Major > Fix For: 12.0.0.Dev05 > > > The default null token isn't supported anymore in Hibernate Search 6. Each field that takes advantage of the {{indexNullAs}} feature should define the null token explicitly. > The {{indexNullAs}} feature was deprecated in Infinispan 11: https://infinispan.org/docs/11.0.x/titles/upgrading/upgrading.html#entity... > Also, Hibernate Search 6 offers an {{exist}} predicate, which is used in Ickle for {{IS NOT NULL}} conditions; so {{indexNullAs}} is no longer as important as before. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12408) Remove support for the default null token on index fields

by Yoann Rodière (Jira)

Yoann Rodière created ISPN-12408: ------------------------------------ Summary: Remove support for the default null token on index fields Key: ISPN-12408 URL: https://issues.redhat.com/browse/ISPN-12408 Project: Infinispan Issue Type: Task Components: Embedded Querying, Remote Querying Reporter: Yoann Rodière Assignee: Yoann Rodière Fix For: 12.0.0.Dev05 The default null token isn't supported anymore in Hibernate Search 6. Each field that takes advantage of the {{indexNullAs}} feature should define the null token explicitly. The {{indexNullAs}} feature was deprecated in Infinispan 11: https://infinispan.org/docs/11.0.x/titles/upgrading/upgrading.html#entity... Also, Hibernate Search 6 offers an {{exist}} predicate, which is used in Ickly for {{IS NOT NULL}} conditions; so {{indexNullAs}} is no longer as important as before. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12407) Remove support for index-time boost

by Yoann Rodière (Jira)

Yoann Rodière created ISPN-12407: ------------------------------------ Summary: Remove support for index-time boost Key: ISPN-12407 URL: https://issues.redhat.com/browse/ISPN-12407 Project: Infinispan Issue Type: Task Components: Embedded Querying, Remote Querying Reporter: Yoann Rodière Assignee: Yoann Rodière Fix For: 12.0.0.Dev05 Index-time boost isn't supported anymore in Hibernate Search 6. Instead, query-time boosting should be used. The feature was deprecated in Infinispan 11: https://infinispan.org/docs/11.0.x/titles/upgrading/upgrading.html#entity... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12406) Upgrade to Hibernate Search 6.0.0.Beta11

by Yoann Rodière (Jira)

Yoann Rodière created ISPN-12406: ------------------------------------ Summary: Upgrade to Hibernate Search 6.0.0.Beta11 Key: ISPN-12406 URL: https://issues.redhat.com/browse/ISPN-12406 Project: Infinispan Issue Type: Task Components: Embedded Querying, Remote Querying Reporter: Yoann Rodière Assignee: Yoann Rodière Fix For: 12.0.0.Dev05 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2020