[JBoss JIRA] (ISPN-11795) Entity mapping deprecations
by Yoann Rodière (Jira)
[ https://issues.redhat.com/browse/ISPN-11795?page=com.atlassian.jira.plugi... ]
Yoann Rodière edited comment on ISPN-11795 at 5/13/20 8:14 AM:
---------------------------------------------------------------
Something else I just noticed: Infinispan 10/11 enables the option {{org.hibernate.search.cfg.Environment#INDEX_UNINVERTING_ALLOWED}}. This means Hibernate Search will accept sorts on fields that are not marked as {{@SortableField}}, but will print a warning every time it does, because that behavior is deprecated.
With Hibernate Search 6, this is no longer allowed: only fields marked as sortable can be sorted on. The option {{org.hibernate.search.cfg.Environment#INDEX_UNINVERTING_ALLOWED}} does not exist anymore.
So, you might want to stress that sorting on non-{{@SortableField}} fields is deprecated.
was (Author: y.rodiere):
Something else I just noticed: Infinispan 10/11 enable the option {{org.hibernate.search.cfg.Environment#INDEX_UNINVERTING_ALLOWED}}. This means Hibernate Search will accept sorts on fields that are not marked as {{@SortableField}}, but will print a warning every time it does, because that behavior is deprecated.
With Hibernate Search 6, this is no longer allowed: only fields marked as sortable can be sorted on. The option {{org.hibernate.search.cfg.Environment#INDEX_UNINVERTING_ALLOWED}} does not exist anymore.
So, you might want to stress that sorting on non-{{@SortableField}} fields is deprecated.
> Entity mapping deprecations
> ---------------------------
>
> Key: ISPN-11795
> URL: https://issues.redhat.com/browse/ISPN-11795
> Project: Infinispan
> Issue Type: Enhancement
> Components: Embedded Querying
> Reporter: Gustavo Fernandes
> Priority: Major
> Labels: query-ispn11
> Fix For: 11.0.0.Final
>
>
> * Custom FieldBridges
> * AnalyzerDef
> * Index time boost
> * Analyzer Discriminator
> * Default Analyzer
> * Default IndexNullAs
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11795) Entity mapping deprecations
by Yoann Rodière (Jira)
[ https://issues.redhat.com/browse/ISPN-11795?page=com.atlassian.jira.plugi... ]
Yoann Rodière edited comment on ISPN-11795 at 5/13/20 7:45 AM:
---------------------------------------------------------------
Something else I just noticed: Infinispan 10/11 enable the option {{org.hibernate.search.cfg.Environment#INDEX_UNINVERTING_ALLOWED}}. This means Hibernate Search will accept sorts on fields that are not marked as {{@SortableField}}, but will print a warning every time it does, because that behavior is deprecated.
With Hibernate Search 6, this is no longer allowed: only fields marked as sortable can be sorted on. The option {{org.hibernate.search.cfg.Environment#INDEX_UNINVERTING_ALLOWED}} does not exist anymore.
So, you might want to stress that sorting on non-{{@SortableField}} fields is deprecated.
was (Author: y.rodiere):
Something else I just noticed: Infinispan 10/11 enable the option {{org.hibernate.search.cfg.Environment#INDEX_UNINVERTING_ALLOWED}}. This means Hibernate Search will accept sorts on fields that are not marked as {{@Sortable}}, but will print a warning every time it does, because that behavior is deprecated.
With Hibernate Search 6, this is no longer allowed: only fields marked as sortable can be sorted on. The option {{org.hibernate.search.cfg.Environment#INDEX_UNINVERTING_ALLOWED}} does not exist anymore.
So, you might want to stress that sorting on non-{{@Sortable}} fields is deprecated.
> Entity mapping deprecations
> ---------------------------
>
> Key: ISPN-11795
> URL: https://issues.redhat.com/browse/ISPN-11795
> Project: Infinispan
> Issue Type: Enhancement
> Components: Embedded Querying
> Reporter: Gustavo Fernandes
> Priority: Major
> Labels: query-ispn11
> Fix For: 11.0.0.Final
>
>
> * Custom FieldBridges
> * AnalyzerDef
> * Index time boost
> * Analyzer Discriminator
> * Default Analyzer
> * Default IndexNullAs
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11795) Entity mapping deprecations
by Yoann Rodière (Jira)
[ https://issues.redhat.com/browse/ISPN-11795?page=com.atlassian.jira.plugi... ]
Yoann Rodière commented on ISPN-11795:
--------------------------------------
Something else I just noticed: Infinispan 10/11 enable the option {{org.hibernate.search.cfg.Environment#INDEX_UNINVERTING_ALLOWED}}. This means Hibernate Search will accept sorts on fields that are not marked as {{@Sortable}}, but will print a warning every time it does, because that behavior is deprecated.
With Hibernate Search 6, this is no longer allowed: only fields marked as sortable can be sorted on. The option {{org.hibernate.search.cfg.Environment#INDEX_UNINVERTING_ALLOWED}} does not exist anymore.
So, you might want to stress that sorting on non-{{@Sortable}} fields is deprecated.
> Entity mapping deprecations
> ---------------------------
>
> Key: ISPN-11795
> URL: https://issues.redhat.com/browse/ISPN-11795
> Project: Infinispan
> Issue Type: Enhancement
> Components: Embedded Querying
> Reporter: Gustavo Fernandes
> Priority: Major
> Labels: query-ispn11
> Fix For: 11.0.0.Final
>
>
> * Custom FieldBridges
> * AnalyzerDef
> * Index time boost
> * Analyzer Discriminator
> * Default Analyzer
> * Default IndexNullAs
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11820) Hot Rod URI
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11820?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11820:
-----------------------------------
Labels: usability (was: )
> Hot Rod URI
> -----------
>
> Key: ISPN-11820
> URL: https://issues.redhat.com/browse/ISPN-11820
> Project: Infinispan
> Issue Type: Feature Request
> Components: Hot Rod
> Affects Versions: 11.0.0.Dev05
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Labels: usability
> Fix For: 11.0.0.CR1, 11.0.0.Final
>
>
> Creating a RemoteCacheManager can be unnecessarily complex for simple scenarios, requiring either a ConfigurationBuilder or a hotrod-client.properties file.
> We should support a URI format as follows:
> {noformat}
> hotrod[s]://[user[:password]@]host[:port][,host2[:port]][?property=value[&property2=value2]]
> {noformat}
> and the constructor to go with it RemoteCacheManager(URI)
> as well as infinispan.client.hotrod.url in hotrod-client.properties
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11820) Hot Rod URI
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11820?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11820:
-----------------------------------
Status: Open (was: New)
> Hot Rod URI
> -----------
>
> Key: ISPN-11820
> URL: https://issues.redhat.com/browse/ISPN-11820
> Project: Infinispan
> Issue Type: Feature Request
> Components: Hot Rod
> Affects Versions: 11.0.0.Dev05
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 11.0.0.CR1, 11.0.0.Final
>
>
> Creating a RemoteCacheManager can be unnecessarily complex for simple scenarios, requiring either a ConfigurationBuilder or a hotrod-client.properties file.
> We should support a URI format as follows:
> {noformat}
> hotrod[s]://[user[:password]@]host[:port][,host2[:port]][?property=value[&property2=value2]]
> {noformat}
> and the constructor to go with it RemoteCacheManager(URI)
> as well as infinispan.client.hotrod.url in hotrod-client.properties
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11820) Hot Rod URI
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11820?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11820:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8313
> Hot Rod URI
> -----------
>
> Key: ISPN-11820
> URL: https://issues.redhat.com/browse/ISPN-11820
> Project: Infinispan
> Issue Type: Feature Request
> Components: Hot Rod
> Affects Versions: 11.0.0.Dev05
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 11.0.0.CR1, 11.0.0.Final
>
>
> Creating a RemoteCacheManager can be unnecessarily complex for simple scenarios, requiring either a ConfigurationBuilder or a hotrod-client.properties file.
> We should support a URI format as follows:
> {noformat}
> hotrod[s]://[user[:password]@]host[:port][,host2[:port]][?property=value[&property2=value2]]
> {noformat}
> and the constructor to go with it RemoteCacheManager(URI)
> as well as infinispan.client.hotrod.url in hotrod-client.properties
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months