optimize_index.json

optimize_index is the parameter file that defines the optimization methods that can be used during the Smart Tables process or manual optimizations launched from the table.

It refers to parameters defined in the Analyzer (Advanced mode).

Parameters

Parameter	Type	Choices/Default	Description
Name	String		Name of the optimization process.
coef	Double		Coefficient for splitting indexes. The more is value is high, the more indexes you will have. (decimal separator: point)
nbDays	Int		Number of days to get queries to analyze on.
minHits	Int		Minimum number of times a field appears in queries, so we should propose it.
spec	String	NOT_SPECIALIZED HALF_SPECIALIZED FULLY_SPECIALIZED	NOT_SPECIALIZED : Expressions are proposed for high cardinality field. HALF_SPECIALIZED : Expressions in SELECT clause and WHERE clause, for high cardinality field, are proposed. FULLY_SPECIALIZED : Expressions are always proposed.
index-hint	String	TUNING FULL	TUNING : Limit indexes changes by maximizing current indexes use. This option let you have fewer, more compact indexes, even if some queries will have to use the K-Store. FULL : All suggestions are given, leading to having at least one index for each query. Can be memory expensive but ensure performance.
automatic	String	CREATE_ONLY CREATE_DELETE	CREATE_ONLY : Create all indexes proposals, but don't remove any. CREATE_DELETE : Create and delete all indexes proposals.
prejoin	Boolean	True False	If true, pre-join indexes are proposed by the analyzer.

Example

Optimize_index

JAVA

{
"optimizations": [
	{
		"name": "Last month tuning",
		"coef": 4.0,
		"nbDays": 30,
		"minHits": 1,
		"spec":"NOT_SPECIALIZED",
		"index-hint":"TUNING",
		"automatic": "CREATE_DELETE",
		"prejoin" : true
	},
	{
		"name": "Last day tuning",
		"coef": 4.0,
		"nbDays": 1,
		"minHits": 1,
		"spec":"NOT_SPECIALIZED",
		"index-hint":"TUNING",
		"automatic": "CREATE_DELETE",
		"prejoin" : true
	},
]
}