Inconsistent filtering on select queries

I know there are some issues with null values in filters, but was wondering if there was an easy fix for this one.

I am trying to run queries where I filter out null values for a given dimension. The dimension is sometimes multivalue and other times just has a single value. I am noticing that the filter works for topN and timeseries queries but doesn’t seem to be fully working for “select” queries. I tried explicitly filtering out both null and “” (know they are treated as the same but thought it would be worth a shot, but no luck).

I am seeing results being returned where the value is:

Is there something else I need to specify to NOT return empty array values as well? Thanks in advance!

Query:
{
“queryType”: “select”,
“dimensions”: [
“FieldName”
],
“metrics”: [
“count”
],
“granularity”: “all”,
“filter”: {
“type”: “and”,
“fields”: [
{
“type”: “not”,
“field”: {
“type”: “selector”,
“dimension”: “FieldName”,
“value”: “”
}
},
{
“type”: “not”,
“field”: {
“type”: “selector”,
“dimension”: “FieldName”,
“value”: null
}
},
{
“type”: “selector”,
“dimension”: “SomeOtherField”,
“value”: “1”
}
]
},
“pagingSpec”: {
“pagingIdentifiers”: {},
“threshold”: 10
},
“dataSource”: “dataSource”,
“intervals”: [
“2015-06-18T16:00:00.000Z/2015-06-18T17:00:00.000Z”
]
}

``

Results:

{
“timestamp”: “2015-06-18T16:00:00.000Z”,
“result”: {
“pagingIdentifiers”: {
“datasource_2015-06-18T00:00:00.000Z_2015-06-19T00:00:00.000Z_2015-06-18T00:00:00.000Z”: 80
},
“events”: [
… results with values yay …
… results with … boo …
{
“segmentId”: “datasource_2015-06-18T00:00:00.000Z_2015-06-19T00:00:00.000Z_2015-06-18T00:00:00.000Z”,
“offset”: 0,
“event”: {
“timestamp”: “2015-06-18T16:19:43.352Z”,
“FieldName”: ,
“count”: null
}
},
{
“segmentId”: “datasource_2015-06-18T00:00:00.000Z_2015-06-19T00:00:00.000Z_2015-06-18T00:00:00.000Z”,
“offset”: 1,
“event”: {
“timestamp”: “2015-06-18T16:19:43.986Z”,
“FieldName”: ,
“count”: null
}
},
… more results with empty field vlaues :frowning:
]
}
}

``

Hi Julien, is this something you can reproduce with the latest RC? We did several fixes to make null handling a lot better on the query side.