Hi there,
Welcome to Drill!  I think you have several problems going on there. First of 
all, the mongo metastore has nothing to do with being able to query mongo with 
Drill. The first thing you need to get working is the mongoDB storage plugin.  
You didn't say whether that is in fact working or not.   Executing a `SHOW 
DATABASES` query in Drill should show you whether Mongo is queryable or not.

Regarding the Mongo metastore, I think you've misunderstood its purpose.  
Drill's metastore exists to provide metadata for query planning for file 
systems.  This data needs to be stored somewhere and the metastore gives you 
the option of storing it in iceberg tables, JDBC databases or MongoDB.  To the 
best of my knowledge, the metastore only works for file systems and thus you 
won't see anything in the metastore from a Drill-MongoDB connection.

With that said, MongoDB itself may provide a lot of the info you are seeking.  
Take a look at the various information_schema queries in Drill and try running 
those on your MongoDB connection.
Good luck!
-- C



> On Aug 23, 2023, at 6:49 AM, Surendar Karunanandan 
> <skarunanan...@solutionsbysms.com> wrote:
> 
> Team, <>
>                I   am using latest version of Drill cluster installed.  We 
> try to query mongodb as plugin storage.
> 
>                I  could not find  any metadata getting  updated (like 
> num_rows,last modified) etc etc.
> 
>                Even I tried to implement mongo metastore as given in 
> thehttps://drill.apache.org/docs/mongo-metastore/    but it does not seems to 
> be working.
> 
>                Mongodb meta tables not getting populated with  metadata. Any 
> help  is appreciated.
> 
> 
> 
> 
> Thanks & regards,
> Sk
> 
>  <https://solutionsbytext.com/>
> 
> Surendar
> Database Administrator
> Text SBT to 77513
> +91 8939953306
> Schedule A MĀ­eeting <https://calendly.com/cbeebe>
> 
> 
> CONFIDENTIALITY NOTICE: This email and any files attached are intended solely 
> for the use of the individual or entity to whom they are addressed. This 
> message may contain information that is confidential, privileged, and/or 
> protected by work product. If you have received this email in error, please 
> notify the sender and delete the email immediately.

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to