-
Notifications
You must be signed in to change notification settings - Fork 16
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
$vectorize: Misleading error when authentication.providerKey
not set
#1124
Comments
Thanks, Val
|
@Hazel-Datastax
This basically says this collection will use header-based vectorize authentication. Correct? |
Correct. It expects either "header-based" or "none" |
I think "Embedding Gateway failed to process request: getCredential error, integration credential is null" error on |
Just one small follow-up question: is there a way to get
If not, we should consider making |
Suppose you create a collection without an
authentication.providerKey
:If you try to use
$vectorize
with this new collection:You get an NPE:
[{"message":"java.lang.NullPointerException: Param was null","errorCode":"SERVER_UNHANDLED_ERROR"}]
similar to #1116.The error message should be better. Ideally throw an error when calling
createCollection()
, but ideally a more helpful error that there's missing credentials likeVECTORIZE_CREDENTIAL_INVALID
would be goodThe text was updated successfully, but these errors were encountered: