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 2022/06/23 22:20:45 UTC

[GitHub] [pinot] mcvsubbu commented on issue #8962: Segments go into error state after adding sortedColumn on already existing realtime table

mcvsubbu commented on issue #8962:
URL: https://github.com/apache/pinot/issues/8962#issuecomment-1164970249

   @priyen did the column exist when you changed the table config to set the column name to be sorted? (Btw, we can only sort on one column, even though it is an array in the table config. Adding second and subsequent col names to the array does not have any effect, iirc).
   
   Maybe this is as simple as not throwing the error if information is not available while constructing the segment. the next segment will pick up the sorting info correctly (and create the inverted index while consuming)


-- 
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