No validator for type <blank>

[bruth]

Error is raised here. My guess is that changes occurred in the data model files that introduced a new type that is not being accounted for.

[bruth]

@murphyke @aaron0browne Any insight on this?

[murphyke]

@bruth No but I can look into it

[murphyke]

@bruth I did a visual diff of the 2.1 and 2.2 directories in master and didn't see any weirdness with type in the schema directories. I know Aaron started making some disruptive changes, but those aren't on master yet. So some debugging will be required.

[bruth]

Thanks for looking at it. It is possible the person who reported it was using 2.0.0. I need to follow up on that point. Otherwise I will commence the debugging.

On Mar 31, 2016, at 10:49 AM, Kevin Murphy notifications@github.com wrote:

@bruth I did a visual diff of the 2.1 and 2.2 directories in master and didn't see any weirdness with type in the schema directories. I know Aaron started making some disruptive changes, but those aren't on master yet. So some debugging will be required.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

[burrowse]

@bruth
We are now seeing this issue after the recent implementation of the BigInteger type in the data models service.

See example of error:

2021/05/20 14:22:44 no validator for type 'biginteger'
2021/05/20 14:22:44 no validator for type 'biginteger'
2021/05/20 14:22:44 no validator for type 'biginteger'
2021/05/20 14:22:44 no validator for type 'biginteger'

Digging around I think the change needs to be made to validators.go. And an attempt is made here:PEDSnet@2a07248

Not knowing enough about how all these things are pieced together. I'm not sure what other changes need to be made. Do a new set of binaries need to be created in infomodels?