[jira] [Comment Edited] (DRILL-7884) Error with list in Mongodb

["James Turton (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DRILL-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477778#comment-17477778 ] 

James Turton edited comment on DRILL-7884 at 1/30/22, 5:32 AM:
---------------------------------------------------------------

Hi, my first thought here is that the ODBC standard does not support complex types like LIST and MAP.  I know that JDBC doesn't and we make use of the java.lang.Object type for LIST and MAP as a fallback.


was (Author: dzamo):
Hi, my first thought here is that probaably ODBC does not support complex types like LIST and MAP.  I know that JDBC doesn't and we make use of the java.lang.Object type for LIST and MAP as a fallback.

> Error with list in Mongodb 
> ---------------------------
>
>                 Key: DRILL-7884
>                 URL: https://issues.apache.org/jira/browse/DRILL-7884
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - ODBC
>    Affects Versions: 1.18.0
>         Environment: CentOS 7.7
> apache-drill-1.18.0
> drill-override.conf
> drill.exec: {
>  cluster-id: "drillbits1",
>  zk.connect: "localhost:2181"
> }
> apache-zookeeper-3.6.2
> Mongodb CE 3.6.5 
>            Reporter: Djamel MALKI
>            Priority: Blocker
>
> Hello,
> We try to connect Apache-drill to Mongodb 3.6.5 with the ODBC driver MapR Drill 1.3 64-bit.
> The connection works well, We have only one collection inside the database with document with this json format :
> {
>  "_id" : ObjectId("600fe61e47f2b8c6335515d0"),
>  "hostid" : "HOST-07A8EEBACFDFA658",
>  "cloudType" : "OnPrem",
>  "hostname" : "lemon-dev02",
>  "logicalCpuCores" : 4,
>  "instanceType" : "NA",
>  "host_cpu_usage_avg" : 17.39,
>  "host_cpu_usage_max" : 42.96,
>  "host_mem_usage_avg" : 46.32,
>  "host_mem_usage_max" : 46.78,
>  "host_mem_used" : 14.552923838297525,
>  "host_avail_hours" : 2,
>  "host_unavail_hours" : 0,
>  "host_mem_avail_bytes" : 16.868035634358723,
>  "host_total_mem" : "NA",
>  "host_trafficIn" : {
>  "ens160" : 0.16
>  },
>  "host_trafficOut" : {
>  "ens160" : 0.3
>  },
>  "Disks" : [ ],
>  {color:#FF0000}"tags"{color} : [
>  "TECHNO_RABBITMQ",
>  "rab",
>  "TECHNO_MONGODB",
>  "gpa",
>  "TECHNO_POSTGRES",
>  "nsm",
>  "rse",
>  "gre",
>  "tech-unix",
>  "ppe",
>  "ide",
>  "mpo",
>  "l3m",
>  "TECHNO_NGINX",
>  "tech-dba",
>  "sma",
>  "TECHNO_JAVA",
>  "api",
>  "inf"
>  ],
>  "FirstSeenInMs" : NumberLong("1606298156021")
> }
> the name of the database in mogodb is : nmo_01_db
> the name of the collection is : hosts
> when we do this request with Apache drill:
> SELECT (`DRILL_2mongo.nmo_301_3db_4hosts`.`tags`) AS `Column_1_1` FROM `mongo.nmo_01_db`.`hosts` AS `DRILL_2mongo.nmo_301_3db_4hosts` GROUP BY (`DRILL_2mongo.nmo_301_3db_4hosts`.`tags`)
> We have this error:
> *UserRemoteException :* SYSTEM ERROR: UnsupportedOperationException: Unable to get size for minor type [LIST] and mode [OPTIONAL]
> org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR: UnsupportedOperationException: Unable to get size for minor type [LIST] and mode [OPTIONAL]
>  
> Regards,
> Djamel



--
This message was sent by Atlassian Jira
(v8.20.1#820001)