GitHub user zellerh opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/939

    [TRAFODION-2456] Improve documentation for UDF parallelism

    Just setting the desired degree of parallelism often doesn't
    actually choose a parallel plan, the UDF writer may also need
    to specify an estimate of the number of rows produced.
    
    Also made the methods that are not intended for the UDR writer
    package-private (no qualifier). This has two good side-effects: One is
    that UDR writers no longer can call these methods (accidentally) and
    the other is that we can set Javadoc to display only public methods,
    which suppresses these package-private methods.

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

    $ git pull https://github.com/zellerh/incubator-trafodion bug/cses_jan-17

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

    https://github.com/apache/incubator-trafodion/pull/939.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 #939
    
----
commit bc5ae4904fb0e70f2f87e61d0c951ac1803c3a1d
Author: Hans Zeller <[email protected]>
Date:   2017-01-30T19:25:59Z

    [TRAFODION-2456] Improve documentation for UDF parallelism
    
    Just setting the desired degree of parallelism often doesn't
    actually choose a parallel plan, the UDF writer may also need
    to specify an estimate of the number of rows produced.
    
    Also made the methods that are not intended for the UDR writer
    package-private (no qualifier). This has two good side-effects: One is
    that UDR writers no longer can call these methods (accidentally) and
    the other is that we can set Javadoc to display only public methods,
    which suppresses these package-private methods.

----


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