[IGNITE-15269] Get rid of JSON code in configuration module

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha2
• Fix Version/s: 3.0.0-alpha3
• Labels: iep-55 ignite-3
• Epic Link: Configuration
• Assignee: Kirill Tkalenko
• Reporter: Ivan Bessonov
• Reviewer: Ivan Bessonov
• Created: 06/Aug/21 10:46
• Updated: 13/Aug/21 07:41
• Resolved: 13/Aug/21 07:41

Description

Right now we have a duplicated logic in configuration framework for HOCON and JSON text representations.

Given that HOCON is the extension of JSON format, it can both parse and produce valid JSON representation. This means that classes like JsonConfigurationVisitor and others are not required anymore and can be deleted.

There's only one problem here: REST code that uses JSON conversion is not covered with tests. We have to be sure that it won't be broken after the change. Maybe write our own tests.

 

Issue Links

• links to: GitHub Pull Request #267