incubator-vxquery-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinayak Borkar (JIRA)" <>
Subject [jira] [Updated] (VXQUERY-91) Temporal functions grouped into a common library for byte based storage
Date Thu, 25 Apr 2013 22:36:17 GMT


Vinayak Borkar updated VXQUERY-91:

    Labels: gsoc2013  (was: )
> Temporal functions grouped into a common library for byte based storage
> -----------------------------------------------------------------------
>                 Key: VXQUERY-91
>                 URL:
>             Project: VXQuery
>          Issue Type: Improvement
>            Reporter: Preston Carman
>            Assignee: Vinayak Borkar
>              Labels: gsoc2013
> VXQuery utilizes Algebricks and Hyracks to build a XQuery process that can run in distributed
system. Reviewing the list of query languages build upon the same base, there is a common
need for temporal functionality. XQuery provides a great base for other languages, like AsterixQL,
in respect to temporal functionality. 
> Building a common library of functionality for both XQuery and AsterixQL would allow
for simplified code base. In addition to only having to implement temporal features in one
place. The new library could fill in the holes in VXQuery's temporal implementation and provide
missing temporal features for AsterixQL. One library would keep more complex temporal features
out of the way.
> Key Features for Library:
>  - Written in Java 
>  - Optimized to work with out objects (use byte arrays)
>  - Standardized temporal API
>  - Useful to other Hyracks applications 
> Review of tasks:
>  - Consolidate temporal code into one library
>  - Update XQuery to use the library
>  - Validate all XQuery temporal functions through the test harness
>  - Create a patch for AsterixQL for to utilize the new library
> Optional tasks:
>  - Temporal Units for the library
>  - Additional non-XQuery temporal features

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message