Skip to content
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

Link the flattened field from the kv processor and nested fields #52239

Closed
jpountz opened this issue Feb 11, 2020 · 3 comments · Fixed by #56794
Closed

Link the flattened field from the kv processor and nested fields #52239

jpountz opened this issue Feb 11, 2020 · 3 comments · Fixed by #56794
Assignees
Labels
>docs General docs changes :Search Foundations/Mapping Index mappings, including merging and defining field types Team:Docs Meta label for docs team Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch

Comments

@jpountz
Copy link
Contributor

jpountz commented Feb 11, 2020

I think we should try to make flattened more easily discoverable in our docs. I'm currently considering linking from:

  • The kv processor because it is one reason how users may end up with field names they don't have control of.
  • The nested field because whenever users are tempted to create nested objects that have two key and value keyword fields, then it's likely a better fit for the flattened field.

Any other ideas where we should link flattened from?

@jpountz jpountz added >docs General docs changes :Search Foundations/Mapping Index mappings, including merging and defining field types labels Feb 11, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-docs (>docs)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search (:Search/Mapping)

@rjernst rjernst added Team:Docs Meta label for docs team Team:Search Meta label for search team labels May 4, 2020
@jrodewig jrodewig assigned jrodewig and unassigned jrodewig May 11, 2020
@lockewritesdocs lockewritesdocs self-assigned this May 14, 2020
@lockewritesdocs
Copy link
Contributor

I think we should try to make flattened more easily discoverable in our docs. I'm currently considering linking from:

  • The kv processor because it is one reason how users may end up with field names they don't have control of.
  • The nested field because whenever users are tempted to create nested objects that have two key and value keyword fields, then it's likely a better fit for the flattened field.

Any other ideas where we should link flattened from?

Adding some links to the sections that Adrien mentioned.

lockewritesdocs pushed a commit to lockewritesdocs/elasticsearch that referenced this issue May 14, 2020
lockewritesdocs pushed a commit that referenced this issue May 19, 2020
* Changes for #52239.

* Incorporating review feedback from Julie T. Also single-sourcing nexted options in the Mapping page and referencing them in the Nested page.

* Moving tip after the introduction and clarifying limits.

* Update docs/reference/mapping.asciidoc

Co-authored-by: James Rodewig <[email protected]>

* Update docs/reference/mapping/types/nested.asciidoc

Co-authored-by: James Rodewig <[email protected]>

Co-authored-by: James Rodewig <[email protected]>
lockewritesdocs pushed a commit to lockewritesdocs/elasticsearch that referenced this issue May 19, 2020
* Changes for elastic#52239.

* Incorporating review feedback from Julie T. Also single-sourcing nexted options in the Mapping page and referencing them in the Nested page.

* Moving tip after the introduction and clarifying limits.

* Update docs/reference/mapping.asciidoc

Co-authored-by: James Rodewig <[email protected]>

* Update docs/reference/mapping/types/nested.asciidoc

Co-authored-by: James Rodewig <[email protected]>

Co-authored-by: James Rodewig <[email protected]>
lockewritesdocs pushed a commit that referenced this issue May 19, 2020
* Changes for #52239.

* Incorporating review feedback from Julie T. Also single-sourcing nexted options in the Mapping page and referencing them in the Nested page.

* Moving tip after the introduction and clarifying limits.

* Update docs/reference/mapping.asciidoc

Co-authored-by: James Rodewig <[email protected]>

* Update docs/reference/mapping/types/nested.asciidoc

Co-authored-by: James Rodewig <[email protected]>

Co-authored-by: James Rodewig <[email protected]>

Co-authored-by: James Rodewig <[email protected]>
lockewritesdocs pushed a commit to lockewritesdocs/elasticsearch that referenced this issue May 19, 2020
* Changes for elastic#52239.

* Incorporating review feedback from Julie T. Also single-sourcing nexted options in the Mapping page and referencing them in the Nested page.

* Moving tip after the introduction and clarifying limits.

* Update docs/reference/mapping.asciidoc

Co-authored-by: James Rodewig <[email protected]>

* Update docs/reference/mapping/types/nested.asciidoc

Co-authored-by: James Rodewig <[email protected]>

Co-authored-by: James Rodewig <[email protected]>
lockewritesdocs pushed a commit that referenced this issue May 19, 2020
* Changes for #52239.

* Incorporating review feedback from Julie T. Also single-sourcing nexted options in the Mapping page and referencing them in the Nested page.

* Moving tip after the introduction and clarifying limits.

* Update docs/reference/mapping.asciidoc

Co-authored-by: James Rodewig <[email protected]>

* Update docs/reference/mapping/types/nested.asciidoc

Co-authored-by: James Rodewig <[email protected]>

Co-authored-by: James Rodewig <[email protected]>

Co-authored-by: James Rodewig <[email protected]>
lockewritesdocs pushed a commit to lockewritesdocs/elasticsearch that referenced this issue May 19, 2020
* Changes for elastic#52239.

* Incorporating review feedback from Julie T. Also single-sourcing nexted options in the Mapping page and referencing them in the Nested page.

* Moving tip after the introduction and clarifying limits.

* Update docs/reference/mapping.asciidoc

Co-authored-by: James Rodewig <[email protected]>

* Update docs/reference/mapping/types/nested.asciidoc

Co-authored-by: James Rodewig <[email protected]>

Co-authored-by: James Rodewig <[email protected]>
lockewritesdocs pushed a commit that referenced this issue May 19, 2020
* Changes for #52239.

* Incorporating review feedback from Julie T. Also single-sourcing nexted options in the Mapping page and referencing them in the Nested page.

* Moving tip after the introduction and clarifying limits.

* Update docs/reference/mapping.asciidoc

Co-authored-by: James Rodewig <[email protected]>

* Update docs/reference/mapping/types/nested.asciidoc

Co-authored-by: James Rodewig <[email protected]>

Co-authored-by: James Rodewig <[email protected]>

Co-authored-by: James Rodewig <[email protected]>
@javanna javanna added Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch and removed Team:Search Meta label for search team labels Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>docs General docs changes :Search Foundations/Mapping Index mappings, including merging and defining field types Team:Docs Meta label for docs team Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants