Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1682#issuecomment-54755433
@carlosfuertes I'm working on a draft this weekend; I'll make a post to the
developers mailing list sometime next week once I've gotten the basics fleshed
out.
Is the duplication of the keys a significant problem in practice? If we
configure the API's HTTP server to use gzip compression, I think the API
responses still shouldn't be too big. If we do choose to remove this
redundancy, would it make more sense to return the data in CSV or TSV format?
You've raised some good questions about sorting, pagination, etc. I think
we should address these in a consistent way throughout the API. Are there some
existing JSON APIs that you think made good decisions for these features?
---
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]