flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From zentol <...@git.apache.org>
Subject [GitHub] flink pull request #2484: [FLINK-4177] Harden CassandraConnectorTest
Date Fri, 09 Sep 2016 11:03:28 GMT
GitHub user zentol opened a pull request:


    [FLINK-4177] Harden CassandraConnectorTest

    This PR (hopefully) resolves the instability issues with the Cassandra connector tests.
    * updated cassandra/driver versions
    * the `cassandra.yaml` was cleaned up
     * removed several configuration values that used the default
     * sorted the remaining settings in alphabetical order
    * the at-least-once sinks were modified to
     * properly log exceptions when close() is called
     * keep track of how many records were not acknowledged yet
    * the tests were modified to
     * start the embedded cassandra instance in a separate process
       * and supply an array of performance related jvm arguments, taken from the cassandra
     * no longer truncate tables; instead every test uses a separate table
     * wait until a connection could be established to cassandra in a retry-loop instead of
waiting for a fixed time
     * no longer run actual flink jobs
     * use increased timeouts
     * clean up temporary files

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/zentol/flink cass_tmp

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2484
commit 64b125343839788530729a2119d1dc92e50e849a
Author: zentol <chesnay@apache.org>
Date:   2016-09-05T09:03:00Z

    [FLINK-4177] Harden CassandraConnectorTest


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message