This repository was archived by the owner on May 31, 2025. It is now read-only.
Replies: 3 comments 1 reply
-
The way to use the cli would be > dw -i <inputName> <pathToBigInput> -f <pathToDWFile> For example > dw -i payload ./MyBigJson.json -f ./MyDWScript.dwl |
Beta Was this translation helpful? Give feedback.
0 replies
-
As I understood from the README, -f, --file means
Specifies output file for the transformation.
…On Wed, Nov 23, 2022 at 7:37 AM Mariano de Achaval ***@***.***> wrote:
The way to use the cli would be
> dw -i <inputName> <pathToBigInput> -f <pathToDWFile>
For example
> dw -i payload ./MyBigJson.json -f ./MyDWScript.dwl
—
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEJSRMYPJHWPHKZ3PUKQVPLWJYFXZANCNFSM6AAAAAASIOLIAE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
Yes!
Thanks for clarifying. I must have read an old version of the README.
…On Thu, Nov 24, 2022 at 7:44 AM Mariano de Achaval ***@***.***> wrote:
No to specify the output is -o . From the --help you will get that
-f,--file <file-path> Specifies the DataWeave file
path to execute.
-o,--output <output-path> Specifies output file for the
transformation if not standard
output will be used.
So if you want to specify the output to be a file instead of the standard
output. You can use for example -o ./MyOutputFile.json
—
Reply to this email directly, view it on GitHub
<#61 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEJSRM5EQXD55CZ4D57IARTWJ5PLJANCNFSM6AAAAAASIOLIAE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I regularly use the DW playground but it cannot handle large input.
I regularly use Studio to test DW scripts but with large input sit can do a JVM ping (death) timeout.
I don't want to deploy my Mule app to Cloudhub and have to debug logs, so I would like a local DW engine that I can feed a complex script, which seems not possible with dw - i input {source-dat-filea < some-big-scripty-file.
Did I miss something.
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions