[Refactor](External) Move Common ODBC Methods to JDBC Class and Add Default config to Disable ODBC Creation (#20566)
This PR addresses the refactoring of common methods that were originally located within the ODBC classes, but were used by the JDBC classes. These methods have now been moved to the JDBC classes to improve code readability and maintainability. In addition, we have disabled the creation of ODBC external tables by default. However, this will not affect the existing usage of ODBC. You can still enable the ODBC external tables through the enable_odbc_table setting. Please be aware that we plan to completely remove the ODBC external tables in future versions, so we recommend using the JDBC Catalog as a priority.
This commit is contained in:
@ -1766,6 +1766,15 @@ public class Config extends ConfigBase {
|
||||
@ConfField(mutable = false, expType = ExperimentalType.EXPERIMENTAL)
|
||||
public static boolean enable_fqdn_mode = false;
|
||||
|
||||
/**
|
||||
* enable use odbc table
|
||||
*/
|
||||
@ConfField(mutable = true, masterOnly = true, description = {
|
||||
"是否开启 ODBC 外表功能,默认关闭,ODBC 外表是淘汰的功能,请使用 JDBC Catalog",
|
||||
"Whether to enable the ODBC appearance function, it is disabled by default,"
|
||||
+ " and the ODBC appearance is an obsolete feature. Please use the JDBC Catalog"})
|
||||
public static boolean enable_odbc_table = false;
|
||||
|
||||
/**
|
||||
* This is used whether to push down function to MYSQL in external Table with query sql
|
||||
* like odbc, jdbc for mysql table
|
||||
|
||||
Reference in New Issue
Block a user