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

Sergey Chugunov edited comment on IGNITE-8560 at 5/23/18 2:04 PM:
------------------------------------------------------------------

Patch artifacts: [PR|https://github.com/apache/ignite/pull/4051], [TC 
run|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll&tab=buildTypeStatusDiv&branch_IgniteTests24Java8=pull%2F4051%2Fhead],
 [review|https://reviews.ignite.apache.org/ignite/review/IGNT-CR-619]


was (Author: sergey-chugunov):
Patch artifacts: [PR|https://github.com/apache/ignite/pull/4051], [TC 
run|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll&tab=buildTypeStatusDiv&branch_IgniteTests24Java8=pull%2F4051%2Fhead]

> Update index validation utility to use statistical check approach
> -----------------------------------------------------------------
>
>                 Key: IGNITE-8560
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8560
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexey Goncharuk
>            Assignee: Sergey Chugunov
>            Priority: Major
>             Fix For: 2.6
>
>
> Currently, the check index feature of {{control.sh}} scans the full data set 
> which has N * logN complexity. On large data sets this takes too long to 
> complete. 
> To mitigate this, I suggest to add an option 
> * to check either first K entries
> * to check each Kth entry



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

Reply via email to