influxdata
[feature request] RENAME TAG
From https://github.com/influxdb/influxdb/issues/828#issuecomment-83224779
e.g. RENAME TAG foo TO bar ON measurement
Would have to update all CQs, too.
:+1:
We need both , tag key change and also tag value change !
Lots of thanks for this awesome tool.
@toni-moreno I have a perfect use case as to why I need to be able to change values. I use collectd to pull in my SNMP values. I performed a firmware upgrade on a line of switches and the ifDesc field name changed on all 8 switches. So now all of the type_instance tag values are different. For example for interface 32 on switch 1 the ifDesc used to be "TenGigabitEthernet 1_0_32" but now that interface is "TenGigabitEthernet 0_32" So the graphs and data retention are broken. Being able to alter/rename/update all tags from before the firmware update would allow the data to be linked up.
I have same use case about SNMP values and waiting for long time for this feature. In the meantime, I dump series, rename tag value with sed and import again, but it's very slow process when I have many interfaces changes.
+1. I can't find a workaround. I can workaround the measurement and field rename, but not the tag.
Eg.
SELECT "old_field_key" AS "new_field_key" INTO new_measurement FROM old_measurement GROUP BY "old_tag_key"
renames field key and measurement, but cannot be extended to rename the tag key.
I'm having the exact same problem as hraftery piecing together data from two databases that contain data about the same measurement but with different names. Another solution would something like
Select sum(value) as value, counter=blub into newmeasurement
so I can tag the new data that going into newmeasurement.
Have anybody found a proper way or a workaround? I am also having the same issue. I renamed a host and now I need to merge the old tagged value of the host with the new one. Is that possible? Thanks George
same here is there a workaround? In my case the scheme changed, and I need to rename a tag like renaming a column name
+1 (really not seeing how this has not been implemented yet, essential as it seems dealing with historical data)
Any update on this? We have a use case of updating existing tag values as well.
How about updating a tag for points matching a query?
In the Key Concepts sample data, imagine that one of the scientists mistakenly recorded the location for measurements between timeA and timeB as 1 instead of 2. How can we update those points? Overwriting with the same (measurement name, time, tag set) tuple can only be used to update fields, not tags.
Newbie alert: I'm a little unclear about the scope of this feature request. Does it cover two related but different capabilities?:
- Be able to rename a tag key for all series in a measurement. E.g. for Key Concepts sample data, rename "location" -> "place"
- Be able to change the a tag value for a one or more series in a measurement. E.g. for Key Concepts sample data,
UPDATE census SET "scientist"="perpetua" WHERE "scientist"="miller"(e.g. person changed their last name)
The RENAME TAG foo TO bar ON measurement suggestion from the OP description seems to describe the first situation but not the second.
For our purposes, the second situation, rename a tag value is by far the most important.
Should this issue really be split in two? Is it the same implementation to support both tag key and tag value changes or are the implementations independent? Which is the most difficult to achieve?
This issue is definitely about the tag key. It's one of a group of issues about renaming keys that used to be one issue.
As dandv and you say, changing tag values is also a challenge, but deserves its own issue because the implications are different. As discussed on StackOverflow and Google Groups, there's no good solution to that either, short of re-inserting all the data and dropping the old. The implication is that tag values form series, so changing a tag value could change the database cardinality. While changing a tag key only affects the metadata.
If you want to go down the dump all, modify, re-import path (brutal, but effective), this comment might help.
This would be an awesome feature. Right now migrating data when a tag value changes is not really possible.
