[
https://issues.apache.org/jira/browse/CRUNCH-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527173#comment-13527173
]
Matthias Friedrich commented on CRUNCH-97:
------------------------------------------
Hmm, there's no way to influence the order in which fields are extracted, which
means I couldn't turn "1,2" into a (2, 1) tuple, for example. This means I
can't always get a tuple where my business key is the first element, which
seems to be a common convention. As a user I would probably use Parse for
prototyping and roll my own for production. I think this whole Scanner stuff
isn't very well suited for this use case, so -0 from me.
> Add helpers for parsing PCollection<String> instances
> -----------------------------------------------------
>
> Key: CRUNCH-97
> URL: https://issues.apache.org/jira/browse/CRUNCH-97
> Project: Crunch
> Issue Type: Improvement
> Components: Core
> Reporter: Josh Wills
> Assignee: Josh Wills
> Fix For: 0.5.0
>
> Attachments: CRUNCH-97.patch, CRUNCH-97-take2.patch,
> CRUNCH-97-Tokenizer-v1.patch, CRUNCH-97v3.patch, CRUNCH-97v4.patch
>
>
> We should make it a bit easier to parse delimited text files into specific
> data types (e.g., ints, floats, etc.) or combinations of types-- e.g., pairs
> of strings and ints, a Tuple3 of booleans, etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira