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

What should Subscription.topic return when the topic is deleted #991

Closed
mziccard opened this issue May 6, 2016 · 2 comments
Closed

What should Subscription.topic return when the topic is deleted #991

mziccard opened this issue May 6, 2016 · 2 comments
Assignees
Labels
api: pubsub Issues related to the Pub/Sub API. type: question Request for information or clarification. Not an issue.

Comments

@mziccard
Copy link
Contributor

mziccard commented May 6, 2016

When a topic is deleted its subscriptions are not. For such subscriptions the topic field assumes the special value "_deleted-topic_:. What should Subscription.topic() getter return in this case? I see two main options (there surely are more).

  • Subscription.topic() returns null
  • Subscription.topic() returns TopicId.of("_deleted-topic_")

Regardless, this should be properly documented.
/cc @aozarov @eschapira to hear your thoughts

@mziccard mziccard added type: question Request for information or clarification. Not an issue. api: pubsub Issues related to the Pub/Sub API. labels May 6, 2016
@eschapira
Copy link

I suggest to have a singleton and add the method isDeleted to topic.
Returning null is semantically correct, but nulls are problematic and can
crash the app inadvertently.

The next question is what to do when any method is called on the deleted
topic. You can throw NotFound on the singleton, or just call the server,
but the error will be less intuitive.
On May 6, 2016 5:29 PM, "Marco Ziccardi" [email protected] wrote:

When a topic is deleted its subscriptions are not. For such subscriptions
the topic field assumes the special value "deleted-topic:. What should
Subscription.topic() getter return in this case? I see two main options
(there surely are more).

  • Subscription.topic() returns null
  • Subscription.topic() returns TopicId.of("deleted-topic")

Regardless, this should be properly documented.
/cc @aozarov https://github.com/aozarov @eschapira
https://github.com/eschapira to hear your thoughts


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#991

@mziccard
Copy link
Contributor Author

Closed with #984

github-actions bot pushed a commit that referenced this issue Jul 14, 2022
Source-Link: googleapis/synthtool@7336562
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-java:latest@sha256:d4b80feffe1579818cdc39466152e9de95789a193408506cd4a1ffbe8804dc00
github-actions bot pushed a commit that referenced this issue Jul 14, 2022
🤖 I have created a release *beep* *boop*
---


## [3.1.0](googleapis/java-aiplatform@v3.0.0...v3.1.0) (2022-07-13)


### Features

* **samples:** add remaining featurestore api samples ([#974](googleapis/java-aiplatform#974)) ([99ea51d](googleapis/java-aiplatform@99ea51d))
* **samples:** added all entity type samples ([#976](googleapis/java-aiplatform#976)) ([f496d8a](googleapis/java-aiplatform@f496d8a))


### Bug Fixes

* enable longpaths support for windows test ([#1485](https://github.com/googleapis/java-aiplatform/issues/1485)) ([#991](googleapis/java-aiplatform#991)) ([c41d394](googleapis/java-aiplatform@c41d394))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
github-actions bot pushed a commit that referenced this issue Sep 15, 2022
🤖 I have created a release *beep* *boop*
---


## [4.8.1](googleapis/java-dialogflow@v4.8.0...v4.8.1) (2022-09-06)


### Dependencies

* Update dependency com.google.cloud ([b0b6edd](googleapis/java-dialogflow@b0b6edd))
* Update dependency com.google.cloud ([3b9ae1d](googleapis/java-dialogflow@3b9ae1d))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
github-actions bot pushed a commit that referenced this issue Oct 4, 2022
- [ ] Regenerate this pull request now.

PiperOrigin-RevId: 477955264

Source-Link: https://togithub.com/googleapis/googleapis/commit/a724450af76d0001f23602684c49cd6a4b3a5654

Source-Link: https://togithub.com/googleapis/googleapis-gen/commit/4abcbcaec855e74a0b22a4988cf9e0eb61a83094
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiNGFiY2JjYWVjODU1ZTc0YTBiMjJhNDk4OGNmOWUwZWI2MWE4MzA5NCJ9
github-actions bot pushed a commit that referenced this issue Oct 5, 2022
🤖 I have created a release *beep* *boop*
---


## [3.1.2](https://togithub.com/googleapis/java-vision/compare/v3.1.1...v3.1.2) (2022-10-03)


### Documentation

* Update comments for image annotator OCR models ([#983](https://togithub.com/googleapis/java-vision/issues/983)) ([5c408fe](https://togithub.com/googleapis/java-vision/commit/5c408fef37777fb9899d9190b89896318f64d262))


### Dependencies

* Update dependency com.google.cloud:google-cloud-core to v2.8.12 ([#984](https://togithub.com/googleapis/java-vision/issues/984)) ([59f683c](https://togithub.com/googleapis/java-vision/commit/59f683ce1933b80a3b6256d9cf7f737c689ba711))
* Update dependency com.google.cloud:google-cloud-core to v2.8.13 ([#992](https://togithub.com/googleapis/java-vision/issues/992)) ([e0882e8](https://togithub.com/googleapis/java-vision/commit/e0882e83f338f4fb530a0c304dfa97bc1977fc56))
* Update dependency com.google.cloud:google-cloud-core to v2.8.14 ([#993](https://togithub.com/googleapis/java-vision/issues/993)) ([efd9c3f](https://togithub.com/googleapis/java-vision/commit/efd9c3fc7863dd4d819e9628d18bb43998f73ef8))
* Update dependency com.google.cloud:google-cloud-core to v2.8.18 ([#995](https://togithub.com/googleapis/java-vision/issues/995)) ([ead37cc](https://togithub.com/googleapis/java-vision/commit/ead37cc0cf1a1af8bb513d89153e30f06ea71f20))
* Update dependency com.google.cloud:google-cloud-core to v2.8.19 ([#1023](https://togithub.com/googleapis/java-vision/issues/1023)) ([ce23a3b](https://togithub.com/googleapis/java-vision/commit/ce23a3b2ae1c49a8df71fd66eda38f4845763cad))
* Update dependency com.google.cloud:google-cloud-shared-dependencies to v3.0.4 ([#1026](https://togithub.com/googleapis/java-vision/issues/1026)) ([71a4c70](https://togithub.com/googleapis/java-vision/commit/71a4c70366ab05af1307d914975aa43a2e5679a7))
* Update dependency com.google.cloud:google-cloud-storage to v2.12.0 ([#986](https://togithub.com/googleapis/java-vision/issues/986)) ([08262f8](https://togithub.com/googleapis/java-vision/commit/08262f87c3ce67eed973ccf9fc2f1f63525f5857))
* Update spring.version to v2.7.4 ([#994](https://togithub.com/googleapis/java-vision/issues/994)) ([8688790](https://togithub.com/googleapis/java-vision/commit/868879044e4296f524d6157d37b8601a5fc8dc4d))

---
This PR was generated with [Release Please](https://togithub.com/googleapis/release-please). See [documentation](https://togithub.com/googleapis/release-please#release-please).
suztomo pushed a commit that referenced this issue Feb 1, 2023
chore: remove check for flatten plugin

We have had the check for the flatten-maven-plugin in each
Cloud Java client repository. However, the behavior of the plugin
has been stable and its not each repository's responsibility to
assert the plugin's behavior. A new check is going to be added at
the googleapis/java-shared-config repository to assert the
plugin's behavior when we upgrade its version.
Source-Link: https://togithub.com/googleapis/synthtool/commit/9266ddc3b17fc15f34d2fb88ce8c5f1a4bfe64b0
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-java:latest@sha256:ae72564aa9c368b9ccd96f4af21f87889fd83b9e60635b80844deb5a2ccd08aa
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: pubsub Issues related to the Pub/Sub API. type: question Request for information or clarification. Not an issue.
Projects
None yet
Development

No branches or pull requests

2 participants