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
Would you consider removing the non-empty delimiter restriction in the delim output codec? I need this when using the chunker input codec that I added in #640 for the use case of transferring a large file from Azure to a local file.
The text was updated successfully, but these errors were encountered:
Ahh of course, rather than allow empty delimiters it's probably better for discovery if we add an explicit append codec, that'll simply write the raw data.
Edit: but I'd also say it's fine to simply instantiate a delim codec with an empty delimiter under the hood to make the implementation simpler.
Looking at the available output codecs, I noticed that
all-bytes
truncates on each message anddelim
doesn't support an empty delimiter.Would you consider removing the non-empty delimiter restriction in the
delim
output codec? I need this when using thechunker
input codec that I added in #640 for the use case of transferring a large file from Azure to a local file.The text was updated successfully, but these errors were encountered: