I realize it's a probably a bit late for you to use it 7 months later, but
I had basically the exact same scenario. ETL process, where I had a
timestamp field giving me dates as a string like this: 20141120012052UTC
I used this transform to fix it
{ "field":
{ "fieldName": "timestamp",
"expression": "timestamp.date(timestamp, 'yyyyMMddHHmmssz')"
}
},
On Thursday, September 24, 2015 at 4:32:57 PM UTC-4, Joe S. wrote:
>
> I'm trying to ETL import from a MySQL database. currently the information
> is in a string with mm/dd/yyyy hh:mm:ss tt format. ex. 8/22/2013 9:43:05 AM
>
> I can't change the format in the database because I have another program
> writing the information to it, but I want to be able to move it into
> orientdb.
>
> Tested this as a transform.
>
> { "field": { "fieldName": "time_modified", "expression": "date(
> $time_modified, 'mm-dd-yyyy hh:mm:ss tt' )" } }
>
>
> How can I use the ETL import to convert it to the proper datetime format?
>
> Alternatively I can leave it as a string, but then I don't think I can
> make calculations against it.
>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
