Due to recent updates, all users are required to create an Altair One account to login to the RapidMiner community. Click the Register button to create your account using the same email that you have previously used to login to the RapidMiner community. This will ensure that any previously created content will be synced to your Altair One account. Once you login, you will be asked to provide a username that identifies you to other Community users. Email us at Community with questions.

When connect to MongoDB date time data are converted to unix timestamp, How come?

TaaTaa Member Posts: 1 Learner III
edited November 2019 in Help


Answers

  • sgenzersgenzer Administrator, Moderator, Employee, RapidMiner Certified Analyst, Community Manager, Member, University Professor, PM Moderator Posts: 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. :smile:
  • David_ADavid_A Administrator, Moderator, Employee, RMResearcher, Member Posts: 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.

    Best,
    David
  • kaymankayman Member Posts: 662 Unicorn
    edited November 2019
    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.
Sign In or Register to comment.