[jira] [Updated] (BEAM-4688) Beam SQL should clean up resources upon termination of the pipeline
[ https://issues.apache.org/jira/browse/BEAM-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beam JIRA Bot updated BEAM-4688: Labels: stale-P2 (was: ) > Beam SQL should clean up resources upon termination of the pipeline > --- > > Key: BEAM-4688 > URL: https://issues.apache.org/jira/browse/BEAM-4688 > Project: Beam > Issue Type: New Feature > Components: dsl-sql >Reporter: Kenneth Knowles >Priority: P2 > Labels: stale-P2 > > Currently {{PubsubIO.read().fromTopic(...)}} always creates a subscription > that will never be deleted. Beam doesn't have an adequate model for cleanup > tasks, but relies on external orchestration to clean up such things. Beam SQL > can do this for LIMIT-bounded queries that actually do terminate. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (BEAM-4688) Beam SQL should clean up resources upon termination of the pipeline
[ https://issues.apache.org/jira/browse/BEAM-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beam JIRA Bot updated BEAM-4688: Labels: (was: stale-P2) > Beam SQL should clean up resources upon termination of the pipeline > --- > > Key: BEAM-4688 > URL: https://issues.apache.org/jira/browse/BEAM-4688 > Project: Beam > Issue Type: New Feature > Components: dsl-sql >Reporter: Kenneth Knowles >Priority: P3 > > Currently {{PubsubIO.read().fromTopic(...)}} always creates a subscription > that will never be deleted. Beam doesn't have an adequate model for cleanup > tasks, but relies on external orchestration to clean up such things. Beam SQL > can do this for LIMIT-bounded queries that actually do terminate. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (BEAM-4688) Beam SQL should clean up resources upon termination of the pipeline
[ https://issues.apache.org/jira/browse/BEAM-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beam JIRA Bot updated BEAM-4688: Priority: P3 (was: P2) > Beam SQL should clean up resources upon termination of the pipeline > --- > > Key: BEAM-4688 > URL: https://issues.apache.org/jira/browse/BEAM-4688 > Project: Beam > Issue Type: New Feature > Components: dsl-sql >Reporter: Kenneth Knowles >Priority: P3 > Labels: stale-P2 > > Currently {{PubsubIO.read().fromTopic(...)}} always creates a subscription > that will never be deleted. Beam doesn't have an adequate model for cleanup > tasks, but relies on external orchestration to clean up such things. Beam SQL > can do this for LIMIT-bounded queries that actually do terminate. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (BEAM-4688) Beam SQL should clean up resources upon termination of the pipeline
[ https://issues.apache.org/jira/browse/BEAM-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Pilloud updated BEAM-4688: - Priority: P4 (was: P3) > Beam SQL should clean up resources upon termination of the pipeline > --- > > Key: BEAM-4688 > URL: https://issues.apache.org/jira/browse/BEAM-4688 > Project: Beam > Issue Type: New Feature > Components: dsl-sql >Reporter: Kenneth Knowles >Priority: P4 > > Currently {{PubsubIO.read().fromTopic(...)}} always creates a subscription > that will never be deleted. Beam doesn't have an adequate model for cleanup > tasks, but relies on external orchestration to clean up such things. Beam SQL > can do this for LIMIT-bounded queries that actually do terminate. -- This message was sent by Atlassian Jira (v8.3.4#803005)