[ https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817632#comment-17817632 ]
Stefan Miklosovic commented on CASSANDRA-19401: ----------------------------------------------- [~nob13] this fixes your issue https://github.com/apache/cassandra/pull/3106 I have not provided any format builds and it might error something else but with this patch, it just "nodetool import ks tb /tmp/mysstables" fine into ks tb > Nodetool import expects directory structure > ------------------------------------------- > > Key: CASSANDRA-19401 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19401 > Project: Cassandra > Issue Type: Bug > Reporter: Norbert Schultz > Priority: Normal > Time Spent: 0.5h > Remaining Estimate: 0h > > According to the > [documentation|https://cassandra.apache.org/doc/4.1/cassandra/operating/bulk_loading.html] > the nodetool import should not rely on the folder structure of the imported > sst files: > {quote} > Because the keyspace and table are specified on the command line for nodetool > import, there is not the same requirement as with sstableloader, to have the > SSTables in a specific directory path. When importing snapshots or > incremental backups with nodetool import, the SSTables don’t need to be > copied to another directory. > {quote} > However when importing old cassandra snapshots, we figured out, that sstables > still need to be in a directory called like $KEYSPACE/$TABLENAME files, even > when keyspace and table name are already present as parameters for the > nodetool import call. > Call we used: > {code} > nodetool import --copy-data mykeyspace mytable /full_path_to/test1 > {code} > Log: > {code} > INFO [RMI TCP Connection(21)-127.0.0.1] 2024-02-15 10:41:06,565 > SSTableImporter.java:72 - Loading new SSTables for mykeyspace/mytable: > Options{srcPaths='[/full_path_to/test1]', resetLevel=true, > clearRepaired=true, verifySSTables=true, verifyTokens=true, > invalidateCaches=true, extendedVerify=false, copyData= true} > INFO [RMI TCP Connection(21)-127.0.0.1] 2024-02-15 10:41:06,566 > SSTableImporter.java:173 - No new SSTables were found for mykeyspace/mytable > {code} > However, when we move the sstables (.db-Files) to > {{alternative/mykeyspace/mytable}} > and import with > {code} > nodetool import --copy-data mykeyspace mytable > /fullpath/alternative/mykeyspace/mytable > {code} > the import works > {code} > INFO [RMI TCP Connection(23)-127.0.0.1] 2024-02-15 10:43:36,093 > SSTableImporter.java:177 - Loading new SSTables and building secondary > indexes for mykeyspace/mytable: > [BigTableReader(path='/mnt/ramdisk/cassandra4/data/mykeyspace/mytable-561a12d0cbe611eead78fbfd293cee40/me-2-big-Data.db'), > > BigTableReader(path='/mnt/ramdisk/cassandra4/data/mykeyspace/mytable-561a12d0cbe611eead78fbfd293cee40/me-1-big-Data.db')] > INFO [RMI TCP Connection(23)-127.0.0.1] 2024-02-15 10:43:36,093 > SSTableImporter.java:190 - Done loading load new SSTables for > mykeyspace/mytable > {code} > We experienced this in Cassandra 4.1.3 on Java 11 (Linux) -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org