nicoloboschi opened a new pull request, #15426:
URL: https://github.com/apache/pulsar/pull/15426

   ### Motivation
   In case of the inbound message is structured (Avro or JSON) the fields order 
may change overtime and there's no fields order guarantee from the Pulsar 
function framework.
   The generated _id field of the document is supposed to be the same 
regardless the input message key fields order.    
   
   ### Modifications
   * New option `canonicalKeyFields` (boolean, default false) to sort the key 
fields. Both for JSON and Avro we have to parse and rewrite the entire payload. 
It may increase the CPU overhead even if the sort is only performed on the keys 
that MUST be lower to 512 bytes in order to suit in the ElasticSearch _id field.
   
   - [x] `doc` 


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

Reply via email to