Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-12174

COPY FROM should raise error for non-existing input files

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Low
    • Resolution: Fixed
    • Fix Version/s: 3.10
    • Component/s: Legacy/Tools
    • Labels:

      Description

      Currently the CSV COPY FROM command will not raise any error for non-existing paths. Instead only "0 rows imported" will be shown as result.

      As the COPY FROM command is often used for tutorials and getting started guides, I'd suggest to give a clear error message in case of a missing input file. Without such error it can be confusing for the user to see the command actually finish, without any clues why no rows have been imported.

      CREATE KEYSPACE test
        WITH REPLICATION = { 'class' : 'NetworkTopologyStrategy', 'datacenter1' : 1 };
      
      USE test;
      
      CREATE TABLE airplanes (
        name text PRIMARY KEY,
        manufacturer ascii,
        year int,
        mach float
      );
      
      COPY airplanes (name, manufacturer, year, mach) FROM '/tmp/1234-doesnotexist';
      Using 3 child processes
      
      Starting copy of test.airplanes with columns [name, manufacturer, year, mach].
      Processed: 0 rows; Rate:       0 rows/s; Avg. rate:       0 rows/s
      0 rows imported from 0 files in 0.216 seconds (0 skipped).
      

        Attachments

          Activity

            People

            • Assignee:
              hnishi Hiroyuki Nishi Assign to me
              Reporter:
              spod Stefan Podkowinski
              Authors:
              Hiroyuki Nishi
              Reviewers:
              Stefania Alborghetti

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment