[NEED HELP] PMC only finalization items for release 2.30.0

[Heejong Lee]

Hi,

I'm finishing 2.30.0 release and need help doing PMC only finalization
items in the release guide (
https://beam.apache.org/contribute/release-guide/#10-finalize-the-release).
Please let me know if any PMC members have some time to do these tasks :)

Thanks!

contributor permission for Beam Jira tickets

[Pascal Gillet]

Hi,

This is Pascal. I identified some little but nonetheless annoying bugs in Beam. 
Can someone add me as a contributor for Beam's Jira issue
tracker? I would like to assign tickets to myself.

My JIRA login: pgillet


Thanks,
Pascal

Re: [Proposal] Enable Branch Protection for `release-.*` branches

[Kenneth Knowles]

Great idea. I think only infra can do it.

On Tue, Jun 8, 2021, 14:27 Robert Burke  wrote:

> During the last branch cleanup, it appears I accidentally deleted the
> release-2.26.0 branch.
>
> Lukasz Cwik pointed this out to me, and fortunately I was able to recover
> and push it back to the repo. However, Brian Hulette then pointed out
> github lets us set up rules to avoid accidental deletion of branches that
> match certain names.
>
>
> https://docs.github.com/en/github/administering-a-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule
>
> So the proposal is we guard our release branches from accidental deletion
> using this mechanism. A repo admin (which I think is probably a PMC
> member?) can do so by following the linked instructions.
>
> My only note is that setting up such a rule sets the protection by
> default, and there shouldn't be any need to select other options (except at
> the PMC's discretion).
>
> Unless there's an objection (in the traditional ~3 day period), could a
> volunteer PMC set up such a protection rule, and prevent my error from
> recurring?
>
> Cheers
> Robert Burke
> Beam Go Busybody.
>
>

Re: [EXTERNAL] Re:

[Raphael Sanamyan]

Hello,

Here is a case where you need to have a statement and a preparedStatementSetter.

  PCollection dataCollection = pipeline.apply(Create.of(data));
  PCollection rowsWritten =
  dataCollection.apply(
  JdbcIO.write()
  .withDataSourceConfiguration(DATA_SOURCE_CONFIGURATION)
  .withBatchSize(10L)
  .withTable(firstTableName)
  .withResults());
  .dataCollection .
  .apply(Wait.on(rowsWritten))
  .apply(
  JdbcIO.write()
  .withDataSourceConfiguration(DATA_SOURCE_CONFIGURATION)
  .withBatchSize(10L)
  .withTable(secondTableName));

  .run();

In this case, we write data to one table and then to the other, but only after 
the window of data has been fully written to the first table. It is not 
possible to do this with the existing JdbcIO.Write functionality.

Another option for this specific case could be extending the existing class 
instead of adding a schemaApi-specific class. We can add additional conditions 
and move some functionality from Write to WriteVoid to infer beamScheama. What 
do you think about these options?

Schema Providers is not very well documented in Beam, and a bit confusing us. 
We using Beam row as a common abstraction in Beam pipelines, which really meets 
our requirements. Looking to Beam docs/code we saw SchemaProviders for some 
IOs. Those providers seem like wrappers around IOs that help work with schemas 
and conversion data to Beam Rows. Сould you please clarify this a little? If we 
want to improve Beam Schema API what is the architecture-right way to do that?


Thank you,
Raphael.

От: Brian Hulette 
Отправлено: 9 июня 2021 г. 19:12:41
Кому: dev
Копия: Reuven Lax; pabl...@google.com; Ilya Kozyrev
Тема: [EXTERNAL] Re:

> And also the ticket and "// TODO: BEAM-10396 use writeRows() when it's 
> available" appeared later than this functionality was added to "JdbcIO.Write".

Note that this TODO has been moved around through a few refactors. It was 
initially added last summer [1].
You're right that JdbcIO.Write's statement generation functionality was added 
about a year before that [2]. It's possible that the author of [1] didn't 
realize [2] was done. Or maybe there's some reason why it doesn't work there?

+1 for Alexey's requests:
- Identify cases where statement generation in JdbcIO.Write is insufficient, if 
they exist (e.g. can we just use it where that TODO is [3]? If not what goes 
wrong?).
- Update documentation to avoid this confusion in the future.

Brian

[1] https://github.com/apache/beam/pull/12145
[2] https://github.com/apache/beam/pull/8962
[3] https://github.com/apache/beam/pull/14954#discussion_r648456230

On Wed, Jun 9, 2021 at 7:49 AM Alexey Romanenko 
mailto:aromanenko@gmail.com>> wrote:
Hello Raphael,

On 9 Jun 2021, at 09:31, Raphael Sanamyan 
mailto:raphael.sanam...@akvelon.com>> wrote:

The "JdbcIO.Write" allows you to write rows without a statement or statement 
preparer, but not all functionality works without them.

Could you show a use case when the current functionality is not enough?


The method "WithResults" requires a statement and statement preparer. And also 
the ticket and "// TODO: 
BEAM-10396 use writeRows() when it's 
available"
 appeared later than this functionality was added to "JdbcIO.Write". And 
without reading the code, just the documentation, it's not clear that the 
schema is enough.

Agree but the documentation can be updated. On the oath hand, it would be great 
to have some examples that show the needs of WriteRows.

Thanks,
Alexey

Thank you,
Raphael.





От: Pablo Estrada mailto:pabl...@google.com>>
Отправлено: 7 июня 2021 г. 22:43:24
Кому: dev; Reuven Lax
Копия: Ilya Kozyrev
Тема: Re:

*** This Message Is From an External Sender ***
+Reuven Lax do you know if this is already supported 
or not?
I have been able to use `JdbcIO.write()` without specifying a statement nor a 
statement preparer. Is that not what's necessary? I've done this with a named 
class with schemas (i.e. not Row) - is this perhaps the difference?
Best
-P.

On Fri, Jun 4, 2021 at 3:44 PM Robert Bradshaw 
mailto:rober...@google.com>> wrote:
That would be great! I don't know much about this particular issue,
but tips for getting started in general can be found at
https://beam.apache.org/contribute/

On Thu, Jun 3, 2021 at 10:55 AM Raphael Sanamyan
mailto:raphael.sanam...@akvelon.com>> wrote:
>
> Hi, community,
>
> I would like to start work on this task  beam-10396, I hope nobody minds?
> Also, if anyone has any details or developments on this task, I would be glad 
> if you could share them.
>
> 

Flaky test issue report (37)

[Beam Jira Bot]

This is your daily summary of Beam's current flaky tests 
(https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20labels%20%3D%20flake)

These are P1 issues because they have a major negative impact on the community 
and make it hard to determine the quality of the software.

https://issues.apache.org/jira/browse/BEAM-12322: 
FnApiRunnerTestWithGrpcAndMultiWorkers flaky (py precommit) (created 2021-05-10)
https://issues.apache.org/jira/browse/BEAM-12309: 
PubSubIntegrationTest.test_streaming_data_only flake (created 2021-05-07)
https://issues.apache.org/jira/browse/BEAM-12307: 
PubSubBigQueryIT.test_file_loads flake (created 2021-05-07)
https://issues.apache.org/jira/browse/BEAM-12303: Flake in 
PubSubIntegrationTest.test_streaming_with_attributes (created 2021-05-06)
https://issues.apache.org/jira/browse/BEAM-12291: 
org.apache.beam.runners.flink.ReadSourcePortableTest.testExecution[streaming: 
false] is flaky (created 2021-05-05)
https://issues.apache.org/jira/browse/BEAM-12200: 
SamzaStoreStateInternalsTest is flaky (created 2021-04-20)
https://issues.apache.org/jira/browse/BEAM-12163: Python GHA PreCommits 
flake with grpc.FutureTimeoutError on SDK harness startup (created 2021-04-13)
https://issues.apache.org/jira/browse/BEAM-12061: beam_PostCommit_SQL 
failing on KafkaTableProviderIT.testFakeNested (created 2021-03-27)
https://issues.apache.org/jira/browse/BEAM-12019: 
apache_beam.runners.portability.flink_runner_test.FlinkRunnerTestOptimized.test_flink_metrics
 is flaky (created 2021-03-18)
https://issues.apache.org/jira/browse/BEAM-11792: Python precommit failed 
(flaked?) installing package  (created 2021-02-10)
https://issues.apache.org/jira/browse/BEAM-11666: 
apache_beam.runners.interactive.recording_manager_test.RecordingManagerTest.test_basic_execution
 is flaky (created 2021-01-20)
https://issues.apache.org/jira/browse/BEAM-11661: hdfsIntegrationTest 
flake: network not found (py38 postcommit) (created 2021-01-19)
https://issues.apache.org/jira/browse/BEAM-11645: beam_PostCommit_XVR_Flink 
failing (created 2021-01-15)
https://issues.apache.org/jira/browse/BEAM-11541: 
testTeardownCalledAfterExceptionInProcessElement flakes on direct runner. 
(created 2020-12-30)
https://issues.apache.org/jira/browse/BEAM-11540: Linter sometimes flakes 
on apache_beam.dataframe.frames_test (created 2020-12-30)
https://issues.apache.org/jira/browse/BEAM-10995: Java + Universal Local 
Runner: WindowingTest.testWindowPreservation fails (created 2020-09-30)
https://issues.apache.org/jira/browse/BEAM-10987: 
stager_test.py::StagerTest::test_with_main_session flaky on windows py3.6,3.7 
(created 2020-09-29)
https://issues.apache.org/jira/browse/BEAM-10968: flaky test: 
org.apache.beam.sdk.metrics.MetricsTest$AttemptedMetricTests.testAttemptedDistributionMetrics
 (created 2020-09-25)
https://issues.apache.org/jira/browse/BEAM-10955: Flink Java Runner test 
flake: Could not find Flink job  (created 2020-09-23)
https://issues.apache.org/jira/browse/BEAM-10866: 
PortableRunnerTestWithSubprocesses.test_register_finalizations flaky on macOS 
(created 2020-09-09)
https://issues.apache.org/jira/browse/BEAM-10501: 
CheckGrafanaStalenessAlerts and PingGrafanaHttpApi fail with Connection refused 
(created 2020-07-15)
https://issues.apache.org/jira/browse/BEAM-10485: Failure / flake: 
ElasticsearchIOTest > testWriteWithIndexFn (created 2020-07-14)
https://issues.apache.org/jira/browse/BEAM-9649: 
beam_python_mongoio_load_test started failing due to mismatched results 
(created 2020-03-31)
https://issues.apache.org/jira/browse/BEAM-9392: TestStream tests are all 
flaky (created 2020-02-27)
https://issues.apache.org/jira/browse/BEAM-9232: 
BigQueryWriteIntegrationTests is flaky coercing to Unicode (created 2020-01-31)
https://issues.apache.org/jira/browse/BEAM-9119: 
apache_beam.runners.portability.fn_api_runner_test.FnApiRunnerTest[...].test_large_elements
 is flaky (created 2020-01-14)
https://issues.apache.org/jira/browse/BEAM-8101: Flakes in 
ParDoLifecycleTest.testTeardownCalledAfterExceptionInStartBundleStateful for 
Direct, Spark, Flink (created 2019-08-27)
https://issues.apache.org/jira/browse/BEAM-8035: 
[beam_PreCommit_Java_Phrase] [WatchTest.testMultiplePollsWithManyResults]  
Flake: Outputs must be in timestamp order (created 2019-08-22)
https://issues.apache.org/jira/browse/BEAM-7992: Unhandled type_constraint 
in 
apache_beam.io.gcp.bigquery_write_it_test.BigQueryWriteIntegrationTests.test_big_query_write_new_types
 (created 2019-08-16)
https://issues.apache.org/jira/browse/BEAM-7827: 
MetricsTest$AttemptedMetricTests.testAllAttemptedMetrics is flaky on 
DirectRunner (created 2019-07-26)
https://issues.apache.org/jira/browse/BEAM-7752: Java Validates 
DirectRunner: testTeardownCalledAfterExceptionInFinishBundleStateful flaky 
(created 

P1 issues report (38)

[Beam Jira Bot]

This is your daily summary of Beam's current P1 issues, not including flaky 
tests 
(https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20priority%20%3D%20P1%20AND%20(labels%20is%20EMPTY%20OR%20labels%20!%3D%20flake).

See https://beam.apache.org/contribute/jira-priorities/#p1-critical for the 
meaning and expectations around P1 issues.

https://issues.apache.org/jira/browse/BEAM-12443: No Information of failed 
Query in JdbcIO (created 2021-06-02)
https://issues.apache.org/jira/browse/BEAM-12436: 
[beam_PostCommit_Go_VR_flink| beam_PostCommit_Go_VR_spark] 
[:sdks:go:test:flinkValidatesRunner] Failure summary (created 2021-06-01)
https://issues.apache.org/jira/browse/BEAM-12422: Vendored gRPC 1.36.0 is 
using a log4j version with security issues (created 2021-05-28)
https://issues.apache.org/jira/browse/BEAM-12396: 
beam_PostCommit_XVR_Direct failed (flaked?) (created 2021-05-24)
https://issues.apache.org/jira/browse/BEAM-12389: 
beam_PostCommit_XVR_Dataflow flaky: Expand method not found (created 2021-05-21)
https://issues.apache.org/jira/browse/BEAM-12387: beam_PostCommit_Python* 
timing out (created 2021-05-21)
https://issues.apache.org/jira/browse/BEAM-12386: 
beam_PostCommit_Py_VR_Dataflow(_V2) failing metrics tests (created 2021-05-21)
https://issues.apache.org/jira/browse/BEAM-12380: Go SDK Kafka IO Transform 
implemented via XLang (created 2021-05-21)
https://issues.apache.org/jira/browse/BEAM-12374: Spark postcommit failing 
ResumeFromCheckpointStreamingTest (created 2021-05-20)
https://issues.apache.org/jira/browse/BEAM-12320: 
PubsubTableProviderIT.testSQLSelectsArrayAttributes[0] failing in SQL 
PostCommit (created 2021-05-10)
https://issues.apache.org/jira/browse/BEAM-12310: 
beam_PostCommit_Java_DataflowV2 failing (created 2021-05-07)
https://issues.apache.org/jira/browse/BEAM-12279: Implement 
destination-dependent sharding in FileIO.writeDynamic (created 2021-05-04)
https://issues.apache.org/jira/browse/BEAM-12256: 
PubsubIO.readAvroGenericRecord creates SchemaCoder that fails to decode some 
Avro logical types (created 2021-04-29)
https://issues.apache.org/jira/browse/BEAM-11959: Python Beam SDK Harness 
hangs when installing pip packages (created 2021-03-11)
https://issues.apache.org/jira/browse/BEAM-11906: No trigger early 
repeatedly for session windows (created 2021-03-01)
https://issues.apache.org/jira/browse/BEAM-11875: XmlIO.Read does not 
handle XML encoding per spec (created 2021-02-26)
https://issues.apache.org/jira/browse/BEAM-11828: JmsIO is not 
acknowledging messages correctly (created 2021-02-17)
https://issues.apache.org/jira/browse/BEAM-11755: Cross-language 
consistency (RequiresStableInputs) is quietly broken (at least on portable 
flink runner) (created 2021-02-05)
https://issues.apache.org/jira/browse/BEAM-11578: `dataflow_metrics` 
(python) fails with TypeError (when int overflowing?) (created 2021-01-06)
https://issues.apache.org/jira/browse/BEAM-11434: Expose Spanner 
admin/batch clients in Spanner Accessor (created 2020-12-10)
https://issues.apache.org/jira/browse/BEAM-11148: Kafka 
commitOffsetsInFinalize OOM on Flink (created 2020-10-28)
https://issues.apache.org/jira/browse/BEAM-11017: Timer with dataflow 
runner can be set multiple times (dataflow runner) (created 2020-10-05)
https://issues.apache.org/jira/browse/BEAM-10670: Make non-portable 
Splittable DoFn the only option when executing Java "Read" transforms (created 
2020-08-10)
https://issues.apache.org/jira/browse/BEAM-10617: python 
CombineGlobally().with_fanout() cause duplicate combine results for sliding 
windows (created 2020-07-31)
https://issues.apache.org/jira/browse/BEAM-10569: SpannerIO tests don't 
actually assert anything. (created 2020-07-23)
https://issues.apache.org/jira/browse/BEAM-10288: Quickstart documents are 
out of date (created 2020-06-19)
https://issues.apache.org/jira/browse/BEAM-10244: Populate requirements 
cache fails on poetry-based packages (created 2020-06-11)
https://issues.apache.org/jira/browse/BEAM-10100: FileIO writeDynamic with 
AvroIO.sink not writing all data (created 2020-05-27)
https://issues.apache.org/jira/browse/BEAM-9564: Remove insecure ssl 
options from MongoDBIO (created 2020-03-20)
https://issues.apache.org/jira/browse/BEAM-9455: Environment-sensitive 
provisioning for Dataflow (created 2020-03-05)
https://issues.apache.org/jira/browse/BEAM-9293: Python direct runner 
doesn't emit empty pane when it should (created 2020-02-11)
https://issues.apache.org/jira/browse/BEAM-8986: SortValues may not work 
correct for numerical types (created 2019-12-17)
https://issues.apache.org/jira/browse/BEAM-8985: SortValues should fail if 
SecondaryKey coder is not deterministic (created 2019-12-17)
https://issues.apache.org/jira/browse/BEAM-8407: [SQL] Some Hive tests 
throw 

Re:

[Brian Hulette]

> And also the ticket and "// TODO: BEAM-10396 use writeRows() when it's
available" appeared later than this functionality was added to
"JdbcIO.Write".

Note that this TODO has been moved around through a few refactors. It was
initially added last summer [1].
You're right that JdbcIO.Write's statement generation functionality was
added about a year before that [2]. It's possible that the author of [1]
didn't realize [2] was done. Or maybe there's some reason why it doesn't
work there?

+1 for Alexey's requests:
- Identify cases where statement generation in JdbcIO.Write is
insufficient, if they exist (e.g. can we just use it where that TODO is
[3]? If not what goes wrong?).
- Update documentation to avoid this confusion in the future.

Brian

[1] https://github.com/apache/beam/pull/12145
[2] https://github.com/apache/beam/pull/8962
[3] https://github.com/apache/beam/pull/14954#discussion_r648456230

On Wed, Jun 9, 2021 at 7:49 AM Alexey Romanenko 
wrote:

> Hello Raphael,
>
> On 9 Jun 2021, at 09:31, Raphael Sanamyan 
> wrote:
>
> The "JdbcIO.Write" allows you to write rows without a statement or
> statement preparer, but not all functionality works without them.
>
>
> Could you show a use case when the current functionality is not enough?
>
>
> The method "WithResults" requires a statement and statement preparer. And
> also the ticket  and "//
> TODO: BEAM-10396 use writeRows() when it's available"
> 
>  appeared
> later than this functionality was added to "JdbcIO.Write". And without
> reading the code, just the documentation, it's not clear that the schema is
> enough.
>
>
> Agree but the documentation can be updated. On the oath hand, it would be
> great to have some examples that show the needs of WriteRows.
>
> Thanks,
> Alexey
>
> Thank you,
> Raphael.
>
>
>
> --
> *От:* Pablo Estrada 
> *Отправлено:* 7 июня 2021 г. 22:43:24
> *Кому:* dev; Reuven Lax
> *Копия:* Ilya Kozyrev
> *Тема:* Re:
>
>  This Message Is From an External Sender 
> +Reuven Lax  do you know if this is already supported
> or not?
> I have been able to use `JdbcIO.write()` without specifying a statement
> nor a statement preparer. Is that not what's necessary? I've done this with
> a named class with schemas (i.e. not Row) - is this perhaps the difference?
> Best
> -P.
>
> On Fri, Jun 4, 2021 at 3:44 PM Robert Bradshaw 
> wrote:
>
>> That would be great! I don't know much about this particular issue,
>> but tips for getting started in general can be found at
>> https://beam.apache.org/contribute/
>>
>> On Thu, Jun 3, 2021 at 10:55 AM Raphael Sanamyan
>>  wrote:
>> >
>> > Hi, community,
>> >
>> > I would like to start work on this task  beam-10396, I hope nobody
>> minds?
>> > Also, if anyone has any details or developments on this task, I would
>> be glad if you could share them.
>> >
>> > Thank you,
>> > Raphael.
>> >
>> >
>
>
>

Re:

[Alexey Romanenko]

Hello Raphael,

> On 9 Jun 2021, at 09:31, Raphael Sanamyan  
> wrote:
> 
> The "JdbcIO.Write" allows you to write rows without a statement or statement 
> preparer, but not all functionality works without them.

Could you show a use case when the current functionality is not enough? 


> The method "WithResults" requires a statement and statement preparer. And 
> also the ticket  and "// 
> TODO: BEAM-10396 use writeRows() when it's available" 
> 
>  appeared later than this functionality was added to "JdbcIO.Write". And 
> without reading the code, just the documentation, it's not clear that the 
> schema is enough.

Agree but the documentation can be updated. On the oath hand, it would be great 
to have some examples that show the needs of WriteRows.

Thanks,
Alexey

> Thank you,
> Raphael.
> 
> 
> 
> От: Pablo Estrada mailto:pabl...@google.com>>
> Отправлено: 7 июня 2021 г. 22:43:24
> Кому: dev; Reuven Lax
> Копия: Ilya Kozyrev
> Тема: Re:
>  
> *** This Message Is From an External Sender ***
> +Reuven Lax  do you know if this is already 
> supported or not?
> I have been able to use `JdbcIO.write()` without specifying a statement nor a 
> statement preparer. Is that not what's necessary? I've done this with a named 
> class with schemas (i.e. not Row) - is this perhaps the difference?
> Best
> -P.
> 
> On Fri, Jun 4, 2021 at 3:44 PM Robert Bradshaw  > wrote:
> That would be great! I don't know much about this particular issue,
> but tips for getting started in general can be found at
> https://beam.apache.org/contribute/ 
> 
> On Thu, Jun 3, 2021 at 10:55 AM Raphael Sanamyan
> mailto:raphael.sanam...@akvelon.com>> wrote:
> >
> > Hi, community,
> >
> > I would like to start work on this task  beam-10396, I hope nobody minds?
> > Also, if anyone has any details or developments on this task, I would be 
> > glad if you could share them.
> >
> > Thank you,
> > Raphael.
> >
> >

Re: beam new feature

[Alexey Romanenko]

Thanks, I left my comments as well.

—
Alexey

> On 8 Jun 2021, at 22:21, Luke Cwik  wrote:
> 
> Thanks, I left a few comments in the doc.
> 
> On Tue, Jun 8, 2021 at 12:26 PM Daria Malkova  > wrote:
> 
> Hi community!
> 
> I've noticed that there is no possibility in Beam JDBC to use partitioning 
> for reading a very large table with millions of rows in parallel (for example 
> when migrating legacy database data to BigQuery).
> I have some ideas which are decribed here in more detailes: 
> https://docs.google.com/document/d/1wBzVhQEhTK23ALzTSZ_CVouEOXTm3w2-LjmO3ieUvFc/edit?usp=sharing
>  
> 
> I would like to start working on the related task I've created 
> https://issues.apache.org/jira/browse/BEAM-12456 
> 
> If anybody have any concerns or proposals please feel free to leave comments 
> at google doc.
> 
> Thank you,
> Daria
> 
> 

Re: Re:

[Raphael Sanamyan]

Hello Pablo!
The "JdbcIO.Write" allows you to write rows without a statement or statement 
preparer, but not all functionality works without them. The method 
"WithResults" requires a statement and statement preparer. And also the 
ticket and "// TODO: 
BEAM-10396 use writeRows() when it's 
available"
 appeared later than this functionality was added to "JdbcIO.Write". And 
without reading the code, just the documentation, it's not clear that the 
schema is enough.Thank you,
Raphael.





От: Pablo Estrada 
Отправлено: 7 июня 2021 г. 22:43:24
Кому: dev; Reuven Lax
Копия: Ilya Kozyrev
Тема: Re:


*** This Message Is From an External Sender ***

+Reuven Lax do you know if this is already supported 
or not?
I have been able to use `JdbcIO.write()` without specifying a statement nor a 
statement preparer. Is that not what's necessary? I've done this with a named 
class with schemas (i.e. not Row) - is this perhaps the difference?
Best
-P.

On Fri, Jun 4, 2021 at 3:44 PM Robert Bradshaw 
mailto:rober...@google.com>> wrote:
That would be great! I don't know much about this particular issue,
but tips for getting started in general can be found at
https://beam.apache.org/contribute/

On Thu, Jun 3, 2021 at 10:55 AM Raphael Sanamyan
mailto:raphael.sanam...@akvelon.com>> wrote:
>
> Hi, community,
>
> I would like to start work on this task  beam-10396, I hope nobody minds?
> Also, if anyone has any details or developments on this task, I would be glad 
> if you could share them.
>
> Thank you,
> Raphael.
>
>