A query on codebase exploration

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

A query on codebase exploration

ghildiya
Hi,

Looking into the codebase, its quite huge.

Any suggestions/guidelines on which parts should one explore first, and to
maintain whole picture too?

Manish
Reply | Threaded
Open this post in threaded view
|

Re: A query on codebase exploration

Aljoscha Krettek-2
Hi Manish,

welcome to the community! You could start from a user program example
and then try and figure out how that leads to job execution. So probably
start with the DataStream WordCount example, figure out what the methods
on DataStream do, that is how they build up a graph of Transformations.
Then try and follow what happens when you call execute(), how the graph
of Transformations is translated eventually to a StreamGraph and then a
JobGraph that is then executed/submitted.

Feel free to ask if you get stuck or have more questions on this.

Aljoscha

On 27.04.20 12:22, Manish G wrote:
> Hi,
>
> Looking into the codebase, its quite huge.
>
> Any suggestions/guidelines on which parts should one explore first, and to
> maintain whole picture too?
>
> Manish
>

Reply | Threaded
Open this post in threaded view
|

Re: A query on codebase exploration

ghildiya
Thanks Aljoscha.

On Mon, Apr 27, 2020 at 5:29 PM Aljoscha Krettek <[hidden email]>
wrote:

> Hi Manish,
>
> welcome to the community! You could start from a user program example
> and then try and figure out how that leads to job execution. So probably
> start with the DataStream WordCount example, figure out what the methods
> on DataStream do, that is how they build up a graph of Transformations.
> Then try and follow what happens when you call execute(), how the graph
> of Transformations is translated eventually to a StreamGraph and then a
> JobGraph that is then executed/submitted.
>
> Feel free to ask if you get stuck or have more questions on this.
>
> Aljoscha
>
> On 27.04.20 12:22, Manish G wrote:
> > Hi,
> >
> > Looking into the codebase, its quite huge.
> >
> > Any suggestions/guidelines on which parts should one explore first, and
> to
> > maintain whole picture too?
> >
> > Manish
> >
>
>