I believe that this error is due to an incompatibility between Mongo's
Extended JSON support and Drill's extended JSON support that is fixed in
1.2 (release imminent e.g. next 24-48 hours). If you want to try out the
fix immediately, you would need to grab the master branch of Drill and
build it yourself.



--
Jacques Nadeau
CTO and Co-Founder, Dremio

On Thu, Oct 15, 2015 at 6:35 AM, Mangold, James <
[email protected]> wrote:

> Hi,
>
> I am trying to query a collection in mongo directly, using this query:
>
> select * from mongo.omegatestbed.testshard4 where ENTITY_ID = 1216515
> limit 1;
>
> ENTITY_ID is indexed, ascending. The columns in the collection may have
> differing data types for the same column name. I get this error:
>
>
>
> Error: SYSTEM ERROR: JsonParseException: Failure while reading
> ExtendedJSON typed value. Expected a VALUE_NUMBER_INT but received a token
> of type VALUE_STRING
>  at [Source: org.apache.drill.exec.vector.complex.fn.SeekableBAIS@74ad855e
> <mailto:org.apache.drill.exec.vector.complex.fn.SeekableBAIS@74ad855e>;
> line: 1, column: 36]
>
> Fragment 1:48
>
> I did run alter system set `store.mongo.all_text_mode` = true prior to
> doing this.
>
>
>
> I have no idea what's wrong or how to query this data. Even worse is that
> I said limit 1. I wouldn't think it would get any other rows.
>
>
>
> Thanks,
>
> James Mangold
>
> Interactive Data
>
> [email protected]<mailto:[email protected]
> >
>
>
> *******************************************************
> This message (including any files transmitted with it) may contain
> confidential and/or proprietary information, is the property of Interactive
> Data Corporation and/or its subsidiaries, and is directed only to the
> addressee(s). If you are not the designated recipient or have reason to
> believe you received this message in error, please delete this message from
> your system and notify the sender immediately. An unintended recipient's
> disclosure, copying, distribution, or use of this message or any
> attachments is prohibited and may be unlawful.
> *******************************************************
>

Reply via email to