SPICE "supported range of dates"

Q&A
, , ,
1

I am getting records rejected by SPICE ingestion with the error code UNSUPPORTED_DATE_VALUE.

What the “supported range of dates” is, is not defined either in

SPICE ingestion error codes - Amazon QuickSight

or in

Using unsupported or custom dates - Amazon QuickSight

Does anyone have any insight?
Thx

2

ps the dates it is complaining about are in a timestamp field in Aurora/Postgres and are 4/2/0219 and 29/1/0007.

Both are, of course, valid dates.

This code reproduces a record which will not load into SPICE.
select ‘0001-01-01’::timestamp AS test_date into test;

3

And the best thing …? I have this set:

image
image547×214 8.56 KB

and I get no notification at all. Clearly skipping records is not considered a problem in QS.

4

Henry was crowned King Henry IV on October 13, 1399. But, apparently, that is a date that cannot be stored in SPICE.

UNSUPPORTED_DATE_VALUE – A date field contains a date that is in a supported format but is not in the supported range of dates, for example “12/31/1399” or “01/01/10000”. For more information, see Using unsupported or custom dates.

Am I reading this correctly?

5

I used the parseDate function with 12/13/1399 and when I include the same in my analysis get the following message

image
image838×216 13.8 KB

So, your assesment is right.

6

Oh dear! That means that every date field imported from the database needs code around it to check it’s acceptable to QS. <groan!>

Looks like my Early Modern History app will have to go on the back burner!

:wink:

Thanks @Giridhar.Prabhu