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 Thu, 07 Jul 2016 13:32:11 GMT

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

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

Github user aljoscha commented on the issue:

    https://github.com/apache/flink/pull/2177
  
    Sorry for chiming in late, but can't - `heap-cutoff-ratio` and `heap-cutoff-min` be general
parameters that apply to all VMs we start?
    
    Same for `master.env.*` and `taskmanager.env.*`. Shouldn't this also apply to all VMs
that we start?


> 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
>          Components: Build System
>            Reporter: Robert Metzger
>            Assignee: 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