1 個回答
- 最新
- 最多得票
- 最多評論
2
Hi Daniel,
This is expected, as in SearchUser operation, the input user itself would be excluded from the search response. The user is not excluded in the response when using SearchFaces as Face and User are different entities. If you want to test out the search performance for this operation, you can create two users that associated with the faces of the same person, e.g. "elizabeth1", "elizabeth2". If you then call SearchUser with "elizabeth1", only "elizabeth2" will be in the response.
已回答 3 個月前
hanks for the reply!
I'm confused, so if it returns the searched user ID within the "SearchedUser" attribute, does the user exist? It seems counterintuitive, especially when searching for a user ID that does not exist, the service returns an error of type "InvalidParameterException", when it should be "ResourceNotFoundException", in my opinion.
aws-particulares rekognition search-users --collection-id KLPNOQFXDTUC --user-id carlos An error occurred (InvalidParameterException) when calling the SearchUsers operation: Request has invalid parameters
In short, I think there is an opportunity for improvement here, but since I am not an AWS engineer, I better sleep with the doubt. I'm going to adapt my application to be compatible with these API responses
I came here to ask the same question, and I agree with Daniel's comment above. I want my application to verify that the user exists in rekognition before attempting to perform operations that involve that user. So for now, if this is the expected behavior, I will assume the user has been created unless it throws an exception.
Sorry if my past answer was ambiguous, let me clarify:
There are three key fields in the SearchUser response: "SearchedUser", "SearchedFace", and "UserMatches".
back to me, so how do I see the details of a specific user in a collection?, such as their status