You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pinot.apache.org by GitBox <gi...@apache.org> on 2021/09/21 18:57:37 UTC

[GitHub] [pinot] kishoreg commented on pull request #7454: bit-sliced index for int, long SV columns

kishoreg commented on pull request #7454:
URL: https://github.com/apache/pinot/pull/7454#issuecomment-924295119


   > Regarding the config (`IndexingConfig`), do you think it makes sense to keep two separate lists for old value range index and new bit-sliced range index? Users might want to mix them since the new one doesn't support MV. Or we can automatically fall back to the old one for MV. Both way are okay to me.
   
   lets not add another list. This is a better implementation. We can enhance fieldconfig to allow users to pick one impl vs other in short term but my take is slicedbitmap will be better in all cases and we wont need bucketed 


-- 
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-unsubscribe@pinot.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org