Skip to content
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

Issue 1786 - 'messageId' and 'publishTime' should not be published #1795

Merged
merged 2 commits into from
Jul 1, 2019

Conversation

LGLO
Copy link
Contributor

@LGLO LGLO commented Jun 29, 2019

Nor should be 'messageId' be required when creating PubSubMessage for publishing.

Purpose

Improve Scala and Java API - don't require redundant parameter
Improve compliance with Google Cloud PubSub HTTP API - don't send fields that shouldn't be sent.

References

References #1786

Changes

  • Added Scala and Java api that doesn't require 'messageId'
  • Do not encode 'messageId' and 'publishTime' when sending JSON body

Background Context

I wanted to create separate case class for publishing PubSub message but I went in a direction to not break code.

If for 1.1 we can break source and binary compatibility, I'd like to contribute other change.

…r required when creating PubSubMessage for publishing.
Copy link
Member

@2m 2m left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. And MiMa says it does not break BC!

@2m 2m added this to the 1.1.0 milestone Jul 1, 2019
@ennru ennru merged commit 977218e into akka:master Jul 1, 2019
@ennru
Copy link
Member

ennru commented Jul 1, 2019

Thank you for your first contribution! Keep them coming!

cheleb pushed a commit to cheleb/alpakka that referenced this pull request Jul 5, 2019
…lished (akka#1795)

* akka#1786 - 'messageId' and 'publishTime' should not be published nor required when creating PubSubMessage for publishing.
@LGLO LGLO deleted the issue-1786-message-id branch July 7, 2019 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants