[jira] [Commented] (ARTEMIS-3026) Allow "reencoding" of application properties on AMQP Large Messages

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247301#comment-17247301 ] 

ASF subversion and git services commented on ARTEMIS-3026:
----------------------------------------------------------

Commit 94f1857914424638db8b6e49f08f326bd49e6809 in activemq-artemis's branch refs/heads/master from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=94f1857 ]

ARTEMIS-3026 Allow "re-encode" of amqp large messages

notice the quotes on "re-encode", as this is just replacing the set of application properties, properties and headers by a new set
if a flag reEncoded is set to true on AMQPLargeMessage


> Allow "reencoding" of application properties on AMQP Large Messages
> -------------------------------------------------------------------
>
>                 Key: ARTEMIS-3026
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3026
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>            Priority: Major
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Currently if Diverts or other things call amqplargeMessage.reencode() this is a moot operation, and there's no way to re-encode the application Properties, Properties or anything in the LargeMessage.
>  
> It should be possible to allow replacing the application properties upon sending. 
>  
> We save the modified application properties anyways on the journal record. So, we should allow ProtonServerSenderContext to replace the original application properties by a new set if reencode() is called anywhere on the message.
>  
> There should be a flag that would be stored as part of the journal allowing the broker to know if the message was ever re-encoded.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)