raghukn commented on issue #14922:
URL: https://github.com/apache/pinot/issues/14922#issuecomment-2630381642
@Jackie-Jiang yes, I was nissing this setting. I had assumed that setting
automatically assumes table null handling is enabled.
Thanks for your inputs.
One question I had was the query output in JSON.
**Query:**
select * from hs_test_tbl_v6 where lead_type is null
**Result JSON:**
{
"resultTable": {
"dataSchema": {
"columnNames": [
"captured_time",
"id",
"lead_type"
],
"columnDataTypes": [
"LONG",
"STRING",
"STRING"
]
},
"rows": [
[
1738563298400,
"0000000155e0441b9b80d3bad74a12b9",
"null"
],
[
1738563298703,
"3",
"null"
]
]
},
"numRowsResultSet": 2,
"partialResult": false,
"exceptions": [],
"numGroupsLimitReached": false,
"timeUsedMs": 8,
"requestId": "1489691015000000080",
"brokerId":
"Broker_pinot-broker-0.pinot-broker-headless.pinot-quickstart.svc.cluster.local_8099",
"numDocsScanned": 2,
"totalDocs": 5,
"numEntriesScannedInFilter": 0,
"numEntriesScannedPostFilter": 6,
"numServersQueried": 1,
"numServersResponded": 1,
"numSegmentsQueried": 1,
"numSegmentsProcessed": 1,
"numSegmentsMatched": 1,
"numConsumingSegmentsQueried": 1,
"numConsumingSegmentsProcessed": 1,
"numConsumingSegmentsMatched": 1,
"minConsumingFreshnessTimeMs": 1738574126676,
"numSegmentsPrunedByBroker": 0,
"numSegmentsPrunedByServer": 0,
"numSegmentsPrunedInvalid": 0,
"numSegmentsPrunedByLimit": 0,
"numSegmentsPrunedByValue": 0,
"brokerReduceTimeMs": 0,
"offlineThreadCpuTimeNs": 0,
"realtimeThreadCpuTimeNs": 0,
"offlineSystemActivitiesCpuTimeNs": 0,
"realtimeSystemActivitiesCpuTimeNs": 0,
"offlineResponseSerializationCpuTimeNs": 0,
"realtimeResponseSerializationCpuTimeNs": 0,
"offlineTotalCpuTimeNs": 0,
"realtimeTotalCpuTimeNs": 0,
"explainPlanNumEmptyFilterSegments": 0,
"explainPlanNumMatchAllFilterSegments": 0,
"traceInfo": {},
"tablesQueried": [
"hs_test_tbl_v6"
]
}
**Question:**
Why does result rows has "null" rather than null in output? The query
clearly looks for IS NULL for this column.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org
