[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-05-02 Thread Stefan Miklosovic (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-19401:
--
  Fix Version/s: 4.0.13
 4.1.5
 5.0-beta2
 5.1-alpha1
 (was: 5.x)
 (was: 4.0.x)
 (was: 4.1.x)
 (was: 5.0.x)
  Since Version: 4.0.0
Source Control Link: 
https://github.com/apache/cassandra/commit/334ca05730d8088f27323166e3ee1505db5cb202
 Resolution: Fixed
 Status: Resolved  (was: Ready to Commit)

> Nodetool import expects directory structure
> ---
>
> Key: CASSANDRA-19401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19401
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/SSTable
>Reporter: Norbert Schultz
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.0.13, 4.1.5, 5.0-beta2, 5.1-alpha1
>
>  Time Spent: 1h 50m
>  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

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-05-01 Thread Stefan Miklosovic (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-19401:
--
Status: Ready to Commit  (was: Review In Progress)

> Nodetool import expects directory structure
> ---
>
> Key: CASSANDRA-19401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19401
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/SSTable
>Reporter: Norbert Schultz
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>  Time Spent: 1h 50m
>  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

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-05-01 Thread Stefan Miklosovic (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-19401:
--
Change Category: Operability
 Status: Review In Progress  (was: Needs Committer)

> Nodetool import expects directory structure
> ---
>
> Key: CASSANDRA-19401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19401
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/SSTable
>Reporter: Norbert Schultz
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>  Time Spent: 1h 50m
>  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

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-04-24 Thread Stefan Miklosovic (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-19401:
--
Status: Needs Committer  (was: Patch Available)

> Nodetool import expects directory structure
> ---
>
> Key: CASSANDRA-19401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19401
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/SSTable
>Reporter: Norbert Schultz
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>  Time Spent: 1h 50m
>  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

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-04-24 Thread Stefan Miklosovic (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-19401:
--
Status: Patch Available  (was: In Progress)

> Nodetool import expects directory structure
> ---
>
> Key: CASSANDRA-19401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19401
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/SSTable
>Reporter: Norbert Schultz
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>  Time Spent: 1h 50m
>  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

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-04-24 Thread Stefan Miklosovic (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-19401:
--
Status: In Progress  (was: Changes Suggested)

> Nodetool import expects directory structure
> ---
>
> Key: CASSANDRA-19401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19401
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/SSTable
>Reporter: Norbert Schultz
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>  Time Spent: 1h 50m
>  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

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-04-18 Thread Stefan Miklosovic (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-19401:
--
Status: Ready to Commit  (was: Changes Suggested)

> Nodetool import expects directory structure
> ---
>
> Key: CASSANDRA-19401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19401
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/SSTable
>Reporter: Norbert Schultz
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>  Time Spent: 1h 20m
>  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

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-04-18 Thread Stefan Miklosovic (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-19401:
--
Status: Changes Suggested  (was: Ready to Commit)

> Nodetool import expects directory structure
> ---
>
> Key: CASSANDRA-19401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19401
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/SSTable
>Reporter: Norbert Schultz
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>  Time Spent: 1h 20m
>  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

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-04-18 Thread Brandon Williams (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-19401:
-
Status: Changes Suggested  (was: Review In Progress)

> Nodetool import expects directory structure
> ---
>
> Key: CASSANDRA-19401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19401
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/SSTable
>Reporter: Norbert Schultz
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>  Time Spent: 1h 20m
>  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

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-04-18 Thread Brandon Williams (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-19401:
-
Status: Review In Progress  (was: Needs Committer)

> Nodetool import expects directory structure
> ---
>
> Key: CASSANDRA-19401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19401
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/SSTable
>Reporter: Norbert Schultz
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>  Time Spent: 1h 20m
>  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

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-04-18 Thread Stefan Miklosovic (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-19401:
--
Status: Needs Committer  (was: Patch Available)

> Nodetool import expects directory structure
> ---
>
> Key: CASSANDRA-19401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19401
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/SSTable
>Reporter: Norbert Schultz
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>  Time Spent: 1h 20m
>  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

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-04-17 Thread Stefan Miklosovic (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-19401:
--
Fix Version/s: 4.0.x

> Nodetool import expects directory structure
> ---
>
> Key: CASSANDRA-19401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19401
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/SSTable
>Reporter: Norbert Schultz
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>  Time Spent: 1h 20m
>  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

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-04-17 Thread Brandon Williams (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-19401:
-
Reviewers: Brandon Williams

> Nodetool import expects directory structure
> ---
>
> Key: CASSANDRA-19401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19401
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/SSTable
>Reporter: Norbert Schultz
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.1.x, 5.0.x, 5.x
>
>  Time Spent: 1h 10m
>  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

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-04-17 Thread Stefan Miklosovic (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-19401:
--
Authors: Stefan Miklosovic
Test and Documentation Plan: CI
 Status: Patch Available  (was: In Progress)

> Nodetool import expects directory structure
> ---
>
> Key: CASSANDRA-19401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19401
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/SSTable
>Reporter: Norbert Schultz
>Priority: Normal
> Fix For: 4.1.x, 5.0.x, 5.x
>
>  Time Spent: 50m
>  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

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-02-15 Thread Brandon Williams (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-19401:
-
 Bug Category: Parent values: Correctness(12982)Level 1 values: Recoverable 
Corruption / Loss(12986)
   Complexity: Normal
  Component/s: Local/SSTable
Discovered By: User Report
Fix Version/s: 4.1.x
   5.0.x
   5.x
 Severity: Normal
   Status: Open  (was: Triage Needed)

> Nodetool import expects directory structure
> ---
>
> Key: CASSANDRA-19401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19401
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/SSTable
>Reporter: Norbert Schultz
>Priority: Normal
> Fix For: 4.1.x, 5.0.x, 5.x
>
>  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

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-02-15 Thread Norbert Schultz (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Norbert Schultz updated CASSANDRA-19401:

Description: 
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)

  was:
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}


> 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:

[jira] [Updated] (CASSANDRA-19401) Nodetool import expects directory structure

2024-02-15 Thread Norbert Schultz (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-19401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Norbert Schultz updated CASSANDRA-19401:

Summary: Nodetool import expects directory structure  (was: nodetool import 
expects directory)

> 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
>
> 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}



--
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