Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jena-dev@incubator.apache.org
Date: Thu, 16 Jun 2011 11:03:47 +0000 (UTC)
From: "Andy Seaborne (JIRA)" <jira@apache.org>
To: jena-dev@incubator.apache.org
Message-ID: 
 <1492728533.10617.1308222227347.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <630580316.423.1307367478969.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Reopened] (JENA-72) TSVInput infinite loop and optional
 binding values not handled
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JENA-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Seaborne reopened JENA-72:
-------------------------------

      Assignee: Paolo Castagna

Reopened - does not cope with (illegal) lines of wrong length yet.

> TSVInput infinite loop and optional binding values not handled
> --------------------------------------------------------------
>
>                 Key: JENA-72
>                 URL: https://issues.apache.org/jira/browse/JENA-72
>             Project: Jena
>          Issue Type: Bug
>          Components: ARQ
>            Reporter: Laurent Pellegrino
>            Assignee: Paolo Castagna
>              Labels: tsvinput
>         Attachments: JENA-72_ARQ_r1136132.patch
>
>
> TSVInput that has been proposed in JENA-69 contains two bugs:
> 1) When you attempt to read an empty ResultSet (i.e. a ResultSet that contain no binding) the code will enter in an infinite loop. This issue is really simple to solve.
> 2) Optional binding values are not supported, especially with the following ResultSet:
> (resultset (?a ?b ?c)
>     (row (?a 1) (?c 4))
>     (row (?a 1) (?b 2) (?c 3)))
> it will be serialized as:
> a....b....c
> 1..........4
> 1....2....3
> When we call tokenizer.next(), we get the next token. The problem is that we are not aware that the tokenizer has consumed two separators (\t), and we cannot detect that the value 4 is associated to the variable c.
> Any idea to handle it?

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