Yes, connect to Hive in 3.8 and 4.2 using ODBC. 3.8 is 32-bit, 4.2 is 64-bit.
We use the "generic ODBC" category, and then point to the ODBC driver/config as set up in ODBC admin.
I can query Hive normally in 4.2 64 bit, that is not the problem.
The problem is when I use Profiling tool from a query results list.
Test#1
steps:
1. launch TDP 4.2 64 bit
2. connect to Hive , using ODBC 64 bit driver (Hortonworks ODBC driver)
3. Run query
4. Examine results
5. select Profiling tab in the results grid
6. Observe the summary profiling information -this works ok
7. Click "full profiling" at top-right -
Expected result : I should get the popup about full profiling options
Actual result: Nothing happens in the UI (but i see the exception in log, as in original post)
Test#2:
1. launch TDP 4.2 64 bit
2. connect to Oracle DB using Oracle driver
3. Run query
4. Examine results
5. select Profiling tab in the results grid
6. Observe the summary profiling information -this works ok
7. Click "full profiling" at top-right -
Expected result : I should get the popup about full profiling options
Actual result: popup appears and I can select Full profiling
8. Observe the full profiling data