nodetool import

Imports SSTables from a directory or list of directories.

Synopsis

nodetool [<connection_options>] import
[--] [-c] [-e] [-l] [-q] [-r] [-t] [-v] [-x]
<keyspace_name> <table_name> <directory> [<directory2> <directoryN>...]

Syntax legend

Syntax conventions Description

Syntax conventions	Description
Italic, bold, or `< >`	Syntax diagrams and code samples use one or more of these styles to mark placeholders for variable values. Replace placeholders with a valid option or your own user-defined value. In CQL statements, angle brackets are required to enclose data types in a set, list, map, or tuple. Separate the data types with a comma. For example: `<datatype2` In Search CQL statements, angle brackets are used to identify the entity and literal value to overwrite the XML element in the schema and `solrconfig` files, such as `@<xml_entity>='<xml_entity_type>'`.
`[ ]`	Square brackets surround optional command arguments. Do not type the square brackets.
`( )`	Parentheses identify a group to choose from. Do not type the parentheses.
`\|`	A pipe separates alternative elements. Type any one of the elements. Do not type the pipe.
`...`	Indicates that you can repeat the syntax element as often as required.
`'`	Single quotation marks must surround literal strings in CQL statements. Use single quotation marks to preserve upper case. + For Search CQL only: Single quotation marks surround an entire XML schema declaration, such as `'<<schema> ... </schema>>'`
`{ }`	Map collection. Curly braces enclose maps (`{ <key_datatype>:<value_datatype> }`) or key value pairs (`{ <key>:<value> }`). A colon separates the key and the value.
`;`	Ends a CQL statement.
`--`	Separate command line options from command arguments with two hyphens. This syntax is useful when arguments might be mistaken for command line options.

Italic, bold, or < >

Syntax diagrams and code samples use one or more of these styles to mark placeholders for variable values. Replace placeholders with a valid option or your own user-defined value.

In CQL statements, angle brackets are required to enclose data types in a set, list, map, or tuple. Separate the data types with a comma. For example: <datatype2

In Search CQL statements, angle brackets are used to identify the entity and literal value to overwrite the XML element in the schema and solrconfig files, such as @<xml_entity>='<xml_entity_type>'.

[ ]

Square brackets surround optional command arguments. Do not type the square brackets.

( )

Parentheses identify a group to choose from. Do not type the parentheses.

|

A pipe separates alternative elements. Type any one of the elements. Do not type the pipe.

...

Indicates that you can repeat the syntax element as often as required.

'

Single quotation marks must surround literal strings in CQL statements. Use single quotation marks to preserve upper case. + For Search CQL only: Single quotation marks surround an entire XML schema declaration, such as '<<schema> ... </schema>>'

{ }

Map collection. Curly braces enclose maps ({ <key_datatype>:<value_datatype> }) or key value pairs ({ <key>:<value> }). A colon separates the key and the value.

;

Ends a CQL statement.

--

Separate command line options from command arguments with two hyphens. This syntax is useful when arguments might be mistaken for command line options.

Options

If an option has a short and long form, both forms are given, separated by a comma.

-h, --host hostname: The hostname or IP address of a remote node or nodes. When omitted, the default is the local machine.
-p, --port jmx_port: The JMX port number.
-pw, --password jmxpassword: The JMX password for authenticating with secure JMX. If a password is not provided, you are prompted to enter one.
-pwf, --password-file jmx_password_filepath: The filepath to the file that stores JMX authentication credentials.
-u, --username jmx_username: The username for authenticating with secure JMX.
--: Separates an option from an argument that could be mistaken for a option.
-c, --no-invalidate-caches: Doesn’t invalidate the row cache when importing the SSTables.
-e, --extended-verify: Runs an extended verify, verifying all values in the new SSTables.
-l, --keep-level: Maintains the existing level on the new SSTables.
-q, --quick: Does a quick import without verifying SSTables, clearing row cache, or checking the data directory.
-r, --keep-repaired: Retains any repaired information from the SSTables.
-t, --no-tokens: Doesn’t verify that all tokens in the new SSTable are owned by the current node.
-v, --no-verify: Doesn’t verify new SSTables.
-x, --fix-serialization-header: Fixes the SSTable serialization-header, if necessary. Serialization-headers are always verified.
keyspace_name: The keyspace name.
table_name: One or more table names, separated by a space.
directory: Directory or directories from which to import the SSTables. Separate multiple directories with spaces.

Examples

Import SSTables from two directories:

nodetool import cycling cyclist_name /var/lib/cassandra/data/cycling/dir1 /var/lib/cassandra/data/cycling/dir2

nodetool import

Synopsis

Options

Examples

Import SSTables from two directories:

Was this helpful?

Give Feedback