8 PM, Aljoscha Krettek
>>>>> wrote:
>>>>>
>>>>>> Why do you wan't to split stuff between the doc in the repository and
>>>>>> the wiki. I for one would always be to lazy to check stuff in a wiki
>>>>>>
gt; >>> all
> > >> > >>> > the people that do not look into a wiki. The overview pages
> for
> > the
> > >> > >>> > internals need to be good and accessible and nicely link to
> the
> > >> wiki
> > >&
gt; >
> > > >> > >>> > Having a good landing page in the regular docs is exactly to
> > not
> > > >> > loose
> > > >> > >>> all
> > > >> > >>> > the people that do not look into a wiki. The overview pa
;> > >>> all
> > >> > >>> > the people that do not look into a wiki. The overview pages
> for
> > the
> > >> > >>> > internals need to be good and accessible and nicely link to
> the
> > >> wiki
> > >&
t; > The overhead of deciding what goes where should not be terribly
> >> > large,
> >> > >>> in
> >> > >>> > my opinion, since there is no really "wrong" place to put it.
> >> > >>> >
> >> > &g
t; >>> in
>> > >>> > my opinion, since there is no really "wrong" place to put it.
>> > >>> >
>> > >>> >
>> > >>> >
>> > >>> > On Mon, Mar 16, 2015 at 9:58 PM, Aljoscha Krettek <
&g
gt; > >>> > On Mon, Mar 16, 2015 at 9:58 PM, Aljoscha Krettek <
> > aljos...@apache.org>
> > >>> > wrote:
> > >>> >
> > >>> >> Why do you wan't to split stuff between the doc in the repository
> > and
> > >>> >>
e repository
> and
> >>> >> the wiki. I for one would always be to lazy to check stuff in a wiki
> >>> >> when there is also a documentation. Plus, this would lead to
> >>> >> additional overhead in deciding what goes where and syncing
ad to
>>> >> additional overhead in deciding what goes where and syncing between
>>> >> the two places for documentation.
>>> >>
>>> >> On Mon, Mar 16, 2015 at 7:59 PM, Stephan Ewen
>>> wrote:
>>> >> > Ah, I tot
58 PM, Aljoscha Krettek <
>> aljos...@apache.org>
>> >>>> wrote:
>> >>>>
>> >>>>> Why do you wan't to split stuff between the doc in the repository and
>> >>>>> the wiki. I for one would always be to l
itory and
> >>>>> the wiki. I for one would always be to lazy to check stuff in a wiki
> >>>>> when there is also a documentation. Plus, this would lead to
> >>>>> additional overhead in deciding what goes where and syncing between
> >&g
tion. Plus, this would lead to
>>>>> additional overhead in deciding what goes where and syncing between
>>>>> the two places for documentation.
>>>>>
>>>>> On Mon, Mar 16, 2015 at 7:59 PM, Stephan Ewen
>>> wrote:
>>>&g
wo places for documentation.
>> >>
>> >> On Mon, Mar 16, 2015 at 7:59 PM, Stephan Ewen
>> wrote:
>> >> > Ah, I totally forgot to add to the internals:
>> >> >
>> >> > - Fault tolerance in Batch mode
>> >> >
&
ternals:
> >> >
> >> > - Fault tolerance in Batch mode
> >> >
> >> > - Fault Tolerance in Streaming Mode, with state handling
> >> >
> >> > On Mon, Mar 16, 2015 at 7:51 PM, Stephan Ewen
> wrote:
> >> >
> &
mode
>> >
>> > - Fault Tolerance in Streaming Mode, with state handling
>> >
>> > On Mon, Mar 16, 2015 at 7:51 PM, Stephan Ewen wrote:
>> >
>> >> Hi all!
>> >>
>> >> I would like to kick of an effort to improve the d
the internals:
> >
> > - Fault tolerance in Batch mode
> >
> > - Fault Tolerance in Streaming Mode, with state handling
> >
> > On Mon, Mar 16, 2015 at 7:51 PM, Stephan Ewen wrote:
> >
> >> Hi all!
> >>
> >> I would like t
;> Hi all!
>>
>> I would like to kick of an effort to improve the documentation of the
>> Flink Architecture and internals. This also means making the streaming
>> architecture more prominent in the docs.
>>
>> Being quite a sophisticated stack, we need to imp
Ah, I totally forgot to add to the internals:
- Fault tolerance in Batch mode
- Fault Tolerance in Streaming Mode, with state handling
On Mon, Mar 16, 2015 at 7:51 PM, Stephan Ewen wrote:
> Hi all!
>
> I would like to kick of an effort to improve the documentation of th
Hi all!
I would like to kick of an effort to improve the documentation of the Flink
Architecture and internals. This also means making the streaming
architecture more prominent in the docs.
Being quite a sophisticated stack, we need to improve the presentation of
how Flink works - to an extend
19 matches
Mail list logo
