alpreu opened a new pull request, #19655:
URL: https://github.com/apache/flink/pull/19655

   ## What is the purpose of the change
   
   This pull request introduces a new file-bases upsert sink for testing 
internal components.
   
   
   ## Brief change log
   
     -  Created a file-based upsert test sink
     - The SinkWriter stores records as key-value pairs in a map, on every 
flush the map is written/appended to the file and cleared. Subsequent flushes 
thus always write out the delta of the next records.
     - Created `BinaryFileUtil` class to provide simple reading from 
Files/Streams that were written from the Sink. This provides both lowlevel 
(ByteBuffer with the serialized records) as well as highlevel (actual record by 
using a DeserializationSchema) access 
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - Added Unit tests and ITCases for the introduced components
   
   ## 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, 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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to