search

xichen2020 / eventdb

Storage for discrete events such as log events or tracing events
Apache License 2.0
9 stars 1 forks source link

Field type incorrect on filter path #126

Closed notbdu closed 5 years ago

notbdu commented 5 years ago

For the following test data:

{"service":"testNamespace","@timestamp":"2019-01-22T13:33:42-08:00","st":true,"sid":{"foo":2,"bar":4},"tt":"active","tz":-6,"v":1.5}
{"service":"testNamespace","@timestamp":"2019-01-22T13:34:42-08:00","st":true,"sid":{"foo":2,"bar":4},"tt":"active","tz":-6,"v":1.5}
{"service":"testNamespace","@timestamp":"2019-01-22T13:35:42-08:00","st":false,"sid":{"foo":3,"bar":6},"tt":"inactive","tz":-6,"v":15}
{"service":"testNamespace","@timestamp":"2019-01-22T13:36:42-08:00","st":false,"sid":{"foo":3,"bar":6},"tt":"inactive","tz":-6,"v":15}
{"service":"testNamespace","@timestamp":"2019-01-22T13:37:42-08:00","st":false,"sid":{"foo":3,"bar":6},"tt":"inactive","tz":-6,"v":15}

Got the following error when attempting to filter against the st field: field [st] does not have values of type bool

notbdu commented 5 years ago

No longer seeing this issue. Seeing a different issue documented here: #151

notbdu commented 5 years ago

Was able to repro this again by filtering on the same field that we're also grouping by.

xichen2020 commented 5 years ago

Was this the same issue with using unsafe.String that got fixed in #134 ? If so can I close this?

notbdu commented 5 years ago

No, this was an issue w/ the fetched field being closed in applyFilters.

xichen2020 commented 5 years ago

Fixed in #153