You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
assignBrowse / onDrop: Consider the possibility of an async initFileFn (#350)
* assignBrowse/onDrop: Consider the possibility of an async initFileFn
When calling *addFile(), FlowChunk are created which, among other things look
for the file size to compute the endByte (and the number of chunks)
If an "initFileFn" is declared *AND* this function is async' it's sane to assume
we need to use `asyncAddFile()` which will bootstrap slightly differently.
By giving the time to run an async `initFileFn` it can, for example, allow the chunk
size to be computed differently regarding the stream initialization.
An example is a stream-crypto later that could had an overhead affecting FlowFile.size
Note: In the case of assignBrowse, the input is set to readonly for the time (async) initFileFn() runs
0 commit comments