Bug 39642

GemStone/S 64 Bit

2.4.8, 2.4.7, 2.4.6, 2.4.5.1, 2.4.5, 2.4.4.8, 2.4.4.7, 2.4.4.6, 2.4.4.5, 2.4.4.4, 2.4.4.3, 2.4.4, 2.4.3, 2.4.2, 2.4.1, 2.4, 2.3.1.6, 2.3.1, 2.3, 2.2.5.4, 2.2.5.3, 2.2.5.2, 2.2.5.1, 2.2.5, 2.2.x, 2.2, 2.1.5, 2.1.4, 2.1.x, 2.0.x

All

n/a

Conversion causes hashed lookups on 8K Strings to fail

String hash in GemStone/S and GemStone/S 64 Bit v1.x uses the first 8K
bytes of the String, while in GemStone/S 64 Bit v2.x, the first 16K bytes
are used.

If a GSS or GS64 1.x repository contains Sets that include Strings over
8K, or dictionaries containing keys that are Strings over 8K, after conversion
to GS64 2.x, hashed lookups on these keys will fail.

Workaround

Avoid using Strings over 8K in Sets or as dictionary keys.  If you must do so, manually rebuild the Set or dictionary after conversion.


Last updated: 8/10/10