[MDEV-11289] CONNECT JDBC connect_class_path not supporting wildcards per spec Created: 2016-11-16 Updated: 2016-11-16 Resolved: 2016-11-16 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - Connect |
| Affects Version/s: | 10.1.19 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | Robert Dyas | Assignee: | Olivier Bertrand |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Environment: |
centos 7 |
||
| Description |
|
The connect_class_path variable in /etc/my.cnf does not appear to support the use of wild cards. Wild cards are commonly used to specify all jar files in a particular folder. See the following for info on how wild cards are supposed to be expanded in the class path: Greatly appreciated if this could be supported! Thank you! |
| Comments |
| Comment by Olivier Bertrand [ 2016-11-16 ] |
|
I know, it failed when I tried it. The use of wild cards is supported by some Java commands such as java or javac. With JDBC tables, the class path is passed as a parameter when creating the Java virtual machine. And unfortunately it is not supported by Java to find JDBC connectors. This limitation comes from Java, not from CONNECT. |