[
https://issues.apache.org/jira/browse/BEAM-6756?focusedWorklogId=344669&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-344669
]
ASF GitHub Bot logged work on BEAM-6756:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Nov/19 23:42
Start Date: 15/Nov/19 23:42
Worklog Time Spent: 10m
Work Description: reuvenlax commented on issue #10003: [BEAM-6756] Create
Iterable type for Schema
URL: https://github.com/apache/beam/pull/10003#issuecomment-554571984
friendly ping
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 344669)
Time Spent: 1h 10m (was: 1h)
> Support lazy iterables in schemas
> ---------------------------------
>
> Key: BEAM-6756
> URL: https://issues.apache.org/jira/browse/BEAM-6756
> Project: Beam
> Issue Type: Sub-task
> Components: sdk-java-core
> Reporter: Reuven Lax
> Assignee: Reuven Lax
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The iterables returned by GroupByKey and CoGroupByKey are lazy; this allows a
> runner to page data into memory if the full iterable is too large. We
> currently don't support this in Schemas, so the Schema Group and CoGroup
> transforms materialize all data into memory. We should add support for this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
