[ 
https://issues.apache.org/jira/browse/BEAM-8391?focusedWorklogId=327696&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-327696
 ]

ASF GitHub Bot logged work on BEAM-8391:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Oct/19 09:35
            Start Date: 14/Oct/19 09:35
    Worklog Time Spent: 10m 
      Work Description: iemejia commented on issue #9783: [BEAM-8391] Update 
type id write methods in `AwsModule`
URL: https://github.com/apache/beam/pull/9783#issuecomment-541578827
 
 
   Merged, thanks again. I just saw you are a jackson maintainer catching up 
downstream, makes sense now :). Never mind about the update suggestion if you 
don't have the time.
 
----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 327696)
    Time Spent: 50m  (was: 40m)

> `AwsModule` of sdks/java/io/amazon-web-services uses deprecated type id write 
> methods
> -------------------------------------------------------------------------------------
>
>                 Key: BEAM-8391
>                 URL: https://issues.apache.org/jira/browse/BEAM-8391
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-aws
>            Reporter: Tatu Saloranta
>            Assignee: Tatu Saloranta
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> `AwsModule` class uses old `typeSerializer.writeTypePrefixForObject()` method 
> in `serializeWithType()`, deprecated in Jackson 2.9. While this still works 
> (and should work for 2.x), it makes sense to use replacement that is fully 
> supported.
> I will provide a patch for this.



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

Reply via email to