[
https://issues.apache.org/jira/browse/IGNITE-9964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanislav Lukyanov updated IGNITE-9964:
---------------------------------------
Description:
SELECT by affinity key doesn't work on a table that was created with a custom
cache template if entries were added through JCache (using withKeepBinary()).
If the first row was added via INSERT and after that another row was added via
withKeepBinary(), SELECT by affinity key works correctly.
If the first row was added via withKeepBinary() and after that another row was
added via INSERT, SELECT by affinity key returns nothing.
was:SELECT by affinity key doesn't work on a table that was created with a
custom cache template if entries were added through JCache (using
withKeepBinary()).
> SQL: query by affinity key fails when a table is created from a custom
> template
> -------------------------------------------------------------------------------
>
> Key: IGNITE-9964
> URL: https://issues.apache.org/jira/browse/IGNITE-9964
> Project: Ignite
> Issue Type: Bug
> Reporter: Stanislav Lukyanov
> Priority: Major
>
> SELECT by affinity key doesn't work on a table that was created with a custom
> cache template if entries were added through JCache (using withKeepBinary()).
> If the first row was added via INSERT and after that another row was added
> via withKeepBinary(), SELECT by affinity key works correctly.
> If the first row was added via withKeepBinary() and after that another row
> was added via INSERT, SELECT by affinity key returns nothing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
