Closed rn-zeiss closed 9 months ago
Hi @rn-zeiss,
Thanks for creating this issue and giving us feedback on the framework! It's indeed a typo on the function name in the function repository, I will create a PR immediately to address this.
Once the PR is complete, you will be facing an additional challenge around the current limitations around formatting datetimes due to missing formatting functionality. We have addressed this in one of the open PR's, which we will finalize in the coming week. It will require you to install the dotnet runtime, because the python framework will be invoking the dotnet datetime implementation just like Data Factory does. This will be explained accordingly in the README.md.
If you have any other feedback on the framework, feel free to share!
I just finalized the PR that also fixes the anticipated formatting, just need a review from my colleagues. Should be tomorrow!
It's approved and available from release version: 0.0.1a83.
Let us know if it works, dont forget to install the dotnet runtime.
It would be awesome if you could share us your use case on arjenkroezen@microsoft.com, cheers!
Thanks, with 0.0.1a83 formatDateTime function now is working fine.
I have a pipeline with some expressions containing formatDateTime function as shown below and always get an ExpressionParsingError exception:
"File_Name": { "value": "@concat(item().TABLESPACE_NAME, '__', item().TABLE_NAME,'.v', formatDateTime(utcnow(), 'yyyyMMdd_HHmmss'), '.parquet')", "type": "Expression" }
Looks just like a typo in the framework code, there I find formatDataTime instead of formatDateTime.
P.S.: Very nice framework you created here for ADF testing. Thanks :thumbsup: