Add support for the new DATE type introduced by elastic/elasticsearch#37693

When:

1. the application binds column-wise to the result set; and
2. the result set contains a number of rows lower than app's rows array buffer (for the bound column); and
3. ES/SQL appends to the first and only result set a cursor that (when executed) returns no further rows (i.e. an "empty cursor"), the driver will return no results back to the application.

The reason being that the result for the last cursor execution is returned as the final result code.

SQLGetInfo()'s attributeSQL_DBMS_VER requires Elasticsearch'es version (mostly for error reporting/logging). This is currently statically defined and need to be changed to deliver whatever the root REST API delivers (http://[::1]:9200 / version / number or qualified).

At the end of running the installer for the 64-bit driver, the installer will launch ODBC Data Source Administrator (32-bit), instead of the ... (64-bit) version.

Consider an automated import and integration execution of the tests in SqlProtocolTestCase.java.

Longer term objective, to bring build scripts inline with .NET clients.

No password protection, no bundling

When the GUI is brought up on connect, the DSN name and description should be made un-editable.
The reason being that these changes are not going to be saved, the GUI is brought up to change the connection parameters only (since potentially an initial connection attempt failed).

Add a client_id JSON request parameter to differentiate between odbc32 and odbc64 clients.

http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/block_install_on_os.html

Support for Alpha:
Windows 10
Windows Server 2016

The credentials are currently stored in the registry in plain text, under ODBC mandated UID and PWD keys. This area needs some effort to find better ways to handle this storage.

The connection attributes SQL_ATTR_CURRENT_CATALOG/SQLGetConnectAttr() requires the current database/catalog and SQL_USER_NAME/SQLGetInfo() the current username.
The implementation needs to be changed from the current SYS CATALOG/first_result and HTTP auth username to using the two now available functions above.

See elastic/elasticsearch#35946

Ensure that the sample data indexed by Kibana works through the driver.

Currently, the only way to configure the tracing of actions the driver is asked to perform is possible by using environment variables. A more practical (and possibly very useful for pre-releases) way of configuring this is through the DSN, per connection. This would require a new tab to the DSN editor:

• enable/disable logging;
• allow choose a directory where to write the log fileS;
• the log level.

Add a new field into the request to indicate what OS the driver is running under.

The driver accesses the registry directly currently when a DSN name is received in the connection string.
This should be replaced with odbccp32.dll's SQLGetPrivateProfileString() & co. instead (for better portability also).

http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/install_vcredist.html

Will implement as a simple check and then bail out if it is not installed, with a prompt to install it.

We do have options to bundle the VC++ modules into the installer using the merge modules, but this adds quite a lot of size to the download - we can defer this decision post-alpha.

Just filing to share a crash event for those who may run into something similar on unsupported Windows OSes.

crash_event.xml.zip

Certainly, Windows 2012 R2 does not meet the pre-requisites for the ODBC driver installation. However, we currently allow the ODBC driver to install successfully (without errors) on this OS version (#146).

I am actually able to bring data into Excel on this OS version and it appears to work fine; the piece that crashes is the Test Connection button from the DSN setup.

as per https://discuss.elastic.co/t/setting-up-odbc-connection-to-es-v6-6/170941

If an ES reply goes over the maximum configured answer size, the error is logged, but no specific error is attached to the database handle OR returned to the caller.

Installer's build.bat needs to be hooked into driver's, so that building of both can be managed by the top-level build.bat.

This currently needs:

• driver's build.bat changed so that: (1) it accepts [a] new parameter[s] to take the signing cert and pass files; (2) the package and clean targets call installer's build.bat with release (if signing) and clean params respectively.
• installer's build.bat clean action should reset installer code: (1) remove any build byproducts; (2) revert any changes made to the code tree (like installer\src\Installer\Properties\AssemblyInfo.cs).
• installer's build.bat should only bootstrap packet when needed (like when building the installer, but not cleaning), to speed up the build lifecycle. Avoid running paket bootstrap on clean.

When opening the GUI on connect (i.e. not while editing existing / adding a new DSN), pressing on the Connect button is propagated to the driver as a Cancel action.

Hi.
I'm setting Elasticsearch SQL ODBC Driver.
At that time I noticed　Can you use File DSN?

The following is written as 「three tabs」.
Configuration

The next step is to configure a DSN. You can choose between the following options mapped on the first three tabs of the Administrator application:

However, only「User DSN」and「System DSN」are written in「2.Configure a DSN」.

Thank you for your review.

Branch from master, backport changes to 6.x

• Merge build processes for driver and MSI into a single build command. This is to simplify the build script process and remove the need to perform cd <dir> commands in the release manager. - @codebrain / @bpintea - #69
• Unit / integration tests for editor dialog after moving to an MVVM or MVC architecture.- @codebrain
• Review AssemblyInfo version patching and ensure consistency across all .NET projects. - @codebrain - https://github.com/bpintea/elasticsearch-sql-odbc/tree/feature/integrate_installer_build
• Consolidate .gitignore files across the repo. - @codebrain - #71
• Ensure copyright year is present in AssemblyInfo files. - @codebrain to find out if needed (none of the other DLLs use year). - https://github.com/bpintea/elasticsearch-sql-odbc/tree/feature/integrate_installer_build
• Align the editor to either all tabs or all space. (The driver uses tabs, but we can delineate between the two). @codebrain to implement editor rules as defined by Microsoft team. - #67
• Chain (tick-box-dependent) the ODBC Data Source Administrator app to the installer - include getting started screen (as per Elasticsearch MSI) @codebrain - #65
• Considerations the VS redistributable @codebrain / @bpintea
• Documentation: installer @codebrain; editor @bpintea
• Blog post prep @bpintea
• DSN editor tooltips? (optional) - #67
• 32-bit build (optional):
• for the driver @bpintea - #76
• for the installer @codebrain - #70, #74, #79
• rename DSN binding DLL to include 32 for 32-bit builds; @bpintea - #63
• integrate x86 build into RM: https://github.com/elastic/release-manager/pull/506
• Validations on DSN editor for:
• Name field - limit to registry key characters - #59
• Ensure all field entries are no longer than 512 characters - #59
• Launch ODBC editor on close (with checkbox) #79

Pressing the "Browse.." button to open the file chooser will make the window unresponsive.
Likely connected to the threading apart. model.

Add documentation about all available parameters in the connection string.

Attempting to remove using the MSI and not using the control panel gives an error saying I need VC 2017 C++ libraries installed.

The cursor received from the server as a wide-string is stored as such and converted from UTF8 to multibyte string using a static buffer.
The static buffer, currently sized to 4K is too small to accommodate the cursor generated for large queries.
The solution here is to simply ditch the buffer, given that that the cursor is actually a Base64 encoded string and thus will straight forward convert to an ASCII string.

When connection testing, the DSN resolution could take some time (a good few seconds, depending on DHCP/DNS setting etc.), especially visible when the hostname is unresolvable. In this case, it might be worth adding a "working" indicator, if there's a quick solution for it.

Review the final form of https://github.com/bpintea/elasticsearch-sql-odbc/blob/feature/install_notice/NOTICE.txt.
Review the file in its installed format, with the 3rd party software licenses and notices included.

Need the following integration tests:

Test 1: Assert correct installation

1. Install driver
2. Assert files copied
3. Assert registry keys are present
4. Install dependent Elasticsearch version
5. Configure DSN
6. Insert document into new index
7. Assert ODBC connection is successful and data retrieved

Test 2: Assert correct un-installation

1. [As per Test 1]
2. Uninstall driver
3. Assert files removed
4. Assert registry keys are deleted

Test 3: Assert upgrade is prevented

1. [As per Test 1]
2. Attempt upgrade to a later version
3. Assert upgrade not taken place

Test 4: Assert operating system check

1. Attempt driver install on unsupported operating system
2. Assert error message received and not installed

Test 5: Assert C++ dependancy check

1. Attempt driver install on operating system without C++ runtime installed
2. Assert error message received and not installed

Test 6: Assert .NET dependancy check

1. Attempt driver install on operating system without .NET framework installed
2. Assert error message received and not installed

Using Pester and the supporting PowerShell scripts from the windows-installers project will get us further with less effort. If expedience is a high priority, this may be preferable. The ODBC installer is a much simpler beast than the Elasticsearch installer, making the simpler approach of Pester vs. xUnit/NUnit less of an issue.

Consider Unit tests for editor dialog after moving to an MVVM or MVC architecture.

The IP datatype uses currently the same ID as text/keyword. This prevents a client from explicitly specifying a value as IP and not just text. Note this limitation, should any developer actually consider using the ODBC API over REST.
Same for geo types, if they will re-use text/keyword ID.

This bug appears sporadically; so far not consistently reproducible.

UJSON4C library's UJDecode() fails to decode received JSON answer; the answer is correct. The failure is always Trailing data.
Sometimes the answer buffer gets corrupted after the function returns, although no writing to it seems to occur in the library.

Log excerpts:

Mon Nov 19 09:57:26 2018 - [DEBUG] post_json()@connect.c:568 [STMT@0x000001CBF9FA6860] POSTing JSON [38] `{"query": "SYS TYPES", "mode": "ODBC"}`.
[...]
Mon Nov 19 09:57:26 2018 - [DEBUG] attach_answer()@queries.c:223 [STMT@0x000001CBF9FA6860] attaching answer [2324]`{"columns":[{"name":"TYPE_NAME","type":"keyword"},{"name":"DATA_TYPE","type":"integer"},{"name":"PRECISION","type":"integer"},{"name":"LITERAL_PREFIX","type":"keyword"},{"name":"LITERAL_SUFFIX","type":"keyword"},{"name":"CREATE_PARAMS","type":"keyword"},{"name":"NULLABLE","type":"short"},{"name":"CASE_SENSITIVE","type":"boolean"},{"name":"SEARCHABLE","type":"short"},{"name":"UNSIGNED_ATTRIBUTE","type":"boolean"},{"name":"FIXED_PREC_SCALE","type":"boolean"},{"name":"AUTO_INCREMENT","type":"boolean"},{"name":"LOCAL_TYPE_NAME","type":"keyword"},{"name":"MINIMUM_SCALE","type":"short"},{"name":"MAXIMUM_SCALE","type":"short"},{"name":"SQL_DATA_TYPE","type":"integer"},{"name":"SQL_DATETIME_SUB","type":"integer"},{"name":"NUM_PREC_RADIX","type":"integer"},{"name":"INTERVAL_PRECISION","type":"integer"}],"rows":[["BYTE",-6,3,"'","'",null,2,false,3,false,false,false,null,0,0,-6,0,10,null],["LONG",-5,19,"'","'",null,2,false,3,false,false,false,null,0,0,-5,0,10,null],["BINARY",-3,2147483647,"'","'",null,2,false,3,true,false,false,null,null,null,-3,0,null,null],["NULL",0,0,"'","'",null,2,false,3,true,false,false,null,null,null,0,0,null,null],["INTEGER",4,10,"'","'",null,2,false,3,false,false,false,null,0,0,4,0,10,null],["SHORT",5,5,"'","'",null,2,false,3,false,false,false,null,0,0,5,0,10,null],["HALF_FLOAT",6,16,"'","'",null,2,false,3,false,false,false,null,0,16,6,0,2,null],["SCALED_FLOAT",6,19,"'","'",null,2,false,3,false,false,false,null,0,19,6,0,2,null],["FLOAT",7,7,"'","'",null,2,false,3,false,false,false,null,0,7,7,0,2,null],["DOUBLE",8,15,"'","'",null,2,false,3,false,false,false,null,0,15,8,0,2,null],["KEYWORD",12,256,"'","'",null,2,true,3,true,false,false,null,null,null,12,0,null,null],["TEXT",12,2147483647,"'","'",null,2,true,3,true,false,false,null,null,null,12,0,null,null],["IP",12,39,"'","'",null,2,false,3,true,false,false,null,null,null,12,0,null,null],["BOOLEAN",16,1,"'","'",null,2,false,3,true,false,false,null,null,null,16,0,null,null],["DATE",93,24,"'","'",null,2,false,3,true,false,false,null,3,3,9,3,null,null],["UNSUPPORTED",1111,0,"'","'",null,2,false,3,true,false,false,null,null,null,1111,0,null,null],["OBJECT",2002,0,"'","'",null,2,false,3,true,false,false,null,null,null,2002,0,null,null],["NESTED",2002,0,"'","'",null,2,false,3,true,false,false,null,null,null,2002,0,null,null]]}`.
Mon Nov 19 09:57:26 2018 - [ERROR] attach_answer()@queries.c:230 [STMT@0x000001CBF9FA6860] failed to decode JSON answer: Trailing data ([2324] `¤² p«U`).

Mon Oct 22 10:00:30 2018 - [DEBUG] post_json()@connect.c:566 [STMT@0x0000018AA177EBC0] POSTing JSON [108] `{"query": "SYS COLUMNS CATALOG '7879474408f44e9ca98d1597e659dfe2' TABLE LIKE 'users' ESCAPE '\\'  LIKE '%'"}`.
[...]
Mon Oct 22 10:00:30 2018 - [DEBUG] attach_answer()@queries.c:222 [STMT@0x0000018AA177EBC0] attaching answer [1665]`{"columns":[{"name":"TABLE_CAT","type":"keyword"},{"name":"TABLE_SCHEM","type":"keyword"},{"name":"TABLE_NAME","type":"keyword"},{"name":"COLUMN_NAME","type":"keyword"},{"name":"DATA_TYPE","type":"integer"},{"name":"TYPE_NAME","type":"keyword"},{"name":"COLUMN_SIZE","type":"integer"},{"name":"BUFFER_LENGTH","type":"integer"},{"name":"DECIMAL_DIGITS","type":"integer"},{"name":"NUM_PREC_RADIX","type":"integer"},{"name":"NULLABLE","type":"integer"},{"name":"REMARKS","type":"keyword"},{"name":"COLUMN_DEF","type":"keyword"},{"name":"SQL_DATA_TYPE","type":"integer"},{"name":"SQL_DATETIME_SUB","type":"integer"},{"name":"CHAR_OCTET_LENGTH","type":"integer"},{"name":"ORDINAL_POSITION","type":"integer"},{"name":"IS_NULLABLE","type":"keyword"},{"name":"SCOPE_CATALOG","type":"keyword"},{"name":"SCOPE_SCHEMA","type":"keyword"},{"name":"SCOPE_TABLE","type":"keyword"},{"name":"SOURCE_DATA_TYPE","type":"short"},{"name":"IS_AUTOINCREMENT","type":"keyword"},{"name":"IS_GENERATEDCOLUMN","type":"keyword"}],"rows":[["7879474408f44e9ca98d1597e659dfe2",null,"users","password",12,"TEXT",0,2147483647,null,null,1,null,null,12,0,2147483647,1,"YES",null,null,null,null,"NO","NO"],["7879474408f44e9ca98d1597e659dfe2",null,"users","password.keyword",12,"KEYWORD",0,2147483647,null,null,1,null,null,12,0,2147483647,1,"YES",null,null,null,null,"NO","NO"],["7879474408f44e9ca98d1597e659dfe2",null,"users","user",12,"TEXT",0,2147483647,null,null,1,null,null,12,0,2147483647,2,"YES",null,null,null,null,"NO","NO"],["7879474408f44e9ca98d1597e659dfe2",null,"users","user.keyword",12,"KEYWORD",0,2147483647,null,null,1,null,null,12,0,2147483647,1,"YES",null,null,null,null,"NO","NO"]]}`.
Mon Oct 22 10:00:30 2018 - [ERROR] attach_answer()@queries.c:228 [STMT@0x0000018AA177EBC0] failed to decode JSON answer (`{"columns":[{"name":"TABLE_CAT","type":"keyword"},{"name":"TABLE_SCHEM","type":"keyword"},{"name":"TABLE_NAME","type":"keyword"},{"name":"COLUMN_NAME","type":"keyword"},{"name":"DATA_TYPE","type":"integer"},{"name":"TYPE_NAME","type":"keyword"},{"name":"COLUMN_SIZE","type":"integer"},{"name":"BUFFER_LENGTH","type":"integer"},{"name":"DECIMAL_DIGITS","type":"integer"},{"name":"NUM_PREC_RADIX","type":"integer"},{"name":"NULLABLE","type":"integer"},{"name":"REMARKS","type":"keyword"},{"name":"COLUMN_DEF","type":"keyword"},{"name":"SQL_DATA_TYPE","type":"integer"},{"name":"SQL_DATETIME_SUB","type":"integer"},{"name":"CHAR_OCTET_LENGTH","type":"integer"},{"name":"ORDINAL_POSITION","type":"integer"},{"name":"IS_NULLABLE","type":"keyword"},{"name":"SCOPE_CATALOG","type":"keyword"},{"name":"SCOPE_SCHEMA","type":"keyword"},{"name":"SCOPE_TABLE","type":"keyword"},{"name":"SOURCE_DATA_TYPE","type":"short"},{"name":"IS_AUTOINCREMENT","type":"keyword"},{"name":"IS_GENERATEDCOLUMN","type":"keyword"}],"rows":[["7879474408f44e9ca98d1597e659dfe2",null,"users","password",12,"TEXT",0,2147483647,null,null,1,null,null,12,0,2147483647,1,"YES",null,null,null,null,"NO","NO"],["7879474408f44e9ca98d1597e659dfe2",null,"users","password.keyword",12,"KEYWORD",0,2147483647,null,null,1,null,null,12,0,2147483647,1,"YES",null,null,null,null,"NO","NO"],["7879474408f44e9ca98d1597e659dfe2",null,"users","user",12,"TEXT",0,2147483647,null,null,1,null,null,12,0,2147483647,2,"YES",null,null,null,null,"NO","NO"],["7879474408f44e9ca98d1597e659dfe2",null,"users","user.keyword",12,"KEYWORD",0,2147483647,null,null,1,null,null,12,0,2147483647,1,"YES",null,null,null,null,"NO","NO"]]}`): Trailing data.

Thu Oct 25 12:21:10 2018 - [DEBUG] post_json()@connect.c:566 [STMT@0x00000273EA3D3040] POSTing JSON [72] `{"query": "SYS TABLES CATALOG LIKE '%' ESCAPE '\\' TYPE 'TABLE','VIEW'"}`.
[...]
Thu Oct 25 12:21:10 2018 - [DEBUG] attach_answer()@queries.c:223 [STMT@0x00000273EA3D3040] attaching answer [775]`{"columns":[{"name":"TABLE_CAT","type":"keyword"},{"name":"TABLE_SCHEM","type":"keyword"},{"name":"TABLE_NAME","type":"keyword"},{"name":"TABLE_TYPE","type":"keyword"},{"name":"REMARKS","type":"keyword"},{"name":"TYPE_CAT","type":"keyword"},{"name":"TYPE_SCHEM","type":"keyword"},{"name":"TYPE_NAME","type":"keyword"},{"name":"SELF_REFERENCING_COL_NAME","type":"keyword"},{"name":"REF_GENERATION","type":"keyword"}],"rows":[["7879474408f44e9ca98d1597e659dfe2","",".kibana","TABLE","",null,null,null,null,null],["7879474408f44e9ca98d1597e659dfe2","",".security-6","TABLE","",null,null,null,null,null],["7879474408f44e9ca98d1597e659dfe2","","employ_name","TABLE","",null,null,null,null,null],["7879474408f44e9ca98d1597e659dfe2","","users","TABLE","",null,null,null,null,null]]}`.
Thu Oct 25 12:21:10 2018 - [ERROR] attach_answer()@queries.c:230 [STMT@0x00000273EA3D3040] failed to decode JSON answer: Trailing data ([775] `6ÈD$æõ`).

Building with .\build.bat type:Release package will produce a .zip file that looks like: esodbc-6.5.0-windows-x86_64.zip/esodbc-6.5.0-windows-x86_64/esodbc-6.5.0-windows-x86_64/esodbc6u.dll, which is incorrect.

Building with .\build.bat type:Release package:-SNAPSHOT will work as expected (no unnecessary 2nd level)

In case of editing or adding a DSN, the Save and Test Connection should only be activated if there is valid input, as follows:

• the Save button requires a DSN Name and Hostname filled in;
• the Test Connection button requires at least the Hostname field filled in. The delux feature here would be do have validation on the field (hostname or IPv4/6), but this only if there is already some ready to use framework functionality (regexps or building a parser here might be inadvisable).

Add the GUI settings for:

• applying the local timezone for times;
• leniency for multivalue fields;
• format of floats.

If the Verify this connection (recommended) tick box is left ticked in the "Advanced..." dialog (or simply don't access the "Advanced..." dialog), the editor will pop up in the "connection" mode and the "Connect" button is never activated.

Instead, it should be pop-up in "save" mode and allow editing the DSN name and description and eventually saving the configuration.

Creating a File DSN will work though if the parameters are provided manually in the "Advanced..." dialog and the connection verification is left out; in this case the editor will simply not be invoked.

https://blogs.msdn.microsoft.com/windows_hardware_certification/2017/11/13/starting-in-february-2018-packages-signed-using-a-sha-1-digest-algorithm-and-certificate-chain-will-no-longer-be-accepted/

Have started a conversation with @kd8drx, @nlao and @russcam about acquiring a new certificate.

For alpha, have agreed that signing with the Elasticsearch MSI certificate or unsigned are acceptable routes.

Light check of the validity of the hostname field: [\w]?http[s]?:// prefix should return specific error message.

Currently, side-by-side installation of different driver versions is only supported if they are for different architectures (i.e. x86 and x64 drivers can co-exist).
This ticket tracks the feature to allow the installer do upgrades within the same architecture; for example a 7.0.1 x86 be upgraded to a 7.0.2 x86. (This currently requires uninstalling the 7.0.1 beforehand.)

https://www.elastic.co/guide/en/elasticsearch/reference/current/sql-odbc-installation.html
The doc says: "If you fail to meet any of the prerequisites the installer will show an error message and abort the installation."

I installed ODBC driver 6.7.0 (esodbc-6.7.0-windows-x86) on a Windows Server 2012 R2 Datacenter machine (Windows Server 6.3 Build 9600) and it installs successfully without an error even though it does not meet the prerequisites.

1. It is probably worth renaming the DLL and LIB files from elasticodbc7u.dll / .lib to esodbc7u.dll / .lib. That makes them 8 characters long and removes the need to worry about MSI short filename generation.
2. The license.txt file... if we can make it a license.rtf (rich text format) file then we can simply include it into the license acceptance window without any modifications.

3. elasticsearch-sql-odbc/driver/setup.c

   Lines 111 to 115 in aedca96

   	/* add a sample DSN */
   	if (! ConfigDSNW(NULL, ODBC_ADD_DSN, lpszDriver, sample_dsn)) {
   	WARN("failed to provision a sample DSN.");
   	/* no further error indication though, install succeedes */
   	}

   : can be removed and replaced by an ODBCDataSouce target in the MSI and have the DSN created in the installation routine.
4. DLL with versioning info.

Evaluate the effort and safety of a 32bit build of the installer.

Note: some preliminary findings out of a quick check:

• code-wise, a s/-windows-x86_64/-windows-x86 in installer/src/Installer/Program.cs:56 would be enough to get a 32bit .msi;
• the target installation should be changed from Program Files to Program Files (x86) [1];
• the installation eventually fails with error 13, potentially related to how the ODBC setup routines are called?
  

[1] The 32bit .msi find the 64bit driver and so it refuses to install -- not sure if the install path might be the only cause -- but this reveals that the name of the driver itself should bear the 32 tag (??).

The code itself can simply be made to work with 32-bit builders, resulting in a 32-bit installer (vs. having a 64-bit installer deliver both 64-bit and 32-bit drivers). Reasons for that could be:

• low effort of having a 32-bit installer (no significant changes required between the builds);
• low RM integration effort (besides the current build.bat setup 64 package we'd add build.bat setup 32 package);
• testing could be run similarly irrespective of underlying platform;
• the 32-bit installer could theoretically be used on 32-bit OSes (small chance of this occurrence, though);
• better user-experience: the user would need to make a choice right from the start and thus be made aware of the split (and of otherwise hidden potential issues later).

When editing an existing DSN, emptying one field that had been previously filled in (like Password) and saving the DSN will send the DSN string back to the driver having the previous value of the field, rather than an empty value, as saved.

In case Elasticsearch would return the incorrect JSON data format for the signaled data type (like float for DATETYPE), ensure that the application would be provided with a diagnostic (not just the SQL_ERROR).

@codebrain ,
I had a look on why building the installer fails on the updated RM VM and I guess the following points might need to be addressed:

• as per error.log, installer\build.bat would need a cd %~dp0 before calling .paket\paket.bootstrapper.exe (so that the .exe can be found);
• the fix above might potentially need to be applied also to the place where ODBCInstaller.exe is invoked:

PS C:\[...]\elasticsearch-sql-odbc\installer> .\src\Installer\bin\Release\ODBCInstaller.exe 7.0.0-alpha9 C:\[...]\elasticsearch-sql-odbc\builds\

Unhandled Exception: System.Exception: The directory '..\..\packages\WixSharp.wix.bin\tools\bin' could not be found
   at ODBCInstaller.Program.Main(String[] args)

The above does work if called from within C:\[...]\elasticsearch-sql-odbc\installer\src\Installer.

• not positive on all possible formats, but ${versionQualifier} for a build candidate can look like alpha1 (see above linked error.log). This wouldn't be accepted by the VersionRegex regex. So I guess either the regex or the command line parameter in build.gradle (and corresponding release line) needs changing;
• the ${versionQualifier} var can also be missing/empty, probably for GA releases?
• with current code, once the versioning string is accepted, it seems that ODBCInstaller.exe is launched with the path to the build directory of the driver as parameter, which errs, since the driver files aren't there:

PS C:\[...]\elasticsearch-sql-odbc> .\installer\build.bat release esodbc-7.0.0-alpha9 C:\[...]\certificate.p12 C:\[...]\passwd.txt
[...]
./src/Installer/bin/Release/OdbcInstaller 7.0.0-alpha9 C:\[...]\elasticsearch-sql-odbc\builds\

Unhandled Exception: System.InvalidOperationException: Sequence contains no matching element
   at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source, Func`2 predicate)
   at ODBCInstaller.Program.GetDriverFileInfo(String zipContentsDirectory)
   at ODBCInstaller.Program.Main(String[] args)

which seems to occur in GetDriverFileInfo. Could it be that b0226ab needs further adjustments to no longer expect a .zip file or to have the .zip previously unzipped?

@Conky5 : could you please confirm when versionQualifier might be empty in build.gradle and what format could it have, when not empty?

Connection testing (with authentication, but no TLS) on a 6.6.2+ release on 32bit only will crash the ODBC Administrator.

Since the MSI signing is not currently done with an EV certificate, the SmartScreen would prompt the user with a warning. Note in the documentation about this, to prepare the user.