Re: [I] DISTINCTCOUNTMV returns incorrect value when field is included in select/group by [pinot]

2024-04-04 Thread via GitHub
Jackie-Jiang commented on issue #12429: URL: https://github.com/apache/pinot/issues/12429#issuecomment-2038564631 Pinot `MV` semantic works as following: - In filter, it is similar to unnest, but each row can only be matched once (e.g. IN (1, 2) will make the row once even if the value co

Re: [I] DISTINCTCOUNTMV returns incorrect value when field is included in select/group by [pinot]

2024-04-02 Thread via GitHub
aw381246 commented on issue #12429: URL: https://github.com/apache/pinot/issues/12429#issuecomment-2031945191 If you group by the same column that is in the distinctcount, every row in the result should have a distinctcount of 1. The only reason pinot is returning a value greater than 1 is

Re: [I] DISTINCTCOUNTMV returns incorrect value when field is included in select/group by [pinot]

2024-04-01 Thread via GitHub
aw381246 commented on issue #12429: URL: https://github.com/apache/pinot/issues/12429#issuecomment-2030514242 @Jackie-Jiang, if I understand `VALUE_IN`, I could specify a specific "host" in the query above, and I'd only get the first row, and the distinct count would = 1 right? But that do

[I] DISTINCTCOUNTMV returns incorrect value when field is included in select/group by [pinot]

2024-02-15 Thread via GitHub
aw381246 opened a new issue, #12429: URL: https://github.com/apache/pinot/issues/12429 If the field passed into the distinctcountmv function is included in the list of select / group by fields, it will return incorrect counts. In the case below, the result for each row should be a dis