-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix BigInt binary incompatibility #177
Comments
Actually, just found out that we already have possible fix: snowplow/snowplow#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 |
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 snowplow/snowplow#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.
The text was updated successfully, but these errors were encountered: