Hi,

There are no schema changes.

I can select * from the table just fine!

Regards,
 -Stefán

On Fri, Sep 18, 2015 at 4:55 PM, Abhishek Girish <abhishek.gir...@gmail.com>
wrote:

> Are you sure there is no schema change occurring between records for a
> column other than *occurred_at?**. *In your second query, since the only
> column being read is *occurred_at, *you may not be hitting the issue. First
> query being a select * would read all columns and may hit this schema
> change error.
>
>
> On Fri, Sep 18, 2015 at 9:16 AM, Stefán Baxter <ste...@activitystream.com>
> wrote:
>
> > This fails:
> >
> >    - select * from dfs.asa.* where occurred_at < '2015-09-18' order by
> >    occurred_at;
> >
> > This, oddly enough, does not fail:
> >
> >    - select occurred_at from dfs.* where occurred_at < '2015-09-18' order
> >    by occurred_at;
> >
> > -ste
> >
> > On Fri, Sep 18, 2015 at 4:08 PM, Stefán Baxter <
> ste...@activitystream.com>
> > wrote:
> >
> > >
> > > The failing select query:
> > >
> > > select * from dfs.* where occurred_at < '2015-09-18' order by
> > occurred_at;
> > >
> > > -ste
> > >
> > > On Fri, Sep 18, 2015 at 4:02 PM, Stefán Baxter <
> > ste...@activitystream.com>
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> Both statements select everything but the CTAS statement included a
> date
> > >> filter + date order.
> > >>
> > >> The date field is always the same (extended json format date ISO) and
> is
> > >> always present so I can say, with 100% certainty, that there is no
> > schema
> > >> change involved.
> > >>
> > >> The select statement fails as well when I add the condition +
> ordering.
> > >>
> > >> Regards,
> > >>  -Stefan
> > >>
> > >> On Fri, Sep 18, 2015 at 3:37 PM, Abdel Hakim Deneche <
> > >> adene...@maprtech.com> wrote:
> > >>
> > >>> This kind of errors usually happens when there is an unsupported
> schema
> > >>> change in the json files, but you should be able to reproduce the
> error
> > >>> with just a select statement. Can you share both queries you tried
> (the
> > >>> failing CTAS and the successful SELECT *) ?
> > >>>
> > >>> Thanks
> > >>>
> > >>> On Fri, Sep 18, 2015 at 5:38 AM, Stefán Baxter <
> > >>> ste...@activitystream.com>
> > >>> wrote:
> > >>>
> > >>> > Hi,
> > >>> >
> > >>> > I have some json files that I want to transform to parquet.
> > >>> >
> > >>> > We have been doing this without any issues but this time around I
> get
> > >>> this
> > >>> > exception:
> > >>> >
> > >>> > Error: SYSTEM ERROR: IllegalStateException: Failure while reading
> > >>> vector.
> > >>> > Expected vector class of
> > >>> org.apache.drill.exec.vector.NullableVarCharVector
> > >>> > but was holding vector class
> > >>> > org.apache.drill.exec.vector.complex.MapVector.
> > >>> >
> > >>> > Fragment 2:0
> > >>> >
> > >>> > [Error Id: 86501e92-5319-4540-9cf3-9a1aede4554b on localhost:31010]
> > >>> > (state=,code=0)
> > >>> >
> > >>> > Adding verbosity adds no additional information regarding the
> > >>> > source/row/column that triggers this reaction.
> > >>> >
> > >>> > I have successfully executed "select * from <same-directory>" and
> > that
> > >>> has
> > >>> > run perfectly. For me this means that the issue is CTAS related.
> > >>> >
> > >>> > I'm running a fresh build from master to execute this.
> > >>> >
> > >>> > Any ideas/pointers?
> > >>> >
> > >>> > Regards,
> > >>> >   -Stefán
> > >>> >
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>>
> > >>> Abdelhakim Deneche
> > >>>
> > >>> Software Engineer
> > >>>
> > >>>   <http://www.mapr.com/>
> > >>>
> > >>>
> > >>> Now Available - Free Hadoop On-Demand Training
> > >>> <
> > >>>
> >
> http://www.mapr.com/training?utm_source=Email&utm_medium=Signature&utm_campaign=Free%20available
> > >>> >
> > >>>
> > >>
> > >>
> > >
> >
>

Reply via email to