@ZorteK Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks. ... View more

great it works ... View more

 so this is also a scam. I was contacted for work after I looked for wirk online. Work is to complete tesks daily to generate reviews. ... View more

Welcome the community @JamesZhang  As this is an older post, we recommend starting a new thread. The new thread will provide the opportunity to provide details specific to your environment that could aid others in providing a more accurate answer to your question. ... View more

Welcome to the community @skylarblu4650. As this post is a year old, I would suggest starting a new thread. That way you can provide details specific to your setup, version, how you encountered the issue and any steps you have tried already. It will provide others more details to assist you.  ... View more

@Zifo1  Have you been able to resolved your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  ... View more

Hi @Fayza , You need to setup the Content-Type as required by the API. There should be "Request Content-Type" property where you can set the value. Also any custom header values can be added as Dynamic Property. The invokehttp processor should be very flexible to accommodate the different API requirements and request types. ... View more

You are awesome @SAMSAL Thanks so much for the great information.  This helps me a lot.  Thank goodness for this community, because I think the documentation is nearly adequate. ... View more

The error you're encountering (OperationalError: TExecuteStatementResp(status=TStatus(statusCode=3, ...) indicates that there was an issue during the execution of the Hive query. The specific error message within the response is Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.tez.TezTask. Here are a few steps you can take to troubleshoot and resolve the issue: Check Hive Query Logs: Review the Hive query logs to get more details about the error. The logs might provide information about the specific query or task that failed, including any error messages or stack traces. You can find the logs in the Hive logs directory. The location may vary based on your Hadoop distribution and configuration. Inspect Query Syntax: Double-check the syntax of your Hive SQL query. Ensure that the query is valid and properly formed. Sometimes, a syntax error can lead to execution failures. Verify Hive Table Existence: Confirm that the Hive table you're querying actually exists. If the table or the specified database is missing, it can lead to errors. Check Permissions: Verify that the user running the Python query has the necessary permissions to access and query the Hive table. Lack of permissions can result in execution errors. Examine Tez Configuration: If your Hive queries use the Tez execution engine, check the Tez configuration. Ensure that Tez is properly configured on your cluster and that there are no issues with the Tez execution. Look for Resource Constraints: The error message mentions TezTask, so consider checking if there are any resource constraints on the Tez execution, such as memory or container size limitations. Update Python Library: Ensure that you are using a compatible version of the Python library for interacting with Hive (e.g., pyhive or pyhive[hive]). Updating the library to the latest version might help resolve certain issues. Test with a Simple Query: Simplify your query to a basic one and see if it executes successfully. This can help isolate whether the issue is specific to the query or a more general problem. After reviewing the logs and checking the mentioned aspects, you should have more insights into what might be causing the error. If the issue persists, consider providing more details about the Hive query and the surrounding context, so we can offer more targeted assistance. ... View more

The error message indicates that there is an issue related to resource allocation in YARN, the resource manager in Hadoop. Specifically, the error mentions that the requested resource exceeds the maximum allowed allocation. Here are some steps you can take to address this issue: Review YARN Configuration: Check the YARN configuration settings, particularly those related to resource allocation. Look for properties such as yarn.scheduler.maximum-allocation-mb and yarn.scheduler.maximum-allocation-vcores. Ensure that the values configured for these properties are sufficient for the resources needed by HiveServer2. Increase Maximum Allocation: If the error persists, you might need to increase the maximum allocation for memory and vCores in the YARN scheduler configuration. Update the yarn.scheduler.maximum-allocation-mb and yarn.scheduler.maximum-allocation-vcores properties in the YARN configuration files. Check NodeManager Resources: Verify the resources available on the NodeManagers in your cluster. The maximum allowed allocation is calculated based on the maximum resources of registered NodeManagers. If the NodeManagers have sufficient resources, you can adjust the YARN configuration accordingly. Monitor Resource Usage: Monitor the resource usage in your YARN cluster using tools like the ResourceManager UI or the YARN command-line tools (yarn top, yarn node -list -all, etc.). Identify any patterns of resource exhaustion or contention that could be causing the issue. Review Hive Configuration: Review the Hive configurations related to resource allocation, such as hive.tez.container.size and other relevant settings. Ensure that they are appropriately configured for your cluster. After making any configuration changes, restart the affected services (YARN, HiveServer2) for the changes to take effect.  ... View more