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

[DOCS][ESQL] Add object type to unsupported field types list #109970

Closed
wants to merge 1 commit into from

Conversation

leemthompo
Copy link
Contributor

No description provided.

@leemthompo leemthompo added >docs General docs changes auto-backport-and-merge Automatically create backport pull requests and merge when ready :Analytics/ES|QL AKA ESQL v8.14.0 v8.15.0 labels Jun 20, 2024
@leemthompo leemthompo self-assigned this Jun 20, 2024
Copy link

Documentation preview:

@elasticsearchmachine elasticsearchmachine added Team:Docs Meta label for docs team Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) labels Jun 20, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-docs (Team:Docs)

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-analytical-engine (Team:Analytics)

@@ -64,6 +64,7 @@ include::processing-commands/limit.asciidoc[tag=limitation]
** `ip_range`
** `long_range`
** `nested`
** `object`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The story here is complicated. Like, what does "support" mean here. We load fields in an object field just fine. But we don't support loading the entire object field as a tree structure.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right maybe add some more color and move it somewhere else in limitations page? :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess move it.... I think it'd look funky to have a bunch of nuance in this list. Especially around the other fields where the answer is pretty simple - we just can't touch these fields.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I guess the question is what weirdnesses are folks going to hit if they try to work with object fields in ES|QL, and are they worth enumerating here at this point in time?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's worth double checking. They don't come back in *. If you refer to them directly they are unsupported, but I don't know what that'll look like. But that's not a "normal" thing to do.

@leemthompo
Copy link
Contributor Author

Let's park this and see if it becomes a recurring question, rather than writing a load of caveat-filled verbiage

@leemthompo leemthompo closed this Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/ES|QL AKA ESQL auto-backport-and-merge Automatically create backport pull requests and merge when ready >docs General docs changes Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) Team:Docs Meta label for docs team v8.14.0 v8.16.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants