You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Laurent Pellegrino (JIRA)" <ji...@apache.org> on 2011/05/27 10:25:47 UTC

[jira] [Issue Comment Edited] (JENA-69) Provide TSVInput reader

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

Laurent Pellegrino edited comment on JENA-69 at 5/27/11 8:25 AM:
-----------------------------------------------------------------

Here a patch that provides the TSVInput class. 

I have updated the classes which provide input reader by mimicking the existing methods (seeResultSetFactory). However, this patch implies to move the NodecLib class from the TDB library to the ARQ library in order to avoid to copy the code. Indeed, TSVOuput serializes the nodes by using FmtUtils.stringForNode(n) and it seems there is no method to do the reverse operation into the ARQ library (see my post on the mailing-list)?

The mode operation is really easy because NodecLib does not depend on other classes from the TDB library. Moreover, this move operation does not introduce any issue because TDB depends on ARQ.

Also, I have tested the TSV serializer/unserializer with a small dataset and added a tiny test into TestResultSetFormat.

      was (Author: laurent.pellegrino):
    Here a patch that provide the TSVInput class. 

I have updated the classes that provide input reader by mimicking the existing methods (seeResultSetFactory). However, this patch implies to move the NodecLib class from the TDB library to the ARQ library in order to avoid to copy the code. Indeed, TSVOuput serializes the nodes by using FmtUtils.stringForNode(n) and it seems there is no method to do the reverse operation into the ARQ library (see my post on the mailing-list)?

The mode operation is really easy because NodecLib does not depend on other classes from the TDB library. Moreover, this move operation does not introduce any issue because TDB depends on ARQ.

Also, I have tested the TSV serializer/unserializer with a small dataset and added a tiny test into TestResultSetFormat.
  
> Provide TSVInput reader
> -----------------------
>
>                 Key: JENA-69
>                 URL: https://issues.apache.org/jira/browse/JENA-69
>             Project: Jena
>          Issue Type: New Feature
>          Components: ARQ, TDB
>            Reporter: Laurent Pellegrino
>            Priority: Blocker
>              Labels: arq, resultset, tdb, tsv, tsvinput
>         Attachments: tsvinput-r1128173-version1.patch
>
>
> As stated into the mailing-list it is possible to serialize a ResultSet by using the TSV format. However, it is not possible to unserialize it (there is no TSVInput implementation).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira