Fine-Grained Privacy Constraints 2 #985
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…or for Fine-Grained Constraints
…temml into FineGrainedPrivacy2
…rede/systemml into FineGrainedPrivacy2" This reverts commit 8d3a649, reversing changes made to 7ea9d74.
Propagator will throw exception if privacy constraint activated.
So that it does not use Serializable interface to serialize DataRange instances
Contributor
Author
|
This PR has been replaced by #1051. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds fine-grained privacy to the privacy constraints. This PR builds on Fine-Grained Privacy Constraints 1.