Last time it was decided to manually cleanup topics and postpone fix. My estimate was that we need to cleanup topics about every two months.
I think, we should cleanup topics manually to mitigate issue and prioritize proper fix. On Fri, May 24, 2019, 12:00 Pablo Estrada <pabl...@google.com> wrote: > Seems like Mikhail created https://issues.apache.org/jira/browse/BEAM-6610 > last > time ^^' > > On Fri, May 24, 2019 at 11:58 AM Kenneth Knowles <k...@apache.org> wrote: > >> Is there a jira tracking this? >> >> Kenn >> >> On Fri, May 24, 2019, 11:50 Andrew Pilloud <apill...@google.com> wrote: >> >>> This came up on the list in before in February: >>> >>> https://lists.apache.org/thread.html/38384d193e6f0af89f00a583e56cff93b18cfaebbf84e743eb900bc5@%3Cdev.beam.apache.org%3E >>> >>> We should be cleaning up topics, but it sounds like we aren't. >>> >>> Andrew >>> >>> On Fri, May 24, 2019 at 11:42 AM Pablo Estrada <pabl...@google.com> >>> wrote: >>> >>>> I've found a bunch of topics created by PubSub integration tests - they >>>> dont seem to be getting cleaned up, perhaps? >>>> >>>> 614 name: >>>> projects/apache-beam-testing/topics/integ-test-PubsubJsonIT-testSelectsPayloadContent- >>>> 614 name: >>>> projects/apache-beam-testing/topics/integ-test-PubsubJsonIT-testSQLLimit- >>>> 222 name: >>>> projects/apache-beam-testing/topics/integ-test-PubsubReadIT-testReadPublicData- >>>> >>>
