[
https://issues.apache.org/jira/browse/CRUNCH-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Wills resolved CRUNCH-315.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.8.3
0.10.0
Pushed to master.
I'm inclined to say we add support for it only if/when someone brings a
compelling use case for it, primarily because it's not a totally trivial change
and (as Micah indicated) there are other mechanisms in place to do it when it's
necessary.
> Empty collection
> ----------------
>
> Key: CRUNCH-315
> URL: https://issues.apache.org/jira/browse/CRUNCH-315
> Project: Crunch
> Issue Type: New Feature
> Reporter: Chao Shi
> Fix For: 0.10.0, 0.8.3
>
> Attachments: CRUNCH-315.patch
>
>
> As discussed in the mailing list [1] and [2], I'd like to add an empty
> collection feature. On the API side, I think we can add a new method in
> Pipeline to create an empty collection. The collection should be a subclass
> of PCollection and behaves like other normal PCollecitons. There are also
> some optimization points that Josh mentioned in [2].
> I haven't thought it clearly. Just put a ticket here and see if anyone else
> has a better idea.
> [1]
> http://mail-archives.apache.org/mod_mbox/crunch-dev/201312.mbox/%3CBLU0-SMTP1337A04FAC6B5F497F7473EADC10%40phx.gbl%3E
> [2]
> http://mail-archives.apache.org/mod_mbox/crunch-dev/201312.mbox/%3CCAH29n6MbSK9gapoC2DgVnhofjAobyasCuZh_0475DuSajV%3DCPg%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
