[
https://issues.apache.org/jira/browse/FLINK-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354839#comment-15354839
]
ASF GitHub Bot commented on FLINK-4127:
---------------------------------------
Github user aljoscha commented on a diff in the pull request:
https://github.com/apache/flink/pull/2177#discussion_r68908810
--- 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 --
Not really, I'm afraid. I just recently disabled it by default because of
the known issues.
What I can gather from the code is that it is a separate sort buffer that
is intended for very large records. It is not obvious from the code what "very
large records" are, however.
The known problem is that key serialization does not work correctly if the
user specified a custom type or if Scala types are used because the
`TypeAnalyzer` is used in the `LargeRecordHandler` to get a `TypeInformation`
on the fly.
> 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)
