You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sentry.apache.org by "Gregory Chanan (JIRA)" <ji...@apache.org> on 2014/07/22 21:40:38 UTC

[jira] [Commented] (SENTRY-354) Test for update.distrib phase overriding

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

Gregory Chanan commented on SENTRY-354:
---------------------------------------

Review request: https://reviews.apache.org/r/23822/

> Test for update.distrib phase overriding
> ----------------------------------------
>
>                 Key: SENTRY-354
>                 URL: https://issues.apache.org/jira/browse/SENTRY-354
>             Project: Sentry
>          Issue Type: Task
>    Affects Versions: 1.3.0
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>         Attachments: SENTRY-354.patch
>
>
> NOTE: I left the Fix Version blank because I think this should go into 1.5.0, i.e. after 1.4.0 is branched, because this requires changing some version numbers that should be done after branching.  I'll add the Fix Version when we branch and it's added to JIRA.
> We need a test for the following issue:
> Solr sets the update.distrib phase param to indicate that update processors before the DistribUpdateProcessor can be skipped. A malicious user could do the same thing in order to skip the update index checks, which happen first (i.e. before the DistribUpdateProcessor). SOLR-5395 (in SOLR 4.6) has a feature "RunAlways" which will always run a given processor regardless of the phase. We should use this feature to ensure the update index processor is always run.



--
This message was sent by Atlassian JIRA
(v6.2#6252)