-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ad-hoc recognizers #677
Ad-hoc recognizers #677
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great! Not sure about the name though, but can be discusssed offline
presidio-analyzer/presidio_analyzer/nlp_engine/spacy_nlp_engine.py
Outdated
Show resolved
Hide resolved
# Conflicts: # docs/analyzer/adding_recognizers.md
@navalev and @SharonHart please re-review. Added some tests and did some better exception handling. |
@navalev any suggestions for the name? |
for lack of better name, lets use ad-hoc :) |
…residio into feature/ad_hoc_recos
Adding the option to add recognizers (regex/deny-list) only in the context of one request.
This allows user to define their own recognizers without having to write code nor redeploy the service, similar to the capability in V1.
Main difference from V1 is that there is no persistency of these recognizers and each request would have to contain the list of recognizers it needs for PII identification. The V1 recognizer store capability is in our future roadmap.
Added:
ad_hoc_recognizers
parameter toAnalyzerEngine.analyze
AnalyzerRequest