dsetool set_core_property
Sets the properties and values in the dse-search.properties resource for the search index.
Sets the properties and values in the dse-search.properties resource for the search index.
Tip: See
.
Synopsis
dsetool set_core_property keyspace_name.table_name shard.set.cover.finder=DYNAMIC|STATIC | shard.shuffling.strategy=HOST|QUERY|HOST_QUERY|RANDOM|SEED | shard.set.cover.finder.inertia=inertia_integer
Syntax conventions | Description |
---|---|
UPPERCASE | Literal keyword. |
Lowercase | Not literal. |
Italics |
Variable value. Replace with a valid option or user-defined value. |
[ ] |
Optional. Square brackets ( [ ] ) surround optional command
arguments. Do not type the square brackets. |
( ) |
Group. Parentheses ( ( ) ) identify a group to choose from. Do
not type the parentheses. |
| |
Or. A vertical bar ( | ) separates alternative elements. Type
any one of the elements. Do not type the vertical bar. |
... |
Repeatable. An ellipsis ( ... ) indicates that you can repeat
the syntax element as often as required. |
'Literal string' |
Single quotation ( ' ) marks must surround literal strings in
CQL statements. Use single quotation marks to preserve upper case. |
{ key:value } |
Map collection. Braces ( { } ) enclose map collections or key
value pairs. A colon separates the key and the value. |
<datatype1,datatype2> |
Set, list, map, or tuple. Angle brackets ( < > ) enclose
data types in a set, list, map, or tuple. Separate the data types with a comma.
|
cql_statement; |
End CQL statement. A semicolon ( ; ) terminates all CQL
statements. |
[ -- ] |
Separate the command line options from the command arguments with two hyphens (
-- ). This syntax is useful when arguments might be mistaken for
command line options. |
' <schema> ... </schema>
' |
Search CQL only: Single quotation marks ( ' ) surround an entire
XML schema declaration. |
@xml_entity='xml_entity_type' |
Search CQL only: Identify the entity and literal value to overwrite the XML element in the schema and solrconfig files. |
- keyspace_name.table_name
- Required. The keyspace and table names of the search index. Keyspace and table names are case-sensitive. Enclose names that contain uppercase in double quotation marks.
- DYNAMIC
- Use randomization in token range and endpoint selection for load balancing. DYNAMIC is the default.
- STATIC
- Requires load balanced client. Suitable for 8+ vnodes. The same query on a node uses the same token ranges and endpoints. Creates fewer token filters, and has better performance than DYNAMIC.
- HOST
- Shards are selected based on the host that received the query.
- QUERY
- Shards are selected based on the query string.
- HOST_QUERY
- Shards are selected by host x query.
- RANDOM
- Suitable only for 8 or fewer vnodes. Different random set of shards are selected with each request (default).
- SEED
- Selects the same shard from one query to another.
- inertia_integer
-
Increasing the inertia value from the default of 1 may improve performance for clusters with more than 1 vnode and more than 20 nodes. The default is appropriate for most workloads.
Examples
To not use randomization to select token ranges and endpoints:
dsetool set_core_property demo.health_data shard.set.cover.finder=STATIC
dsetool reload_core demo.health_data reindex=false
To use default randomization to select token ranges and endpoints:
dsetool set_core_property demo.health_data shard.set.cover.finder=DYNAMIC
dsetool reload_core demo.health_data reindex=false
Tip: As
shown in the examples, after setting the core property value, be sure to reload the search
index. While you can use
set_core_property
per cluster, reloading the
search index must occur per Data Center. In cqlsh
, you can use
RELOAD SEARCH INDEX
. Example:
RELOAD SEARCH INDEX ON demo.health_data;You do not need to reindex the specified table unless schema changes were made. Refer to .