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

Igor Zadubinin updated IGNITE-16680:
------------------------------------
    Description: 
Currently the only information about the cache expiry policy while executing
{code:java}
control.sh --cache list . --config{code}
command is information about expiry policy factory class. This information may 
not always be complete due to the fact that not all expire policy factory 
classes implement toString method. I propose to make a feature that adds cache 
expire policy information, regardless of the toString method implementation in 
the above classes.

  was:Currently the only information about the cache expiry policy while 
executing control.sh --cache list . --config command is information about 
expiry policy factory class. This information may not always be complete due to 
the fact that not all expire policy factory classes implement toString method. 
I propose to make a feature that adds cache expire policy information, 
regardless of the toString method implementation in the above classes.


> Add cache expiry policy info to control.sh script
> -------------------------------------------------
>
>                 Key: IGNITE-16680
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16680
>             Project: Ignite
>          Issue Type: New Feature
>          Components: control.sh
>            Reporter: Igor Zadubinin
>            Assignee: Igor Zadubinin
>            Priority: Minor
>
> Currently the only information about the cache expiry policy while executing
> {code:java}
> control.sh --cache list . --config{code}
> command is information about expiry policy factory class. This information 
> may not always be complete due to the fact that not all expire policy factory 
> classes implement toString method. I propose to make a feature that adds 
> cache expire policy information, regardless of the toString method 
> implementation in the above classes.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to