Is it possible to Serialise this Schema Object?

[samiem41]

Schema v7Schema = schemaLoaderBuilder.build().load().build();

We deal with huge draft7 schemas which takes considerable amount of time to be converted into Schema Java Object which can they be used for validation purposes. We wanted to optimize this process of creation for this Schema Object by keeping serialized version of Schema object in the cache and then reading them quickly and derserializing it.

However, serialising the Schema Object using gson library was ending up with this kind of error:
java.lang.IllegalArgumentException: Class org.everit.json.schema.ReferenceSchema declares multiple JSON fields named 'title'; conflict is caused by fields org.everit.json.schema.ReferenceSchema#title and org.everit.json.schema.Schema#title

Just wanted to check if this is something even feasible for this complex Schema object or not?

[erosb]

However, serialising the Schema Object using gson library

Using gson looks like a quite over-engineered solution. If you want to convert a Schema object into a json string then just call its Schema.toString() method.

[samiem41]

Sure, we can definitely get the stringified content using toString() however, would it be possible to deserialize that string into Schema object ?

Basically, I am trying to avoid this step: ( as its extremely expensive ~ 20 seconds )
Schema v7Schema = schemaLoaderBuilder.build().load().build();

[erosb]

Maybe you could just keep the Schema object itself in memory, for the application's lifecycle. It is immutable and safe to reuse.

[samiem41]

Thanks for answering quickly. :)

That's fair @erosb , however this Schema objects are quite big in nature & it keeps on growing with the number of schemas that we need to retain / pod ( business requirement - close to 25K JSON schemas get cached )

Here is my idea:

I want to keep this serialized copy of Schema Object in a fast cache , so that it can be retrieved by all the pods which are part of my cluster on demand, so that I don't need to burn my heap on all of them & can potentially claim the memory ( rather than keeping it till lifetime )

Basically, I am trying to avoid this step: ( as its extremely expensive ~ 20 seconds )
Schema v7Schema = schemaLoaderBuilder.build().load().build();
If I reclaim the memory by removing the object from heap, I would have to take a hit of SLA if this same schema needs to be constructed again from scratch.

[erosb]

Hello @samiem41 please take a look at PR #525 thanks