Fix line break

This commit is contained in:
Robert Schulze 2023-06-14 07:50:26 +00:00
parent b1f0a91b78
commit f4cfb9e370
No known key found for this signature in database
GPG Key ID: 26703B55FB13728A

View File

@ -131,7 +131,6 @@ The `GRANULARITY` parameter determines how many ANN sub-indexes are created. Big
sub-indexes, up to the point where a column (or a column's data part) has only a single sub-index. In that case, the sub-index has a sub-indexes, up to the point where a column (or a column's data part) has only a single sub-index. In that case, the sub-index has a
"global" view of all column rows and can directly return all granules of the column (part) with relevant rows (there are at most "global" view of all column rows and can directly return all granules of the column (part) with relevant rows (there are at most
`LIMIT [N]`-many such granules). In a second step, ClickHouse will load these granules and identify the actually best rows by performing a `LIMIT [N]`-many such granules). In a second step, ClickHouse will load these granules and identify the actually best rows by performing a
brute-force distance calculation over all rows of the granules. With a small `GRANULARITY` value, each of the sub-indexes returns up to brute-force distance calculation over all rows of the granules. With a small `GRANULARITY` value, each of the sub-indexes returns up to
`LIMIT N`-many granules. As a result, more granules need to be loaded and post-filtered. Note that the search accuracy is with both cases `LIMIT N`-many granules. As a result, more granules need to be loaded and post-filtered. Note that the search accuracy is with both cases
equally good, only the processing performance differs. It is generally recommended to use a large `GRANULARITY` for ANN indexes and fall equally good, only the processing performance differs. It is generally recommended to use a large `GRANULARITY` for ANN indexes and fall