Running openSeaChest_LogParser without the --outputLog flag is intended to print the output to the screen. However, previously, running openSeaChest_LogParser without --outputLog would print the output in JSON format, regardless of whether or not a different print type (e.g. CSV or Text) was specified with --printType. Meanwhile, the correct format was set to a file with a .jsn file extension (even if the print type differed).
For example, running the LogParser with a CSV print type but no outputLog would result in JSON output being printed to the screen (stdout) and CSV output being sent to a .jsn file. The following image illustrates this.
The desired output for such a situation would be CSV output printed to stdout (rather than JSON) and to a .csv file (rather than .jsn). My changes result in the following situation.
A similar situation could occur with the Prom print type. Currently, with --printType prom, JSON is printed to stdout, and Prom output is sent to a .jsn file.
My changes result in Prom printed to stdout and sent to a .prom file.
JSON is still used as the default if no print type is specified (just as before), so if JSON is specified as the print type or the argument is omitted, JSON is printed to stdout and to a .json file. The only difference is that the file extension was changed to .json, which is the proper extension according to the RFC 8259 internet standard.
Swiss3003
commented
4 years ago
Running openSeaChest_LogParser without the
--outputLogflag is intended to print the output to the screen. However, previously, running openSeaChest_LogParser without--outputLogwould print the output in JSON format, regardless of whether or not a different print type (e.g. CSV or Text) was specified with--printType. Meanwhile, the correct format was set to a file with a .jsn file extension (even if the print type differed).For example, running the LogParser with a CSV print type but no outputLog would result in JSON output being printed to the screen (stdout) and CSV output being sent to a .jsn file. The following image illustrates this.
The desired output for such a situation would be CSV output printed to stdout (rather than JSON) and to a .csv file (rather than .jsn). My changes result in the following situation.
A similar situation could occur with the Prom print type. Currently, with
--printType prom, JSON is printed to stdout, and Prom output is sent to a .jsn file.My changes result in Prom printed to stdout and sent to a .prom file.
JSON is still used as the default if no print type is specified (just as before), so if JSON is specified as the print type or the argument is omitted, JSON is printed to stdout and to a .json file. The only difference is that the file extension was changed to .json, which is the proper extension according to the RFC 8259 internet standard.