Hi,
I'm noticing some strange behavior with a graph that I don't recall seeing before. The graph reads a .xlsx, reformats the data and writes to a flat file via a UniversalDataWriter. This graph is scheduled to run on the server daily. If there is no input file for the XLSDataReader, the graph fails. Not a problem, there may or may not be a file to process on any given day.
However, even when the graph fails in this way, an empty output file is being created by the UniversalDataWriter.
Is this normal behavior?? I honestly don't think it did this before. Only recently. In my experience, when a graph fails, there is no output. Is there a setting that would cause this? Server is 3.4.3
Thanks for any help with this issue.
pro7
I'm noticing some strange behavior with a graph that I don't recall seeing before. The graph reads a .xlsx, reformats the data and writes to a flat file via a UniversalDataWriter. This graph is scheduled to run on the server daily. If there is no input file for the XLSDataReader, the graph fails. Not a problem, there may or may not be a file to process on any given day.
However, even when the graph fails in this way, an empty output file is being created by the UniversalDataWriter.
Is this normal behavior?? I honestly don't think it did this before. Only recently. In my experience, when a graph fails, there is no output. Is there a setting that would cause this? Server is 3.4.3
Thanks for any help with this issue.
pro7
-
Hi pro7,
That is a normal behavior in that version of CloverETL, the Universal Data Writer can or may write blank file even if there is no data to write. In later versions there is a property that can turn this off, which was added in version 4.1 and higher, you can read more details here. I would highly recommend that you take the time to upgrade and take advantage of this feature. -
Thank you Pedro. We have our 4.1 server in place and are working to migrate there, however we're running into a problem communicating with the LDAP. I am in the process of writing this up and will be submitting to support. Thanks again for your reply.
pro7
Please sign in to leave a comment.
Comments 2