Camel-Olingo2: The metadata constraints '[Nullable=true, MaxLength=16]' do not match the literal

Question

I'm using camel-olingo2 component for query SAP SuccessFactors on ODataV2 endpoints. The route is:

        from("direct:start")
            .to(olingoEndpoint)
            .process(paging)
            .loopDoWhile(simple("\${header.CamelOlingo2.\$skiptoken} != null"))
            .to(olingoEndpoint)
            .process(paging)
            .end()

Paging processor is:

    Processor paging = new Processor() {
    @Override
    void process(Exchange g) throws Exception {
        ODataDeltaFeed feed = g.in.getMandatoryBody(ODataDeltaFeed)
        if (consumer) feed.getEntries().forEach(consumer)
        String next = feed.getFeedMetadata().getNextLink()
        if (next) {
            List<NameValuePair> lst = URLEncodedUtils.parse(new URI(next), StandardCharsets.UTF_8)
            NameValuePair skiptoken = lst.find { it.name == "\$skiptoken" }
            g.out.headers."CamelOlingo2.\$skiptoken" = skiptoken.value
        } else {
            g.out.headers.remove("CamelOlingo2.\$skiptoken")
        }
    }
}

Everything is OK with most of entities but there are fields for several entities with wrong nullability or data length so I got:

Caused by: org.apache.olingo.odata2.api.edm.EdmSimpleTypeException: The metadata constraints '[Nullable=true, MaxLength=16]' do not match the literal 'Bor.Kralja Petra I.16'.
at org.apache.olingo.odata2.core.edm.EdmString.internalValueOfString(EdmString.java:62)
at org.apache.olingo.odata2.core.edm.AbstractSimpleType.valueOfString(AbstractSimpleType.java:91)
at org.apache.olingo.odata2.core.ep.consumer.JsonPropertyConsumer.readSimpleProperty(JsonPropertyConsumer.java:236)
at org.apache.olingo.odata2.core.ep.consumer.JsonPropertyConsumer.readPropertyValue(JsonPropertyConsumer.java:169)

In documentation for Olingo2 camel component I cannot find the way to disable this checking or other walkaround. Can you suggest me the good way? Please do not recommend server-side data changes, ex metadata modifiyng, it's out of scope for this task.

I have plan B: to use HTTPS requests with JSON parsing, it's quite simple but little boring.