Key is not used for partitionning #228

Activity

1. lcobucci commented on Jul 23, 2018

   

   lcobucci

   on Jul 23, 2018

   Contributor

   More actions

   @mantzas can you please check if #218 fulfils your needs?
2. mantzas commented on Jul 23, 2018

   

   mantzas

   on Jul 23, 2018

   Last edited by mantzas

   Author

   More actions

   @lcobucci is this not already implemented in the library?
3. lcobucci commented on Jul 23, 2018

   

   lcobucci

   on Jul 23, 2018

   Contributor

   More actions

   @mantzas nope, that's why I'm asking you to check that particular branch. I'll be reviewing it further this week to integrate, but will be only available in v3.x
4. mantzas commented on Jul 23, 2018

   

   mantzas

   on Jul 23, 2018

   Author

   More actions

   @lcobucci yes, this is what's needed from our side. We integrated the current code in our codebase to make this work now. We will wait until v3 to get the library then. Thanks man
5. demyanovs commented on Jul 27, 2018

   

   demyanovs

   on Jul 27, 2018

   Last edited by demyanovs

   More actions

   @mantzas @lcobucci
   Currently, in order not to change this client and wait for the merge #218, you can get information directly from the broker and proceed as follows:

   $broker = \Kafka\Broker::getInstance();
   $topic_infos = $broker->getTopics();
   $topic_meta = $topic_infos[$topic_title];
   $part_nums = array_keys($topic_meta);
   if ($key) {
       $part_id = $part_nums[crc32($key) % count($part_nums)];
   } else {
       shuffle($part_nums);
       $part_id = $part_nums[0];
   }
   

   And then set partId

   $producer->send([
       [
           'topic' => $topic_title,
           'value' => $message,
           'partId' => $part_id,
       ],
   ]);
   
6. mantzas commented on Jul 27, 2018

   

   mantzas

   on Jul 27, 2018

   Author

   More actions

   @demyanovs done this already based on #218. it's running in production already. thanks.
7. mantzas

   closed this as completedon Jul 27, 2018