GitHub user paul-rogers opened a pull request:

    https://github.com/apache/drill/pull/753

    DRILL-5260: Extend "Cluster Fixture" test framework

    - Config option to suppress printing of CSV and other output. (Allows
    printing for single tests, not printing when running from Maven.)
    
    - Parsing of query profiles to extract plan and run time information.
    
    - Fix bug in log fixture when enabling logging for a package.
    
    - Improved ZK support.
    
    - Set up the new CTTAS default temporary workspace for tests.
    
    - Clean up persistent storage files on disk to avoid CTTAS startup
    failures.
    
    - Provides a set of examples for how to use the cluster fixture.

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

    $ git pull https://github.com/paul-rogers/drill DRILL-5260

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

    https://github.com/apache/drill/pull/753.patch

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

    This closes #753
    
----
commit 40080d663545c6f0a5a413cf18866611a2bc5b3f
Author: Paul Rogers <[email protected]>
Date:   2017-02-18T01:39:20Z

    DRILL-5260: Extend "Cluster Fixture" test framework
    
    - Config option to suppress printing of CSV and other output. (Allows
    printing for single tests, not printing when running from Maven.)
    
    - Parsing of query profiles to extract plan and run time information.
    
    - Fix bug in log fixture when enabling logging for a package.
    
    - Improved ZK support.
    
    - Set up the new CTTAS default temporary workspace for tests.
    
    - Clean up persistent storage files on disk to avoid CTTAS startup
    failures.
    
    - Provides a set of examples for how to use the cluster fixture.

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to