Github user ezhulenev commented on the pull request:

    https://github.com/apache/spark/pull/1717#issuecomment-57515222
  
    Honestly I would prefer passing BoundingBox as a restriction for 
geolocation instead of 2-dimensional array, but passing Twitter4j object looks 
for me more natural, especially when authorization from Twitter4j is already a 
part of public API.
    
    I think it would be better to create some layer on top of FilterQuery, to 
be able define restrictions in bounding-boxes and (?implicitly) transform them 
into FilterQuery object later


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to