Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Pivot function to GEL #82

Closed
tfmorris opened this issue Oct 15, 2012 · 2 comments
Closed

Add Pivot function to GEL #82

tfmorris opened this issue Oct 15, 2012 · 2 comments
Labels
imported from old code repo Issue imported from Google Code in 2010 Priority: Medium Represents important issues that need to be addressed but are not urgent Type: Feature Request Identifies requests for new features or enhancements. These involve proposing new improvements.
Milestone

Comments

@tfmorris
Copy link
Member

Original author: thadguidry (June 22, 2010 19:17:40)

GEL could perhaps use a new pivot function. Something like pivot[rowIndex%VAR](rowIndex modulo VARIABLE) that would split into multiple columns a single column, multi-value rowed file based on the row.index sequence that would need to be split such as rows 1-3, or rows 1-5 recurring etc. Currently, I was able to accomplish some of the functionality by using Jython expression of 'return rowIndex%2' to facet even and odd rows and then export and copy-paste combine externally in MS Excel, then re-import into gw. More beneficial would be to expand upon the UI for Edit Column/Split into Several Columns. Whereby a 3rd option would use the new pivot function to map rows to columns. Essentially a lazy pivot function.

Original issue: http://code.google.com/p/google-refine/issues/detail?id=82

@tfmorris
Copy link
Member Author

From thadguidry on June 22, 2010 19:30:32:
Example file of data to be split into columns is attached. Sometimes the use case will include more than 2 rows of "TYPES" to be split into columns, but in this example file it's just 2 rows each.

@tfmorris
Copy link
Member Author

From dfhu...@google.com on August 08, 2010 06:31:14:
Fixed by r1133.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
imported from old code repo Issue imported from Google Code in 2010 Priority: Medium Represents important issues that need to be addressed but are not urgent Type: Feature Request Identifies requests for new features or enhancements. These involve proposing new improvements.
Projects
None yet
Development

No branches or pull requests

1 participant