You'll need to put your leaf fields inside a map vector to refer to them in
the way you want.
On Mar 4, 2016 5:04 PM, "Jiang Wu" wrote:
> We are working on a custom Drill storage plugin to retrieve data from a
> proprietary a JSON based storage. The drill version being
We are working on a custom Drill storage plugin to retrieve data from a
proprietary a JSON based storage. The drill version being used is 1.4.0.
Assuming the data is a JSON looking like this:
{
...
"topping": {
"id": "5001, 5002, ...",
...
}
...
}
When we submit this
Yes, this works.
Thank you,
-Stefán
On Fri, Mar 4, 2016 at 8:55 PM, Jinfeng Ni wrote:
> Can you try this:
>
> select sold_to, count(*) as trans_count from dfs.asa.`/transactions`
> group by sold_to
> having count(*) > 70;
>
> This is because column alias in the SELECT
Having fails as well
On Fri, Mar 4, 2016 at 8:00 PM, Bob Rumsby wrote:
> Without trying it or seeing your tables/files, I would expect this to work:
>
> select sold_to, count(*) as trans_count from dfs.asa.`/transactions`
> group by sold_to
> having trans_count > 70;
>
>
Without trying it or seeing your tables/files, I would expect this to work:
select sold_to, count(*) as trans_count from dfs.asa.`/transactions`
group by sold_to
having trans_count > 70;
On Fri, Mar 4, 2016 at 11:53 AM, Stefán Baxter
wrote:
> Hi,
>
> Having adds to
Hi,
Having adds to the trouble and claims that the field needs to be grouped
and then fails the same way if it's added to group by.
I ended up wrapping this in a "with <> as ()" but that is far from ideal.
Regards,
-Stefán
On Fri, Mar 4, 2016 at 7:50 PM, Bob Rumsby
Hi,
I'm using parquet+drill and the following statement works just fine:
select sold_to, count(*) as trans_count from
dfs.asa.`/processed/venuepoint/transactions` where group by sold_to;
When addin this where clause nothing is returned:
select sold_to, count(*) as trans_count from
Hey Assaf, is there anything in the logs? Can you email me them directly or
put on gist (can't attach to mailing list emails).
If nothing there, can you enable Java assertions by adding -ea to
drill-env.sh and see if we get a more helpful log or error messages?
thanks,
Jacques
--
Jacques
Run the bad query multiple times.
Prior to each run, remove the first character of the like string.
Stop when the query no longer kills drill.
If the condition here, then, that would SEEM to mean that the problem is
in parsing the query.
If that doesn't work, change the 2nd query to = '%'
is there a space between 1 and back tick in your first field?
On Friday, March 4, 2016, Assaf Lowenstein wrote:
> Hello Drillers!
> My Drill setup is very simple, querying static gz files that hold jsons.
> Everything was running smooth but we're now seeing what seems to be a
Hello,
i have configured a cluster with 2 Slaves. I have already succesfull hadoop,
apache hbase, apache drill installed and configured.In the next step i want to
vizualize data from hbase with tableau, but i don't find any posibility to
install Tableau on Ubuntu.
How can i do this on
Hello Drillers!
My Drill setup is very simple, querying static gz files that hold jsons.
Everything was running smooth but we're now seeing what seems to be a crash
with a very simple query. here are the details.
This query works
*select `column1`, column2, myTable.`user`, column3 from
12 matches
Mail list logo