[
https://issues.apache.org/jira/browse/IGNITE-26467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-26467:
---------------------------------------
Description:
We have validation procedure (see
{{{}QueryTypeDescriptorImpl#validateIndexes{}}}) on entry modification, which
checks indexed fields and prohibit to insert entries with wrong indexed field
type.
There are several issues with this procedure:
* Only explicitely created indexes are checked. Indexes '_key_PK' and
'AFFINITY_KEY' are not validated.
* One field can be validated several times, if this field used for more than
one index.
* Unprotected iteration over {{idxs}} HashMap can potentially throw
{{ConcurrentModificationException.}}
* KEY_FIELD_NAME and VAL_FIELD_NAME are checked against it's own class
(effectevely no-op)
was:
We have validation procedure (see \{{QueryTypeDescriptorImpl#validateIndexes}})
on entry modification, which checks indexed fields and prohibit to insert
entries with wrong indexed field type.
There are several issues with this procedure:
* Only explicitely created indexes are checked. Indexes '_key_PK' and
'AFFINITY_KEY' are not validated.
* One field can be validated several times, if this field used for more than
one index.
* Unprotected iteration over {{idxs}} HashMap can potentially throw
{{ConcurrentModificationException.}}
* KEY_FIELD_NAME and VAL_FIELD_NAME are checked against it's own class
(effectevely no-op for user classes and will throw an error for BinaryObject)
> Field type for affinity index is not validated
> ----------------------------------------------
>
> Key: IGNITE-26467
> URL: https://issues.apache.org/jira/browse/IGNITE-26467
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: ise
>
> We have validation procedure (see
> {{{}QueryTypeDescriptorImpl#validateIndexes{}}}) on entry modification, which
> checks indexed fields and prohibit to insert entries with wrong indexed field
> type.
> There are several issues with this procedure:
> * Only explicitely created indexes are checked. Indexes '_key_PK' and
> 'AFFINITY_KEY' are not validated.
> * One field can be validated several times, if this field used for more than
> one index.
> * Unprotected iteration over {{idxs}} HashMap can potentially throw
> {{ConcurrentModificationException.}}
> * KEY_FIELD_NAME and VAL_FIELD_NAME are checked against it's own class
> (effectevely no-op)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
