Any chance of INFORMATION SCHEMA updates like storing it in any database instead of in-memory data

[porika-v]

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

[jnturton]

Have you looked at the Drill metastore?

https://drill.apache.org/docs/using-drill-metastore/ https://drill.apache.org/docs/rdbms-metastore/

[porika-v]

this works only with parquet data, I can't use with HIVE

[jnturton]

Have you looked looked at the Hive metastore?

[porika-v]

I have connected to HIVE Metastore, but my application depends mainly on metadata, so we are drill INFORMATION SCHEMA as it is virtual datastore and we have use metadata. queries are too slow on INFORMATION SCHEMA. ANY SUGGESTIONS WOULD HELP ME GREAT. THANK YOU

[jnturton]

Using a WHERE clause that constrains the "schema" column with an equality and or a LIKE predicate in your information schema query will usually help.

On 06 January 2023 06:48:23 SAST, Porika Venkatesh @.***> wrote:

I have connected to HIVE Metastore, but my application depends mainly on metadata, so we are drill INFORMATION SCHEMA as it is virtual datastore and we have use metadata. queries are too slow on INFORMATION SCHEMA. ANY SUGGESTIONS WOULD HELP ME GREAT. THANK YOU

-- Reply to this email directly or view it on GitHub: https://github.com/apache/drill/issues/2732#issuecomment-1373140572 You are receiving this because you commented.

Message ID: @.***> -- Sent from my Android device with K-9 Mail. Please excuse my brevity.