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

ASF GitHub Bot commented on PIRK-16:
------------------------------------

Github user tellison commented on the issue:

    https://github.com/apache/incubator-pirk/pull/17
  
    As well as supporting the original format, this PR allows for a more 
concise form, like this:
    
    ```
    <schema>
        <schemaName>fakeDataSchema</schemaName>
        <element>
            <name>elementName1</name>
            <type>string</type>
        </element>
        <element>
            <name>elementName2</name>
            <type>int</type>
            <isArray/>
            
<partitioner>org.apache.pirk.schema.data.partitioner.PrimitiveTypePartitioner</partitioner>
        </element>
        <element>
            <name>elementName3</name>
            <type>string</type>
            <isArray/>
            
<partitioner>org.apache.pirk.schema.data.partitioner.IPDataPartitioner</partitioner>
        </element>
    </schema>
    ```
    Note: ```elementName1``` has no ```isArray``` element, so it is not an 
array; the other two don't need to specify a value for ```isArray```.


> Define XML schema definition files for Pirk's data and query schemas
> --------------------------------------------------------------------
>
>                 Key: PIRK-16
>                 URL: https://issues.apache.org/jira/browse/PIRK-16
>             Project: PIRK
>          Issue Type: Improvement
>            Reporter: Tim Ellison
>            Assignee: Tim Ellison
>
> Pirk uses XML files to specify a data schema for the target data, and a query 
> schema for the query type.
> This improvement provides the XML schema definition (XSD) for these files, 
> allowing parsers to check the validity of the Pirk schemas.
> These XSDs should probably be available locally (in the deployment JAR) and 
> remotely (on the Pirk website).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to