[
https://issues.apache.org/jira/browse/PIRK-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392288#comment-15392288
]
ASF GitHub Bot commented on PIRK-19:
------------------------------------
GitHub user tellison opened a pull request:
https://github.com/apache/incubator-pirk/pull/26
[PIRK-19] Make DataSchema/QuerySchema Agnostic of Persistent Representation
- Tidy-up API methods and add javadoc.
- Separating schema loading code from data schema representation.
- Introduce data schema registry for loaded schemas.
- Make schema names case preserving on load, and case sensitive on API
usage.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tellison/incubator-pirk dataschema
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-pirk/pull/26.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 #26
----
commit 45f7d2fedd22cf577d7f500d779c1af7952d2b3e
Author: Tim Ellison <[email protected]>
Date: 2016-07-25T16:50:19Z
Refactoring DataSchema
- Tidy-up API methods and add javadoc.
- Separating schema loading code from data schema representation.
- Introduce data schema registry for loaded schemas.
- Make schema names case preserving on load, and case sensitive on API
usage.
----
> Make DataSchema/QuerySchema Agnostic of Persistent Representation
> -----------------------------------------------------------------
>
> Key: PIRK-19
> URL: https://issues.apache.org/jira/browse/PIRK-19
> Project: PIRK
> Issue Type: Bug
> Components: Data and Query Schemas
> Reporter: Ellison Anne Williams
> Assignee: Tim Ellison
>
> Make the DataSchema and QuerySchema classes agnostic of their potential
> persistent representations, then have 'providers' that applications can use
> to load/store in a variety of formats.
> For example, in LoadDataSchemas, the data schema XML file is parsed to create
> a DataSchema object (one for each data schema specified). The DataSchema
> object could be created from other sources.
> Perhaps JSON representation would be a good starting place.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
