I'm working on updating our Beam DDL code to use the DDL execution
functionality that recently merged into core calcite. This enables us to
take advantage of Calcite JDBC as a way to use Beam SQL. As part of that I
need to reconcile the Beam SQL Environments with the Calcite Schema (which
is calcit
Hello,
I am created a new thread for this updated document, I will finalize this
document on Apr 26, and begin writing PRs next week. I have taken feedback
and have incorporated these ideas into the proposal.
I have listed some areas for discussion above,
https://s.apache.org/beam-fn-api-metrics
Thank you so much!
This one seems architecturally not possible but I'll try to help with
others.
On Mon, 23 Apr 2018, 20:03 Ismaël Mejía, wrote:
> Done, assigned the ticket. You now have the contributor role so you can
> self-assign other tickets in the future.
> Welcome!
>
>
> On Mon, Apr 23,
Done, assigned the ticket. You now have the contributor role so you can
self-assign other tickets in the future.
Welcome!
On Mon, Apr 23, 2018 at 5:34 AM, Jean-Baptiste Onofré
wrote:
> Welcome aboard !
>
> Pretty sure a PMC member will do the change in Jira quickly (unfortunately
> I don't have
Hi guys,
I noticed a failure in the performance tests job for spark (I did not take a
look at the others): it seems to be related
to a schema update in the bigQuery output.
BigQuery error in load operation: Error processing job
'apache-beam-testing:bqjob_r2527a0e444514f2b_0162f128db2b_1': In