[
https://issues.apache.org/jira/browse/IGNITE-16680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17506395#comment-17506395
]
Ignite TC Bot commented on IGNITE-16680:
----------------------------------------
{panel:title=Branch: [pull/9884/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9884/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6348302&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently the only information about the cache expiry policy while executing
> {code:java}
> control.sh --cache list . --config{code}
> command is the information about expiry policy factory class. This
> information may not always be useful 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)
