Member since
02-22-2017
15
Posts
2
Kudos Received
0
Solutions
03-03-2017
10:30 AM
@Nixon Rodrigues hdp version for the sandbox working without the fix: 2.5.0.0-1245, atlas version: 0.7.0.2.5 hdp version for the cluster working with the fix: 2.5.3.0-37, atlas version: 0.7.0
... View more
03-01-2017
02:26 PM
@Ayub Khan Yes for few tables the lineage result shows as - "Lineage data not found". I am not sure that whether it has nothing to show or it just fetches null edges and vertices because the api call takes a longer duration to complete. Do you need to see some specific section of the application logs? Also I did not find anything related to the issue but incase you still need it then maybe you can tell me what exactly are you looking for as the logs contain some extra information.
... View more
03-01-2017
12:20 PM
@Nixon Rodrigues Could you please explain it a bit as when I checked the TreeLayoutView.js file in hdp2.5 sandbox, the line(which you suggested me to change) in fetchCollection: function(url, isParent) is: this.childCollection.fetch({ reset:true }); similar to what I have in my cluster but in case of hdp2.5 sandbox taxonomy terms are displayed without making the change but for the cluster the terms were not being shown earlier on UI but after the change suggested by you it worked.
... View more
02-28-2017
02:45 PM
@Nixon Rodrigues Thanks this worked...earlier was not able to test the issue properly as was js was cached in the browser and was not fetching the updated js file..
... View more
02-28-2017
12:50 PM
@Nixon Rodrigues Made the required changes but not able to see the taxonomy Subterms on UI.
... View more
02-28-2017
11:27 AM
@Nixon Rodrigues HDP Version: 2.5.3.0-37 Atlas Version: 0.7.0
... View more
02-24-2017
04:04 AM
2 Kudos
I created a subterm in Atals Web UI by selecting "Create Subterm" option under Catalogs. The message clearly displays subterm created. I can even retieve all the subterms using the api http://host:port/api/atlas/v1/taxonomies/Catalog/terms But they dont appear under Catalog dropdown menu. On debugging I found Atlas to be calling an API http://host:port/api/atlas/v1/taxonomies/Catalog/terms?hierarchy/path:.&_=1487799123750 which returns empty json I changed this API to http://host:port/api/atlas/v1/taxonomies/Catalog/terms?hierarchy/path:/ and this worked in my java application. So I changed the URL building javascript TreeLayoutTerm.js to replace hierarchy/path:. -> hierarchy/path:/ Now the request that goes through web ui is something like http://host:port/api/atlas/v1/taxonomies/Catalog/terms?hierarchy/path:/&_=1487799123750 But still it is fetching empty JSON. Is this a bug of wrong path being sent to server or is there something I am missing like restart of depending services etc. Any help would be highly appreciable
... View more
Labels:
- Labels:
-
Apache Atlas
02-24-2017
03:55 AM
yeah sorry its two different apis...could still you please help me figure out why lineage data is not being fetched or how could i really check in the db it there is no data....also is there some method to improve this performance...as it usually takes 3-4 mins to fetch data for small tables which is way too much
... View more
02-24-2017
03:53 AM
As a am a newbie could you please tell me which logs to attach here..
... View more
02-22-2017
05:55 PM
On my atlas web UI, selecting a table takes too much time to fetch lineage and incase of big tables after loading for too long it just displays "No Lineage Data Found"
on checking the requests made which are taking long I found one REST API's being called 2 times which take somewhere between 3-5 mins. Sometimes it successfully fetches data and displays lineage but in case of too big tables no lineage data appears. The API which is being called twice is:- Request URL:http://hostname:port/api/atlas/lineage/c797bffa-37d0-4b23-b168-998ffc4855e3/inputs/graph?_=1487780877854 JSON Response {"requestId":"qtp1177377518-69414 - 3e3301e8-4944-429e-96fe-9ef640684372","results":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct","typeName":"__tempQueryResultStruct523","values":{"vertices":{},"edges":{}}}} Time Taken 3.7 minutes. I guess the request is taking too long to process and hence empty vertices and edges are recieved in the JSON Response.
Is there someway I can increase the time for this request to be processed or better improve the performance altogether by using some caching mechanism or something.
... View more
Labels:
- Labels:
-
Apache Atlas