[Bigdata-developers] FW: [bigdata(r)] #141: SPO.hashCode() always returns zero (linear scaling in default graph queries)

[Bryan T. <br...@sy...>]

All,

Matt just pointed out a bug introduced by the XSD inlining.  The bug primarily effects quads query and would have been introduced in 0.83.0. This is fixed in the trunk.  The issue is inline below.

Thanks,
Bryan 

-----Original Message-----
From: bigdata(r) [mailto:no...@so...] 
Sent: Thursday, August 12, 2010 12:50 PM
Subject: Re: [bigdata(r)] #141: SPO.hashCode() always returns zero (linear scaling in default graph queries)

#141: SPO.hashCode() always returns zero (linear scaling in default graph
queries)
-----------------------------------+------------------------------------
-----------------------------------+----
  Reporter:  thompsonbry           |       Owner:  thompsonbry           
      Type:  defect                |      Status:  closed                
  Priority:  critical              |   Milestone:                        
 Component:  Bigdata RDF Database  |     Version:  BIGDATA_RELEASE_0_83_2
Resolution:  fixed                 |    Keywords:                        
-----------------------------------+------------------------------------
-----------------------------------+----
Changes (by thompsonbry):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Bug fix to SPO.hashCode() per
 https://sourceforge.net/apps/trac/bigdata/ticket/141.

 The historical behavior of SPO.hashCode() was based on the int64 term  identifiers. Since the hash code is now computed from the int32 hash codes  of the (s,p,o) IV objects, the original bit math was resulting in a hash  code which was always zero (any 32 bit value shifted right by 32 bits is  zero).  The change was to remove the bit math.

 Committed revision 3441.

--
Ticket URL: <http://sourceforge.net/apps/trac/bigdata/ticket/141#comment:1>
bigdata(r) <http://www.bigdata.com/blog>
bigdata(r) is a scale-out storage and computing fabric supporting optional transactions, very high concurrency, and very high aggregate IO rates.