https://github.com/pjfanning/fury-scala-test

Test using Fury serialization with Scala classes
https://github.com/pjfanning/fury-scala-test

fury scala serialization

Last synced: 29 days ago
JSON representation

Test using Fury serialization with Scala classes

• Host: GitHub
• URL: https://github.com/pjfanning/fury-scala-test
• Owner: pjfanning
• License: apache-2.0
• Created: 2023-10-24T19:38:21.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2023-10-29T09:19:47.000Z (about 1 year ago)
• Last Synced: 2024-10-14T11:29:35.537Z (2 months ago)
• Topics: fury, scala, serialization
• Language: Scala
• Homepage:
• Size: 22.5 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# fury-scala-test

 

Test using [Fury](https://github.com/alipay/fury) serialization with Scala classes.

It is recommended that you read the [Fury Scala Guide](https://github.com/alipay/fury/blob/main/docs/guide/scala_guide.md).

Ideally, users should not disable class registration because this is an important protection against

[Remote Code Execution](https://en.wikipedia.org/wiki/Arbitrary_code_execution).

The problem is that you need to register a number of internal Scala classes when using features like

* Options

* Collections

* Enumerations

* Objects (Scala 2.13+)

This is because Fury relies on internal Scala class serialization and this exposes the innards of the Scala

class representation. Have a look at the test cases in this project to see some examples.

Fury has not been optimized for Scala class uses. There are open issues but it could be a big undertaking to create optimized serializers/deserailizers

for Scala collections, etc.