dsetool reload_core

Reloads the search index to recognize changes to schema or configuration. The dsetool unload_core command runs on all nodes in the cluster and supports DSE authentication with -l USERNAME -p PASSWORD.

To reload the core and prevent reindexing, accept the default values reindex=false and deleteAll=false.

Synopsis

dsetool reload_core <keyspace_name>.<table_name>
[coreOptions=<yamlFile> | coreOptionsInline=<key1:value1#key2:value2#...>]
[deleteAll=(true|false)]
[distributed=(true|false)]
[reindex=(true|false)]
[schema=<path>]
[solrconfig=<path>]

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.

schema=<path>

Path of the UTF-8 encoded search index schema file. Cannot be specified when generateResources=true.

To ensure that non-indexed fields in the table are retrievable by queries, you must include those fields in the schema file. For more information, see Solr single-pass CQL queries.

solrconfig=PATH

Provide the path to the UTF-8 encoded search index configuration file. Cannot be specified when generateResources=true.

distributed=(true|false)

Whether to distribute and apply the operation to all nodes in the local datacenter.

True applies the operation to all nodes in the local datacenter. Distributing a re-index to an entire datacenter degrades performance severely in that datacenter.
False applies the operation only to the node it was sent to.

reindex=(true|false)

Whether to reindex the data when search indexes are auto-generated with generateResources=true. Reindexing works on a datacenter (DC) level. Reindex only once per search-enabled DC. Repeat the reindex command on other data centers as required.

true (default) - Reindexes the data. Accepts reads and keeps the current search index while the new index is building.
false - Does not reindex the data. You can check and customize search index resources before indexing.

deleteAll=( true|false )

true - deletes the already existing index before reindexing; search results will return either no or partial data while the index is rebuilding.
false - does not delete the existing index, causing the reindex to happen in-place; search results will return partially incorrect results while the index is updating. Default.

During reindexing, a series of criteria routes sub-queries to the nodes most capable of handling them. See Shard routing for distributed queries.

Examples

To make the pending search index active:

dsetool reload_core demo.health_data coreOptionsInline="directory_factory_class:solr.EncryptedFSDirectoryFactory"

To upload the changed resource file:

dsetool reload_core demo.health_data coreOptionsInline="directory_factory_class:solr.EncryptedFSDirectoryFactory"

dsetool reload_core

Synopsis

Examples

Was this helpful?

Give Feedback