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
Scala Hadoop Shred: bump Iglu Scala Client to 0.3.0 #1221
Comments
This is one of the most painful (albeit rare) failure states we have currently... |
Should this ticket move to iglu-scala-client? It seems like the best place to make the change is in the Resolver class itself. |
Completely agree! |
fblundun
changed the title
Scala Hadoop Shred: maintain a cache of missing schemas
Scala Hadoop Shred: bump Iglu Scala Client to 0.3.0
Jul 28, 2015
fblundun
added a commit
that referenced
this issue
Aug 12, 2015
fblundun
added a commit
that referenced
this issue
Aug 17, 2015
fblundun
added a commit
that referenced
this issue
Aug 19, 2015
fblundun
added a commit
that referenced
this issue
Aug 19, 2015
fblundun
added a commit
that referenced
this issue
Aug 24, 2015
fblundun
added a commit
that referenced
this issue
Aug 26, 2015
fblundun
added a commit
that referenced
this issue
Sep 25, 2015
fblundun
added a commit
that referenced
this issue
Sep 25, 2015
alexanderdean
pushed a commit
that referenced
this issue
Jan 14, 2016
chuwy
pushed a commit
to snowplow/snowplow-rdb-loader
that referenced
this issue
Sep 5, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
That way, we don't have to do an expensive resolution process on every single event which is referencing a non-existent schema
The text was updated successfully, but these errors were encountered: