- Newest
- Most votes
- Most comments
Hello,
Throwing an InvalidParameterException is currently expected behavior when calling CompareFaces[1] and one of the images does not have a valid face. Based on your description, to minimize API calls, we recommend you call DetectFaces for the images only after CompareFaces returns an InvalidParameterException. That said, we realize this can be optimized further and have filed a feature request in our backlog for consideration. Thank you for your valuable feedback!”
https://docs.aws.amazon.com/rekognition/latest/dg/API_CompareFaces.html
thanks,
yes, I ended up calling detect_face() first to stop getting the bogus error from compare_face() if there is no face on JPG.
I could also modify code to ignore this error but that it creates a problem if there is a real invalid parameter error - not due to missing face.
it is just surprising and frustrating that this behavior has been known since 2017-2018 and it still not fixed at end of 2021.
Relevant content
- asked a year ago
- asked 6 months ago
- AWS OFFICIALUpdated 19 days ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago