Re: table schema for parquet file is not working

2023-07-12 Thread James Turton
Hi Prabhakar From what I recall, Drill won't consider a provided schema when querying Parquet because Parquet files bundle their own schema. You might need to use a SQL function like COALESCE(TRAN_AMOUNT, 1.11) and possibly put that in a SQL view for reuse. Regards James On 2023/07/11

Re: Respecting formats restriction when using storage-plugins-override.conf

2023-07-12 Thread Charles Givre
My sense of what is happening in your use case is that the configs that exist in the UI are overriding the conf file. What it seems like you want is the opposite order of precedence. I've never used the conf files for this, so I don't have a lot of experience with that, but it would seem

Re: Respecting formats restriction when using storage-plugins-override.conf

2023-07-12 Thread Charles Givre
Hi Stefan, My biggest piece of advice here would just be to make sure the plugins specified in the override file do not conflict with the UI-based configs. It may make sense to have completely different configs in each location. IE: dfs-conf and (plain) dfs. I think that should solve all

Re: Respecting formats restriction when using storage-plugins-override.conf

2023-07-12 Thread Stefan Ziegler
Hi Charles not sure if I understand you correctly: what do you mean with “not conflicting”. My attempt is to not use the UI at all to configure storages. I thought this can be achieved by overriding the defaut storages with the “override” file. This seems to work except the strange behaviour

Re: Respecting formats restriction when using storage-plugins-override.conf

2023-07-12 Thread Stefan Ziegler
Thanks. Yes. I'm going to try the renaming approach. Not a rant but isn't the whole point of a "storage-plugins-override.conf" to override storage plugin configuration? Btw: I'm in embedded mode. So I guess I can also use the config files from /tmp/drill after "fixing" the format configuration