Skip to content

[typo](docs) As per doris#37949, starting with versions 2.0.14, 2.1.5 and 3.0.1, support_phrase defaults to true if parser is specified, false otherwise. #1939

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
KassieZ merged 1 commit into from
Apr 23, 2025
Merged

[typo](docs) As per doris#37949, starting with versions 2.0.14, 2.1.5 and 3.0.1, support_phrase defaults to true if parser is specified, false otherwise. #1939

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/table-design/index/inverted-index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ Syntax explanation:
**Specifies whether the index supports MATCH_PHRASE phrase query acceleration**
<p>- true: supported, but the index requires more storage space</p>
<p>- false: not supported, more storage efficient, can use MATCH_ALL to query multiple keywords</p>
<p>- default false</p>
<p>- From versions 2.0.14, 2.1.5 and 3.0.1, the default is true if parser is set. Otherwise default to false.</p>

For example, the following example specifies Chinese tokenization, coarse-grained mode, and supports phrase query acceleration.
```sql
Expand Down
2 changes: 1 addition & 1 deletion ...-CN/docusaurus-plugin-content-docs/current/table-design/index/inverted-index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,7 @@ table_properties;
**用于指定索引是否支持 MATCH_PHRASE 短语查询加速**
<p>- true 为支持，但是索引需要更多的存储空间</p>
<p>- false 为不支持，更省存储空间，可以用 MATCH_ALL 查询多个关键字</p>
<p>- 默认 false</p>
<p>- 从 2.0.14, 2.1.5 和 3.0.1 版本开始，如果指定了 parser 则默认为 true，否则默认为 false</p>

例如下面的例子指定中文分词，粗粒度模式，支持短语查询加速。
```sql
Expand Down
2 changes: 1 addition & 1 deletion ...docusaurus-plugin-content-docs/version-2.0/table-design/index/inverted-index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,7 @@ table_properties;
**用于指定索引是否支持 MATCH_PHRASE 短语查询加速**
<p>- true 为支持，但是索引需要更多的存储空间</p>
<p>- false 为不支持，更省存储空间，可以用 MATCH_ALL 查询多个关键字</p>
<p>- 默认 false</p>
<p>- 从 2.0.14, 2.1.5 和 3.0.1 版本开始，如果指定了 parser 则默认为 true，否则默认为 false</p>

例如下面的例子指定中文分词，粗粒度模式，支持短语查询加速。
```sql
Expand Down
2 changes: 1 addition & 1 deletion ...docusaurus-plugin-content-docs/version-2.1/table-design/index/inverted-index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,7 @@ table_properties;
**用于指定索引是否支持 MATCH_PHRASE 短语查询加速**
<p>- true 为支持，但是索引需要更多的存储空间</p>
<p>- false 为不支持，更省存储空间，可以用 MATCH_ALL 查询多个关键字</p>
<p>- 默认 false</p>
<p>- 从 2.0.14, 2.1.5 和 3.0.1 版本开始，如果指定了 parser 则默认为 true，否则默认为 false</p>

例如下面的例子指定中文分词，粗粒度模式，支持短语查询加速。
```sql
Expand Down
2 changes: 1 addition & 1 deletion ...docusaurus-plugin-content-docs/version-3.0/table-design/index/inverted-index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,7 @@ table_properties;
**用于指定索引是否支持 MATCH_PHRASE 短语查询加速**
<p>- true 为支持，但是索引需要更多的存储空间</p>
<p>- false 为不支持，更省存储空间，可以用 MATCH_ALL 查询多个关键字</p>
<p>- 默认 false</p>
<p>- 从 2.0.14, 2.1.5 和 3.0.1 版本开始，如果指定了 parser 则默认为 true，否则默认为 false</p>

例如下面的例子指定中文分词，粗粒度模式，支持短语查询加速。
```sql
Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-2.0/table-design/index/inverted-index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ Syntax explanation:
**Specifies whether the index supports MATCH_PHRASE phrase query acceleration**
<p>- true: supported, but the index requires more storage space</p>
<p>- false: not supported, more storage efficient, can use MATCH_ALL to query multiple keywords</p>
<p>- default false</p>
<p>- From versions 2.0.14, 2.1.5 and 3.0.1, the default is true if parser is set. Otherwise default to false.</p>

For example, the following example specifies Chinese tokenization, coarse-grained mode, and supports phrase query acceleration.
```sql
Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-2.1/table-design/index/inverted-index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,7 @@ Syntax explanation:
**Specifies whether the index supports MATCH_PHRASE phrase query acceleration**
<p>- true: supported, but the index requires more storage space</p>
<p>- false: not supported, more storage efficient, can use MATCH_ALL to query multiple keywords</p>
<p>- default false</p>
<p>- From versions 2.0.14, 2.1.5 and 3.0.1, the default is true if parser is set. Otherwise default to false.</p>

For example, the following example specifies Chinese tokenization, coarse-grained mode, and supports phrase query acceleration.
```sql
Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-3.0/table-design/index/inverted-index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ Syntax explanation:
**Specifies whether the index supports MATCH_PHRASE phrase query acceleration**
<p>- true: supported, but the index requires more storage space</p>
<p>- false: not supported, more storage efficient, can use MATCH_ALL to query multiple keywords</p>
<p>- default false</p>
<p>- From versions 2.0.14, 2.1.5 and 3.0.1, the default is true if parser is set. Otherwise default to false.</p>

For example, the following example specifies Chinese tokenization, coarse-grained mode, and supports phrase query acceleration.
```sql
Expand Down
Loading