Github user nkronenfeld commented on the pull request:
https://github.com/apache/spark/pull/136#issuecomment-38506453
I think my initial sliding method PR addresses @pwendell 's concerns here -
but runs afoul of some other concerns raised by @rxin about code complexity.
Whichever approach ends up deemed superior overall, I would suggest that
there being two PR's for the same operation suggests it isn't all that niche.
As a data point, our use had nothing to do with machine learning - it involved
deriving travel paths from individual location reports.
One suggestion for this PR - make sure the tests include a case with empty
partitions between non-empty partitions.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
