You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The current implementation of the ParseXML produces output that is difficult for users to manipulate, particularly when the XML is complicated. The current design loses the sense of key:value pairs which is helpful for understanding the data, and, more importantly, parses the XML into arrays, which are difficult to manipulate in OTTL, and don't provide a stable path that can be used to access the data.
Describe the solution you'd like
PR 35210 has a proposed new parsing version that maintains backward compatibility with the current implementation. (Updated to point to PR off observIQ repo)
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
I'm going to make a few comments on #35210 but I think it's going to be worth bringing the discussion back here to focus on proposed changes to the format.
Component(s)
pkg/ottl
Is your feature request related to a problem? Please describe.
The current implementation of the ParseXML produces output that is difficult for users to manipulate, particularly when the XML is complicated. The current design loses the sense of key:value pairs which is helpful for understanding the data, and, more importantly, parses the XML into arrays, which are difficult to manipulate in OTTL, and don't provide a stable path that can be used to access the data.
Describe the solution you'd like
PR 35210 has a proposed new parsing version that maintains backward compatibility with the current implementation. (Updated to point to PR off observIQ repo)
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: