-
Notifications
You must be signed in to change notification settings - Fork 156
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
[FOLLOWUP][PR514] Update to use the newer Kryo 5.5.0 #747
base: develop
Are you sure you want to change the base?
Conversation
Registration is required by default in Kryo5: https://github.com/EsotericSoftware/kryo/wiki/Migration-to-v5#configuration-changes
This reverts commit 5c8310d.
FYI: @nicknezis, @johnynek, @regadas |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #747 +/- ##
===========================================
+ Coverage 91.85% 91.87% +0.01%
===========================================
Files 46 46
Lines 1425 1427 +2
Branches 28 35 +7
===========================================
+ Hits 1309 1311 +2
Misses 116 116
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
I have sent this mail to the chill-user list regarding this pull request: https://groups.google.com/g/chill-user/c/t5y8xBEjTXY Hi Chill maintainers / users, Is this twitter/chill project still active? The latest chill version depends on 4.0.2. Are there any chance for a new chill release which can include the following pull request? [FOLLOWUP][PR514] Update to use the newer Kryo 5.5.0: #747 We would like to migrate Apache Spark and Apache Livy to Kryo5 and we are blocked due to this missing pull request. Thanks in advance for any responses! |
Hey! Things have been a bit busy on my side, but I'll see if I can pick up things here in the coming days. Thanks for the poke and PR. 🙏 |
Thanks @regadas! |
Hi, I hope we can get this soon! It will be a good step forward to unify everything to Kryo 5. |
/* nb: thriftStructClass doesn't actually have type Class[T] it has type Class[_ <: T] | ||
* this lie is courtesy of the Kryo API | ||
* */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this comment should make be dropped now that the kryo api has changed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @eejbyfeldt,
Thanks for the review! I do not know the answer but if you think we may drop it, I am happy to implement it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where do you see this that kryo api has changed and we may drop this comment?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems to be that kryo went from Class[T]
api to a Class[_ <: T]
in kryo 5. So the comment basically consistent of two statements
nb: thriftStructClass doesn't actually have type Class[T] it has type Class[_ <: T]
and
this lie is courtesy of the Kryo API
My understanding was that the second statement is not longer true as there is no longer any lying going on (thrift and kryo 5 has matching apis). While the first statement is still true it does not really add any useful information anymore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While the first statement is still true it does not really add any useful information anymore.
Ok, I have just deleted it.
Hi @regadas, Sorry to trouble you, but did you a chance to take a look at this pull request? I wonder if you could tell me when can we expect a new chill release which include it? I really appreciate your reply in advance. |
Hello, is there still an intention to merge this PR? |
@@ -53,7 +53,7 @@ val sharedSettings = Seq( | |||
"org.scalacheck" %% "scalacheck" % "1.15.2" % "test", | |||
"org.scalatest" %% "scalatest" % "3.2.15" % "test", | |||
"org.scalatestplus" %% "scalatestplus-scalacheck" % "3.1.0.0-RC2" % "test", | |||
"com.esotericsoftware" % "kryo-shaded" % kryoVersion | |||
"com.esotericsoftware" % "kryo" % kryoVersion |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the description in the Kryo repository, it seems that com.esotericsoftware.kryo:kryo5:5.5.0
should be used?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @LuciferYang,
I agree with you! Yes, it would be better to use com.esotericsoftware.kryo:kryo5:5.5.0. I have switched to versionless kryo5 package to fix all mimaReport issues. We can switch back to this artifact any time before it would be merged. (I have mentioned this in the PR's description as well). Related commit: 0a6dda1
Currently the main issue is that we cannot go further with this PR because seems like there is no active maintainer of this twitter/chill repository. :-( I am just a simple contributor who opened this PR.
Hello ~ Is there any progress on this PR? |
Hi Chill team,
This is a follow up on this PR: #514
Main changes:
I have already tested with sbt test and all tests passed.