Re: JSON Data with dot in keyname

The JIRA is well filled out. On Mon, Oct 12, 2015 at 10:57 AM, Kristine Hahn wrote: > lgtm > > Kristine Hahn > Sr. Technical Writer > 415-497-8107 @krishahn skype:krishahn > > > On Mon, Oct 12, 2015 at 10:45 AM, John Omernik wrote: > > > I've created https://issues.apache.org/jira/browse/DRIL

Re: JSON Data with dot in keyname

lgtm Kristine Hahn Sr. Technical Writer 415-497-8107 @krishahn skype:krishahn On Mon, Oct 12, 2015 at 10:45 AM, John Omernik wrote: > I've created https://issues.apache.org/jira/browse/DRILL-3922 for this > issue. I put in notes to reproduce, and why it's important (data > exploration). Could

Re: JSON Data with dot in keyname

I've created https://issues.apache.org/jira/browse/DRILL-3922 for this issue. I put in notes to reproduce, and why it's important (data exploration). Could someone please take a quick look at it to ensure that something I may have done in creating the JIRA doesn't affect the chances of it getting

Re: JSON Data with dot in keyname

Yep, it fails on select *: select `top.ping`[3].type from dfs.`/Users/khahn/drill/apache-drill-1.2.0-SNAPSHOT/sample-data/donuts.json`; *+-+* *| **EXPR$0 ** |* *+-+* *| *Powdered Sugar * |* *| *null * |* *| *null * |* *| *null

Re: JSON Data with dot in keyname

Kristine, if you have that handy, with the first topping to top.ping, can you try select * just to validate that it's failing like the data I am seeing fail? Once I get confirmation, I'll file a JIRA. On Mon, Oct 12, 2015 at 12:12 PM, Kristine Hahn wrote: > Using the donuts.json > < > https://g

Re: JSON Data with dot in keyname

That is correct, if this is failing in a select *, that is a bug. Can you please file a JIRA? On Mon, Oct 12, 2015 at 10:27 AM, Paul Ilechko wrote: > Well, if it's json then you do know the field names, they are right there > in the document > > On Mon, Oct 12, 2015 at 1:25 PM, John Omernik wro

Re: JSON Data with dot in keyname

Well of course, however, the json may not be easily read by a human, (pretty printed vs not) and might have lots of fields with nesting making it even harder to successfully read.. To explore the data, if we had it so we could select * from the file, then hone in on there, unless you are advocating

Re: JSON Data with dot in keyname

Well, if it's json then you do know the field names, they are right there in the document On Mon, Oct 12, 2015 at 1:25 PM, John Omernik wrote: > Interesting, so we can't use select * on those items. I think that should > be a bug of some sort in that it's hard to explore the json data if you >

Re: JSON Data with dot in keyname

Interesting, so we can't use select * on those items. I think that should be a bug of some sort in that it's hard to explore the json data if you don't know the field names ahead of time. This is one of the situations where having the select * works really well for learning the data. (Am I missing

Re: JSON Data with dot in keyname

I tried out using the example you shared. Saw the same failures. However, this worked for me: > select `hello.yoko`, yousayyes from dfs.`/Users/agirish/abc.json`; +-++ | hello.yoko | yousayyes | +-++ | goodbye | isayno | +-+

Re: JSON Data with dot in keyname

Using the donuts.json file, I changed the first topping to top.ping and was able to query successfully using back ticks like this: select `top.ping`[3].type from > dfs.`/Users/khahn/drill/apache-drill-1.2.0-SNAPSHOT/sa

JSON Data with dot in keyname

I am getting some data that seems well formed, except for there are dots in some of the key names. Basically, something like ip.src seems to be making it fail with a "Field References must be singular names" I am using the MapR Packaged Drill 1.2. I can prove this out with {"hello":"goodbye",