[
https://issues.apache.org/jira/browse/IGNITE-9964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659624#comment-16659624
]
ASF GitHub Bot commented on IGNITE-9964:
----------------------------------------
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/5054
IGNITE-9964: Added test.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9964
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5054.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5054
----
----
> 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)
