Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-3683

Add optional errordir for .bad and .err to cpimport (like in cpimport.bin)

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.5.2
    • Component/s: cpimport
    • Labels:
      None

      Description

      cpimport.bin include the possibility of custom directory for .bad and .err files.

      If cpimport will be called manually, .bad and .err files will be saved in the directory like the import files.

      If for some reason (policy etc.) only read access is possible, .bad and .err files can't be written.

      So a custom directory for writing the logs would be good.

      This option already exists in cpimport.bin

      cpimport.bin -h

        -L send *.err and *.bad (reject) files here
      

      And already declared in we_bulkload.h

       std::string  fErrorDir;             // Opt dir for *.err and *.bad files
       
       inline const std::string& BulkLoad::getErrorDir( ) const
      {
          return fErrorDir;
      }
      

      So maybe an easy solution would be to add this option also in cpimport and set the errordir like cpimport.cpp

      case 'L':                                // -L: Error log directory
                  {
                      curJob.setErrorDir( optarg );
                      break;
                  }
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dleeyh Daniel Lee
              Reporter:
              Richard Richard Stracke
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.