[ 
https://issues.apache.org/jira/browse/IGNITE-11788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Chudov updated IGNITE-11788:
----------------------------------
    Description: 
Both following cases related to executing commands in control.sh

1. New boolean field *succeeded* {color:#333333}in 
{color}*org.apache.ignite.internal.processors.cache.verify.**IdleVerifyResultV2*
 is not serialized. It may affect the case when there are no caches matching 
idle_verify command filters: possibly user can get odd output message.

2. Cache name parsing now assumes that cache names can be given as regexps - it 
may affect the case when cache name contains regexp special characters: user 
can get error message about incorrect regular expression.

  was:
Both following cases related to executing commands in control.sh

1. New boolean field *succeeded* {color:#333333}in 
{color}*org.apache.ignite.internal.processors.cache.verify.*

*IdleVerifyResultV2* is not serialized. It may affect the case when there are 
no caches matching idle_verify command filters: possibly user can get odd 
output message.

2. Cache name parsing now assumes that cache names can be given as regexps - it 
may affect the case when cache name contains regexp special characters: user 
can get error message about incorrect regular expression.


> Fix issues related to IGNITE-10896
> ----------------------------------
>
>                 Key: IGNITE-11788
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11788
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Denis Chudov
>            Assignee: Denis Chudov
>            Priority: Major
>             Fix For: 2.8
>
>
> Both following cases related to executing commands in control.sh
> 1. New boolean field *succeeded* {color:#333333}in 
> {color}*org.apache.ignite.internal.processors.cache.verify.**IdleVerifyResultV2*
>  is not serialized. It may affect the case when there are no caches matching 
> idle_verify command filters: possibly user can get odd output message.
> 2. Cache name parsing now assumes that cache names can be given as regexps - 
> it may affect the case when cache name contains regexp special characters: 
> user can get error message about incorrect regular expression.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to