[
https://issues.apache.org/jira/browse/IGNITE-13367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180492#comment-17180492
]
Ignite TC Bot commented on IGNITE-13367:
----------------------------------------
{panel:title=Branch: [pull/8162/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8162/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Control Utility{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5550045]]
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerMetadataTest.testMetadataRemoveWrongType - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerMetadataTest.testMetadataForInternalClassesIsNotRegistered -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5550047&buildTypeId=IgniteTests24Java8_RunAll]
> meta --remove command usage improvements
> ----------------------------------------
>
> Key: IGNITE-13367
> URL: https://issues.apache.org/jira/browse/IGNITE-13367
> Project: Ignite
> Issue Type: Improvement
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Command for removing metadata has the following issues:
> # In 'Type not found' scenario it prints long stack traces to console instead
> of short information about requested type.
> # When used it registers some internal classes which are not supposed to go
> through binary metadata registration protocol.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
