New section on restricted views.

At the moment, there are several links under the general heading
"Conceptual Topics." They'll get sorted out as we get more depth in the
materials. As you suggest, there should probably be a broader description
of Views in relation to Kite, and this would fall into that section of the
guide.

~D


On Mon, Aug 4, 2014 at 2:24 PM, Tom White <notifications@github.com> wrote:

> In Restricted-Views.md:
>
> > @@ -0,0 +1,12 @@
> > +---
> > +layout: page
> > +title: Restricted Views
> > +---
> > +
> > +Kite lets you write records to views. Kite then adds the records to the source tables. Kite does not store data in the wrong location when you write to a view. This prevents loss or corruption of data. In the context of a MapReduce or Crunch job, writing records to the wrong place causes the job to fail with an `IllegalArgument` exception.
> > +
> > +For example, you might have a Movies dataset partitioned by decade. Your application works with a view on that dataset. Your application attempts to store a record with a release date of 1941 in the 1950s partition. The operation fails.
> > +
> > +It's important to write your applications so that they "do the right thing" when they write to a view. This will avoid the exception and its unhelpful message.
> > +
> > +If storage rules are not significant in your application, you can override these checks.
>
> You avoid these checks by writing to the top-level dataset rather than a
> view. Then writes will always succeed.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/kite-sdk/kite-docs/pull/27/files#r15782256>.
>