Member since
12-01-2015
7
Posts
0
Kudos Received
0
Solutions
02-15-2019
05:22 PM
Reported as this Apache issue: https://issues.apache.org/jira/browse/HIVE-21135 Fixed here but not backported as of HDP 3.1.0.0: https://issues.apache.org/jira/browse/HIVE-21018
... View more
11-28-2018
09:48 AM
Functionality asked for by this question, submission of HPL/SQL via JDBC/ODBC (which requires HiveServer2 support for this) is not implemented yet: https://issues.apache.org/jira/browse/HIVE-17596 Until this is done, submission via the command line is the only option.
... View more
06-27-2017
08:02 PM
In our case it was related to this stack guard kernel patch: CVE-2017-1000364 kernel: heap/stack gap jumping via unbounded stack allocations https://access.redhat.com/errata/RHSA-2017:1484
... View more
11-03-2016
02:33 AM
Note the falcon jar actually needed is: /usr/hdp/current/falcon-server/oozie/ext/falcon-oozie-el-extension.jar NOT the cli or client falcon jar files.
... View more
09-22-2016
08:16 PM
Note the above query didn't work for us on PostgreSQL 9.2 where Ambari is using the ambari schema instead of public; the following query works in our case: SELECT
c.cluster_name,
cs.service_name,
cc.type_name,
sc.version
FROM ambari.clusterservices cs
JOIN ambari.serviceconfig sc
ON cs.service_name = sc.service_name
AND cs.cluster_id = sc.cluster_id
JOIN ambari.serviceconfigmapping scm
ON sc.service_config_id = scm.service_config_id
JOIN ambari.clusterconfig cc
ON scm.config_id = cc.config_id
AND sc.cluster_id = cc.cluster_id
JOIN ambari.clusters c
ON cc.cluster_id = c.cluster_id
AND sc.stack_id = c.desired_stack_id
WHERE sc.group_id IS NULL
AND sc.service_config_id = (SELECT MAX(service_config_id)
FROM ambari.serviceconfig sc2
WHERE sc2.service_name = sc.service_name
AND sc2.cluster_id = sc.cluster_id)
GROUP BY c.cluster_name,
cs.service_name,
cc.type_name,
sc.version;
... View more
06-21-2016
08:07 PM
In our case this was caused by the queues being stopped in yarn due to an upgrade. We changed the queues from STOPPED to RUNNING in capacity-scheduler.xml then restarted yarn and the problem was fixed.
... View more
03-16-2016
11:59 PM
Until the API gets fixed to clean things up correctly, here's a PostgreSQL anonymous code block which cleans up the stuff it leaves behind which we used: DO $
DECLARE
u record;
r record;
p record;
BEGIN
FOR u IN select id, login_id from x_portal_user where login_id not in (select user_name from x_user)
LOOP
RAISE NOTICE 'User roles in x_portal_user_role:';
FOR r IN select id, user_id, user_role from x_portal_user_role where user_id = u.id
LOOP
RAISE NOTICE USING MESSAGE = ' ' || r.user_role;
RAISE NOTICE USING MESSAGE = 'DELETE from x_portal_user_role WHERE id = ' || r.id;
-- Uncomment next line to perform action
--EXECUTE 'DELETE from x_portal_user_role WHERE id = ' || r.id;
END LOOP;
RAISE NOTICE 'User permissions in x_user_module_perm:';
FOR p IN select id, user_id, module_id from x_user_module_perm where user_id = u.id
LOOP
RAISE NOTICE USING MESSAGE = ' ' || (select module from x_modules_master where id = p.module_id);
RAISE NOTICE USING MESSAGE = 'DELETE from x_user_module_perm where id = ' || p.id;
-- Uncomment next line to perform action
--EXECUTE 'DELETE from x_user_module_perm where id = ' || p.id;
END LOOP;
RAISE NOTICE USING MESSAGE = 'DELETE FROM x_portal_user WHERE id = ' || u.id;
-- Uncomment next line to perform action
--EXECUTE 'DELETE FROM x_portal_user WHERE id = ' || u.id;
RAISE NOTICE ' ';
END LOOP;
END$;
... View more