sgenzerAdministrator, Moderator, Employee, RapidMiner Certified Analyst, Community Manager, Member, University Professor, PM ModeratorPosts: 2,959 Community Manager
hi @Taa hmm I have no idea why that is being converted to epoch time but it's easily remedied with the Numerical to Date operator.
2
David_AAdministrator, Moderator, Employee, RMResearcher, MemberPosts: 297 RM Research
Hi,
if I remember it was because in the mongoDB entries it wasn't possible to store dates consistently.
As Scott correctly pointed out, parsing the dates afterwards can be easily done. The other way round (transforming the date into a String of your desired format) can be done with Generate Attribute.
Mongo date format is ISO UTC format on display, but in reality just a numeric value. So when you import the date format is the numeric representation. As already mentioned numeric to date format converts it back to a date format, but basically it remains the same number behind the scenes.
Storing a date back to Mongo is therefore easiest done by using the numeric Epoch format and adding .$date to your attribute. Mongo will then nicely convert it again to ISODate format.
Answers
David
Storing a date back to Mongo is therefore easiest done by using the numeric Epoch format and adding .$date to your attribute. Mongo will then nicely convert it again to ISODate format.