pirk-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PIRK-19) Make DataSchema/QuerySchema Agnostic of Persistent Representation
Date Wed, 27 Jul 2016 02:20:20 GMT

    [ https://issues.apache.org/jira/browse/PIRK-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394947#comment-15394947

ASF GitHub Bot commented on PIRK-19:

Github user ellisonanne commented on a diff in the pull request:

    --- Diff: src/main/java/org/apache/pirk/schema/query/QuerySchemaLoader.java ---
    @@ -246,8 +231,11 @@ private static QuerySchema loadQuerySchemaFile(String schemaFile,
boolean hdfs,
         // Create the query schema object
    -    querySchema = new QuerySchema(schemaName, dataSchemaName, elementNames, selectorName,
dataElementSize, filterNamesSet, filter);
    +    DataFilter filter = instantiateFilter(filterTypeName, filterNamesSet);
    +    querySchema = new QuerySchema(schemaName, dataSchemaName, selectorName, filterTypeName,
filter, dataElementSize);
    --- End diff --
    Will go ahead and merge and we can address/not address the small item above as desired

> 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
> Perhaps JSON representation would be a good starting place.

This message was sent by Atlassian JIRA

View raw message