Add support for filter in pc_translator. #2287
Open
Conversation
This file contains 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
facebook-github-bot
added
CLA Signed
|
This pull request was exported from Phabricator. Differential Revision: D44702838 |
Differential Revision: D44617759 fbshipit-source-id: 11e1253802c5642b3b4bdfd8e10cf67b8a8983c5
Differential Revision: D44618035 fbshipit-source-id: f36d9abba81a638a7f82508b66c050a217ed87a7
Differential Revision: D44634384 fbshipit-source-id: 30c87e6c39bffcec815f5b0b838d2ea2c8ebb2df
Differential Revision: D44645325 fbshipit-source-id: 8b3efd3e9785884d7e2d8b1696ea826d511e0cb5
Summary: Pull Request resolved: #2287 # Context As per PC Translator design, we need a runtime library will be called during PC run. This library will be called at the beginning of PC run to encode specified fields in publisher side input into a encoded breakdown (aggregation) Ids based on active PC instruction sets for the run. The library will filter the active PC Instruction sets for the run based on parsing the pcs_features i.e. gatekeepers for the particular run. # Product decisions In this stack we would focus solely on functionality required for private lift runs. We would focus on the MVP implementation of the library and its integration with fbpcf ORAM encoder library in this stack. # Stack 1. Create runtime pc_translator library. 2. Add logic to retrieve and parse PC instruction set, filtered based on the active gatekeepers for the run. 3. Integrate pc_translator library with fbpcf ORAM encoder. 4. Add logic to generate transformed publisher output with encoded breakdown ID and write the output. 5. Add support for filter constraints in pc_translator. # In this diff Add support for filter constraints in pc_translator. Differential Revision: D44702838 Privacy Context Container: L416713 fbshipit-source-id: b60909247067a97a7b8a5d13c9e80fc400f96456
|
This pull request was exported from Phabricator. Differential Revision: D44702838 |
ajinkya-ghonge
force-pushed
the
export-D44702838
branch
from
b4c540b
to
7236864
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary:
Context
As per PC Translator design, we need a runtime library will be called during PC run. This library will be called at the beginning of PC run to encode specified fields in publisher side input into a encoded breakdown (aggregation) Ids based on active PC instruction sets for the run. The library will filter the active PC Instruction sets for the run based on parsing the pcs_features i.e. gatekeepers for the particular run.
Product decisions
In this stack we would focus solely on functionality required for private lift runs.
We would focus on the MVP implementation of the library and its integration with fbpcf ORAM encoder library in this stack.
Stack
In this diff
Add support for filter constraints in pc_translator.
Differential Revision:
D44702838
Privacy Context Container: L416713