Info |
---|
Valid from Datafari v6 onwards This documentation is valid from Datafari v6 onwardsThis was a test connector, replaced by a native csv connector without the need for jdbc The CSV JDBC driver for the JDBC connector differs a little bit from the other drivers in the way it should be configured to properly work. The native CSV connector is documented: CSV Connector |
As a reminder, the proper JDBC CSV driver to use is the following: https://github.com/jprante/jdbc-driver-csv
1. Database connection
Unlike the other drivers, it does not require a database host and/or port, a database name, a user and a password, even if, unfortunately, those parameters are mandatory for the JDBC connector. So you must set something for those parameters anyway, whatever you want BUT an empty string !
The only parameter that is really important and that matters, is the “Database raw connection string”. The CSV JDBC driver must connect to a local folder (local on the machine where the job using the CSV driver will run), containing CSV files you want to crawl. So the “Database raw connection string” must be set with the absolute path of the local folder containing the CSV files to crawl, for example ‘/home/francelabs/csv’. The specified folder and all the files it contains must also have read permissions for the user running the MCF instance, which is ‘datafari’ by default on a standard Datafari installation. We recommend the files to be at the root of the specified folder, we have not tested the behavior with subfolders.
2. CSV column separator
Currently, the separator used for columns in the CSV files is not configurable, IT MUST BE a comma char: ,
3. Queries
Concerning the queries, there are some things to understand in order to build working ones.
...