-
Notifications
You must be signed in to change notification settings - Fork 642
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
Google Cloud Pub/Sub ordering key #2863 #2864
Conversation
At least one commit author ([email protected]) is not linked to a user. See https://help.github.com/en/articles/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user |
|
||
/** | ||
* Java API | ||
*/ | ||
def create(data: java.util.Optional[String], | ||
attributes: java.util.Optional[java.util.Map[String, String]], | ||
messageId: String, | ||
publishTime: Instant) = | ||
publishTime: Instant, | ||
orderingKey: java.util.Optional[String]) = | ||
new PubSubMessage(Option(data.orElse(null)), |
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.
To stay source compatible for Java users, you should add an overload for create
with the new orderingKey
and keep the existing create
with its signature. (Just as you did with PublishMessage
.)
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.
Done
Some Java code got reformatted again. Please run |
Formatted - both Java and Scala |
Our binary compatibility check complains now. https://github.com/akka/alpakka/runs/6154638614?check_suite_focus=true#step:6:530 |
Binary compatibility fixed |
Sorry, test compilation fixed |
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.
Thank you for going through all the quirks the binary compatibility promise requires.
LGTM.
#2863