[jira] [Commented] (IGNITE-12659) [ML] Remove broken sub-modules in ML

["Ignite TC Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-12659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034556#comment-17034556 ] 

Ignite TC Bot commented on IGNITE-12659:
----------------------------------------

{panel:title=Branch: [pull/7407/head] Base: [master] : Possible Blockers (23)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests 20|https://ci.ignite.apache.org/viewLog.html?buildId=5041368]]
* IgniteCacheTestSuite2: IgniteCacheClientNodeChangingTopologyTest.testLock - Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2: IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxNearEnabledNoRemap - Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2: IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxPutAllMultinode - Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2: IgniteCacheClientNodeChangingTopologyTest.testAtomicPrimaryPutAllMultinode - Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2: IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxMessageClientFirstFlag - Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2: IgniteCacheClientNodeChangingTopologyTest.testLockAllMultinode - Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2: IgniteCacheClientNodeChangingTopologyTest.testAtomicPutAllPrimaryMode - Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2: IgniteCacheClientNodeChangingTopologyTest.testAtomicNoRemapPrimaryMode - Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2: IgniteCacheClientNodeChangingTopologyTest.testPessimisticTx - Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2: IgniteCacheClientNodeChangingTopologyTest.testOptimisticTxMessageClientFirstFlag - Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2: IgniteCacheClientNodeChangingTopologyTest.testAtomicGetAndPutPrimaryMode - Test has low fail rate in base branch 0,0% and is not flaky
... and 9 tests blockers

{color:#d04437}Queries 1{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=5041394]]
* IgniteBinaryCacheQueryTestSuite: IndexingCachePartitionLossPolicySelfTest.testReadWriteSafeWithPersistence[TRANSACTIONAL] - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Continuous Query 1{color} [[tests 2|https://ci.ignite.apache.org/viewLog.html?buildId=5041313]]
* IgniteCacheQuerySelfTestSuite3: CacheContinuousQueryFailoverAtomicNearEnabledSelfSelfTest.testMultiThreadedFailover - New test duration 63s is more that 1 minute
* IgniteCacheQuerySelfTestSuite3: CacheContinuousQueryFailoverAtomicNearEnabledSelfSelfTest.testFailoverStartStopBackup - New test duration 66s is more that 1 minute

{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5041418&buildTypeId=IgniteTests24Java8_RunAll]

> [ML] Remove broken sub-modules in ML
> ------------------------------------
>
>                 Key: IGNITE-12659
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12659
>             Project: Ignite
>          Issue Type: Bug
>          Components: ml
>            Reporter: Alexey Zinoviev
>            Assignee: Alexey Zinoviev
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> After testing phase we investigated that the next sub-modules are broken and should be removed from the release branch 2.8
>  * tensorflow (it uses deprecated IGFS and current solution in tf.contrib could n't connect to Ignite now)
>  * tensorflow-ml-parser (it has a lot of bugs and doesn't work with tf 2.0)
>  * mleap-ml-parser (CVE, Ignite ML couldn't work with metadata)
>  * outdated genetic algorithms what are not supported now and are not formatted and refactored for the years (it's not a part of ML historically)
> also due to connect with Hadoop, Spark and another libraries it has a few CVE related to the old dependencies in Hadoop libraries
>  
> P.S. I suppose all these solutions should be moved to the separate project ignite-ml-extensions for the independent developement



--
This message was sent by Atlassian Jira
(v8.3.4#803005)