hjtran commented on PR #32740: URL: https://github.com/apache/beam/pull/32740#issuecomment-2426549199
Hey all, thanks for the reviews! Here's an example with AggregationSum <img width="1728" alt="image" src="https://github.com/user-attachments/assets/2be7dd74-a49b-4143-b767-22df8b887372";> ``` The results of this example are taken from the Apache Beam Playground cache. 2024-10-02 15:17:04,163 [INFO] Using Any for unsupported type: typing.Sequence[~T] 2024-10-02 15:17:04,388 [INFO] Missing pipeline option (runner). Executing pipeline using the default runner: DirectRunner. 2024-10-02 15:17:04,574 [WARNING] Dependencies required for Interactive Beam PCollection visualization are not available, please use: `pip install apache-beam[interactive]` to install necessary dependencies to enable all data visualization features. 2024-10-02 15:17:04,574 [WARNING] You cannot use Interactive Beam features when you are not in an interactive environment such as a Jupyter notebook or ipython terminal. 2024-10-02 15:17:04,888 [INFO] Creating state cache with size 104857600 55 ``` - The first INFO message it's not really even clear which transform is causing this. - The second message is a bit distracting imo since I don't think you can even use a different runner in Playground and the user is likely here just to learn about combiners. - The first warning message is again imo a bit distracting as the likely user probably isn't interested in this interactive visualization from beam - The second warning message is again not relevant - The final INFO message is hard for a user to even know what it's referring to The final logged "55" is what actually relates to the example, but it is dwarfed by the irrelevant messages that come before it. I've gotten feedback that it's hard to tell that there's any output related to the example. I've been using Playground as a way to teach people the Beam model and abstractions and I think this kind of logging makes it a lot harder to do that. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
