-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Update docs of DeepsetCloudDocumentStore #2460
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.
DEFAULT_API_ENDPOINT
in haystack/document_stores/deepsetcloud.py can be safely removed. Instead please adjust DEFAULT_API_ENDPOINT
in haystack/utils/deepsetcloud.py. This is the one that acts as default if neither the api_key
param nor the env variable has been set.
The remaining parts look good to me :-)
@@ -9,7 +9,7 @@ | |||
from haystack.utils import DeepsetCloud | |||
|
|||
|
|||
DEFAULT_API_ENDPOINT = f"DC_API_PLACEHOLDER/v1" # TODO | |||
DEFAULT_API_ENDPOINT = "https://api.cloud.deepset.ai/api/v1" |
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 like this is superfluous. The actual DEFAULT_API_ENDPOINT
has moved to haystack/utils/deepsetcloud.py. There it makes sense to adjust it. But this one can be safely removed.
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.
Ok, adjusted it
Co-authored-by: tstadel <60758086+tstadel@users.noreply.github.com>
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.
LGTM!
Proposed changes:
Updating a few doc strings of the DeepsetCloudDocumentStore
@tstadel not sure about the usage of "DEFAULT_API_ENDPOINT". Where is this one actually used? Does it make sense to update it to the actual endpoint now?
Status (please check what you already did):