[feature request] Insert new tags to existing values, like update

[mvadu]

Can we have a query syntax which allows to insert/attach a new set of tags (along with exiting ones) to values/rows that are already part of a measurement?

My use case: I created a measurement from PerfMon log, which already has Host= tag. Now I want to categorize the data by applications, so I want to add tags like "App1=, App2=" assuming I can have two apps hosted on same server.

Then I want to be able to say Update <measurement name> add <tag name=value> where <some condition based on tags>

[airyland]

+1

[beckettsean]

This feature would require a fairly major architectural change to the database and is not something we will do this year, if ever. Closing the request for now.

[mvadu]

Please consider this during your next architecture review. I think this would be required in many enterprise situations, where you make a mistake while inserting values, and realize it later. Having an option to update would be a life saver!

[ivanscattergood]

Hi,
I have been two specific use cases for this functionality

1. Obfuscation of data for testing / demo purposes.
   As the data we deal with is Market data the Tags within the data may actually refer to a ticker and given the other attributes of the data you can work out trade information. I am currently working on a data set which I have been asked to Obfuscate for a demo. To achieve this I am currently loading the dataset into memory and writing it back in with new tags. (This would be simplified by the insert into functionality that has been proposed in Should be able to force recalculation of continuous query for given time interval #211)

2. Change of the Tag value in the real world
   Imagine that one of the tags in your data referenced the Name of a department, if that department name changed it would be good to be able to change it historically, rather than having to have the two tag values running in tandem.
   In the world of Data Warehousing this is known as slowly changing dimensions:
   http://datawarehouse4u.info/SCD-Slowly-Changing-Dimensions.html

[rapport]

+1 For us events are usually only recognising in the data following a reasoning step after capture. And, we want to tag data with its event once its recognised. I am considering using continuous queries to do some of this tagging after capture but it seems inefficient and I am not sure it will work for all our use cases

[srikara]

+1

[mrh666]

+1
This is will be surprisingly useful feature! Sometimes our developers sending metrics not following the namespace requirement, but following some pre-defined hardcoded application name structure (storm metrics collector for example) and those metrics have a lot of value for research.

[jarlwolfganger]

+1, if you guys aren't going to add this in some time soon could you at least add work around options to the current documentation since there was nothing mentioning appending tags to an existing measurement.

+1 this is definitely needed in many real-world solutions as architectural changes might need additional tags.

[hgomez-sonarsource]

+1 to add this feature since as of today, there is no other options than to dump a measure in ASCII, hack ASCII file and send it back to a new measure via wireprotocol.

[hgomez-sonarsource]

For now, I updated my InfluxDB Fetcher tool (https://github.com/hgomez/influxdb) to transform fields in tags so I could reimport them in proper format

[jincejames]

+1