You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Rupert Westenthaler (Commented) (JIRA)" <ji...@apache.org> on 2012/01/10 12:12:39 UTC

[jira] [Commented] (CLEREZZA-670) Integer MAX/MIN value overflow in Comparator of the RDF JSON serializer

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

Rupert Westenthaler commented on CLEREZZA-670:
----------------------------------------------

Hi all, there seem to be additional issues. I will do some additional debugging and provide further updates.
                
> Integer MAX/MIN value overflow in Comparator of the RDF JSON serializer
> -----------------------------------------------------------------------
>
>                 Key: CLEREZZA-670
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-670
>             Project: Clerezza
>          Issue Type: Bug
>          Components: rdf.serialize
>            Reporter: Rupert Westenthaler
>              Labels: rdf/json
>         Attachments: CLEREZZA-670_rdf.rdfjson.int_value_overflow_in_subject_comparator
>
>
> The implementation of the SUBJECT_COMPARATOR within the RdfJsonSerializingProvider sometimes encounters an int MAX/MIN value overflow.
> In such cases the compare method erroneously returns an 
>  * negative value - on a max value overflow or an
>  * positive value - on a min value overflow.
> what causes the Triple array used for the serialization not being correctly sorted. In such cases subjects do appear multiple times within the generated json output.
> To solve this one needs to replace the substraction of "hashA" from "hashB" with a boolean check that returns a -1/+1.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira