[
https://issues.apache.org/jira/browse/GEODE-9220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342927#comment-17342927
]
Geode Integration commented on GEODE-9220:
------------------------------------------
Seen in [WindowsIntegrationTestOpenJDK11
#202|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/202]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0224/test-results/integrationTest/1620770128/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0224/test-artifacts/1620770128/windows-integrationtestfiles-OpenJDK11-1.15.0-build.0224.tgz].
> Switch unit and integration tests to use JedisCluster
> -----------------------------------------------------
>
> Key: GEODE-9220
> URL: https://issues.apache.org/jira/browse/GEODE-9220
> Project: Geode
> Issue Type: Test
> Components: redis
> Reporter: Jens Deppe
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> This won't make sense for some commands that are not 'cluster aware' - for
> example {{INFO}}. Commands that act on a key are all cluster aware.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
