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/09 11:49:00 UTC
[jira] [Resolved] (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:all-tabpanel ]
Ivan Rakov resolved IGNITE-9785.
--------------------------------
Resolution: Fixed
Code changes look good.
.NET fails arribed from older version of master (already fixed).
[~alex_pl], thanks for your contribution!
> 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 on "read-only" state on Ignite node. In 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
> 3) Any attempt to update data via SQL API should fail
> 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)