Skip to content
This repository has been archived by the owner on Aug 13, 2019. It is now read-only.

groupColumn cannot be a column added by the mapper #1

Open
nkuehn opened this issue Mar 29, 2015 · 2 comments
Open

groupColumn cannot be a column added by the mapper #1

nkuehn opened this issue Mar 29, 2015 · 2 comments

Comments

@nkuehn
Copy link
Collaborator

nkuehn commented Mar 29, 2015

Hi,
I just tried a mapping that uses a column that's added by the same mapping file as "groupColumn".
Result is an empty CSV with just the column names line.

It would be nice if this were supported or at leas explicitly caught and/or documented.

@OlegIlyenko
Copy link
Contributor

groupColumn was designed to preserve the order of rows from the original file (or at least subsets of the rows). Can you please explain you use-case? It would be really helpful, especially how you create this new column: is it copied from some other column with or without transformations?

@nkuehn
Copy link
Collaborator Author

nkuehn commented Apr 7, 2015

HI, in this case the grouping "ID" is a concatenation of three other identifiers in the source data (category, Manufacturer, Model), which define a group only "combination unique". To me it seems rather like a question of processing order: Process Column transforms and additions first, then do the grouping, then add the variant counter column. But that may be a limited view of what's going on inside.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants