[
https://issues.apache.org/jira/browse/SOLR-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585256#action_12585256
]
Ryan McKinley commented on SOLR-527:
------------------------------------
I agree neither should approach should be committed.
But I sympathize with the general request to make slave machines read-only. I
think the problem Sean is trying to solve is to have confidence that his slave
machines won't accidentally update or something like that.
Other approaches are to make the file system read-only for the slave machine
(but not for running rsync)
Perhaps with SOLR-465, their could be a read only Directory instance...
> An XML commit only request handler
> ----------------------------------
>
> Key: SOLR-527
> URL: https://issues.apache.org/jira/browse/SOLR-527
> Project: Solr
> Issue Type: New Feature
> Components: update
> Affects Versions: 1.3
> Reporter: Sean Timm
> Priority: Trivial
> Attachments: ReadOnlyUpdateProcessorFactory.java,
> ReadOnlyUpdateProcessorFactory.java, SOLR-527.patch
>
>
> This request handler only permits <commit/> messages. It is provided as one
> way to prevent adds and deletes on a Solr slave machine that could
> potentially be accessed by outside parties where a firewall or other access
> control is either not possible or not desired.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
