ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: documentation suggestions
Date Thu, 05 Oct 2017 06:29:00 GMT
Denis,

Thanks for your comments.

The pages I suggested have to do with the "getting started" or "how to's"
for Ignite. Burying it inside of other docs will not make sense. That is
why I suggested adding them under "Basic Concepts" section, i.e. keep them
very visible.

D.

On Thu, Oct 5, 2017 at 12:07 AM, Denis Magda <dmagda@apache.org> wrote:

> Please see inline
>
> > On Oct 4, 2017, at 5:17 AM, Dmitriy Setrakyan <dsetrakyan@apache.org>
> wrote:
> >
> > I would like to propose some changes to the Ignite documentation:
> >
> >   - Under Basic Concepts add the following pages:
> >      - "How to load data”
>
> This should go to “Data Loading” or Streaming sections that appear at the
> top of the doc. We have more room there once new SQL doc is released.
>
> >      - "SQL vs Scan"
> >      - "SQL vs Key-Value”
>
> Yes, it’s needed. The production readiness might be a good alternative to
> host the pages.
>
> >      - more?
> >   - For persistence section, add the following pages:
> >      - Write-Ahead-Log (WAL)
> >         - BTW, I could not find WAL modes anywhere in documentation
> >      - Main Store (or Checkpointing)
>
> Presently, everything is in a good fit on a single persistence page. The
> navigation menu on the readme.io <http://readme.io/> is lengthy and might
> scary the one who sets off Ignite journey. It takes several seconds to
> scroll it down to brace for the volume you should absorb. Let’s release the
> new SQL doc and see how much space is free there before extracting pages
> out of the paragraphs. Also we can try out subpages.
>
> WAL modes documentation: https://issues.apache.org/jira/browse/IGNITE-6558
> <https://issues.apache.org/jira/browse/IGNITE-6558>
>
> —
> Denis
>
> >      - Configuration
> >
> > Thoughts?
> >
> > D.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message