Hi Beam Team,
Can somebody help me understand what are the factors behind SDK Harness
memory usage? My first guess is that the SDK Harness memory usage depends
on:
1. User code (i.e. DoFns)
2. Bundle size
Basically, the maximum memory usage an SDK Harness needs is however much
memory it takes
Merged it. Please be on the lookout for bugs I have introduced, since they
could result in issues slipping through the cracks.
On Wed, Dec 7, 2022 at 3:31 PM Kenneth Knowles wrote:
> OK I did my best in https://github.com/apache/beam/pull/24585
>
> Yet another thought I had: Do we really need
<<< text/html; charset=UTF-8: Unrecognized >>>
We could probably add a lint that rejects the spelling `task("` pretty
easily that would catch most of these.
On Thu, Dec 8, 2022 at 11:34 AM Luke Cwik via dev
wrote:
> I have found the Gradle build reports very useful to enumerate
> deprecations and an easier thing to look at over the command
I have found the Gradle build reports very useful to enumerate deprecations
and an easier thing to look at over the command line output.
On Thu, Dec 8, 2022 at 8:26 AM Damon Douglas via dev
wrote:
> Thank you, Kerry, for your kind and encouraging words!
>
> Kenn, I wondered as well whether
Thank you, Kerry, for your kind and encouraging words!
Kenn, I wondered as well whether there exist proactive options. I know
that gradle will warn of soon-to-be deprecated syntax in the build.gradle
files when executing gradle tasks on the command-line. Perhaps we can
start there. Not to
This is your daily summary of Beam's current high priority issues that may need
attention.
See https://beam.apache.org/contribute/issue-priorities for the meaning and
expectations around issue priorities.
Unassigned P1 Issues:
https://github.com/apache/beam/issues/24415 [Bug]: Cannot find
