[jira] [Updated] (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 updated IGNITE-9785: --- Description: 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. was: 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 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. > 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)
[jira] [Updated] (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 updated IGNITE-9785: --- Description: 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 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. was: 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. > 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 > 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)
