You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by "robertwb (via GitHub)" <gi...@apache.org> on 2025/03/19 19:14:52 UTC

[I] [Bug]: Docker worker containers are confusingly named. [beam]

robertwb opened a new issue, #34350:
URL: https://github.com/apache/beam/issues/34350

   ### What happened?
   
   Names like apache/beam_python3.12_sdk:2.63.0 seem to imply that these provide a fully working SDK usable for developing Beam pipelines. We should clearly indicate in the name that these are *worker* images whose sole intent is use by workers for distributed execution of pipelines. 
   
   ### Issue Priority
   
   Priority: 2 (default / most bugs should be filed as P2)
   
   ### Issue Components
   
   - [ ] Component: Python SDK
   - [ ] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [ ] Component: IO connector
   - [ ] Component: Beam YAML
   - [ ] Component: Beam examples
   - [ ] Component: Beam playground
   - [ ] Component: Beam katas
   - [ ] Component: Website
   - [ ] Component: Infrastructure
   - [ ] Component: Spark Runner
   - [ ] Component: Flink Runner
   - [ ] Component: Samza Runner
   - [ ] Component: Twister2 Runner
   - [ ] Component: Hazelcast Jet Runner
   - [ ] Component: Google Cloud Dataflow Runner


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug]: Docker worker containers are confusingly named. [beam]

Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn commented on issue #34350:
URL: https://github.com/apache/beam/issues/34350#issuecomment-2839070528

   It appears 2.65.0 milestone added due to the issue gets re-opened. Removing it for now


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug]: Docker worker containers are confusingly named. [beam]

Posted by "liferoad (via GitHub)" <gi...@apache.org>.
liferoad commented on issue #34350:
URL: https://github.com/apache/beam/issues/34350#issuecomment-2822864561

   This will introduce breaking changes. I am not sure it is worth doing it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug]: Docker worker containers are confusingly named. [beam]

Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn commented on issue #34350:
URL: https://github.com/apache/beam/issues/34350#issuecomment-3564289382

   updated java/python/go dockerhub image description, e.g.
   
   > Worker harness container images for the Apache Beam Java SDK on Java 8.
   
   Close this issue for now.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug]: Docker worker containers are confusingly named. [beam]

Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn commented on issue #34350:
URL: https://github.com/apache/beam/issues/34350#issuecomment-3564268794

   At least we can modify the description in 
   
   https://hub.docker.com/repository/docker/apache/beam_python3.12_sdk/general
   
   to make it clear it is primarily used by worker. However there are many hard coded places rely on current naming (both internally in Dataflow and on Beam), and presumably Beam users' CI/CD can also have this issue.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug]: Docker worker containers are confusingly named. [beam]

Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn commented on issue #34350:
URL: https://github.com/apache/beam/issues/34350#issuecomment-3250005020

   This Issue is marked as Beam 3 - Milestone 1: No Code and ML focus. Please help us burning down the open blocker tasks.
   
   * If this issue is solved, close it. If it is obsolete, close as not planned. If it is no longer necessary for Beam 3, move it out of the Milestone.
   
   * If the work is pending, please be reminded that Milestone 1 is targeted for completion by Beam 2.72 cut (Feb 18, 2026)
   
   * If this issue involves multiple milestones (e.g. remove a public API should first mark it as deprecated, scoped in Milestone 1; then finally remove it in Beam 3 release candidate, scoped in Milestone 3) and Milestone 1 portion has completed, consider move the Issue to Milestone 3.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug]: Docker worker containers are confusingly named. [beam]

Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn closed issue #34350: [Bug]: Docker worker containers are confusingly named.
URL: https://github.com/apache/beam/issues/34350


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug]: Docker worker containers are confusingly named. [beam]

Posted by "liferoad (via GitHub)" <gi...@apache.org>.
liferoad closed issue #34350: [Bug]: Docker worker containers are confusingly named.
URL: https://github.com/apache/beam/issues/34350


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug]: Docker worker containers are confusingly named. [beam]

Posted by "robertwb (via GitHub)" <gi...@apache.org>.
robertwb commented on issue #34350:
URL: https://github.com/apache/beam/issues/34350#issuecomment-2822777446

   Thanks for updating the docs. I would propose we rename the containers themselves, e.g. as `apache/beam_python3.12_worker:2.63.0` to forestall any confusion for people who don't happen to come across that page of the documentation. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug]: Docker worker containers are confusingly named. [beam]

Posted by "robertwb (via GitHub)" <gi...@apache.org>.
robertwb commented on issue #34350:
URL: https://github.com/apache/beam/issues/34350#issuecomment-2822997309

   I was proposing doing it only for releases going forward. Not worth it to
   change old images that are already releaded (and possibly referenced
   widely).
   
   On Tue, Apr 22, 2025 at 6:53 PM liferoad ***@***.***> wrote:
   
   > This will introduce breaking changes. I am not sure it is worth doing it.
   >
   > —
   > Reply to this email directly, view it on GitHub
   > <https://github.com/apache/beam/issues/34350#issuecomment-2822864561>, or
   > unsubscribe
   > <https://github.com/notifications/unsubscribe-auth/AADWVAMZ5OKLS5VCCKR7EE3223XCTAVCNFSM6AAAAABZLVH7WWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRSHA3DINJWGE>
   > .
   > You are receiving this because you modified the open/close state.Message
   > ID: ***@***.***>
   > *liferoad* left a comment (apache/beam#34350)
   > <https://github.com/apache/beam/issues/34350#issuecomment-2822864561>
   >
   > This will introduce breaking changes. I am not sure it is worth doing it.
   >
   > —
   > Reply to this email directly, view it on GitHub
   > <https://github.com/apache/beam/issues/34350#issuecomment-2822864561>, or
   > unsubscribe
   > <https://github.com/notifications/unsubscribe-auth/AADWVAMZ5OKLS5VCCKR7EE3223XCTAVCNFSM6AAAAABZLVH7WWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRSHA3DINJWGE>
   > .
   > You are receiving this because you modified the open/close state.Message
   > ID: ***@***.***>
   >
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org