-
Notifications
You must be signed in to change notification settings - Fork 44
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
igluctl: fix false failure message in push command #313
Comments
Hey @oguzhanunlu, here's info you requested. Sorry - I didn’t give you enough information about this one. Basically "schema registry" here is ours Scala Repo Server. You can assemble a fatjar and try to upload schemas for example from Iglu Central to it. Another way would be to use Snowplow Mini for it, but I think former option should be much faster. So, just launch a Scala Registry on your local machine and everything else should be easy. |
Hey @oguzhanunlu, just as heads-up, could you please check all iglu subprojects with Scala 2.12 for this json4s-extraction bug? $ cd 0-common
$ grep -r extract\[ . ...or similar. We don't want to hit this in other places. |
@chuwy , trying to reproduce, I can't assemble scala repo server, I get |
@oguzhanunlu our compiled assets available at http://dl.bintray.com/snowplow/snowplow-generic/ (please fix the wiki page, also). Problem most likely that you have SBT 1.0, while repo uses very old one. To avoid issues like this, please use |
@chuwy Your first assumption is true. Problem is |
When overriding an existing schema with 0.3.0 we're getting this error:
But upload actually works. 0.2.0 works without problems. It seems that problem is that Igluctl cannot deserialize above message into ServerMessage and ends up in this branch.
@oguzhanunlu, I believe this is same kind of problem we had with JSON Schema AST. Was that method also called
asString
?The text was updated successfully, but these errors were encountered: