Coming soon: We’re working on a brand new, revamped Community experience. Want to receive updates? Sign up now!
I upgraded from 3.x to 4.x DSS and one of my previously working cleanup scripts stopped parsing the date.
Looks like it checks out there but when processing we see this warning:
[12:49:25] [WARN] [dku.shaker.date] - SHAKER_BAD_DATE: Failed to parse '2017-02-13t07:27:41 cst' using format 'yyyy-MM-dd'T'HH:mm:ss z', at position 20
So, that format in the warning won't work because it has internal single quotes and is surrounded by single quotes. Not sure if that is something that would have changed between versions. I tried various escaping \'T\', "T", \T. I can't seem to get it to parse this date the way it did before... Any clues to what I'm doing wrong?
EDIT: I used a regex replace to pop the 'T' out of that column. Still not parsing date.
Hi, with a little testing, I would say it's the lowercase cst that the parser objects to in that row.