GitHub user tellison opened a pull request:
https://github.com/apache/incubator-pirk/pull/18
[WIP] Serialization and storage changes to Querier, Query, and Response.
- Introduce serialization services that can flatten objects into a
variety of different formats. Currently just reusing the Java
serialization code until the project is ready to adopt other
serializers.
- Introduce storage services that can store objects and retrieve them.
Currently just reusing the local file system and HDFS. The storage
service uses one of the serialization services to flatten the objects.
- Remove code from Querier, Query, and Response that was serializing
and storing each of them; and update the callers to use the storage
services.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tellison/incubator-pirk serialization
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-pirk/pull/18.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #18
----
commit aef6aea88896f808c578e3660785a9b8483e375d
Author: Tim Ellison <[email protected]>
Date: 2016-07-22T14:40:12Z
Serialization and storage changes to Querier, Query, and Response.
- Introduce serialization services that can flatten objects into a
variety of different formats. Currently just reusing the Java
serialization code until the project is ready to adopt other
serializers.
- Introduce storage services that can store objects and retrieve them.
Currently just reusing the local file system and HDFS. The storage
service uses one of the serialization services to flatten the objects.
- Remove code from Querier, Query, and Response that was serializing
and storing each of them; and update the callers to use the storage
services.
----
---
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.
---
