Hi all,
This week is the last one I'm working on Beam. It was a pleasure to contribute
to this project. I've learned a lot and had really good time with you guys!
The IT world is quite small so there is no goodbye. See you in the future in
the Web and another great projects!
You can find me at
Piotr,
Thanks a lot for your contributions, it was very useful and made Beam more
stable and finally even better! And it was always interesting to work with you
=)
I wish you all the best in your next adventure but feel free to get back to
Beam and contribute in any way as you can. It is alway
Yeah this looks like a Calcite issue. Thank you Kyle for marking
https://issues.apache.org/jira/browse/BEAM-9379 as a blocker!
On Tue, Dec 15, 2020 at 6:44 PM Robin Qiu wrote:
> No. That seems new to me. I can take a look. It says it's an issue on
> Calcite side.
>
> On Tue, Dec 15, 2020 at 5:13
I can guess that the same issues mentioned here probably will affect
the usability for people trying Beam's interactive SQL on Unbounded IO
too.
We should really take into account that the performance of the SDF
based path should be as good or better than the previous version
before considering it
Hey everyone,
I need some help related to running LoadTest on the local machine.
Reference to the file (*apache_beam.io.gcp.bigquery_read_perf_test* ) I
find the command to run LoadTest but I am not sure about the parameters to
be passed in this command can someone please help me out on this and g
Thank you Piotr and best wishes!
On Wed, Dec 16, 2020 at 8:46 AM Alexey Romanenko
wrote:
> Piotr,
>
> Thanks a lot for your contributions, it was very useful and made Beam more
> stable and finally even better! And it was always interesting to work with
> you =)
>
> I wish you all the best in yo
Thank you Piotr for your contributions.
On Wed, 16 Dec 2020 at 09:16, Ahmet Altay wrote:
> Thank you Piotr and best wishes!
>
> On Wed, Dec 16, 2020 at 8:46 AM Alexey Romanenko
> wrote:
>
>> Piotr,
>>
>> Thanks a lot for your contributions, it was very useful and made Beam
>> more stable and fi
I agree, Ismael.
>From my current investigation, the performance overhead should majorly come
from the frequency of checkpoint in
OutputAndTimeBoundedSplittableProcessElementinvoker[1], which is hardcoded
in the DirectRunner(every 1 seconds or 100 elements)[2]. I believe
configuring these numbers
+Pablo Estrada +Heejong Lee
+Chamikara
Jayalath
On Wed, Dec 16, 2020 at 9:15 AM Faisal Maqsood <
faisal.maqs...@venturedive.com> wrote:
> Hey everyone,
> I need some help related to running LoadTest on the local machine.
> Reference to the file (*apache_beam.io.gcp.bigquery_read_perf_test* )
I haven't tried this, but in general.
metrics_dataset = A BigQuery dataset (to publish metrics)
metrics_table = A BigQuery table name
staging_location = A GCS bucket (of the form gs://...) (also I think this
should be optional since 'staging_location' defaults to 'temp_location')
temp_location = A
Hi folks,
Attached is the December 2020 Beam Community Update. The purpose of this
newsletter is purely community focused, giving folks the visibility to the
insights of the health and growth of the community. This newsletter does
not cover project releases or feature updates. Please let me know i
Hi All!!
For ./gradlew :sdks:java:container:pullLicenses , i have been getting:
Process 'command './license_scripts/license_script.sh'' finished with
non-zero exit value 1
The issue is closely related to
https://issues.apache.org/jira/browse/BEAM-9913.
If anyone has an idea about this issue? Please
Thank you for all your contributions! Good luck in your future endeavors :)
Brian
On Wed, Dec 16, 2020 at 9:35 AM Griselda Cuevas wrote:
> Thank you Piotr for your contributions.
>
> On Wed, 16 Dec 2020 at 09:16, Ahmet Altay wrote:
>
>> Thank you Piotr and best wishes!
>>
>> On Wed, Dec 16, 20
Sometimes you have to ctrl-f in the logs to find an error message [1].
02:54:05 > Task :sdks:java:container:pullLicenses
02:54:05 ERROR:root:['xz-1.5']
02:54:05 ERROR:root: Licenses were
not able to be pulled automatically for some dependencies. Please searc
Thanks Piotr,
You made an impact on Beam! Best wishes in the future projects and
feel welcome whenever you want to contribute again.
Ismaël
On Wed, Dec 16, 2020 at 9:02 PM Brian Hulette wrote:
>
> Thank you for all your contributions! Good luck in your future endeavors :)
>
> Brian
>
> On Wed
It sounds reasonable. I am wondering also on the consequence of these
parameters for other runners (where it is every 10 seconds or 1
elements) + their own configuration e.g. checkpointInterval,
checkpointTimeoutMillis and minPauseBetweenCheckpoints for Flink. It
is not clear for me what would
Making it as the PipelineOptions was my another proposal but it might take
some time to do so. On the other hand, tuning the number into
something acceptable is low-hanging fruit.
On Wed, Dec 16, 2020 at 12:48 PM Ismaël Mejía wrote:
> It sounds reasonable. I am wondering also on the consequence
Thank you Piotr for all your contributions so far! Wish all the best!
-Rui
On Wed, Dec 16, 2020 at 12:36 PM Ismaël Mejía wrote:
> Thanks Piotr,
>
> You made an impact on Beam! Best wishes in the future projects and
> feel welcome whenever you want to contribute again.
>
> Ismaël
>
>
>
> On Wed
I tried changing my build locally to 10 seconds and 10,000 elements but it
didn't seem to make much of a difference, it still takes a few minutes for
elements to begin actually showing up to downstream stages from the Pubsub
read. I can see elements being emitted
from OutputAndTimeBoundedSplittabl
If all it takes is bumping these numbers up a bit, that seems like a
reasonable thing to do ASAP. (I would argue that perhaps they shouldn't be
static, e.g. it might be preferable to start emitting results right away,
but use larger batches for the steady state if there are performance
benefits.)
Hi all,
Thank you for your work so far on this release.
I have cut the release branch[1] - I will go over a snapshot build, and the
remaining JIRA issues in the next few days. Please contact me directly for
your cherry-picks, and we can arrange to bring them into the release.
Thanks!
-P.
[1] https
It's not a portable execution on DirectRunner so I would expect that
outputs from OutputAndTimeBoundedSplittableProcessElementInvoker should be
emitted immediately. For SDF execution on DirectRunner, the overhead could
come from the SDF expansion, SDF wrapper and the invoker.
Steve, based on your
Thank you for sharing this. I particularly find the user voice section
insightful.
On Wed, Dec 16, 2020 at 11:19 AM Brittany Hermann
wrote:
> Hi folks,
>
> Attached is the December 2020 Beam Community Update. The purpose of this
> newsletter is purely community focused, giving folks the visibili
Thank you Piotr!
On Thu, Dec 17, 2020 at 5:30 AM Rui Wang wrote:
> Thank you Piotr for all your contributions so far! Wish all the best!
>
>
> -Rui
>
> On Wed, Dec 16, 2020 at 12:36 PM Ismaël Mejía wrote:
>
>> Thanks Piotr,
>>
>> You made an impact on Beam! Best wishes in the future projects an
24 matches
Mail list logo
