[#SES-245] Binary table/tuple results format doesn't support long string values

Issue Details [XML]

Key:	SES-245
Type:	Improvement
Status:	Closed
Resolution:	Fixed
Priority:	Major
Assignee:	Arjohn Kampman
Reporter:	Arjohn Kampman
Votes:	0
Watchers:	0

Operations

If you were logged in you would be able to see more operations.

Sesame

Binary table/tuple results format doesn't support long string values

Created: 28/Feb/06 12:00 PM Updated: 18/Sep/08 04:43 AM

Component/s:

HTTP Server

Affects Version/s:

2.0-alpha-3, 2.0-alpha-2, 2.0-alpha-1, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2, 1.2-RC2, 1.2-RC1, 1.1.3, 1.1.2, 1.1.1

Fix Version/s:

2.0-beta2

Issue Links:

Dependency

This issue depends on:
	~~SES-244~~ non-standard UTF-8 encoding used for ...

Description

The reader and writer for Sesame's binary tuple/table results format are based on java.io.DataInputStream and java.io.DataOutputStream. The methods offered in these classes for reading and writing strings are limited to 65536 bytes for the UTF-8 encoded string. This is likely to be too limited as the RDF stores (and Java in general) can store strings consisting of 2^31 characters, consisting of 2 bytes per character.

All

Comments

Change History

Sort Order:

[ Permlink ]

Comment by Arjohn Kampman [28/Feb/07 07:49 PM]

Format now uses 32-bit integers to specifiy the length of (UTF-8 encoded) strings. Format version number has been updated to '2'. Fix available in revision 2442:
http://src.aduna-software.org/viewvc/org.openrdf/?rev=2442&view=rev