The new tagging also helps if they identify the runner separately (flink,
spark, google-cloud-dataflow, etc.)
On Tue, Jul 9, 2019, 10:16 AM Rui Wang wrote:
> I also agree `apache-beam` + `python` or `java` is an option. I can try to
> tag SO questions by this option when there is a need to see h
I also agree `apache-beam` + `python` or `java` is an option. I can try to
tag SO questions by this option when there is a need to see how it will
work.
Thanks for all of your participation to this discussion!
-Rui
On Tue, Jul 9, 2019 at 9:49 AM Kenneth Knowles wrote:
> With the new filtering
With the new filtering UI, I think separate `apache-beam` tag and `python`
or `java` tag seems perfect. No users are using apache-beam-java,
apache-beam-python, or apache-beam-go so I don't think we need to make it
up.
Kenn
On Tue, Jul 9, 2019 at 9:38 AM Pablo Estrada wrote:
> I am able to crea
I am able to create the tags if we decide to go that way:)
I have seen users relying on the 'python' tag, along with the 'apache-beam'
tag to specify an SDK. Maybe that's enough? What advantage would come from
a dedicated beam tag?
Perhaps users will be more easily accustomed to use the apache-be
That sounds like a good idea to me.
On Wed, Jul 3, 2019 at 10:45 AM Rui Wang wrote:
> Hi Community,
>
> When reading apache-beam related questions in stackoverflow, it happens
> that some questions only mention version number(e.g. 2.8.0) but not mention
> which SDK related. Sometimes I can tell
Hi Community,
When reading apache-beam related questions in stackoverflow, it happens
that some questions only mention version number(e.g. 2.8.0) but not mention
which SDK related. Sometimes I can tell which SDK it is from code snippets,
sometime I cannot as there is no code snippet. So in order t
