Closed Hipska closed 1 year ago
@Hipska Actual issue or mistake ?
What do you mean? Since installing this version, the data in the DB now wrongly has +
signs instead of spaces. So I would say actual issue indeed!
@Hipska What receiver that reproduce a problem ? In unit tests for tagged uploader (https://github.com/go-graphite/carbon-clickhouse/blob/master/uploader/tagged.go#L182) no problems with spaces, when I check. In plain tcp spaces don't work (space is a separator), other receivers don't tested at now.
Oh sorry, I'm using the telegraf_http_json receiver.
Yes, bug is reproduce, i'll fix them.
@Hipska Can You test against current master ?
I guess you mean #125 should have fixed it? Would have been nice to reference this issue on that PR. I also can't see clearly what the exact change to fix it was, as you also did a lot of other changes like replacing stuff to other packages.
Also add tests for escape/unescape cycle (for see that produce original string). https://github.com/go-graphite/carbon-clickhouse/pull/125/files#diff-c712f15e9e4d29bfb013ce058f25bba8b43766b29cb5b37e7d013381e209247eR56
Hi @msaf1980, yes current master looks okay, no more +
sign in the tag values..
Since 0.11.3 tag values that contain a space are now stored with the space replaced by a
+
sign.This conflicts when having tag values that also have a
+
sign, and this also breaks existing graphite queries where selecting with space was done.Spaces are allowed: https://graphite.readthedocs.io/en/latest/tags.html#carbon