[ERROR] failed to parse field [Class/attribute] of type [date] in document #252
-
I am getting this error when trying to ingest a product that is in a valid PDS4 date format:
Is this a bug? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
To store date fields in Elasticserch, the values have to be converted to ISO-8601 "instant" format (e.g., "2013-10-24T00:49:37.457Z"). The current Harvest will only try to convert fields containing "date" string in their names (improvement planned for future here). As a workaround, you can update your Harvest config to specify fields you want to convert that do not have "date" in their names. See the Harvest documentation here |
Beta Was this translation helpful? Give feedback.
-
One other possible explanation for this error is a possible invalid date. The PDS4 schematron rules contain a bug that don't sufficiently check (1) days of month, for example: <stop_date_time>2012-06-31T02:22:47.956Z</stop_date_time> Note there are only 30 days in June. (2) allows 60 seconds to be specified, for example: <stop_date_time>2012-06-30T02:22:60Z</stop_date_time> Note this should really be |
Beta Was this translation helpful? Give feedback.
To store date fields in Elasticserch, the values have to be converted to ISO-8601 "instant" format (e.g., "2013-10-24T00:49:37.457Z").
The current Harvest will only try to convert fields containing "date" string in their names (improvement planned for future here).
As a workaround, you can update your Harvest config to specify fields you want to convert that do not have "date" in their names. See the Harvest documentation here