From 52cacdb89bb29f355e0c3a33c3250ac2d3fea036 Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Tue, 14 Apr 2020 03:09:39 +0000 Subject: Add latest changes from gitlab-org/gitlab@master --- .../documentation/site_architecture/index.md | 44 +++++++++++----------- doc/development/elasticsearch.md | 5 ++- 2 files changed, 25 insertions(+), 24 deletions(-) (limited to 'doc/development') diff --git a/doc/development/documentation/site_architecture/index.md b/doc/development/documentation/site_architecture/index.md index bd870399978..56dd3821b1c 100644 --- a/doc/development/documentation/site_architecture/index.md +++ b/doc/development/documentation/site_architecture/index.md @@ -20,29 +20,27 @@ from where content is sourced, the `gitlab-docs` project, and the published outp ```mermaid graph LR - A[gitlab-foss/doc] - B[gitlab/doc] - C[gitlab-runner/docs] - D[omnibus-gitlab/doc] - E[charts/doc] - F[gitlab-docs] - A --> F - B --> F - C --> F - D --> F - E --> F - F -- Build pipeline --> G - G[docs.gitlab.com] - H[/ce/] - I[/ee/] - J[/runner/] - K[/omnibus/] - L[/charts/] - G --> H - G --> I - G --> J - G --> K - G --> L + A[gitlab/doc] + B[gitlab-runner/docs] + C[omnibus-gitlab/doc] + D[charts/doc] + E[gitlab-docs] + A --> E + B --> E + C --> E + D --> E + E -- Build pipeline --> F + F[docs.gitlab.com] + G[/ce/] + H[/ee/] + I[/runner/] + J[/omnibus/] + K[/charts/] + F --> H + F --> I + F --> J + F --> K + H -- symlink --> G ``` You will not find any GitLab docs content in the `gitlab-docs` repository. diff --git a/doc/development/elasticsearch.md b/doc/development/elasticsearch.md index feff0ba7c8a..b6f863b8bea 100644 --- a/doc/development/elasticsearch.md +++ b/doc/development/elasticsearch.md @@ -60,12 +60,15 @@ Please see the `sha_tokenizer` explanation later below for an example. #### `code_analyzer` -Used when indexing a blob's filename and content. Uses the `whitespace` tokenizer and the filters: `code`, `edgeNGram_filter`, `lowercase`, and `asciifolding` +Used when indexing a blob's filename and content. Uses the `whitespace` tokenizer and the filters: [`code`](#code), [`edgeNGram_filter`](#edgengram_filter), `lowercase`, and `asciifolding` The `whitespace` tokenizer was selected in order to have more control over how tokens are split. For example the string `Foo::bar(4)` needs to generate tokens like `Foo` and `bar(4)` in order to be properly searched. Please see the `code` filter for an explanation on how tokens are split. +NOTE: **Known Issues**: +Currently the [Elasticsearch code_analyzer doesn't account for all code cases](../integration/elasticsearch.md#known-issues). + #### `code_search_analyzer` Not directly used for indexing, but rather used to transform a search input. Uses the `whitespace` tokenizer and the `lowercase` and `asciifolding` filters. -- cgit v1.2.3