Skip to content

Commit c5cbff6

Browse files
updates formatting on word
1 parent cf1c18f commit c5cbff6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

supporting-blog-content/lexical-and-semantic-search-with-elasticsearch/ecommerce_dense_sparse_project.ipynb

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1238,9 +1238,9 @@
12381238
"\n",
12391239
"It should be noted that while the semantic search query provides more relevant results, it is also more computationally expensive than the lexical search query. This is because the semantic search query requires the calculation of vector representations, which can be computationally intensive. \n",
12401240
"\n",
1241-
"Ultimately, it is recommended to use the semantic_text type when implementing semantic search for a few key reasons:\n",
1241+
"Ultimately, it is recommended to use the `semantic_text` type when implementing semantic search for a few key reasons:\n",
12421242
"- Query structure is simple and easy to understand.\n",
1243-
"- Implementing the semantic_text type requires minimal changes to the index mapping and query.\n",
1243+
"- Implementing the `semantic_text` type requires minimal changes to the index mapping and query.\n",
12441244
"- Setting up an ingest pipeline and inference endpoint is unnecessary.\n",
12451245
"\n",
12461246
"Using `spare_vector` and `dense_vector` types are more complex and requires additional setup, but can be useful in certain scenarios where semantic search needs to be customized beyond standard semantic text search. This could be a change in the similarity algorithm, use of different vectorization models, or any necessary preprocessing steps. \n",

0 commit comments

Comments
 (0)