Re: Querying Nested Data in Mongo does not produce the results.

Thanks Kathleen. SELECT camic.provenance.image.case_id caseid from mongo.users.`contacts2` camic where camic.provenance.image.case_id > 10; works for me as well. I have also resolved the bug report that I opened as "Invalid" Regards, Pradeeban. On Thu, Aug 18, 2016 at 5:33 PM, Kathleen Li

[jira] [Resolved] (DRILL-4855) Querying MongoDB collection with nested data fails

[ https://issues.apache.org/jira/browse/DRILL-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathiravelu Pradeeban resolved DRILL-4855. -- Resolution: Invalid We cannot reference column aliases in the following

Re: Querying Nested Data in Mongo does not produce the results.

Hi Prdedeeban, Please check out the following doc: http://drill.apache.org/docs/select-statements/ Column Aliases. You cannot reference column aliases in the following clauses: * WHERE * GROUP BY * HAVING http://drill.apache.org/docs/select-statements/ The following works for me without

Querying Nested Data in Mongo does not produce the results.

Hi, I have this simple data in a Mongo database. {"_id":{"$oid":"56a784b76952647b7b51c562"},"provenance":{"image":{"case_id":100,"subject_id":"TCGA"}}} When I run *SELECT camic.provenance.image.case_id caseidFROM mongo.users.`contacts2` camic* I get the below. +-+ | caseid |

[GitHub] drill issue #572: DRILL-4854: Fix logic error in drill-config.sh

Github user sudheeshkatkam commented on the issue: https://github.com/apache/drill/pull/572 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] drill pull request #572: DRILL-4854: Fix logic error in drill-config.sh

GitHub user paul-rogers opened a pull request: https://github.com/apache/drill/pull/572 DRILL-4854: Fix logic error in drill-config.sh This change should go into 1.8 as it fixes a minor regression introduced during 1.8. The recent changes to the launch scripts introduced a

[jira] [Created] (DRILL-4854) Incorrect logic in log directory checks in drill-config.sh

Paul Rogers created DRILL-4854: -- Summary: Incorrect logic in log directory checks in drill-config.sh Key: DRILL-4854 URL: https://issues.apache.org/jira/browse/DRILL-4854 Project: Apache Drill

Re: C++ protobuf files

I just opened DRILL-4853 jira and PR https://github.com/apache/drill/pull/571 for the protobuf source files update. Laurent On Thu, Aug 18, 2016 at 9:49 AM, Laurent Goujon wrote: > Thanks Sékine, > > After fiddling around and with a little help from Venki (who told me about

[GitHub] drill pull request #571: DRILL-4853: Update C++ protobuf source files

GitHub user laurentgo opened a pull request: https://github.com/apache/drill/pull/571 DRILL-4853: Update C++ protobuf source files Add support for prepared statements and metadata querying You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (DRILL-4853) Update C++ protobuf source files

Laurent Goujon created DRILL-4853: - Summary: Update C++ protobuf source files Key: DRILL-4853 URL: https://issues.apache.org/jira/browse/DRILL-4853 Project: Apache Drill Issue Type: Task

Re: C++ protobuf files

Thanks Sékine, After fiddling around and with a little help from Venki (who told me about the CMakeList.txt files under src/protobuf), I was able to refresh the files using the following command in the build directory: $ make fixProtobufs cpProtobufs This should copy the refreshed files over to

[jira] [Created] (DRILL-4852) COUNT(*) query over 26M rows slower by 2x on mapr drill 1.8.0

Khurram Faraaz created DRILL-4852: - Summary: COUNT(*) query over 26M rows slower by 2x on mapr drill 1.8.0 Key: DRILL-4852 URL: https://issues.apache.org/jira/browse/DRILL-4852 Project: Apache Drill

Re: C++ protobuf files

Laurent, I used this on 1.7 branch (commit 7800aebdca845466a8d912f0f59c00cda093b01f) : PYTHONPATH="/home/scoulibaly/python/build/lib.linux-x86_64-2.7" /home/scoulibaly/protobuf/src/protoc --cpp_out="." --proto_path="." *.proto Just update to your actual Python path and to your actual protoc