SteNicholas opened a new pull request #12717:
URL: https://github.com/apache/flink/pull/12717


   ## What is the purpose of the change
   
   *`java.lang.NoSuchFieldError: NO_INTS` is caused by conflicting versions of 
the jackson libraries. flink-connector-kinesis uses the 1.11.754 version of 
`aws-java-sdk-kinesis` and `aws-java-sdk-core`. The version of 
`aws-java-sdk-core` uses the 2.6.7 version of `jackson-dataformat-cbor`, which 
repository refers to [AWS SDK For Java Core 
1.11.754](https://mvnrepository.com/artifact/com.amazonaws/aws-java-sdk-core/1.11.754).
 Flink generally uses the 2.10.1 version of jackson and the version of 
jackson-dataformat-cbor couldn't correctly parse the CBOR data format.*
   
   ## Brief change log
   
     - *Modify the version of `jackson-dataformat-cbor` dependency in 
flink-connector-kinesis to use 2.6.7.*
   
   ## Verifying this change
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (**yes** / no)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** 
/ don't know)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / **no** / 
don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (**not applicable** / docs / 
JavaDocs / not documented)
   


----------------------------------------------------------------
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:
[email protected]


Reply via email to