[Bug]: PubsubMessage should be renamed to PubSubMessage to reduce confusion

[aaltay]

What happened?

Beam has PubsubMessage PubSubMessage PubsubMessages. The use is inconsistent and confusing. It would be good to use a standard naming scheme. (PubSubMessage seems to be the correct version based on the product name.)

This might require a breaking change, and if that it is the case we might need to hold on until the next major version.

Issue Priority

Priority: 3

Issue Component

Component: io-java-gcp

[Amar3tto]

PubSubMessage naming will be not consistent, because:

1. We have PubsubIO and other classes (not PubSubIO)
2. com.google.pubsub.v1 has PubsubMessage class.

PubsubMessage naming also wouldn't be consistent, because:

1. com.google.cloud.pubsublite.proto has PubSubMessage
2. RunnerApi has PubSubReadPayload and other classes

[Amar3tto]

FYI @aaltay

[aaltay]

Thank you for the analysis @Amar3tto. I think this is still an inconsistency and an issue. But I understand your point, it may not be feasible to address this. In that case we can close this as won't fix / infeasible.