MapR has pushed an independent advanced release of Drill 1.2-ish that likely has this fix.
On Thu, Oct 15, 2015 at 7:56 AM, Kamesh <kamesh.had...@gmail.com> wrote: > Hi James, > Which version of Drill are you using?. Also whether any of the documents > contain field of data type timestamp or date?. > If so, recently we have fixed issues in handling timestamp/date and binary > date type. > These fixes are targeted for *1.2.0* release, which will happen very soon. > > On Thu, Oct 15, 2015 at 7:05 PM, Mangold, James < > james.mang...@interactivedata.com> 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 > > > > james.mang...@interactivedata.com<mailto: > james.mang...@interactivedata.com > > > > > > > > > ******************************************************* > > 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. > > ******************************************************* > > > > > > -- > Kamesh. >
