Wrong Encoding Of Property using Oracle Big Data Spatial and Graph
Last updated on MARCH 15, 2016
Applies to:Oracle Big Data Spatial and Graph - Version 1.1 and later
With Oracle Big Data Spatial and Graph seeing wrong encoding of property if using in-memory analytics on Hadoop (ServerInstance remoteInstance = Pgx.getInstance(gpxUrl);), then pgxVertex.getProperty() returns wrong encoding of string.
If we start localInstance:
then encoding is correct.
One example property value that got wrong encoding over the remote instance is a music string in Russian:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms