ransactions.
>>
>>
>> On Wed, Sep 2, 2015 at 9:21 AM, Robert Metzger
>> wrote:
>>
>>> I'm starting a new discussion thread for the bigpetstore-flink
>>> integration ...
>>>
>>>
>>> I took a closer look into the code
If a lot of the data is generated locally, this may face the same issue as
Greg did with oversized payloads (dropped by Akka).
On Wed, Sep 2, 2015 at 3:21 PM, Robert Metzger wrote:
> I'm starting a new discussion thread for the bigpetstore-flink integration
> ...
>
>
> I too
#x27;m starting a new discussion thread for the bigpetstore-flink
>> integration ...
>>
>>
>> I took a closer look into the code you've posted.
>> It seems to me that you are generating a lot of data locally on the
>> client, before you actually submit a j
ew discussion thread for the bigpetstore-flink integration
> ...
>
>
> I took a closer look into the code you've posted.
> It seems to me that you are generating a lot of data locally on the
> client, before you actually submit a job to Flink. (Both "customers" and
> &q
The scale out data is the transactions.
>
> The seed data needs to be the same, shipped to ALL nodes, and then
>
> the nodes generate transactions.
>
>
> On Wed, Sep 2, 2015 at 9:21 AM, Robert Metzger
> wrote:
>
>> I'm starting a new discussion thread for the big
I'm starting a new discussion thread for the bigpetstore-flink integration
...
I took a closer look into the code you've posted.
It seems to me that you are generating a lot of data locally on the client,
before you actually submit a job to Flink. (Both "customers" and &q
