You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Rakov (JIRA)" <ji...@apache.org> on 2018/10/03 14:52:00 UTC
[jira] [Commented] (IGNITE-9785) Introduce read-only state in local
node context
[ https://issues.apache.org/jira/browse/IGNITE-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637048#comment-16637048 ]
Ivan Rakov commented on IGNITE-9785:
------------------------------------
PR: https://github.com/apache/ignite/pull/4895
TC run: https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&branch_IgniteTests24Java8=pull%2F4895%2Fhead
> Introduce read-only state in local node context
> -----------------------------------------------
>
> Key: IGNITE-9785
> URL: https://issues.apache.org/jira/browse/IGNITE-9785
> Project: Ignite
> Issue Type: New Feature
> Reporter: Ivan Rakov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Fix For: 2.8
>
>
> It would be useful to have option to switch "read-only" state on Ignite node. Under read-only state:
> 1) Any attempt to update data via Cache API should throw exception
> 2) Any attempt to update data via DataStreamer should throw exception
> Local read-only state may be helpful in further implementing global read-only cluster state, which can be switched via user API.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)