Hello cloudera community,   we have the following problem:   we are using powerbi with hortonworks odbc driver to connect to hive in cluster ambari 2.6.2.2, hdp 2.6.5   the connection is made successfully, but when making a query on a table that has 23 thousand rows, it returns the following error below:   Erro do OLE DB ou do ODBC : [DataSource.Error] ERROR [HY000] [Hortonworks][Hardy] (35) Error from server: error code: '0' error message: 'Invalid OperationHandle: OperationHandle [opType=EXECUTE_STATEMENT, getHandleIdentifier()=0345789f-6c9a-4990-adf5-f823232338]'.. if we make a query putting a limiter of at most 10,000 thousand lines in the select, the result is ok what could be causing this problem?   PS: there are queries in powerbi with the same ODBC in other tables that have more than 200 thousand rows and the result is OK too   ... View more

hello cloudera community,   we are trying to create a keytab with the main one:   "HTTP/hostname@DOMAIN.LOCAL"   with the command:   ktpass -princ HTTP/hostname@DOMAIN.LOCAL -mapuser livy-http -crypto ALL -ptype KRB5_NT_PRINCIPAL -pass password2022 -target domain.local -out c:\temp\livy-http.keytab   but I try to validate the ticket with this keytab returns the error:   Exception: krb_error 24 Pre-authentication information was invalid (24) Pre-authentication information was invalid   KrbException: Pre-authentication information was invalid (24) at sun.security.krb5.KrbAsRep.<init>(Unknown Source) at sun.security.krb5.KrbAsReqBuilder.send(Unknown Source) at sun.security.krb5.KrbAsReqBuilder.action(Unknown Source) at sun.security.krb5.internal.tools.Kinit.<init>(Unknown Source) at sun.security.krb5.internal.tools.Kinit.main(Unknown Source) Caused by: KrbException: Identifier doesn't match expected value (906) at sun.security.krb5.internal.KDCRep.init(Unknown Source) at sun.security.krb5.internal.ASRep.init(Unknown Source) at sun.security.krb5.internal.ASRep.<init>(Unknown Source) ... 5 more     this user "livy-http" is already created in AD and with the SPN "HTTP/hostname@DOMAIN.LOCAL" attached to it   what are we doing wrong? ... View more