ODBC Manager also addresses some of the problems. Users may also encounter unixODBC, mac:ODBC, and other driver managers. Mac Classic a/k/a Mac OS 9: OpenLink's Mac Classic client installer provides its own driver manager for this platform. Many applications that support ODBC/OleDB for database access also support ADO.NET. If that option is available you should be able to use it by registering VistaDB as an ADO.NET provider for the current process. For details on how to register VistaDB as an ADO.NET provider, see Deploying VistaDB with your Application.
ODBC driver managers use configuration files to define and configure ODBC datasources and drivers. To configure an ODBC connection for Mac OS X, note the followingprocedure:
Step 1: Driver Installer Updates Sample Configuration Files
Before you connect to Drill through an ODBC client tool on Mac OS X, the driver installer copies the following configuration files in /Library/mapr/drill/Setup
to your home directory unless the files already exist in your home directory:
mapr.drillodbc.ini
odbc.ini
odbcinst.ini
In your home directory, rename the files as hidden files. Use sudo if necessary:
.mapr.drillodbc.ini
.odbc.ini
.odbcinst.ini
The installer for Mac OS X creates a sample user DSN in odbc.ini
in either of the following locations:
~/Library/ODBC/odbc.ini
~/.odbc.ini
Depending on the driver manager you use, the user DSN in one of these files will be effective.
Note
The System and User DSN use different ini files in different locations on OS X.
Step 2: Set Environment Variables
The driver installer installs the .mapr.drillodbc.ini
file to your home directory and adds an entry to the $HOME/.odbc.ini
file.
If you installed the iODBC driver manager using the DMG, the dynamic linker (DYLD) libraries are installed in /usr/local/iODBC/lib
. The launchd.conf
file contains contents such as the following:
Restart the Mac OS X or run launchctl load /etc/launchd.conf
.
Step 3: Define the ODBC Data Sources in .odbc.ini
Vistadb Odbc Drivers For Mac
Define the ODBC data sources in the ~/.odbc.ini
configuration file for your environment.
You set the following properties for using Drill in embedded mode:
You set the following properties for using Drill in distributed mode:
Authentication Properties
If the Drillbit requires authentication, uncomment the AuthenticationType, add an AuthenticationType, and configure properties. If the Drillbit does not require authentication (or to configure no password protection), you can use the No Authentication option. You do not need to configure additional settings.
- Kerberos
- See the MIT Kerberos documentation for installing and configuring a Kerberos environment, which is beyond the scope of the information provided here.
- To specify the Kerberos mechanism:
- Set the AuthenticationType to Kerberos.
- Set the KrbServiceHost property to the FQDN of the Drill server host.
- Set the KrbServiceName property to the Kerberos service principal name of the Drill server.
- Plain (or Basic Authentication)
- Configure the UID to an appropriate name for accessing the Drill server.
- Set the PWD property to the password corresponding to the UID.
To configure no password protection, select No Authentication.
Direct and ZooKeeper Quorum Properties
To use Drill in distributed mode, set ConnectionType to Zookeeper, get the ZKQuorum and ZKClusterID values from the drill-override.conf
file, and define the ZKQuorum and ZKClusterID properties. Format ZKQuorum as a comma separated list of ZooKeeper nodes in the following format:<host name/ip address> : <port number>, <host name/ip address> : <port number>, . . .
For example:
ZKQuorum=centos23:5181,centos28:5181,centos29:5181
ZKClusterID=docs41cluster-drillbits
To use Drill in local mode, do not define the ZKQuorum and ZKClusterID properties. Start Drill using the drill-localhost command, set ConnectionType to Direct, and define HOST and PORT properties. For example:
HOST=<IP address of drillbit>:5181
PORT=31010
Driver Configuration Options describes configuration options available for controlling thebehavior of DSNs using the Drill ODBC Driver.
Sample Configuration File
The following sample shows a possible configuration for using Drill in embedded mode.
Note
The password should be provided in the connection string or ODBC application at connection time, not in the INI file.
Step 4: Configure the Drill ODBC Driver
Configure the Drill ODBC Driver for your environment by modifying the .mapr.drillodbc.ini
configurationfile. This configures the driver to work with your ODBC driver manager. The following sample shows a possible configuration, which you can use as is if you installed the default iODBC driver manager.
Example
Configuring .mapr.drillodbc.ini
To configure the Drill ODBC Driver in the .mapr.drillodbc.ini
configuration file, complete the following steps:
Open the
.mapr.drillodbc.ini
configuration file in a text editor.Edit the DisableAsync setting if you want to enable a synchronous ODBC connection for performance reasons. Change the default 0 to 1 to disable the asynchronous and enable the synchronous connection. A change in state occurs during driver initialization and is propagated to all driver DSNs.
- Save the
.mapr.drillodbc.ini
configuration file.
Vistadb Odbc Drivers For Mac Os
Next Step
Vistadb Odbc Drivers For Mac Catalina
Refer to Testing the ODBC Connection.