write opentsdb does something odd to tags

[dmehra]

When I write a point with tags, the write works fine, but subsequent read doesn't show the tags, only time, name and value. However if I include a read filter on a tag, then all tags also show up in the result set.
The same behavior is not observed for points which weren't written in with juttle, but instead generated by tcollector that comes in this docker image; all their tags are shown in plain read.

Also, tag values that contain spaces do something even odder: the write succeeds, but I can't read back those points at all, see below.

Example of needing to filter on the tag in order to see tag value in the data:

juttle> emit -points [ { time: '2016-01-02T02:02:02.222Z', name: 'dm.my.test', value: 0.002, tag1: 'mytag1.22', tag2: 'mytag2.22', tag3: '52' } ] | write opentsdb 
juttle> read opentsdb -from :2016-01-01: -name 'dm.my.test'
┌────────────────────────────────────┬───────────────┬────────────────────────────────┐
│ time                               │ name          │ value                          │
├────────────────────────────────────┼───────────────┼────────────────────────────────┤
│ 2016-01-01T01:01:01.111Z           │ dm.my.test    │ 41                             │
├────────────────────────────────────┼───────────────┼────────────────────────────────┤
│ 2016-01-02T02:02:02.222Z           │ dm.my.test    │ 0.0020000000949949026          │
└────────────────────────────────────┴───────────────┴────────────────────────────────┘

juttle> read opentsdb -from :2016-01-01: -name 'dm.my.test' tag3 = '52'
┌────────────────────────────────────┬───────────────┬────────────────────────────────┬──────────────┬──────────────┬──────────┐
│ time                               │ name          │ value                          │ tag1         │ tag2         │ tag3     │
├────────────────────────────────────┼───────────────┼────────────────────────────────┼──────────────┼──────────────┼──────────┤
│ 2016-01-02T02:02:02.222Z           │ dm.my.test    │ 0.0020000000949949026          │ mytag1.22    │ mytag2.22    │ 52       │
└────────────────────────────────────┴───────────────┴────────────────────────────────┴──────────────┴──────────────┴──────────┘

juttle> read opentsdb -from :2016-01-01: -name 'df.bytes.used' |head 1
┌────────────────────────────────────┬────────────────────┬─────────────────┬──────────┬──────────────────┬───────────────┐
│ time                               │ name               │ value           │ fstype   │ host             │ mount         │
├────────────────────────────────────┼────────────────────┼─────────────────┼──────────┼──────────────────┼───────────────┤
│ 2016-02-12T07:34:04.000Z           │ df.bytes.used      │ 13029310464     │ ext4     │ f5796f87a78f     │ /etc/hosts    │
└────────────────────────────────────┴────────────────────┴─────────────────┴──────────┴──────────────────┴───────────────┘

Example of not reading back the data at all if the tag string contained spaces:

juttle> emit -points [ { time: '2016-01-01T01:01:02.112Z', name: 'test.test', value: 12, tag1: 'a little tag' } ] | write opentsdb
juttle> read opentsdb -from :2016-01-01: -name 'test.test'
└───────────┴───────────┘
juttle> read opentsdb -from :2016-01-01: -name 'test.test' tag1='a little tag'
└───────────┴───────────┘

juttle> emit -points [ { time: '2016-01-01T01:01:01.111Z', name: 'test.test', value: 11, tag1: 'a_little_tag' } ] | write opentsdb
juttle> read opentsdb -from :2016-01-01: -name 'test.test'
┌────────────────────────────────────┬──────────────┬──────────┬──────────────────┐
│ time                               │ name         │ value    │ tag1             │
├────────────────────────────────────┼──────────────┼──────────┼──────────────────┤
│ 2016-01-01T01:01:01.111Z           │ test.test    │ 11       │ a_little_tag     │
└────────────────────────────────────┴──────────────┴──────────┴──────────────────┘

As you can see, the point whose tag was a little tag (with spaces) doesn't get read back at all.