-
Notifications
You must be signed in to change notification settings - Fork 156
[Manage data] Add 'Index mapping and text analysis' #334
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.
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
Merged
Changes from 5 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
c6c424d
[Manage data] Add 'Index mapping and text analysis'
kilfoyle bf0638c
Remove problem links, temporarily
kilfoyle de3b401
Merge branch 'main' into 367/mapping-text-analysis
kilfoyle 2aca44c
Fix links to use absolute paths
kilfoyle 2bddba2
Merge branch 'main' into 367/mapping-text-analysis
kilfoyle 5be5ff0
Update manage-data/ingest/transform-enrich/index-mapping-text-analysi…
kilfoyle File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
6 changes: 3 additions & 3 deletions
6
manage-data/ingest/transform-enrich/index-mapping-text-analysis.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
# Index mapping and text analysis | ||
|
||
% What needs to be done: Write from scratch | ||
As part of planning how your incoming data might be transformed and enriched as it is ingested, you may want to customize how the data should be organized inside {{es}} and how text fields should be analyzed. | ||
|
||
% GitHub issue: docs-projects#367 | ||
Refer to [Mapping](/manage-data/data-store/mapping.md) to learn about the dynamic mapping rules that Elasticsearch runs by default to identify the data types in your data and to store it in matching fields. You can also configure your own custom mappings to take full control over how your data is organized in the documents in an Elasticsarch index. | ||
|
||
% Scope notes: This should be a stub page that makes it clear to the reader that next step in transforming/enriching data at ingest time is using index mapping and text analysis, and linking to where these concepts are documented in more detail (above in the The Elasticsearch data store section). | ||
Refer to [Text analysis](/manage-data/data-store/text-analysis.md) to learn how to configure an analyzer to run on incoming text, in order to ensure that relevant documents are retrieved from text-based queries. You can opt to use one of several built-in analyzers, or create a custom analyzer for your specific use cases. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.