1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
I believe the root cause is a typo in ZoneId. According to utility documentation formats is based on DateTimeFormatter which uses TZDB IDs for TimeZones. According to this it should be either Asia/Calcutta
or Asia/Kolkata
. You can find a helpful list of time zones here
répondu il y a 2 ans
Contenus pertinents
- demandé il y a 4 mois
- demandé il y a 7 mois
- demandé il y a un an
- Réponse acceptéedemandé il y a 8 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
Thanks for the answer, but I get following error.
can't serialize value (/createpayInfo/date) : Unable to serialize
2022-03-28 12:34:59+0530
as a valid DateTime Object.Changing the type from AWSDateTime to String fixed the issue. Seems other time zone value is not accepted when value is inserted in dynamodb.