[GitHub] [hive] asolimando commented on pull request #4050: HIVE-27065: Exception in partition column statistics update with SQL Server db when histogram statistics is not enabled

["asolimando (via GitHub)" <gi...@apache.org>]

asolimando commented on PR #4050:
URL: https://github.com/apache/hive/pull/4050#issuecomment-1425333371

   @VenuReddy2103 thanks for your PR, I have a couple of questions: did you try with other backend DBs as well? Did you encounter a similar error? I am curious because this part of the code does not seem to be DB specific, so I'd rather confirm quickly if that's an issue only with MSSQL or if it's more general, and that we don't regress on other databases by using `setBytes()` in place of `setObject()`.
   
   Have you tried the same code when histogram is actually computed? Did it fail? I am asking because it might be an artifact of the uninitialized `histogram` field.
   
   Since the `bitvector` field is totally analogous (same data type, `byte array`, and written with `setObject()`), apart from the fact that it is always computed, I am wondering if that's not the real difference, as it's successfully written to MSSQL with the `.setObject()` call. 
   
   Can you update here with the actual return value of `mPartitionColumnStatistics.getHistogram()` and of `mPartitionColumnStatistics.getBitVector()` at the time of the call by putting a breakpoint in the `insertIntoPartColStatTable` function? That would help shed some light on what's actually going on there.
   
   Thanks!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: gitbox-unsubscribe@hive.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: gitbox-unsubscribe@hive.apache.org
For additional commands, e-mail: gitbox-help@hive.apache.org