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

[BUG] Rename does not work with nested fields #2740

Open
lezzago opened this issue Jun 12, 2024 · 2 comments
Open

[BUG] Rename does not work with nested fields #2740

lezzago opened this issue Jun 12, 2024 · 2 comments
Labels
bug Something isn't working catch-all acknowledged Marks issues caught in catch-all triage for searchability

Comments

@lezzago
Copy link
Member

lezzago commented Jun 12, 2024

What is the bug?
Rename does not work with nested fields. When I tried to rename a nested field, the renamed field would just have empty values. This is an example query that has issues:

source=otel-metrics-2024.05| rename `attributes.resource.attributes.service@name` as ServiceName | dedup ServiceName | fields ServiceName

How can one reproduce the bug?
Make a similar query to the one below that renames a nested field

source=otel-metrics-2024.05| rename `attributes.resource.attributes.service@name` as ServiceName | fields ServiceName

What is the expected behavior?
The values from the renamed field should not be empty

What is your host/environment?

  • OS: AWS OpenSearch 2.11
@lezzago lezzago added bug Something isn't working untriaged labels Jun 12, 2024
@lezzago lezzago changed the title [BUG] Rename does not work with backtick fields [BUG] Rename does not work with nested fields Jun 12, 2024
@LantaoJin
Copy link
Member

Not sure if it relates to opensearch-project/OpenSearch#14355. @penghuo, how does the RenameOperator work in SQL engine? If the implementation relates to rename field processor, it might be the bug of OpenSearch Core.

@dblock dblock removed the untriaged label Jul 1, 2024
@dblock
Copy link
Member

dblock commented Jul 1, 2024

[Catch All Triage - Attendees 1, 2, 3, 4, 5]

@Swiddis Swiddis added the catch-all acknowledged Marks issues caught in catch-all triage for searchability label Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working catch-all acknowledged Marks issues caught in catch-all triage for searchability
Projects
None yet
Development

No branches or pull requests

4 participants