fix: PerfAPI codegen supports reading a feed that has a subset of the schema

[eduardoramirez]

Prevents the generated Perf API from throwing exceptions when used against an older version of the feed.

repro

• add a new field to schema
• re-generate the client
• populate the feed in test, test works
• release code to prod but don't update feed in prod yet. PerfAPI throws ArrayOutOfBounds on getter for field that isn't populated in feed but exists in schema

[Sunjeet]

Shouldn't these (Integer, Long, Float, and Double) return Integer.MIN_VALUE/Float.NaN etc.? Just going by the classic generated API-
In LongTypeAPI.java,

public Long getValueBoxed(int ordinal) {
        long l;
        if(fieldIndex[0] == -1) {
            l = missingDataHandler().handleLong("Long", ordinal, "value");
        ...

[eduardoramirez]

hmm interesting... in the actual generated code for something like MidInsightsDelegateLookupImpl the getter for primitive and boxed long looks like this:

    public long getMovieId(int ordinal) {
        ordinal = typeAPI.getMovieIdOrdinal(ordinal);
        return ordinal == -1 ? Long.MIN_VALUE : typeAPI.getAPI().getLongTypeAPI().getValue(ordinal);
    }

    public Long getMovieIdBoxed(int ordinal) {
        ordinal = typeAPI.getMovieIdOrdinal(ordinal);
        return ordinal == -1 ? null : typeAPI.getAPI().getLongTypeAPI().getValueBoxed(ordinal);
    }

[Sunjeet]

Hmm yeah looks like the defaults aren't consistently applied in the generated api

[Sunjeet]

Lets ship this improvement for now, I've tracked the fix for consistently applying defaults in this issue

[Sunjeet]

For Boolean this seems to match what the classic API would return