Skip to content
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

utils/publish.py search_ingest should log http.response from the search ingest lambda #187

Open
ericblau opened this issue Apr 21, 2023 · 0 comments

Comments

@ericblau
Copy link
Collaborator

Evidently it is possible to get a 200 response from Globus Search ingest, with zero documents ingested. (This can happen if the index has exceeded its 1000 fields--but the error message will only be in the Globus Search Task.) Thus, the dlhub_sdk search_ingest function should log the response from Globus Search ingest even when "successful" so that the user has the Globus Search taskid to try to figure out why their document doesn't show up in the index.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant