You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I have been digging into the Langchain code. The UNSTRUCTURED_API_URL appears to utilize partition_multiple_via_api within unstructured.partition.api
detail ref:langchain-ai/langchain#21488
The user is using a private URL, and its SSL is private, so it requires to skip SSL verification for requests.
and now. partition_multiple_via_api no way to do that
Describe alternatives you've considered
Perhaps we could reuse **request_kwargs which contains request data. We can retrieve parameters from **request_kwargs and utilize them in requests.
partition_multiple_via_api:
We can pass a custom requests.Session to the unstructured-client like this. We can certainly add a flag to the Loader to set this up before the partition call.
Is your feature request related to a problem? Please describe.
I have been digging into the Langchain code. The
UNSTRUCTURED_API_URL
appears to utilizepartition_multiple_via_api
withinunstructured.partition.api
detail ref:langchain-ai/langchain#21488
The user is using a private URL, and its SSL is private, so it requires to skip SSL verification for requests.
and now.
partition_multiple_via_api
no way to do thatDescribe the solution you'd like
It seems to me that we might consider providing **kwargs to support this scenario.
requests support params: https://github.com/psf/requests/blob/2d5f54779ad174035c5437b3b3c1146b0eaf60fe/src/requests/api.py#L14
Describe alternatives you've considered
Perhaps we could reuse
**request_kwargs
which contains request data. We can retrieve parameters from**request_kwargs
and utilize them inrequests
.partition_multiple_via_api:
unstructured/unstructured/partition/api.py
Line 105 in e4c8959
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: