-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Better error response for wrong datetime format in REST filter #3531
Labels
Comments
timvisee
changed the title
Better error handling for datetime in REST filter
Better error response for wrong datetime format in REST filter
Feb 5, 2024
Much needed. I'd rather have it parse multiple formats, but for now I don't mind having at least a better error message. |
@kartikchoubisa it is already merged |
/bounty $100 |
💎 $100 bounty • QdrantSteps to solve:
Thank you for contributing to qdrant/qdrant! Add a bounty • Share on socials
|
/attempt #3531
|
9 tasks
💡 @gsaivinay submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
We recently merged #3395 which adds a datetime payload index.
Currently, the datetime parser is very strict, only allowing RFC 3339 formats in our REST API. A common format such as
YYYY-MM-DD HH:MM:SS
is currently not accepted.If you'd send the following request:
You'd receive the following error:
This error is very confusing.
Describe the solution you'd like
We'd strongly prefer a more descriptive error message instead.
Something like this would be a lot better:
Describe alternatives you've considered
None
Additional context
Related issue: #3529
The text was updated successfully, but these errors were encountered: