-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Multitenancy #85
Multitenancy #85
Conversation
Hi @amn41 Let me know what you think about this. |
looks cool! I'll check it out. Are there any mitie compatibility issues, e.g. could your branch in principle be merged into MITIE master? |
Yes, It can be merged into MITIE master. In the original implementaion of MITIE, get_feature_vector() of total_word_feature_extractor used the same temp variable (to avoid reallocating) for storing intermediate values. But now its allocated freshly for each function call. So these changes might not be suitable for general MITIE users. |
You can take a look at the relevant PR for MITIE mit-nlp/MITIE#88 |
The PR mit-nlp/MITIE#88 has been accepted. So now we can provide a feature extractor while doing the prediction. Its there for both |
Hi I'm currently working on a developing a multi tenant application based on rasa, and I was wondering if there's more thorough documentation for this part available ? @amn41 |
Where I can find the documentation for achieving multi-tenancy? |
* Removed return value as default slot * added ability to use multiple defaults for cli parameters
addresses #36
nlp
instance, if all models are spaCy and in the same languageserver_model_dir
inconfig.json
with a json obj, e.g."server_model_dir":{"one":"model_XXXXX","two":"model_YYYY"}
where the keys act as aliases. Then add amodel
param to HTTP requests, e.g.localhost:5000/parse?q=hello&model=one
test_multitenancy.py