Github user ezhulenev commented on the pull request:
https://github.com/apache/spark/pull/1717#issuecomment-57560702
Twitter4j Authorization already leaked into public API, so FilterQuery
doesn't make things much worse.
I personally don't like Twitter4j for too javaish API (two dimensional
array) and not super clear documentation. But adding completely new type-based
scala facade and keeping Authorization at the same time, I don't feel that it's
right.
Building another twitter client... does't sound fun as well. I think that
FilterQuery gives enough flexibility with minimal costs. And scala-typed
"facade" can be out of Spark, depending on requirements (geo, lang, etc...)
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
