Member since
11-30-2016
85
Posts
7
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3219 | 03-15-2017 07:33 AM |
03-08-2022
03:25 AM
Update for more recent versions of the platform: unfortunately the `/gremlin` endpoint has been removed from modern Atlas APIs, but you can use the special `_NOT_CLASSIFIED` identifier in the search DSL to meet this requirement. So the query would simply be something like: hive_column isA _NOT_CLASSIFIED
... View more
02-19-2018
01:40 PM
There is no such V2 REST API currently. For this requirement , you can use the search APIs. Example : /api/atlas/v2/search/basic?typeName=type_name /api/atlas/v2/search/dsl?typeName=type_name
... View more
08-14-2018
11:57 AM
2 Kudos
Hey @J Koppole, I connected to hive using JayDeBeApi python package. To establish JDBC Connection, Download Hive Uber JDBC Jar created by @Tim Veil. Steps to connect has been mentioned on JayDeBeApi link: I am pasting sample code snippet below import jaydebeapi;
conn = jaydebeapi.connect("org.apache.hive.jdbc.HiveDriver","<hive_jdbc_url>",["<username>", "<password>"],"/path/to/hive-jdbc-uber-<version>.jar")
curs = conn.cursor();
curs.execute("select * from some_table");
curs.close()
... View more
10-14-2017
02:14 PM
Thank you @Ashutosh Mestry.
... View more
08-10-2017
09:45 AM
Thank you @Bryan Bende, I will try Storm.
... View more
11-14-2017
02:07 PM
Thank you @Parag Redij
... View more
08-03-2017
04:30 PM
Hi, pls see for the solution at https://issues.apache.org/jira/browse/ATLAS-396 "Creating an entity with non-existing type results in "Unable to deserialize json" error " is the actual cause of this error.
... View more
06-28-2017
01:28 PM
Hey Eyad, Ty. I will try to implement the same.
... View more
06-23-2017
10:59 AM
1 Kudo
@subash sharma The error messages you are seeing shows some issues with ssh configurations.
error : "host key verification failed" This error message shows that the ssh client is not able to verify 'edge-node-hostname'. It is possible that the entry for 'edge-node-hostname' is not available in the known_hosts file located in the home directory of the user you are running NiFi as. If you are running NiFi as root, check the known_hosts file in /root/.ssh/known_hosts. And if NiFi is running as a non-root user, check the '.ssh/known_hosts' files in the home directory of that user. You can also run the following command which would then ask you for a confirmation in yes/no input format to add the entry of the 'edge-node-hostname' in the known_hosts file. sudo -u <NiFi_user> ssh username@edge-node-hostname
error : "Pseudo-Terminal will not be allocated because stdin is not a terminal" This error message is because you are just trying to obtain a remote shell in the executeProcess processor which is not possible. You can either add a command to be run after ssh succeeds or you can add -t -t arguments to ssh command which should help. ssh username@edge-node-hostname date
OR ssh -t -t username@edge-node-hostname
... View more
06-20-2017
01:50 PM
In many scenarios, users might want to create the ranger policies in advance before the actual resources are created. So policy creation cannot be blocked based on resources. Moreover, wildcards are supported in policies.
... View more