Hello, I'm trying to create some ACL rules in Ranger for Kafka topics. Since the user wants to access several topics that start with the same name, i tried to add the topic_name* in the topic field, but it doesn't work. Only if i put the topic full name.  I tried to look in the documentation and it seems that Ranger accepts wildcards, but i couldn't find any example. Can some advise on this? Thank you Paula ... View more

Hello, I want to upgrade my kafka cluster installed with HDF 3.3.1.0 to the latest version (HDF 3.4) which has kafka 2.1. As per Kafka 2.1 release notes, it added JDK11 support. From Hortonworks support matrix page i only see up to jdk8 support. Is Java11 supported (for HDF and ambari-latest versions)? ... View more

Hello, I have a scenario with a Hadoop cluster installed with HDP2.6.5 and a Kafka cluster installed with HDF 3.3.0 with Ranger Service configured. I want to store the Ranger Audit logs in HDFS so I setup in kafka the property xasecure.audit.destination.hdfs.dir pointing to the HDFS directory. Case one: when using the namenode in the URI the logs are stored in HDFS successfully (xasecure.audit.destination.hdfs.dir=hdfs://namenode_FQDN>:8020/ranger/audit) Case two: Using a haproxy, since i have namenode HA enabled and want to point always to the active NN, i get the following error 2019-04-02 12:00:13,841 ERROR [kafka.async.summary.multi_dest.batch_kafka.async.summary.multi_dest.batch.hdfs_destWriter] org.apache.ranger.audit.provider.BaseAuditHandler (BaseAuditHandler.java:329) - Error writing to log file. java.io.IOException: DestHost:destPort <ha_proxy_hostname>:8085 , LocalHost:localPort <kafka_broker_hostname>/10.212.164.50:0. Failed on local exception: java.io.IOException: org.apache.hadoop.ipc.RpcException: RPC response exceeds maximum data length Is there any extra config to be set? Thanks ... View more

Hello, I'm trying to automate the creation of a kerberized HDF cluster using openstack VMs, using blueprints. The principals are not managed by ambari, I first configured the cluster manually and then downloaded the blueprint. When i try to create a cluster with that blueprint i get the following error curl -H "X-Requested-By ambari" -X POST -u admin:admin http://amabri-host:8080/api/v1/clusters/clusterName -d @hostmapping.json { "status" : 400, "message" : "Topology validation failed: org.apache.ambari.server.topology.InvalidTopologyException: kdc.admin.credential is missing from request." Do i need to add any extra param to the curl request? ... View more

I'm trying to export the oozie workflows/coordinators/bundles from HUE3.9 version and import into  HUE4.2 version. I'm using exporting and importing via UI, not command line.   When importing to the most recent version, is complains about Invalid JSON. Looking into the logs i see that it refers to a missing field "parent_directory" that i don't see in 3.9 DB but is now in 4.2. Is there a way to import, skipping these errors? Thanks ... View more

  Hello, i installed HUE4.2 version compiling the code from git. It works all fine, but when i try to load the data from the old HUE (3.9.0) i get an error regarding a non existing field   Before upgrading i did the following steps 1-Stop HUE 2- backup the db ( hue/build/env/bin/hue dumpdata > ./hue-mysql.json) 3- dropped the database  4- Created a new empty database    CREATE   DATABASE  huedb  DEFAULT   CHARACTER SET  utf8  DEFAULT   COLLATE = utf8_bin ; 5- Synchronized the new dabase    hue/build/env/bin/hue syncdb --noinput     hue/build/env/bin/hue migrate  6- And loaded the data previously backup     hue/build/env/bin/hue loaddata ./hue-mysql.json   I get this error File "/app/hue/build/env/lib/python2.7/site-packages/Django-1.11-py2.7.egg/django/db/models/options.py", line 619, in get_field       raise FieldDoesNotExist("%s has no field named '%s'" % (self.object_name, field_name)) django.core.serializers.base.DeserializationError: Problem installing fixture '/app/temp/hue-dump.json': ContentType has no field named 'name'   I compared the tables from the 3.9 and 4.2 versions and i see a difference in the fields mysql> describe django_content_type;   3.9 +-----------+--------------+------+-----+---------+----------------+ | Field         | Type             | Null | Key | Default | Extra             | +-----------+--------------+------+-----+---------+----------------+ | id           | int(11)         | NO       | PRI | NULL       | auto_increment | | name         | varchar(100) | NO       |         | NULL       |                   | | app_label | varchar(100) | NO       | MUL | NULL       |                   | | model         | varchar(100) | NO       |         | NULL       |                   | +-----------+--------------+------+-----+---------+----------------+   4.2.0 mysql> describe django_content_type; +-----------+--------------+------+-----+---------+----------------+ | Field         | Type             | Null | Key | Default | Extra             | +-----------+--------------+------+-----+---------+----------------+ | id           | int(11)         | NO       | PRI | NULL       | auto_increment | | app_label | varchar(100) | NO       | MUL | NULL       |                   | | model         | varchar(100) | NO       |         | NULL       |                   | +-----------+--------------+------+-----+---------+----------------+   The name field is not present anymore. Is there any extra step that i should considered when migrating the database: I'm using a mySQL standalone DB (not using CDH) Thank you Paula ... View more