The issue is that for those customers who do have such storage plugin
names, it's too late to rename after an offline upgrade - as there is no
easy way to access the storage plugin configurations if Drillbits are down
(due to Drillbit start-up failing). Might be okay, if admins perform a
rolling
>From the Drill code workspaces are already case insensitive (though the
documentation states the opposite). Since there were no complaints from the
users so far, I believe there are not many (if any) who uses the same names
in different case.
Regarding those users that already have duplicating
Paul, I think this proposal was specific to storage plugin and workspace
*names*. And not for the whole of Drill.
I agree it makes sense to have these names case insensitive, to improve
user experience. The only impact to current users I can think of is if
someone created two storage plugins dfs
Hi All,
As it turns out, this topic has been discussed, in depth, previously. Can't
recall if it was on this list, or in a JIRA.
We face a number of constraints:
* As was noted, for some data sources, the data source itself has case
insensitive names. (Windows file systems, RDBMSs, etc.)
* In
Yes, that seems ok to me...since the plugin name and workspace are logical
entities and don't correspond to a path.
There could be compatibility issues if certain users have relied on the
case-sensitive names, but those would be temporary.
Aman
On Tue, Jun 12, 2018 at 8:35 AM, Arina Yelchiyeva <
To make it clear we have three notions here: storage plugin name, workspace
(schema) and table name (dfs.root.`/tmp/t`).
My suggestion is the following:
Storage plugin names to be case insensitive (DFS vs dfs, INFORMATION_SCHEMA
vs information_schema).
Workspace (schemas) names to be case
Drill is dependent on the underlying file system's case sensitivity. On
HDFS one can create 'hadoop fs -mkdir /tmp/TPCH' and /tmp/tpch which are
separate directories.
These could be set as workspace in Drill's storage plugin configuration and
we would want the ability to query both. If we
