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

   ## What is the purpose of the change
   
   Add a flink source for Cassandra database compliant with 
[FLIP-27](https://cwiki.apache.org/confluence/display/FLINK/FLIP-27%3A+Refactor+Source+Interface)
   
   ## Brief change log
   
   Implement everything needed for the source: enumerator, cassandra splits, 
source reader, split reader etc... + the related unit tests and integration 
tests.
   
   Moved the annotated Pojo class used in Cassandra batch example to a common 
place (tests / casssandra utils) to be able to use it with both example and 
source tests
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   - CassandraSourceITCase: integration test using the new source test 
framework and a Cassandra test container
   - CassandraEnumeratorStateSerializerTest and CassandraSplitSerializerTest:  
for serialization tests
   - CassandraQueryTest: tests for query generation and query sanity checks
   - SplitsGeneratorTest: test for ring ranges creation (use for splits)
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): add connector base 
and connector test utils
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: adds a new `@Public(Evolving)` API
     - The serializers: add some new ones
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? yes
     - If yes, how is the feature documented? javadoc
   
   R: @zentol 
   CC: @MartijnVisser 


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