Hi Vince, We are working on enhancing extended JSON support for Drill. Please refer DRILL-2879 <https://issues.apache.org/jira/browse/DRILL-2879>.
On Wed, May 20, 2015 at 5:01 PM, Vince Gonzalez <[email protected]> wrote: > Congrats on 1.0! > > Is there any way in Drill to parse extendedJSON in "shell" (as opposed to > strict) mode? > > According to > http://docs.mongodb.org/manual/reference/mongodb-extended-json/#date $date > needs to be a quoted string in "strict" mode. In shell mode, it can be a > signed integer. This makes sense given the error message. More detail > below. > > > The following query fails: > > 0: jdbc:drill:zk=local> select * from > dfs.`/Users/vince/data/stocks/stocks.json` limit 1; > Error: DATA_READ ERROR: Error parsing JSON - Failure while reading > ExtendedJSON typed value. Expected a VALUE_STRING but received a token of > type VALUE_NUMBER_INT > > File /Users/vince/data/stocks/stocks.json > Record 1 > Column 717 > Fragment 0:0 > > [Error Id: c746ca77-92e6-45ed-a5f1-9a6fd8f25ca2 on 192.168.56.1:31010] > (state=,code=0) > > Looks like the extendedJSON value for a $date is the issue. Column 717 has > this nested JSON object attached to the "Earnings Date" key: > > "Earnings Date" : { "$date" : 1384464600000 } > > The date should be a string, but it's not. According to the reference, in > shell mode, this would be acceptable. > > FWIW, I did try store.json.all_text_mode=true for this and the query fails > the same way. > > Thanks, > > --vince > -- Kamesh.
