Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-7997

Bring --logdest back to command line task option

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Invalid
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: log, pipe_base
    • Labels:
    • Team:
      Data Access and Database

      Description

      The command line option --logdest existed for specifying a log file destination in the CmdLineTask interface, and was removed in DM-6999 per RFC-203. But such functionality is still wanted, as Paul Price commented in RFC-203 (09/Sep/16):

      I think dumping the log to a file is such an important and common operation that it needs to be supported as a first-class command-line option. Having to write two lines of obscure configuration in a separate file for every command-line operation is too burdensome.

        Attachments

          Issue Links

            Activity

            Hide
            swinbank John Swinbank added a comment -

            Looks like a task framework issue, so assigning to the DAX team. Fritz Mueller, please push back if you disagree.

            Show
            swinbank John Swinbank added a comment - Looks like a task framework issue, so assigning to the DAX team. Fritz Mueller , please push back if you disagree.
            Hide
            salnikov Andy Salnikov added a comment -

            Paul Price, do you really need logging destination separate from standard output or can you survive with just regular standard output/error redirection?

            Merlin Fisher-Levine, you mentioned on RFC-203 that --logdest is essential for multicore jobs, could the multicore issue (I'm not totally sure what it is exactly) be solved by redirecting output instead of --logdest?

            Show
            salnikov Andy Salnikov added a comment - Paul Price , do you really need logging destination separate from standard output or can you survive with just regular standard output/error redirection? Merlin Fisher-Levine , you mentioned on RFC-203 that --logdest is essential for multicore jobs, could the multicore issue (I'm not totally sure what it is exactly) be solved by redirecting output instead of --logdest?
            Hide
            price Paul Price added a comment -

            I want to be able to log to both stdout and a file simultaneously (I want to see what's happening, and get a record of it). I could do this with pex_logging, so our capability has been reduced with the adoption of the new log package.

            I think the mutlicore issue is separate.

            Show
            price Paul Price added a comment - I want to be able to log to both stdout and a file simultaneously (I want to see what's happening, and get a record of it). I could do this with pex_logging, so our capability has been reduced with the adoption of the new log package. I think the mutlicore issue is separate.
            Hide
            swinbank John Swinbank added a comment -

            I want to be able to log to both stdout and a file simultaneously (I want to see what's happening, and get a record of it).

            tee?

            Show
            swinbank John Swinbank added a comment - I want to be able to log to both stdout and a file simultaneously (I want to see what's happening, and get a record of it). tee ?
            Hide
            price Paul Price added a comment - - edited

            tee?

            Yeah, I guess so. It feels like a reduction in capability and/or convenience, but maybe that's just a feeling.

            Show
            price Paul Price added a comment - - edited tee ? Yeah, I guess so. It feels like a reduction in capability and/or convenience, but maybe that's just a feeling.
            Hide
            salnikov Andy Salnikov added a comment -

            Paul Price, sorry, I know practically nothing about pex_logging, from what you say I guess that --logdest did not just redirect logging output to a file but instead duplicated it, is that right? I do agree with John that we should be using standard tools instead of try to reimplement that in pipeline - standard tools are standard and more flexible.

            I still want to hear what is the issue with multicore.

            Show
            salnikov Andy Salnikov added a comment - Paul Price , sorry, I know practically nothing about pex_logging, from what you say I guess that --logdest did not just redirect logging output to a file but instead duplicated it, is that right? I do agree with John that we should be using standard tools instead of try to reimplement that in pipeline - standard tools are standard and more flexible. I still want to hear what is the issue with multicore.
            Hide
            swinbank John Swinbank added a comment -

            Given that this hasn't been a big deal for 3.5 years, and since it's (presumably) all different in Gen3, I'm closing as “Won't Fix”. Please reopen if you disagree.

            Show
            swinbank John Swinbank added a comment - Given that this hasn't been a big deal for 3.5 years, and since it's (presumably) all different in Gen3, I'm closing as “Won't Fix”. Please reopen if you disagree.
            Hide
            tjenness Tim Jenness added a comment -

            Somehow this ticket is still open despite John Swinbank's comment from over a year ago.

            gen3 commands all support --log-file command line option to write the log to a file so I will close this as invalid.

            Show
            tjenness Tim Jenness added a comment - Somehow this ticket is still open despite John Swinbank 's comment from over a year ago. gen3 commands all support --log-file command line option to write the log to a file so I will close this as invalid.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              hchiang2 Hsin-Fang Chiang
              Watchers:
              Andy Salnikov, Fritz Mueller, Hsin-Fang Chiang, John Swinbank, Merlin Fisher-Levine, Paul Price, Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.