Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/1717#issuecomment-57408771
Aah I looking at the wrong docs (twitter4j.Query rather than
twitter4j.FilterQuery). Looking at FilterQuery, I find that it has many
functionalities, tracking, etc. Not just locations, and count, one may want to
do any of the things that is provided in FilterQuery. It makes me wonder that,
rather than adding location, and count, a better, more scalable approach is to
add the ability to add your own filter query object. The user can set whatever
filters they want in a FilterQuery object and pass it on to the
`TwitterUtils.createStream(filterQuery)`. This is prevent the bloat in the
number of combinations of `TwitterUtils.createStream`.
What do you think? @sjbrunst @ezhulenev
---
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]
