You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pinot.apache.org by GitBox <gi...@apache.org> on 2019/01/28 18:14:24 UTC

[GitHub] mcvsubbu edited a comment on issue #3717: kafka consume problem

mcvsubbu edited a comment on issue #3717: kafka consume problem
URL: https://github.com/apache/incubator-pinot/issues/3717#issuecomment-458241244
 
 
   I realized that one (hacky) way to stop consumption and still answer queries is to set the realtime broker address to an invalid one, and restart the servers. The segments completed so far will be available for queries (until their expiration time).
   
   Another hacky way is to set 
   pinot.server.segment.uploader.https.enabled to true
   pinot.server.segment.uploader.https.controller.port to some invalid port
   
   this will consume upto the next segment completion point, and try to commit the segment and fail. In that case, the last consumed (but not completed) segment will also be available for query.
   
   I am still not clear why you would want to stop consumption and yet query the table. If you can provide a use case for that, maybe we can address that asa feature.
   @ly923976094 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

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