shounakmk219 commented on issue #11893:
URL: https://github.com/apache/pinot/issues/11893#issuecomment-2231122702

   Hey @jadami10 , I tried to follow the mentioned steps with the latest master 
and was not able to reproduce the issue. 
   Would like to get some more context on this. 
   
   > And I can clearly see in the index_map that .dictionary.startOffset and 
.dictionary.size are set
   
   From my observations the older segments which didn’t had the new column, end 
up having null value for that column and stay on the dictionary encoding as its 
marked as a sorted column. Changing to no dict will not have effect on such 
segments.
   
   Regarding the error
   ```
   QueryExecutionError:
     java.lang.UnsupportedOperationException
   at 
org.apache.pinot.segment.spi.index.reader.ForwardIndexReader.getInt(ForwardIndexReader.java:372)
   at 
org.apache.pinot.core.common.DataFetcher$ColumnValueReader.readStringValues(DataFetcher.java:576)
   at 
org.apache.pinot.core.common.DataFetcher.fetchStringValues(DataFetcher.java:239)
   at 
org.apache.pinot.core.common.DataBlockCache.getStringValuesForSVColumn(DataBlockCache.java:277)
   ```
   [This code 
path](https://github.com/apache/pinot/blob/master/pinot-core/src/main/java/org/apache/pinot/core/common/DataFetcher.java#L391)
 should be taken when [dictionary is not 
enabled](https://github.com/apache/pinot/blob/master/pinot-core/src/main/java/org/apache/pinot/core/common/DataFetcher.java#L383)
 on a column so most probably this error log is coming while accessing the 
newer segments which have no dictionary on the 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to