flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4127) Clean up configuration and check breaking API changes
Date Tue, 28 Jun 2016 18:53:57 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353525#comment-15353525
] 

ASF GitHub Bot commented on FLINK-4127:
---------------------------------------

Github user greghogan commented on a diff in the pull request:

    https://github.com/apache/flink/pull/2177#discussion_r68819516
  
    --- Diff: docs/setup/config.md ---
    @@ -85,6 +85,8 @@ The default fraction for managed memory can be adjusted using the `taskmanager.m
     
     - `taskmanager.memory.preallocate`: Can be either of `true` or `false`. Specifies whether
task managers should allocate all managed memory when starting up. (DEFAULT: false)
     
    +- `taskmanager.runtime.large-record-handler`: Whether to use the LargeRecordHandler when
spilling. This feature is experimental. (DEFAULT: false)
    --- End diff --
    
    Have we documented when it would be useful to enable `LargeRecordHandler`?


> Clean up configuration and check breaking API changes
> -----------------------------------------------------
>
>                 Key: FLINK-4127
>                 URL: https://issues.apache.org/jira/browse/FLINK-4127
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Robert Metzger
>             Fix For: 1.1.0
>
>         Attachments: flink-core.html, flink-java.html, flink-scala.html, flink-streaming-java.html,
flink-streaming-scala.html
>
>
> For the upcoming 1.1. release, I'll check if there are any breaking API changes and if
the documentation is up tp date with the configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message