Open chuwy opened 6 years ago
Actually, just found out that we already have possible fix: https://github.com/snowplow/snowplow/issues/3767
this is just a qa check with #174
were you able to check this @oguzhanunlu ?
No I haven't tested this @BenFradet
Could you please do it @oguzhanunlu, before starting with Iglu sprint. Just close if test is successful
Hey @BenFradet @chuwy , I checked and we get this error for 10000000000000000000000000000000000000000000000000
.
That is quite sad. I think we'll have to prioritize JSON Schema validator refactoring in Iglu Client, I believe problem is there.
Since this isn't directly related to Snowplow Mini, I removed this issue from the release milestone.
The last version to contain
public NumericNode numberNode(BigInteger v)
is 2.8.11.6. From 2.9.0 this function becomes
public ValueNode numberNode(BigInteger v)
So we do have a binary incompatibility in Stream Enrich jar, probably related to https://github.com/snowplow/snowplow/issues/3744.
I'm actually 99% sure that problem lays not in Snowplow Mini (probably in Stream Enrich), but it is the only place where we can easily test and reproduce it, so leaving here.
Having very big numbers as JSON Schema's
maximum
(e.g. 10000000000000000000000000000000000000000000000000) our users get following error:From internal conversation:
Snowplow Mini 0.4.0 (Stream Enrich 0.12.0) worked fine with these big integers.