You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to index large amounts of data from hive to solr and I would like to use Tez, as it is faster. When I run a query to insert data into the Solr managed external table, it works fine but it takes a very long time and eventually times out because of hive.
Trying to use Tez, Tez gives me errors when I try to do anything with the Solr managed table, like select count(*) or insert records in it. I thought it was a file permission issue so I changed the permissions on the solr collection folder so that anyone in the group where solr use is would be able to insert into the table and that also did not work.
Is this a known issue with the hive-solr plugin? or I am missing something?
Thanks for your help.
The text was updated successfully, but these errors were encountered:
I can't find the stack trace, do not know where it is. I went to ambari-yarn, and looked into the resource manager and I could not find any logs for the application in question.
The only error I get is : FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.tez.TezTask.
I am trying to index large amounts of data from hive to solr and I would like to use Tez, as it is faster. When I run a query to insert data into the Solr managed external table, it works fine but it takes a very long time and eventually times out because of hive.
Trying to use Tez, Tez gives me errors when I try to do anything with the Solr managed table, like select count(*) or insert records in it. I thought it was a file permission issue so I changed the permissions on the solr collection folder so that anyone in the group where solr use is would be able to insert into the table and that also did not work.
Is this a known issue with the hive-solr plugin? or I am missing something?
Thanks for your help.
The text was updated successfully, but these errors were encountered: