[
https://issues.jboss.org/browse/ISPN-9021?page=com.atlassian.jira.plugin....
]
Adrian Nistor updated ISPN-9021:
--------------------------------
Description:
All types that are not annotated are currently fully indexed for backward compat with
first version of remote query (which did not have protobuf annotations to control
indexing).
This behaviour is very inefficient and confusing for users that do not intend to use
indexing (non-indexed query works anyway).
Given the history of this behaviour we cannot remove it until next major version. Until
then we can offer the choice of disabling it per each schema file via a boolean protobuf
file-level option named 'enable_default_indexing', which when absent is considered
to to be true. Setting it to false will disable indexing of types that do not have
indexing annotations.
Whenever default indexing is used a warning will be logged in order to motivate people to
switch to annotations.
was:
All types that are not annotated are currently fully indexed for backward compat with
first version of remote query (which did not have protobuf annotations to control
indexing).
This behaviour is very inefficient and confusing for users that do not intend to use
indexing (non-indexed query works anyway).
Given the history of this behaviour we cannot remove it until next major version. Until
then we can offer the choice of disabling it per each schema file via a boolean protobuf
file-level option named 'enable_default_indexing', which when absent is considered
to to be true. Setting it to false will disable indexing of types that do not have
indexing annotations.
Remote query: add option to disable default indexing per schema file
--------------------------------------------------------------------
Key: ISPN-9021
URL:
https://issues.jboss.org/browse/ISPN-9021
Project: Infinispan
Issue Type: Enhancement
Reporter: Adrian Nistor
Assignee: Adrian Nistor
Fix For: 9.3.0.Final
All types that are not annotated are currently fully indexed for backward compat with
first version of remote query (which did not have protobuf annotations to control
indexing).
This behaviour is very inefficient and confusing for users that do not intend to use
indexing (non-indexed query works anyway).
Given the history of this behaviour we cannot remove it until next major version. Until
then we can offer the choice of disabling it per each schema file via a boolean protobuf
file-level option named 'enable_default_indexing', which when absent is considered
to to be true. Setting it to false will disable indexing of types that do not have
indexing annotations.
Whenever default indexing is used a warning will be logged in order to motivate people to
switch to annotations.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)