On Tue, Nov 5, 2019 at 10:32 AM Hai Lu wrote:
>
> Starting the expansion service in the job server is helpful. But having to
> expose the port number and to include the address in the
> beam.ExternalTransform is still a hassle. Giving a hard-coded port number
> might be the only solution right
Starting the expansion service in the job server is helpful. But having to
expose the port number and to include the address in
the beam.ExternalTransform is still a hassle. Giving a hard-coded port
number might be the only solution right now but it's not a very clean
solution in our case.
To clarify, starting up the Flink Job Server by default starts up an
Expansion Service on the hard-coded, default port 8097.
On Mon, Nov 4, 2019 at 2:02 PM Thomas Weise wrote:
>
> The expansion service can be provided by the job server, as done in the Flink
> runner. It needs to be available at
The expansion service can be provided by the job server, as done in the
Flink runner. It needs to be available at pipeline construction time, but
there is no need to run a separate service.
Thomas
On Mon, Nov 4, 2019 at 12:03 PM Robert Bradshaw wrote:
> On Mon, Nov 4, 2019 at 11:54 AM
On Mon, Nov 4, 2019 at 11:54 AM Chamikara Jayalath wrote:
>
> On Mon, Nov 4, 2019 at 11:01 AM Hai Lu wrote:
>>
>> Hi,
>>
>> We're looking into leveraging the cross language pipeline feature in our
>> Beam pipelines on Samza runner. While the feature seems to work well, the
>> PTransform
On Mon, Nov 4, 2019 at 11:01 AM Hai Lu wrote:
> Hi,
>
> We're looking into leveraging the cross language pipeline feature in our
> Beam pipelines on Samza runner. While the feature seems to work well, the
> PTransform expansion as a standalone service isn't very convenient.
> Particularly that
Hi,
We're looking into leveraging the cross language pipeline feature in our
Beam pipelines on Samza runner. While the feature seems to work well, the
PTransform expansion as a standalone service isn't very convenient.
Particularly that the Python pipeline needs to specify the address of the
