You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/main/java/org/typesense/model/CollectionSchema.java
+26-1Lines changed: 26 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ public class CollectionSchema {
24
24
**/
25
25
privateStringname = null;
26
26
27
-
@Schema(example = "[{\"name\":\"company_name\",\"type\":\"string\",\"facet\":false},{\"name\":\"num_employees\",\"type\":\"int32\",\"facet\":false},{\"name\":\"country\",\"type\":\"string\",\"facet\":true}]", required = true, description = "A list of fields for querying, filtering and faceting")
27
+
@Schema(example = "[{\"name\":\"num_employees\",\"type\":\"int32\",\"facet\":false},{\"name\":\"company_name\",\"type\":\"string\",\"facet\":false},{\"name\":\"country\",\"type\":\"string\",\"facet\":true}]", required = true, description = "A list of fields for querying, filtering and faceting")
28
28
/**
29
29
* A list of fields for querying, filtering and faceting
30
30
**/
@@ -42,6 +42,12 @@ public class CollectionSchema {
42
42
**/
43
43
privateList<String> tokenSeparators = null;
44
44
45
+
@Schema(example = "true", description = "Enables experimental support at a collection level for nested object or object array fields. This field is only available if the Typesense server is version `0.24.0.rcn34` or later.")
46
+
/**
47
+
* Enables experimental support at a collection level for nested object or object array fields. This field is only available if the Typesense server is version `0.24.0.rcn34` or later.
48
+
**/
49
+
privateBooleanenableNestedFields = false;
50
+
45
51
@Schema(description = "List of symbols or special characters to be indexed. ")
46
52
/**
47
53
* List of symbols or special characters to be indexed.
@@ -129,6 +135,24 @@ public CollectionSchema addTokenSeparatorsItem(String tokenSeparatorsItem) {
129
135
returnthis;
130
136
}
131
137
138
+
/**
139
+
* Enables experimental support at a collection level for nested object or object array fields. This field is only available if the Typesense server is version `0.24.0.rcn34` or later.
Copy file name to clipboardExpand all lines: src/main/java/org/typesense/model/MultiSearchParameters.java
+75Lines changed: 75 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,24 @@ public class MultiSearchParameters {
44
44
**/
45
45
privateStringprefix = null;
46
46
47
+
@Schema(description = "If infix index is enabled for this field, infix searching can be done on a per-field basis by sending a comma separated string parameter called infix to the search query. This parameter can have 3 values; `off` infix search is disabled, which is default `always` infix search is performed along with regular search `fallback` infix search is performed if regular search does not produce results")
48
+
/**
49
+
* If infix index is enabled for this field, infix searching can be done on a per-field basis by sending a comma separated string parameter called infix to the search query. This parameter can have 3 values; `off` infix search is disabled, which is default `always` infix search is performed along with regular search `fallback` infix search is performed if regular search does not produce results
50
+
**/
51
+
privateStringinfix = null;
52
+
53
+
@Schema(description = "There are also 2 parameters that allow you to control the extent of infix searching max_extra_prefix and max_extra_suffix which specify the maximum number of symbols before or after the query that can be present in the token. For example query \"K2100\" has 2 extra symbols in \"6PK2100\". By default, any number of prefixes/suffixes can be present for a match.")
54
+
/**
55
+
* There are also 2 parameters that allow you to control the extent of infix searching max_extra_prefix and max_extra_suffix which specify the maximum number of symbols before or after the query that can be present in the token. For example query \"K2100\" has 2 extra symbols in \"6PK2100\". By default, any number of prefixes/suffixes can be present for a match.
56
+
**/
57
+
privateIntegermaxExtraPrefix = null;
58
+
59
+
@Schema(description = "There are also 2 parameters that allow you to control the extent of infix searching max_extra_prefix and max_extra_suffix which specify the maximum number of symbols before or after the query that can be present in the token. For example query \"K2100\" has 2 extra symbols in \"6PK2100\". By default, any number of prefixes/suffixes can be present for a match.")
60
+
/**
61
+
* There are also 2 parameters that allow you to control the extent of infix searching max_extra_prefix and max_extra_suffix which specify the maximum number of symbols before or after the query that can be present in the token. For example query \"K2100\" has 2 extra symbols in \"6PK2100\". By default, any number of prefixes/suffixes can be present for a match.
62
+
**/
63
+
privateIntegermaxExtraSuffix = null;
64
+
47
65
@Schema(example = "num_employees:>100 && country: [USA, UK]", description = "Filter conditions for refining youropen api validator search results. Separate multiple conditions with &&.")
48
66
/**
49
67
* Filter conditions for refining youropen api validator search results. Separate multiple conditions with &&.
@@ -301,6 +319,60 @@ public MultiSearchParameters prefix(String prefix) {
301
319
returnthis;
302
320
}
303
321
322
+
/**
323
+
* If infix index is enabled for this field, infix searching can be done on a per-field basis by sending a comma separated string parameter called infix to the search query. This parameter can have 3 values; `off` infix search is disabled, which is default `always` infix search is performed along with regular search `fallback` infix search is performed if regular search does not produce results
324
+
* @return infix
325
+
**/
326
+
@JsonProperty("infix")
327
+
publicStringgetInfix() {
328
+
returninfix;
329
+
}
330
+
331
+
publicvoidsetInfix(Stringinfix) {
332
+
this.infix = infix;
333
+
}
334
+
335
+
publicMultiSearchParametersinfix(Stringinfix) {
336
+
this.infix = infix;
337
+
returnthis;
338
+
}
339
+
340
+
/**
341
+
* There are also 2 parameters that allow you to control the extent of infix searching max_extra_prefix and max_extra_suffix which specify the maximum number of symbols before or after the query that can be present in the token. For example query \"K2100\" has 2 extra symbols in \"6PK2100\". By default, any number of prefixes/suffixes can be present for a match.
* There are also 2 parameters that allow you to control the extent of infix searching max_extra_prefix and max_extra_suffix which specify the maximum number of symbols before or after the query that can be present in the token. For example query \"K2100\" has 2 extra symbols in \"6PK2100\". By default, any number of prefixes/suffixes can be present for a match.
0 commit comments