You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, events that consist of strings are serialized in Pravega using JavaSerializer. This is not ideal because 1) it is difficult to use in non-Java environments, 2) it adds unnecessary framing, and 3) it uses inefficient UTF-16 encoding.
A new commit has been added to Pravega to provide a UTF-8 serializer (pravega/pravega@78c5ade)
All samples that currently use JavaSerializer should be converted to use UTF8StringSerializer to demonstrate this best practice. Note that this is a breaking change as JavaSerializer is a different encoding than UTF-8.
Currently, events that consist of strings are serialized in Pravega using JavaSerializer. This is not ideal because 1) it is difficult to use in non-Java environments, 2) it adds unnecessary framing, and 3) it uses inefficient UTF-16 encoding.
A new commit has been added to Pravega to provide a UTF-8 serializer (pravega/pravega@78c5ade)
All samples that currently use JavaSerializer should be converted to use UTF8StringSerializer to demonstrate this best practice. Note that this is a breaking change as JavaSerializer is a different encoding than UTF-8.
For more information on why UTF-8 is preferred over UTF-16: http://utf8everywhere.org/
The text was updated successfully, but these errors were encountered: