-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
OTTL ConvertCase for dot.delimited.case #18084
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@seankhliao Would replace_pattern or replace_match work for you? |
I skipped over it thinking it was a single match variant I think it only works if combined with converting to snake case first, ConvertCase will handle acronyms which is difficult to replicate in regex eg |
I sent in #18275 for the case I raised here ( Though I'm wondering if |
@seankhliao you raise an interesting point. I certainly don't want to keep adding new cases for each character that someone wants to delimit with. I think it would be good to expose A couple ideas:
I think before we merge in your PR we should come to a conclusion on this. @evan-bradley @bogdandrutu what do you think? I lean towards @seankhliao's idea or option 1. |
I'm split with options 1 and 2. If we add an extra parameter, one will always be unused, and to me that's a little odd. On the other hand, overloading it with either cases or character delimiters feels like we're mixing up two concepts (even if they're fairly closely related). I think one thing that would help me feel better about option 2 is if we added a few more common separators ( One thing I like about option 3 is that it is explicit. It makes the difference between the two ideas (naming case vs. delimiter) very clear, even if there is some overlap in functionality. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
With #20879 I think optional parameters will be the solution to this issue. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Optional Parameter support is released which means we can come back to this issue. I feel the solution is to add a new optional parameter |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
It would be nice to find a common term between "delimiter" and "case" and have a function that has |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
pkg/ottl
Is your feature request related to a problem? Please describe.
I'd like to convert metric/attribute names into a standardized form of
dot.delimited.names
Describe the solution you'd like
ConvertCase learns a new
toCase
value ofdot
Describe alternatives you've considered
replace_all_*
functions only work on maps, not a string as required for changing the metric name.Additional context
No response
The text was updated successfully, but these errors were encountered: