[jira] [Created] (ATLAS-1886) DSL queries with LIKE fail for composite searches
Hemanth Yamijala created ATLAS-1886: --- Summary: DSL queries with LIKE fail for composite searches Key: ATLAS-1886 URL: https://issues.apache.org/jira/browse/ATLAS-1886 Project: Atlas Issue Type: Improvement Components: atlas-core Affects Versions: 0.9-incubating Reporter: Hemanth Yamijala Search DSL was enhanced to support the LIKE query in ATLAS-1807. This was a great enhancement from a usability point of view and works as expected for String attributes of a type - like hive_table.name, hive_table.owner etc. Another type of query that is useful is composite searches - for e.g. hive_tables in a DB (given a DB name). This query currently works - hive_table where db.name='xyz'. However, when we try a 'like' operator here, it fails - i.e. hive_table where db.name LIKE '*xyz*' - this returns an error: Discovery query failed `hive_table` db.name LIKE '*financ*' Can this be looked into if its an easy fix? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1818) Performance of Basic Search that Uses indexQuery Takes Long Time to Fetch Results
[ https://issues.apache.org/jira/browse/ATLAS-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016897#comment-16016897 ] Hemanth Yamijala commented on ATLAS-1818: - [~ashutoshm], thanks for taking up this really useful improvement! One question: Regarding your last point - is the intention to provide faceted search in searchUsingBasicQuery that might follow a Lucene syntax or some such? > Performance of Basic Search that Uses indexQuery Takes Long Time to Fetch > Results > - > > Key: ATLAS-1818 > URL: https://issues.apache.org/jira/browse/ATLAS-1818 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: trunk, 0.8-incubating >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry > Fix For: trunk, 0.8-incubating > > Attachments: ATLAS-1818.patch > > Original Estimate: 120h > Time Spent: 96h > Remaining Estimate: 24h > > h3. Background > An environment that is setup with 100K hive_tables each with 84 columns. > The basic search with query parameter specified is executed. Results take 75 > secs to appear. > h3. Analysis & Findings > Similar test was performed with smaller data set (200 hive_tables each with > 81 columns) resulted in less than ideal performance. > Atlas Basic Search API uses _graph.indexQuery_ for performing search. This > uses _Solr_ for doing the search. > There are 2 aspects that affect performance: > * Solr's default for returning max query set when no limit is specified is > 100K. In the test scenario, this is returning entire result set. > * Once result set is returned, _EntityDiscoveryService.searchUsingBasicQuery_ > does a sequential scan to weed out pertinent data. This operation is > proportional to size of the result set. > h3. Solution > Following changes will improve performance: > * Solr's max result set property is governed by > _atlas.graph.index.search.max-result-set-size_. It will make sense to set > this to a lower number. > * Modify Solr's configuration _solrconfig.xml_ to use _FastLRUCache_. > * Modify _EntityDiscoveryService.searchUsingBasicQuery_ to form a query that > takes additional paramters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1707) Atlas WUI on continues loading behind FireWall
[ https://issues.apache.org/jira/browse/ATLAS-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977865#comment-15977865 ] Hemanth Yamijala commented on ATLAS-1707: - Looks good to me. +1. Thanks > Atlas WUI on continues loading behind FireWall > -- > > Key: ATLAS-1707 > URL: https://issues.apache.org/jira/browse/ATLAS-1707 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.7-incubating > Environment: Atlas: Version":"0.7.0.2.5.3 > JDK 1.8 > Linux >Reporter: Ernani Pereira de Mattos Junior >Assignee: Nixon Rodrigues > Labels: patch, test > Fix For: 0.9-incubating > > Attachments: ATLAS-1707.2.patch, ATLAS-1707.patch, index.html, > index.html.original > > > Atlas is behind a FW in which does return a response. We Identify index.html > was loading googleapis css does not have a timeout and proceed with the WUI; > ref:http://tinyurl.com/lan4by9 > By removing the bellow line from the html file, there were no problem. > href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,400italic,600,600italic,700,700italic"; > rel="stylesheet" type="text/css"> > 1. Shouldn't be applications self-contain in case of such situation? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1707) Atlas WUI on continues loading behind FireWall
[ https://issues.apache.org/jira/browse/ATLAS-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977128#comment-15977128 ] Hemanth Yamijala commented on ATLAS-1707: - [~ashutoshm], I believe we might need something slightly different. Firstly, the specific fonts we are using are licensed under Open Font License. Please see https://fonts.google.com/specimen/Source+Sans+Pro. This is the font we use, AFAIK. The general process is to copy the license text of the actual license into a file (as you've done) under the 3rdparty licenses folder. Next, we must reference this from the LICENSE file in the top folder of the Atlas project. For e.g. like in this line: This product bundles bootstrap-datepicker 4.14.30, which is available under MIT License. For details, see 3party-licenses/bootstrap-datepicker-LICENSE > Atlas WUI on continues loading behind FireWall > -- > > Key: ATLAS-1707 > URL: https://issues.apache.org/jira/browse/ATLAS-1707 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.7-incubating > Environment: Atlas: Version":"0.7.0.2.5.3 > JDK 1.8 > Linux >Reporter: Ernani Pereira de Mattos Junior >Assignee: Nixon Rodrigues > Labels: patch, test > Fix For: 0.9-incubating > > Attachments: ATLAS-1707.1.patch, ATLAS-1707.patch, index.html, > index.html.original > > > Atlas is behind a FW in which does return a response. We Identify index.html > was loading googleapis css does not have a timeout and proceed with the WUI; > ref:http://tinyurl.com/lan4by9 > By removing the bellow line from the html file, there were no problem. > href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,400italic,600,600italic,700,700italic"; > rel="stylesheet" type="text/css"> > 1. Shouldn't be applications self-contain in case of such situation? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1707) Atlas WUI on continues loading behind FireWall
[ https://issues.apache.org/jira/browse/ATLAS-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974968#comment-15974968 ] Hemanth Yamijala commented on ATLAS-1707: - We may need to make sure that the Open Font License is included in the License file we have. Please verify this. Can be done in another JIRA if required. > Atlas WUI on continues loading behind FireWall > -- > > Key: ATLAS-1707 > URL: https://issues.apache.org/jira/browse/ATLAS-1707 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.7-incubating > Environment: Atlas: Version":"0.7.0.2.5.3 > JDK 1.8 > Linux >Reporter: Ernani Pereira de Mattos Junior >Assignee: Nixon Rodrigues > Labels: patch, test > Fix For: 0.9-incubating > > Attachments: ATLAS-1707.patch, index.html, index.html.original > > > Atlas is behind a FW in which does return a response. We Identify index.html > was loading googleapis css does not have a timeout and proceed with the WUI; > ref:http://tinyurl.com/lan4by9 > By removing the bellow line from the html file, there were no problem. > href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,400italic,600,600italic,700,700italic"; > rel="stylesheet" type="text/css"> > 1. Shouldn't be applications self-contain in case of such situation? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1704) amend Atlas simple security to add glossary
[ https://issues.apache.org/jira/browse/ATLAS-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950279#comment-15950279 ] Hemanth Yamijala commented on ATLAS-1704: - Is this different from ATLAS-1703? Seems to be a duplicate. > amend Atlas simple security to add glossary > - > > Key: ATLAS-1704 > URL: https://issues.apache.org/jira/browse/ATLAS-1704 > Project: Atlas > Issue Type: Sub-task >Reporter: David Radley > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1416) UI: It would be nice to sort the properties in the details page of an entity by name
[ https://issues.apache.org/jira/browse/ATLAS-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15797088#comment-15797088 ] Hemanth Yamijala commented on ATLAS-1416: - [~davidrad], I was thinking of the sort functionality in the UI. I was however imagining they would be pre-sorted, but maybe having an explicit sort would work too. To be clear, the JIRA is only about the UX, and nothing to do with the API. > UI: It would be nice to sort the properties in the details page of an entity > by name > > > Key: ATLAS-1416 > URL: https://issues.apache.org/jira/browse/ATLAS-1416 > Project: Atlas > Issue Type: Improvement >Reporter: Hemanth Yamijala > > The Atlas UI has a Details page for every entity. In the "Properties" tab of > this pane, it currently enumerates all properties of the entity. Currently > the order seems random and hence is not very easy to grok. It would be nice > to have these sorted by property name to make location of required details > easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1416) UI: It would be nice to sort the properties in the details page of an entity by name
Hemanth Yamijala created ATLAS-1416: --- Summary: UI: It would be nice to sort the properties in the details page of an entity by name Key: ATLAS-1416 URL: https://issues.apache.org/jira/browse/ATLAS-1416 Project: Atlas Issue Type: Improvement Reporter: Hemanth Yamijala The Atlas UI has a Details page for every entity. In the "Properties" tab of this pane, it currently enumerates all properties of the entity. Currently the order seems random and hence is not very easy to grok. It would be nice to have these sorted by property name to make location of required details easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1408) Creating an attribute definition of array type, where the elements have a dot in the typename causes issues
[
https://issues.apache.org/jira/browse/ATLAS-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765891#comment-15765891
]
Hemanth Yamijala commented on ATLAS-1408:
-
[~madhan.neethiraj] pointed me to the '.' being the problem. Irrespective of
the solutions to this specific problem, it would be nice to not get the server
into an unrecoverable state.
> Creating an attribute definition of array type, where the elements have a dot
> in the typename causes issues
> ---
>
> Key: ATLAS-1408
> URL: https://issues.apache.org/jira/browse/ATLAS-1408
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Hemanth Yamijala
>Priority: Critical
>
> I created a type File.v1 and then another type FileSet.v1 which contains an
> array of File.v1 type instances. The creation was using the
> {{AtlasClient.createType(TypeDef)}} API. This returned back successfully.
> However, post this Atlas server went into a funny state where simple DSL
> queries like {{hive_table}} started failing. Looking the application logs,
> noticed this error post the registration of the FileSet.v1 type:
> {code}
> 2016-12-20 13:46:53,960 INFO - [pool-2-thread-4 -
> 8eaf688d-9cd4-46dc-92da-d84991512e9b:] ~ TypeSystem reset invoked by
> TypeRegistry changes (DefaultMetadataService:749)
> Many types restored and then
> 2016-12-20 13:46:54,266 ERROR - [pool-2-thread-4 -
> 8eaf688d-9cd4-46dc-92da-d84991512e9b:] ~ Failed to restore type-system after
> TypeRegistry changes (DefaultMetadataService:759)
> org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown
> datatype: array
> at
> org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)
> at
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.getDataType(TypeSystem.java:669)
> at
> org.apache.atlas.typesystem.types.AttributeInfo.(AttributeInfo.java:46)
> at
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.constructAttributeInfo(TypeSystem.java:496)
> at
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.constructHierarchicalType(TypeSystem.java:540)
> at
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.orderAndConstructTypes(TypeSystem.java:583)
> at
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.verifyTypes(TypeSystem.java:709)
> at
> org.apache.atlas.typesystem.types.TypeSystem.createTransientTypeSystem(TypeSystem.java:346)
> at
> org.apache.atlas.services.DefaultMetadataService.onChange(DefaultMetadataService.java:753)
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$TypeRegistryUpdateHook.notifyListeners(AtlasTypeDefGraphStore.java:940)
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$TypeRegistryUpdateHook.onComplete(AtlasTypeDefGraphStore.java:924)
> {code}
> DSL failures post this error had this trace:
> {code}
> 2016-12-20 13:49:55,398 ERROR - [pool-2-thread-8 -
> 3d671edf-9dce-4656-a5e3-04e3d3bd3ade:] ~ Unable to get entity list for
> dslQuery hive_table (MetadataDiscoveryResource:141)
> org.apache.atlas.discovery.DiscoveryException: Invalid expression : hive_table
> at
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:139)
> at
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.searchByDSL(GraphBackedDiscoveryService.java:124)
> at
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:51)
> at
> org.apache.atlas.web.resources.MetadataDiscoveryResource.searchUsingQueryDSL(MetadataDiscoveryResource.java:135)
> at sun.reflect.GeneratedMethodAccessor41.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> {code}
> Restarting the server caused more issues because the types restoration failed
> as in the error in the first stack trace, which caused failures in
> initializations and so, effectively, the server did not come up. The
> workaround was the delete the HBase titan table and start over again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-1408) Creating an attribute definition of array type, where the elements have a dot in the typename causes issues
Hemanth Yamijala created ATLAS-1408:
---
Summary: Creating an attribute definition of array type, where the
elements have a dot in the typename causes issues
Key: ATLAS-1408
URL: https://issues.apache.org/jira/browse/ATLAS-1408
Project: Atlas
Issue Type: Bug
Affects Versions: 0.8-incubating
Reporter: Hemanth Yamijala
Priority: Critical
I created a type File.v1 and then another type FileSet.v1 which contains an
array of File.v1 type instances. The creation was using the
{{AtlasClient.createType(TypeDef)}} API. This returned back successfully.
However, post this Atlas server went into a funny state where simple DSL
queries like {{hive_table}} started failing. Looking the application logs,
noticed this error post the registration of the FileSet.v1 type:
{code}
2016-12-20 13:46:53,960 INFO - [pool-2-thread-4 -
8eaf688d-9cd4-46dc-92da-d84991512e9b:] ~ TypeSystem reset invoked by
TypeRegistry changes (DefaultMetadataService:749)
Many types restored and then
2016-12-20 13:46:54,266 ERROR - [pool-2-thread-4 -
8eaf688d-9cd4-46dc-92da-d84991512e9b:] ~ Failed to restore type-system after
TypeRegistry changes (DefaultMetadataService:759)
org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown datatype:
array
at org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)
at
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.getDataType(TypeSystem.java:669)
at org.apache.atlas.typesystem.types.AttributeInfo.(AttributeInfo.java:46)
at
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.constructAttributeInfo(TypeSystem.java:496)
at
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.constructHierarchicalType(TypeSystem.java:540)
at
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.orderAndConstructTypes(TypeSystem.java:583)
at
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.verifyTypes(TypeSystem.java:709)
at
org.apache.atlas.typesystem.types.TypeSystem.createTransientTypeSystem(TypeSystem.java:346)
at
org.apache.atlas.services.DefaultMetadataService.onChange(DefaultMetadataService.java:753)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$TypeRegistryUpdateHook.notifyListeners(AtlasTypeDefGraphStore.java:940)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$TypeRegistryUpdateHook.onComplete(AtlasTypeDefGraphStore.java:924)
{code}
DSL failures post this error had this trace:
{code}
2016-12-20 13:49:55,398 ERROR - [pool-2-thread-8 -
3d671edf-9dce-4656-a5e3-04e3d3bd3ade:] ~ Unable to get entity list for dslQuery
hive_table (MetadataDiscoveryResource:141)
org.apache.atlas.discovery.DiscoveryException: Invalid expression : hive_table
at
org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:139)
at
org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.searchByDSL(GraphBackedDiscoveryService.java:124)
at
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:51)
at
org.apache.atlas.web.resources.MetadataDiscoveryResource.searchUsingQueryDSL(MetadataDiscoveryResource.java:135)
at sun.reflect.GeneratedMethodAccessor41.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
{code}
Restarting the server caused more issues because the types restoration failed
as in the error in the first stack trace, which caused failures in
initializations and so, effectively, the server did not come up. The workaround
was the delete the HBase titan table and start over again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-1389) Ping REST API entrypoint
[
https://issues.apache.org/jira/browse/ATLAS-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15753163#comment-15753163
]
Hemanth Yamijala commented on ATLAS-1389:
-
Would the {{admin/status}} API not be sufficient for this? Is the intention to
just check reachability, or have a more detailed notion of what a healthy Atlas
server means? Even if the latter, could the {{admin/status}} endpoint be
enhanced to return additional information?
> Ping REST API entrypoint
>
>
> Key: ATLAS-1389
> URL: https://issues.apache.org/jira/browse/ATLAS-1389
> Project: Atlas
> Issue Type: New Feature
>Reporter: David Kantor
>Assignee: Jeffrey Hagelberg
>
> Provide a lightweight ping API to allow clients to check status of Atlas
> server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-1346) Search APIs should return empty list instead of throwing exception
[ https://issues.apache.org/jira/browse/ATLAS-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711228#comment-15711228 ] Hemanth Yamijala commented on ATLAS-1346: - A long while back, on ATLAS-805, we discovered that Titan's read only operations also could end up mutating some underlying indexes. Without proper transaction boundaries, this seemed to cause some failures for operations run after the read queries - please look at this comment in particular: https://issues.apache.org/jira/browse/ATLAS-805?focusedCommentId=15289274&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15289274 So, could you please double-check if removing transactionality is still OK? > Search APIs should return empty list instead of throwing exception > -- > > Key: ATLAS-1346 > URL: https://issues.apache.org/jira/browse/ATLAS-1346 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: 0.8-incubating > > > Currently the APIs return a 404 when there's no result found in the > repository which causes the graph transaction to rollback, instead the search > API should return an empty list and the rest layer should translate it to a > 404 or the read-only APIs should be excluded from the GraphTransaction > interceptor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (ATLAS-1271) dadad
[ https://issues.apache.org/jira/browse/ATLAS-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala closed ATLAS-1271. --- > dadad > - > > Key: ATLAS-1271 > URL: https://issues.apache.org/jira/browse/ATLAS-1271 > Project: Atlas > Issue Type: Bug >Reporter: dreal hakim > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-1201) using progaurd in android for cordova plugin
[ https://issues.apache.org/jira/browse/ATLAS-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-1201. - Resolution: Invalid This is unlikely to be an Apache Atlas project issue. Could you please open this against the right project? > using progaurd in android for cordova plugin > > > Key: ATLAS-1201 > URL: https://issues.apache.org/jira/browse/ATLAS-1201 > Project: Atlas > Issue Type: Bug >Reporter: lokesh > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-1189) Server Signature validation on client failed while using only CA in the client truststore
[ https://issues.apache.org/jira/browse/ATLAS-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-1189. - Resolution: Invalid I am suspecting this is not an Apache Atlas project issue, but maybe some other project. Could you please confirm? If yes, please file a JIRA against the right component. If it is related to Atlas, please reopen the issue and provide some more information in the report. Thanks! > Server Signature validation on client failed while using only CA in the > client truststore > - > > Key: ATLAS-1189 > URL: https://issues.apache.org/jira/browse/ATLAS-1189 > Project: Atlas > Issue Type: Bug >Reporter: Libois Claude > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1145) Storm hook with kafka topic and hive bolt picks wrong hive table name
[
https://issues.apache.org/jira/browse/ATLAS-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15505596#comment-15505596
]
Hemanth Yamijala commented on ATLAS-1145:
-
[~sarath.ku...@gmail.com], Some time back I had a working version of Kafka to
Hive storm topology capturing lineage into Atlas etc. Code is here:
https://github.com/yhemanth/storm-samples/blob/master/src/main/java/com/dsinpractice/storm/samples/WordCountTopology.java
However, we shifted focus from Hive to HDFS for later testing.
The main issue AFAIK is to setup Hive for streaming accurately. It took some
time for me to figure that out. Wish I had documented the steps more clearly
:-(
These are properties I have in my hive-site which *I think* were used to get
these to work. Please use these in case they are of help.
{code}
hive.support.concurrency
true
hive.enforce.bucketing
true
hive.exec.dynamic.partition.mode
nonstrict
hive.compactor.initiator.on
true
hive.txn.manager
org.apache.hadoop.hive.ql.lockmgr.DbTxnManager
hive.compactor.initiator.on
true
hive.compactor.worker.threads
1
{code}
> Storm hook with kafka topic and hive bolt picks wrong hive table name
> --
>
> Key: ATLAS-1145
> URL: https://issues.apache.org/jira/browse/ATLAS-1145
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Sarath Subramanian
>
> Storm hook with kafka topic and hive bolt picks kafka topic name as hive
> table name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ATLAS-1176) MultipartStream need readBodyDataStream
[
https://issues.apache.org/jira/browse/ATLAS-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala resolved ATLAS-1176.
-
Resolution: Invalid
The issue does not seem to be a part of Atlas project. Please assign against
right project.
> MultipartStream need readBodyDataStream
> ---
>
> Key: ATLAS-1176
> URL: https://issues.apache.org/jira/browse/ATLAS-1176
> Project: Atlas
> Issue Type: Improvement
>Reporter: shuaib hasan khwaja
>
> Currently MultipartStream has support for "readBodyData", which basically
> read the body data and write in out stream. It work great, if plan to have
> body in memory or write in disk. But not work when you want to upstream some
> where else.
> Its a good idea to get the InputStream for part body and use it for upload to
> upstream. Some thing like...
> public InputStream readBodyDataStream(OutputStream output) IOException {
> return newInputStream();
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ATLAS-1173) Doc: Minor editorial bug in the example given for property atlas.server.ha.zookeeper.auth
[
https://issues.apache.org/jira/browse/ATLAS-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala reassigned ATLAS-1173:
---
Assignee: Hemanth Yamijala
> Doc: Minor editorial bug in the example given for property
> atlas.server.ha.zookeeper.auth
> -
>
> Key: ATLAS-1173
> URL: https://issues.apache.org/jira/browse/ATLAS-1173
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Minor
> Attachments: ATLAS-1173.patch
>
>
> In {{Configuration.twiki}}, we have specified the example for Zookeeper
> security configs as follows (under the High Availability Properties).
> {code}
> atlas.server.ha.zookeeper.acl=auth:sasl:cli...@comany.com
> {code}
> The auth: prefix in the value is incorrect and should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1173) Doc: Minor editorial bug in the example given for property atlas.server.ha.zookeeper.auth
[
https://issues.apache.org/jira/browse/ATLAS-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated ATLAS-1173:
Attachment: ATLAS-1173.patch
Very trivial patch fixing the issue.
> Doc: Minor editorial bug in the example given for property
> atlas.server.ha.zookeeper.auth
> -
>
> Key: ATLAS-1173
> URL: https://issues.apache.org/jira/browse/ATLAS-1173
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Priority: Minor
> Attachments: ATLAS-1173.patch
>
>
> In {{Configuration.twiki}}, we have specified the example for Zookeeper
> security configs as follows (under the High Availability Properties).
> {code}
> atlas.server.ha.zookeeper.acl=auth:sasl:cli...@comany.com
> {code}
> The auth: prefix in the value is incorrect and should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1173) Doc: Minor editorial bug in the example given for property atlas.server.ha.zookeeper.auth
[
https://issues.apache.org/jira/browse/ATLAS-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated ATLAS-1173:
Affects Version/s: 0.7-incubating
> Doc: Minor editorial bug in the example given for property
> atlas.server.ha.zookeeper.auth
> -
>
> Key: ATLAS-1173
> URL: https://issues.apache.org/jira/browse/ATLAS-1173
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Minor
> Attachments: ATLAS-1173.patch
>
>
> In {{Configuration.twiki}}, we have specified the example for Zookeeper
> security configs as follows (under the High Availability Properties).
> {code}
> atlas.server.ha.zookeeper.acl=auth:sasl:cli...@comany.com
> {code}
> The auth: prefix in the value is incorrect and should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-1173) Doc: Minor editorial bug in the example given for property atlas.server.ha.zookeeper.auth
Hemanth Yamijala created ATLAS-1173:
---
Summary: Doc: Minor editorial bug in the example given for
property atlas.server.ha.zookeeper.auth
Key: ATLAS-1173
URL: https://issues.apache.org/jira/browse/ATLAS-1173
Project: Atlas
Issue Type: Bug
Reporter: Hemanth Yamijala
Priority: Minor
In {{Configuration.twiki}}, we have specified the example for Zookeeper
security configs as follows (under the High Availability Properties).
{code}
atlas.server.ha.zookeeper.acl=auth:sasl:cli...@comany.com
{code}
The auth: prefix in the value is incorrect and should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ATLAS-972) Create entity response for a request with multiple entities is not returning back all definitions
[ https://issues.apache.org/jira/browse/ATLAS-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-972. Resolution: Duplicate > Create entity response for a request with multiple entities is not returning > back all definitions > - > > Key: ATLAS-972 > URL: https://issues.apache.org/jira/browse/ATLAS-972 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala > > Create multiple entities in the same POST request to > http:///api/atlas/entities. The response contains an > element called definition. But this contains only the first entity object in > the request and not all entity definitions. This is inconsistent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1153) When ATLAS_HOOK topic is not created by Atlas, it is not reading messages from the beginning
[
https://issues.apache.org/jira/browse/ATLAS-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455113#comment-15455113
]
Hemanth Yamijala commented on ATLAS-1153:
-
[~ayubkhan], was there any offset committed for the topic before you deleted
and recreated it?
> When ATLAS_HOOK topic is not created by Atlas, it is not reading messages
> from the beginning
>
>
> Key: ATLAS-1153
> URL: https://issues.apache.org/jira/browse/ATLAS-1153
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Khan
> Fix For: trunk
>
>
> When ATLAS_HOOK topic is not created by Atlas, it is not reading messages
> from the beginning
> Steps to repro:
> 1. Stop atlas.
> 2. Delete ATLAS_HOOK Topic and check it is actually deleted.
> 3. Create some hive tables(more than 3, preferrable) from hive client.
> 4. Now check that ATLAS_HOOK topic is created and also has messages for above
> hive tables.
> 5. Now restart Atlas. Ideally Atlas should start consuming messages from
> offset '0' but looks like it is consuming the latest one.
> I have also verified that 'auto.offset.reset' is set to 'smallest', which
> should ideally force the consumer to read messages from offset '0'.
> {noformat}
> 2016-09-01 10:46:41,378 INFO - [main:] ~ Property auto.commit.enable is
> overridden to false (VerifiableProperties:68)
> 2016-09-01 10:46:41,379 INFO - [main:] ~ Property auto.offset.reset is
> overridden to smallest (VerifiableProperties:68)
> 2016-09-01 10:46:41,379 WARN - [main:] ~ Property bootstrap.servers is not
> valid (VerifiableProperties:83)
> 2016-09-01 10:46:41,379 INFO - [main:] ~ Property group.id is overridden to
> atlas (VerifiableProperties:68)
> 2016-09-01 10:46:41,379 WARN - [main:] ~ Property hook.group.id is not valid
> (VerifiableProperties:83)
> 2016-09-01 10:46:41,379 WARN - [main:] ~ Property key.deserializer is not
> valid (VerifiableProperties:83)
> 2016-09-01 10:46:41,380 WARN - [main:] ~ Property key.serializer is not
> valid (VerifiableProperties:83)
> {noformat}
> Kafka commands
> {noformat}
> [root@atlas-pixie-dust-test-7-unsecure-1 bin]# ./kafka-topics.sh --zookeeper
> 172.22.74.193:2181,172.22.74.192:2181 --list
> ATLAS_ENTITIES
> ATLAS_HOOK
> __consumer_offsets
> [root@atlas-pixie-dust-test-7-unsecure-1 bin]# ./kafka-topics.sh --zookeeper
> 172.22.74.193:2181,172.22.74.192:2181 --topic ATLAS_HOOK --delete
> Topic ATLAS_HOOK is marked for deletion.
> Note: This will have no impact if delete.topic.enable is not set to true.
> [root@atlas-pixie-dust-test-7-unsecure-1 bin]# ./kafka-topics.sh --zookeeper
> 172.22.74.193:2181,172.22.74.192:2181 --list
> ATLAS_ENTITIES
> __consumer_offsets
> {noformat}
> Atlas logs showing initOffset set to 3, ideally this should be set to zero.
> {noformat}
> 2016-09-01 10:46:41,590 INFO - [main:] ~
> [atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c], begin
> rebalancing consumer
> atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c try #0
> (ZookeeperConsumerConnector:68)
> 2016-09-01 10:46:41,841 INFO - [main:] ~
> [ConsumerFetcherManager-1472726801467] Stopping leader finder thread
> (ConsumerFetcherManager:68)
> 2016-09-01 10:46:41,841 INFO - [main:] ~
> [ConsumerFetcherManager-1472726801467] Stopping all fetchers
> (ConsumerFetcherManager:68)
> 2016-09-01 10:46:41,842 INFO - [main:] ~
> [ConsumerFetcherManager-1472726801467] All connections stopped
> (ConsumerFetcherManager:68)
> 2016-09-01 10:46:41,843 INFO - [main:] ~
> [atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c], Cleared
> all relevant queues for this fetcher (ZookeeperConsumerConnector:68)
> 2016-09-01 10:46:41,845 INFO - [main:] ~
> [atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c], Cleared
> the data chunks in all the consumer message iterators
> (ZookeeperConsumerConnector:68)
> 2016-09-01 10:46:41,849 INFO - [main:] ~
> [atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c], Releasing
> partition ownership (ZookeeperConsumerConnector:68)
> 2016-09-01 10:46:41,900 INFO - [main:] ~ Starting round-robin assignment
> with consumers
> ArrayBuffer(atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c)
> (RoundRobinAssignor:68)
> 2016-09-01 10:46:41,901 INFO - [main:] ~ Consumer
> atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c rebalancing
> the following partitions for topic ATLAS_HOOK: ArrayBuffer(0)
> (RoundRobinAssignor:68)
> 2016-09-01 10:46:41,955 INFO - [main:] ~
> [atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c],
> atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c-0
> successfully owned partition 0 for topic ATLAS_HOOK
> (ZookeeperConsumerConnector:68
[jira] [Resolved] (ATLAS-1150) A Cassandra node gets corrupted and contains only "key" and "column1" columns
[ https://issues.apache.org/jira/browse/ATLAS-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-1150. - Resolution: Invalid Not an Atlas issue. Please file against the right component > A Cassandra node gets corrupted and contains only "key" and "column1" columns > -- > > Key: ATLAS-1150 > URL: https://issues.apache.org/jira/browse/ATLAS-1150 > Project: Atlas > Issue Type: Bug >Reporter: Michal Lefler > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1110) Improve Atlas Entity Rest API to show Hive column type (e.g int) as a JSON Object.
[
https://issues.apache.org/jira/browse/ATLAS-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414899#comment-15414899
]
Hemanth Yamijala commented on ATLAS-1110:
-
[~davidrad], there are two API endpoints that relate to Atlas entities (which
is slightly unfortunate). The fully functional one is the one that [~shwethags]
pointed out: {{api/atlas/entities/:entity_guid:}}. The *values* attribute I
referred to is present in that API. The one you are using is
{{api/atlas/v1/entities/:entity_guid:}}. Note the *v1* in the URL. This was
developed as part of the Business Taxonomy feature, which is kind of
early-access at this stage. I would suggest you use the endpoint Shwetha
referred to for getting information about Atlas entities. Hope that helps.
> Improve Atlas Entity Rest API to show Hive column type (e.g int) as a JSON
> Object.
> ---
>
> Key: ATLAS-1110
> URL: https://issues.apache.org/jira/browse/ATLAS-1110
> Project: Atlas
> Issue Type: Improvement
>Reporter: David Radley
>
> Issuing a REST call to see the details of an entity which is a Hive column I
> issue:
> curl h --user admin:admin
> http://127.0.0.1:21000/api/atlas/v1/entities/d4e349c4-353b-4f03-8bc0-e894d559b74e
> I get
> "href":
> "http://127.0.0.1:21000/api/atlas/v1/entities/d4e349c4-353b-4f03-8bc0-e894d559b74e";,
> "name": "total_emp",
> "id": "d4e349c4-353b-4f03-8bc0-e894d559b74e",
> "type": "hive_column",
> "creation_time": "2016-06-24:00:20:13",
> "entityText": "hive_column type int table hive_table createTime Fri
> Jun 24 00:20:10 UTC 2016 lastAccessTime Fri Jun 24 00:20:10 UTC 2016
> retention 0 parameters numFiles 1 COLUMN_STATS_ACCURATE true
> transient_lastDdlTime 1466727619 totalSize 46069 tableType MANAGED_TABLE
> temporary false qualifiedName default.sample_08@Sandbox name sample_08 owner
> hive qualifiedName default.sample_08.total_emp@Sandbox name total_emp owner
> hive",
> "modified_time": "2016-06-24:00:20:24",
> "owner": "hive",
> "qualifiedName": "default.sample_08.total_emp@Sandbox",
> "state": "ACTIVE",
> "version": 0,
> "super_types": [
> "Asset",
> "Referenceable"
> ],
> I am looking to get hold of the real type (int in this case) - I can see that
> in the entityText there as an int. It would be really helpful if this type
> (and the other information) was properly exposed in the API as json objects;
> not a text string that I need to parse which potentially could change its
> content.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-1110) Improve Atlas Entity Rest API to show Hive column type (e.g int) as a JSON Object.
[ https://issues.apache.org/jira/browse/ATLAS-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414684#comment-15414684 ] Hemanth Yamijala commented on ATLAS-1110: - The entity definition for a hive column already defines the column type as an attribute. When we GET the entity using Atlas REST API, we should be seeing a *values* attribute which is a map that contains all the attributes defined for a type with the values of the specific entity being retrieved. In the report above, I am not sure if the entire response is captured. Can you please check the entire response, or paste it here for reference? > Improve Atlas Entity Rest API to show Hive column type (e.g int) as a JSON > Object. > --- > > Key: ATLAS-1110 > URL: https://issues.apache.org/jira/browse/ATLAS-1110 > Project: Atlas > Issue Type: Improvement >Reporter: David Radley > > Issuing a REST call to see the details of an entity which is a Hive column I > issue: > curl h --user admin:admin > http://127.0.0.1:21000/api/atlas/v1/entities/d4e349c4-353b-4f03-8bc0-e894d559b74e > I get > "href": > "http://127.0.0.1:21000/api/atlas/v1/entities/d4e349c4-353b-4f03-8bc0-e894d559b74e";, > "name": "total_emp", > "id": "d4e349c4-353b-4f03-8bc0-e894d559b74e", > "type": "hive_column", > "creation_time": "2016-06-24:00:20:13", > "entityText": "hive_column type int table hive_table createTime Fri > Jun 24 00:20:10 UTC 2016 lastAccessTime Fri Jun 24 00:20:10 UTC 2016 > retention 0 parameters numFiles 1 COLUMN_STATS_ACCURATE true > transient_lastDdlTime 1466727619 totalSize 46069 tableType MANAGED_TABLE > temporary false qualifiedName default.sample_08@Sandbox name sample_08 owner > hive qualifiedName default.sample_08.total_emp@Sandbox name total_emp owner > hive", > "modified_time": "2016-06-24:00:20:24", > "owner": "hive", > "qualifiedName": "default.sample_08.total_emp@Sandbox", > "state": "ACTIVE", > "version": 0, > "super_types": [ > "Asset", > "Referenceable" > ], > I am looking to get hold of the real type (int in this case) - I can see that > in the entityText there as an int. It would be really helpful if this type > (and the other information) was properly exposed in the API as json objects; > not a text string that I need to parse which potentially could change its > content. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1083) Perf experiments: With 25 threads/users running to ~20 hours - trying to create unique class type with "com.thinkaurelius.titan.diskstorage.locking.PermanentLockingExce
[
https://issues.apache.org/jira/browse/ATLAS-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407187#comment-15407187
]
Hemanth Yamijala commented on ATLAS-1083:
-
[~ayubkhan], There are two config parameters that help with this locking
performance. These are documented here:
http://atlas.incubator.apache.org/Configuration.html under the "Performance
Configuration Items" section. For greater number of users, we might need to
configure these to higher than the default values for avoiding this exception.
Can you please try out with these and see how it goes?
> Perf experiments: With 25 threads/users running to ~20 hours - trying to
> create unique class type with
> "com.thinkaurelius.titan.diskstorage.locking.PermanentLockingException: Could
> not lock the keyColumn KeyColumn" - seems like deadlock situation.
> ---
>
> Key: ATLAS-1083
> URL: https://issues.apache.org/jira/browse/ATLAS-1083
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
> Attachments: CreateTypes.jmx, jstackdump.txt
>
>
> Perf experiments: With 25 threads/users running to ~20 hours - trying to
> create unique class type fails with
> "com.thinkaurelius.titan.diskstorage.locking.PermanentLockingException: Could
> not lock the keyColumn KeyColumn" - seems like deadlock situation.
> *HDP-Build: HDP-2.5.0.0-1114*
> Steps to reproduce:
> 1. With 25 users per second, create a unique class type.
> 2. Run this for approximately 20 hours.
> 3. Below exception is seen in the application logs
> 4. Looking at the jstack dump, possibly this is because some of the threads
> are waiting for the lock which is held other thread
> 5. Attaching jstack trace and jmeter jmx file used for the same.
> 6. Providing application log link for reference.
> {noformat}
> 2016-08-03 06:09:36,164 ERROR - [qtp1342234299-63262 -
> b63be1d3-5ce9-484c-a907-70fc2aa5a047:] ~ Could not commit transaction
> [102122] due to exception (StandardTitanGraph:731)
> com.thinkaurelius.titan.diskstorage.locking.PermanentLockingException: Could
> not lock the keyColumn KeyColumn [k=0x 0- 0- 0- 0- 0- 0- 2- 9, c=0x
> 16-200] on CF {} e
> at
> com.thinkaurelius.titan.diskstorage.hbase.HBaseKeyColumnValueStore.handleLockFailure(HBaseKeyColumnValueStore.java:161)
> at
> com.thinkaurelius.titan.diskstorage.hbase.HBaseKeyColumnValueStore.acquireLock(HBaseKeyColumnValueStore.java:142)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.KCVSProxy.acquireLock(KCVSProxy.java:40)
> at
> com.thinkaurelius.titan.diskstorage.BackendTransaction.acquireEdgeLock(BackendTransaction.java:220)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.prepareCommit(StandardTitanGraph.java:466)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.commit(StandardTitanGraph.java:635)
> at
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1337)
> at
> com.thinkaurelius.titan.graphdb.database.management.ManagementSystem.commit(ManagementSystem.java:207)
> at
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.commit(GraphBackedSearchIndexer.java:387)
> at
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.onAdd(GraphBackedSearchIndexer.java:188)
> at
> org.apache.atlas.services.DefaultMetadataService.onTypesAdded(DefaultMetadataService.java:684)
> at
> org.apache.atlas.services.DefaultMetadataService.createOrUpdateTypes(DefaultMetadataService.java:254)
> at
> org.apache.atlas.services.DefaultMetadataService.createType(DefaultMetadataService.java:237)
> at
> org.apache.atlas.web.resources.TypesResource.submit(TypesResource.java:94)
> at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceCl
[jira] [Commented] (ATLAS-1062) suggested model improvement
[ https://issues.apache.org/jira/browse/ATLAS-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395392#comment-15395392 ] Hemanth Yamijala commented on ATLAS-1062: - [~davidrad], there is some implementation of this in ATLAS-819. We do have a couple of base classes that model these common attributes, and there are some system attributes that are mandatorily available in all attributes. There was feedback from the community that other than system attributes, the base classes with common attributes are more advisory and not mandatory (https://issues.apache.org/jira/browse/ATLAS-819?focusedCommentId=15299053&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15299053), which seemed a more flexible model to adopt. Also, the type system documentation has been updated but not pushed to public site with details about these system defined classes and attributes. Until there is a doc push, you could possibly use the docs that come up with the local build as reference - or even just look up https://github.com/apache/incubator-atlas/blob/master/docs/src/site/twiki/TypeSystem.twiki. > suggested model improvement > --- > > Key: ATLAS-1062 > URL: https://issues.apache.org/jira/browse/ATLAS-1062 > Project: Atlas > Issue Type: Improvement >Reporter: David Radley > > I look at the Type architecture and I see that many elements have a name - it > seems there should be a higher abstraction for named things. > I suggest the highest thing IDataType in the Types architecture diagram have > : > - a manditory name > - a manditory global unique identifier > - an optional short and long description > - a curator / owner > - associated notes (notes are free form text that could be added we track, > author, date , version if we allow notes to be updated). > It would make sense to have a higher level object that contains these > attributes, where IDataType is a subtype and a Term interface are subtypes. > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1057) Build break
[ https://issues.apache.org/jira/browse/ATLAS-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394499#comment-15394499 ] Hemanth Yamijala commented on ATLAS-1057: - I tried compiling when I saw this error, and it did indeed fail. But I retried it just now and it seems to be working fine. Maybe a transient repo issue? Can you please try again and see if it is working? > Build break > --- > > Key: ATLAS-1057 > URL: https://issues.apache.org/jira/browse/ATLAS-1057 > Project: Atlas > Issue Type: Bug >Reporter: David Radley > > I am installing Atlas for the first time. By > git clone https://git-wip-us.apache.org/repos/asf/incubator-atlas.git atlas > cd atlas > export MAVEN_OPTS="-Xmx1536m -XX:MaxPermSize=512m" && mvn clean install > I get an error building titan which looks like a dependancy issue. the > console shows: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) > on project atlas-titan: Error resolving project artifact: Could not transfer > artifact org.restlet.jee:org.restlet:pom:2.3.0 from/to apache.snapshots.repo > (https://repository.apache.org/content/groups/snapshots): handshake alert: > unrecognized_name for project org.restlet.jee:org.restlet:jar:2.3.0 -> [Help > 1] > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1022) Update typesystem wiki with details
[ https://issues.apache.org/jira/browse/ATLAS-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-1022: Attachment: ATLAS-1022.patch The attached patch pretty much rewrites the information in the type system twiki and provides a lot more information about * types * entities * attributes of types * system defined types It removes some images referenced in the previous version of the wiki. It needs expansion on traits which I shall do in a follow-up JIRA. > Update typesystem wiki with details > --- > > Key: ATLAS-1022 > URL: https://issues.apache.org/jira/browse/ATLAS-1022 > Project: Atlas > Issue Type: Improvement >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > Attachments: ATLAS-1022.patch > > > The current typesystem wiki page has a few issues: > * The descriptions are a bit too terse and can be expanded from a newbie's > perspective. > * The formatting is messed up. > Since the type system is so central to Atlas, it can be given some more love. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-347) Atlas search APIs should allow pagination of results
[ https://issues.apache.org/jira/browse/ATLAS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376331#comment-15376331 ] Hemanth Yamijala commented on ATLAS-347: [~shwethags], I have raised some comments on review board. They are pretty superficial for the most part. For the crux of the change in the Scala DSL code - it would be fair to say I've not reviewed it at all given I am not conversant with Scala. I do hope [~guptaneeru] has covered those areas. I plan to do the next best thing, which is to run some tests and validate. Will try that out sometime later. > Atlas search APIs should allow pagination of results > > > Key: ATLAS-347 > URL: https://issues.apache.org/jira/browse/ATLAS-347 > Project: Atlas > Issue Type: Improvement >Reporter: Hemanth Yamijala >Assignee: Shwetha G S >Priority: Critical > Fix For: 0.8-incubating > > Attachments: ATLAS-347-v2.patch, ATLAS-347.patch > > > Currently, we can search for all entities of type like a hive table or hive > column (query string is hive_table or hive_column). The API returns all > results at one shot in this case. With a sufficiently large number of > entities, this would be a huge list and a lot of data flowing from server to > UI. To scale this better, we should have a way of specifying to get a page of > results at a time in the API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1021) Update Atlas architecture wiki
[ https://issues.apache.org/jira/browse/ATLAS-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-1021: Attachment: ATLAS-1021-1.patch test-patch did not apply because of the binary image files in the diff. Re-generated the patch with --binary option and it seems to apply fine locally. Trying again. > Update Atlas architecture wiki > -- > > Key: ATLAS-1021 > URL: https://issues.apache.org/jira/browse/ATLAS-1021 > Project: Atlas > Issue Type: Improvement >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > Attachments: ATLAS-1021-1.patch, ATLAS-1021.patch > > > There have been some new additions to the Atlas architecture including new > apps like Business Taxonomy. This JIRA is to update the wiki with this > information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1022) Update typesystem wiki with details
Hemanth Yamijala created ATLAS-1022: --- Summary: Update typesystem wiki with details Key: ATLAS-1022 URL: https://issues.apache.org/jira/browse/ATLAS-1022 Project: Atlas Issue Type: Improvement Reporter: Hemanth Yamijala Assignee: Hemanth Yamijala The current typesystem wiki page has a few issues: * The descriptions are a bit too terse and can be expanded from a newbie's perspective. * The formatting is messed up. Since the type system is so central to Atlas, it can be given some more love. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1021) Update Atlas architecture wiki
[ https://issues.apache.org/jira/browse/ATLAS-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-1021: Attachment: ATLAS-1021.patch Attached patch is updated with documentation I had created some time back. It updates the architecture diagram to include newer components as well as pretty much rewrites the descriptions to be more current. It also removes an image that is no longer used in this patch. > Update Atlas architecture wiki > -- > > Key: ATLAS-1021 > URL: https://issues.apache.org/jira/browse/ATLAS-1021 > Project: Atlas > Issue Type: Improvement >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > Attachments: ATLAS-1021.patch > > > There have been some new additions to the Atlas architecture including new > apps like Business Taxonomy. This JIRA is to update the wiki with this > information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1021) Update Atlas architecture wiki
Hemanth Yamijala created ATLAS-1021: --- Summary: Update Atlas architecture wiki Key: ATLAS-1021 URL: https://issues.apache.org/jira/browse/ATLAS-1021 Project: Atlas Issue Type: Improvement Reporter: Hemanth Yamijala There have been some new additions to the Atlas architecture including new apps like Business Taxonomy. This JIRA is to update the wiki with this information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-1021) Update Atlas architecture wiki
[ https://issues.apache.org/jira/browse/ATLAS-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala reassigned ATLAS-1021: --- Assignee: Hemanth Yamijala > Update Atlas architecture wiki > -- > > Key: ATLAS-1021 > URL: https://issues.apache.org/jira/browse/ATLAS-1021 > Project: Atlas > Issue Type: Improvement >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > > There have been some new additions to the Atlas architecture including new > apps like Business Taxonomy. This JIRA is to update the wiki with this > information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-992) Added support for message queue properties an Selectors in Apache.NMS.MSMQ
[
https://issues.apache.org/jira/browse/ATLAS-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala resolved ATLAS-992.
Resolution: Invalid
This does not seem to be an Apache Atlas project's issue. Could you please file
this against the right component?
> Added support for message queue properties an Selectors in Apache.NMS.MSMQ
> --
>
> Key: ATLAS-992
> URL: https://issues.apache.org/jira/browse/ATLAS-992
> Project: Atlas
> Issue Type: Improvement
>Reporter: Stephane Ramet
> Attachments: 2016-07-05 - Apache.NMS.MSMQ.patch
>
>
> The proposed package implements the following enhancements :
> 1. Support for communication of message properties between compatible peers
> The DefaultMessageConverter has been enhanced, so as to marshall custom
> message properties in the MSMQ Message.Extension field, along with the
> NMSCorrelationID which was already marshalled in this field.
> An additional flag specifies whether the MSMQ Message.Label field should be
> populated with the NMSType (as currently - default value) or with the value
> of a message property called "Label".
> 2. Support for selectors
> A parser for selection strings has been introduced.
> It is based on the Apache.ActiveMQ V4 implementation, ported from Java to C#.
> MessageReaders have been developped, that support various types of filtering:
> - no filtering when no selector strings are specified.
> - filtering based on the Id (NMSMessageID), CorrelationId (NMSCorrelationID)
> or LookupId properties.
> - filtering based on any other valid selection string.
> MessageReaders have been introduced in MessageConsumers and QueueBrowsers.
> The generic filtering system, based on a selection string, has - at least -
> two limitations:
> - it cannot be fully included in the build chains: the source code is
> generated from SelectorParser.csc (a port of ActiveMQ's SelectorParser.jj) by
> CSharpCC (https://github.com/deveel/csharpcc, a port of JavaCC, now
> unmaintained). Due to limitations and/or bugs in the CSharpCC (eg. support
> for namespace {}), the generated code must be rectified manually. A port to
> another parser generator (eg. ANTLR) would certainly be required.
> - selection is performed by the client, by browsing through the messages in
> the queue, via MessageQueue.GetMessageEnumerator2(), and retrieving only the
> matching messages via MessageQueue.ReceiveByLookupId. When the queue gets
> very long and the relevant messages are sparse, performance becomes an issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-988) HiveHookIT.testInsertIntoTable is broken
Hemanth Yamijala created ATLAS-988:
--
Summary: HiveHookIT.testInsertIntoTable is broken
Key: ATLAS-988
URL: https://issues.apache.org/jira/browse/ATLAS-988
Project: Atlas
Issue Type: Bug
Affects Versions: 0.8-incubating
Reporter: Hemanth Yamijala
Priority: Blocker
Atlas master is broken, I suspect with changes due to ATLAS-917.
{code}
testInsertIntoTable(org.apache.atlas.hive.hook.HiveHookIT) Time elapsed: 0.524
sec <<< FAILURE!
java.lang.AssertionError: expected:<0> but was:<1>
at
org.apache.atlas.hive.hook.HiveHookIT.runCommandWithDelay(HiveHookIT.java:1157)
at org.apache.atlas.hive.hook.HiveHookIT.runCommand(HiveHookIT.java:123)
at
org.apache.atlas.hive.hook.HiveHookIT.testInsertIntoTable(HiveHookIT.java:566)
Results :
Failed tests:
HiveHookIT.testInsertIntoTable:566->runCommand:123->runCommandWithDelay:1157
expected:<0> but was:<1>
{code}
{code}
2016-07-04 19:47:44,136 ERROR - [main:] ~ Exception: java.io.IOException:
Cannot run program "/usr/bin/hadoop" (in directory
"/Users/hyamijala/projects/hwx/atlas/src/atlas/addons/hive-bridge"): error=2,
No such file or directory (MapredLocalTask:316)
java.io.IOException: Cannot run program "/usr/bin/hadoop" (in directory
"/Users/hyamijala/projects/hwx/atlas/src/atlas/addons/hive-bridge"): error=2,
No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1047)
at java.lang.Runtime.exec(Runtime.java:617)
at java.lang.Runtime.exec(Runtime.java:450)
at
org.apache.hadoop.hive.ql.exec.mr.MapredLocalTask.executeInChildVM(MapredLocalTask.java:289)
at
org.apache.hadoop.hive.ql.exec.mr.MapredLocalTask.execute(MapredLocalTask.java:138)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:88)
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1653)
at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1412)
at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1195)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1059)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1049)
at
org.apache.atlas.hive.hook.HiveHookIT.runCommandWithDelay(HiveHookIT.java:1156)
at org.apache.atlas.hive.hook.HiveHookIT.runCommand(HiveHookIT.java:123)
at
org.apache.atlas.hive.hook.HiveHookIT.testInsertIntoTable(HiveHookIT.java:566)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:132)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:112)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:147)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
Caused by: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:185)
at java.lang.ProcessImpl.start(ProcessImpl.java:130)
at java.lan
[jira] [Commented] (ATLAS-970) Remove glyphicon from login.jsp
[ https://issues.apache.org/jira/browse/ATLAS-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361337#comment-15361337 ] Hemanth Yamijala commented on ATLAS-970: Looks good to me. +1. > Remove glyphicon from login.jsp > --- > > Key: ATLAS-970 > URL: https://issues.apache.org/jira/browse/ATLAS-970 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Blocker > Attachments: ATLAS-970.1.patch, ATLAS-970.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-979) Search: search on boolean values is not working
[
https://issues.apache.org/jira/browse/ATLAS-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360983#comment-15360983
]
Hemanth Yamijala commented on ATLAS-979:
Yes.
> Search: search on boolean values is not working
> ---
>
> Key: ATLAS-979
> URL: https://issues.apache.org/jira/browse/ATLAS-979
> Project: Atlas
> Issue Type: Bug
>Reporter: Hemanth Yamijala
>
> Create an type with a boolean attribute and an entity of the type. Search
> using DSL with the query "typeName where boolean_attribute = true". This is
> failing with an exception as below:
> {code}
> org.apache.atlas.discovery.DiscoveryException: Invalid expression :
> hbase_table where isEnabled = true
> at
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:139)
> at
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.searchByDSL(GraphBackedDiscoveryService.java:124)
> at
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
> at
> org.apache.atlas.web.resources.MetadataDiscoveryResource.searchUsingQueryDSL(MetadataDiscoveryResource.java:116)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> ...
> Caused by: org.apache.atlas.AtlasException: Cannot combine types: boolean and
> boolean
> at org.apache.atlas.query.TypeUtils$.combinedType(TypeUtils.scala:56)
> at
> org.apache.atlas.query.Expressions$ComparisonExpression.dataType$lzycompute(Expressions.scala:639)
> at
> org.apache.atlas.query.Expressions$ComparisonExpression.dataType(Expressions.scala:628)
> at
> org.apache.atlas.query.Expressions$ComparisonExpression.dataType(Expressions.scala:623)
> at
> org.apache.atlas.query.Expressions$FilterExpression.dataType$lzycompute(Expressions.scala:672)
> at
> org.apache.atlas.query.Expressions$FilterExpression.dataType(Expressions.scala:667)
> at
> org.apache.atlas.query.QueryProcessor$.validate(QueryProcessor.scala:49)
> at
> org.apache.atlas.query.QueryProcessor.validate(QueryProcessor.scala)
> at
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:144)
> at
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:134)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-970) Remove glyphicon from login.jsp
[
https://issues.apache.org/jira/browse/ATLAS-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359020#comment-15359020
]
Hemanth Yamijala commented on ATLAS-970:
[~kevalbhatt18], I see two references to this here:
{code}
dashboardv2/public/css/scss/form.scss:.input-group-btn .glyphicon {
dashboardv2/public/css/scss/loader.scss:.glyphicon-spin {
{code}
Are these required, or can they also be removed?
Other than that, looks good to me.
> Remove glyphicon from login.jsp
> ---
>
> Key: ATLAS-970
> URL: https://issues.apache.org/jira/browse/ATLAS-970
> Project: Atlas
> Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Blocker
> Attachments: ATLAS-970.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-985) ENTITY_DELETE entity notification does not change state of deleted entity
Hemanth Yamijala created ATLAS-985: -- Summary: ENTITY_DELETE entity notification does not change state of deleted entity Key: ATLAS-985 URL: https://issues.apache.org/jira/browse/ATLAS-985 Project: Atlas Issue Type: Bug Reporter: Hemanth Yamijala * Delete an entity. * Look at the corresponding Entity notification in ATLAS_ENTITIES topic. The event has the right details for the deleted entity (GUID, etc,) but the state is set to ACTIVE still. This is slightly confusing as the entity was deleted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-984) TRAIT_DELETE entity notification event does not contain the deleted trait information
Hemanth Yamijala created ATLAS-984: -- Summary: TRAIT_DELETE entity notification event does not contain the deleted trait information Key: ATLAS-984 URL: https://issues.apache.org/jira/browse/ATLAS-984 Project: Atlas Issue Type: Bug Reporter: Hemanth Yamijala * Disassociate a trait instance from an entity. * Look at the corresponding Entity notification event that is triggered. The event contains a traits structure which is empty. This provides no information when integrating about what the trait is that was deleted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-983) Search: When selecting an attribute that is a reference or set of references, not all attribute definitions are returned.
Hemanth Yamijala created ATLAS-983: -- Summary: Search: When selecting an attribute that is a reference or set of references, not all attribute definitions are returned. Key: ATLAS-983 URL: https://issues.apache.org/jira/browse/ATLAS-983 Project: Atlas Issue Type: Bug Reporter: Hemanth Yamijala DSL Search allows to select an attribute that is a reference or collection of other references. For e.g. query="hive_table, select columns" As part of the search response, a dataType attribute is returned that is supposed to contain a list of attribute definitions pertaining to the entity that is being returned in the search results. In this case, it does not return all the attribute definitions, but only the first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-982) Search response is slightly inconsistent with other request / response types in Atlas
Hemanth Yamijala created ATLAS-982: -- Summary: Search response is slightly inconsistent with other request / response types in Atlas Key: ATLAS-982 URL: https://issues.apache.org/jira/browse/ATLAS-982 Project: Atlas Issue Type: Improvement Reporter: Hemanth Yamijala In search responses that return entity encodings, there are slight differences to the entity definition structure that is used in all other APIs: * id is encoded as $id$ * typeName is encoded as $typeName$ * In the dataType attribute that returns a TypesDef structure encoding, the attribute encoding for multiplicity is different. It doesn't cast the value to a string like "optional" or "required", instead it expands it as min 0, max 0 etc. These can be made consistent with respect to EntityDefinition and TypesDef structures used in other APIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-981) Search: 'has' clause is not working
Hemanth Yamijala created ATLAS-981: -- Summary: Search: 'has' clause is not working Key: ATLAS-981 URL: https://issues.apache.org/jira/browse/ATLAS-981 Project: Atlas Issue Type: Bug Reporter: Hemanth Yamijala http://atlas.incubator.apache.org/Search.html mentions the 'has' clause as: bq. has can be used to filter Entities that have a value for a particular Attribute. So, trying type_name has attribute_name is not returning any results, althouth attribute_name has values in entities of that type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-980) UI: Search with select attributes is not showing any results
[ https://issues.apache.org/jira/browse/ATLAS-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358825#comment-15358825 ] Hemanth Yamijala commented on ATLAS-980: There is probably some relation between this and ATLAS-971. > UI: Search with select attributes is not showing any results > > > Key: ATLAS-980 > URL: https://issues.apache.org/jira/browse/ATLAS-980 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala > > Fire a query of the form "typeName where attribute=value, select a1, a2, a3" > where a1, a2, a3 are some attributes of typeName. The UI displays the number > of results fetched, but does not display anything in the UI - it is a blank > screen. > The API response is correct and has the right values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-980) UI: Search with select attributes is not showing any results
Hemanth Yamijala created ATLAS-980: -- Summary: UI: Search with select attributes is not showing any results Key: ATLAS-980 URL: https://issues.apache.org/jira/browse/ATLAS-980 Project: Atlas Issue Type: Bug Reporter: Hemanth Yamijala Fire a query of the form "typeName where attribute=value, select a1, a2, a3" where a1, a2, a3 are some attributes of typeName. The UI displays the number of results fetched, but does not display anything in the UI - it is a blank screen. The API response is correct and has the right values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-979) Search: search on boolean values is not working
Hemanth Yamijala created ATLAS-979:
--
Summary: Search: search on boolean values is not working
Key: ATLAS-979
URL: https://issues.apache.org/jira/browse/ATLAS-979
Project: Atlas
Issue Type: Bug
Reporter: Hemanth Yamijala
Create an type with a boolean attribute and an entity of the type. Search using
DSL with the query "typeName where boolean_attribute = true". This is failing
with an exception as below:
{code}
org.apache.atlas.discovery.DiscoveryException: Invalid expression : hbase_table
where isEnabled = true
at
org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:139)
at
org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.searchByDSL(GraphBackedDiscoveryService.java:124)
at
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
at
org.apache.atlas.web.resources.MetadataDiscoveryResource.searchUsingQueryDSL(MetadataDiscoveryResource.java:116)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
...
Caused by: org.apache.atlas.AtlasException: Cannot combine types: boolean and
boolean
at org.apache.atlas.query.TypeUtils$.combinedType(TypeUtils.scala:56)
at
org.apache.atlas.query.Expressions$ComparisonExpression.dataType$lzycompute(Expressions.scala:639)
at
org.apache.atlas.query.Expressions$ComparisonExpression.dataType(Expressions.scala:628)
at
org.apache.atlas.query.Expressions$ComparisonExpression.dataType(Expressions.scala:623)
at
org.apache.atlas.query.Expressions$FilterExpression.dataType$lzycompute(Expressions.scala:672)
at
org.apache.atlas.query.Expressions$FilterExpression.dataType(Expressions.scala:667)
at
org.apache.atlas.query.QueryProcessor$.validate(QueryProcessor.scala:49)
at org.apache.atlas.query.QueryProcessor.validate(QueryProcessor.scala)
at
org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:144)
at
org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:134)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-978) UI: When disassociating a business term from an entity, the Trait delete API is used
Hemanth Yamijala created ATLAS-978: -- Summary: UI: When disassociating a business term from an entity, the Trait delete API is used Key: ATLAS-978 URL: https://issues.apache.org/jira/browse/ATLAS-978 Project: Atlas Issue Type: Improvement Reporter: Hemanth Yamijala UI: When disassociating a business term from an entity, the Trait delete API is used. However, when associating a business term to an entity, the Business catalog API is used. This seems inconsistent, although the end result is the same in both cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-977) Business Catalog API to associate term to entity calls the resource "tag" instead of "term"
Hemanth Yamijala created ATLAS-977:
--
Summary: Business Catalog API to associate term to entity calls
the resource "tag" instead of "term"
Key: ATLAS-977
URL: https://issues.apache.org/jira/browse/ATLAS-977
Project: Atlas
Issue Type: Improvement
Reporter: Hemanth Yamijala
The business catalog API to associate a term to entity is as follows:
POST
http:///api/atlas/v1/entities/{entity_guid}/tags/{fully_qualified_name_of_term}
The resource name tags is inconsistent with what is used elsewhere - where it
is referred to as "terms" or "term"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-976) AtlasClient is missing DELETE_TRAIT API
Hemanth Yamijala created ATLAS-976: -- Summary: AtlasClient is missing DELETE_TRAIT API Key: ATLAS-976 URL: https://issues.apache.org/jira/browse/ATLAS-976 Project: Atlas Issue Type: Improvement Reporter: Hemanth Yamijala AtlasClient has API to add a trait instance to an entity, but it doesn't contain a delete trait instance from entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-975) Lineage response should return qualifiedNames instead of names
Hemanth Yamijala created ATLAS-975: -- Summary: Lineage response should return qualifiedNames instead of names Key: ATLAS-975 URL: https://issues.apache.org/jira/browse/ATLAS-975 Project: Atlas Issue Type: Bug Reporter: Hemanth Yamijala Currently the lineage response returns the name attribute of datasets, but this could be the same as the name is a short form name of DataSets (inherited from the Asset type). In the lineage UI, this results in vertices having the same name and is slightly confusing. This can be improved by using qualified names (inherited from the Referenceable type) that is a unique name -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-974) Entity definitions with incorrect boolean attribute encodings are failing
Hemanth Yamijala created ATLAS-974: -- Summary: Entity definitions with incorrect boolean attribute encodings are failing Key: ATLAS-974 URL: https://issues.apache.org/jira/browse/ATLAS-974 Project: Atlas Issue Type: Bug Reporter: Hemanth Yamijala * Create a type with a boolean attribute * Create an entity of the type, set the boolean attribute as "abc" This creation succeeds. * Get the entity: It has the value of the boolean attribute set to false. This is somewhat confusing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-973) Simplify Lineage query response
Hemanth Yamijala created ATLAS-973: -- Summary: Simplify Lineage query response Key: ATLAS-973 URL: https://issues.apache.org/jira/browse/ATLAS-973 Project: Atlas Issue Type: Improvement Reporter: Hemanth Yamijala Currently, lineage query response is leaking a lot of abstractions. While the request for creating a lineage is quite succinct in terms of Process and DataSet objects, the response talks in terms of Vertices, Edges etc. This can be improved. Filing this here for discussion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-972) Create entity response for a request with multiple entities is not returning back all definitions
Hemanth Yamijala created ATLAS-972: -- Summary: Create entity response for a request with multiple entities is not returning back all definitions Key: ATLAS-972 URL: https://issues.apache.org/jira/browse/ATLAS-972 Project: Atlas Issue Type: Bug Reporter: Hemanth Yamijala Create multiple entities in the same POST request to http:///api/atlas/entities. The response contains an element called definition. But this contains only the first entity object in the request and not all entity definitions. This is inconsistent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-967) Remove unused logo file and footer.
[ https://issues.apache.org/jira/browse/ATLAS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-967. Resolution: Fixed I committed this to 0.7 branch and master. Thanks for a quick turnaround on this, [~kevalbhatt18]! > Remove unused logo file and footer. > --- > > Key: ATLAS-967 > URL: https://issues.apache.org/jira/browse/ATLAS-967 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Hemanth Yamijala >Assignee: Keval Bhatt >Priority: Blocker > Fix For: 0.7-incubating > > Attachments: ATLAS-967.1.patch, ATLAS-967.patch > > > There is an unused footer and icon dashboardv2/public/img/logo-green.png. > This is not used in the UI and hence should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-967) Remove unused logo file and footer.
[ https://issues.apache.org/jira/browse/ATLAS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356920#comment-15356920 ] Hemanth Yamijala commented on ATLAS-967: +1 for the patch. Verified the files are deleted. Also, built and checked UI once for sanity testing. Looks fine. > Remove unused logo file and footer. > --- > > Key: ATLAS-967 > URL: https://issues.apache.org/jira/browse/ATLAS-967 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Hemanth Yamijala >Assignee: Keval Bhatt >Priority: Blocker > Fix For: 0.7-incubating > > Attachments: ATLAS-967.1.patch, ATLAS-967.patch > > > There is an unused footer and icon dashboardv2/public/img/logo-green.png. > This is not used in the UI and hence should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-967) Remove unused logo file and footer.
Hemanth Yamijala created ATLAS-967: -- Summary: Remove unused logo file and footer. Key: ATLAS-967 URL: https://issues.apache.org/jira/browse/ATLAS-967 Project: Atlas Issue Type: Bug Affects Versions: 0.7-incubating Reporter: Hemanth Yamijala Priority: Blocker Fix For: 0.7-incubating There is an unused footer and icon dashboardv2/public/img/logo-green.png. This is not used in the UI and hence should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-967) Remove unused logo file and footer.
[ https://issues.apache.org/jira/browse/ATLAS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-967: --- Assignee: Keval Bhatt > Remove unused logo file and footer. > --- > > Key: ATLAS-967 > URL: https://issues.apache.org/jira/browse/ATLAS-967 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Hemanth Yamijala >Assignee: Keval Bhatt >Priority: Blocker > Fix For: 0.7-incubating > > > There is an unused footer and icon dashboardv2/public/img/logo-green.png. > This is not used in the UI and hence should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-964) Cleanup NOTICE and LICENSE
[
https://issues.apache.org/jira/browse/ATLAS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356566#comment-15356566
]
Hemanth Yamijala commented on ATLAS-964:
+1
> Cleanup NOTICE and LICENSE
> --
>
> Key: ATLAS-964
> URL: https://issues.apache.org/jira/browse/ATLAS-964
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-964.patch
>
>
> {noformat}
> Hi,
> We have removed the glyphicons fonts, updated the license and notice to
> match the source contents. Will you be able to do a quick check to see if
> we are missing anything here:
> https://github.com/apache/incubator-atlas/tree/0.7-incubating?
> License looks good to me only two very minor things I can see you / may not
> want to change:
> - No need for the quotes around MIT license or the like. I've seen this done
> elsewhere but can't think of a reason for doing so. Rabbit ears / scare
> quotes [1] can imply that it's actually not the correct license or that it's
> a MIT like license.
> - Why not legally required I include the a pointer to the public domain text.
> Notice is a bit odd, why have the section "Titan also includes software from
> other open source projects including..."? Are these things bundled or just
> dependancies? If they are just dependancies there is no need to mention then
> in NOTICE, move them to a DEPENDENCIES files if you think it is useful
> information to tell the user of the software.
> (Feel free to post this to the list for discussion if you want)
> Thanks,
> Justin
> 1. https://en.wikipedia.org/wiki/Scare_quotes
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-963) UI: Entity details is not display String array attribute values correctly
Hemanth Yamijala created ATLAS-963:
--
Summary: UI: Entity details is not display String array attribute
values correctly
Key: ATLAS-963
URL: https://issues.apache.org/jira/browse/ATLAS-963
Project: Atlas
Issue Type: Bug
Reporter: Hemanth Yamijala
If an entity definition contains an attribute that is a JSON array of strings,
the UI is not rendering this properly.
The attribute value will be of type:
{code}
attribute_name: [ value1, value2, ... ]
{code}
For example:
{code}
"columnNames":[ "cssnsi", "mylookca" ]
{code}
The same issue may be there for other types of array attribute values like
array of ints, booleans etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-958) Add licenses for dashboard dependencies
[
https://issues.apache.org/jira/browse/ATLAS-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355253#comment-15355253
]
Hemanth Yamijala commented on ATLAS-958:
There is a RAT check failure.. Can you please cover this as well?
{code}
Unapproved licenses:
/Users/hyamijala/projects/hwx/atlas/src/atlas/dashboardv2/public/css/bootstrap-sidebar.css
{code}
> Add licenses for dashboard dependencies
> ---
>
> Key: ATLAS-958
> URL: https://issues.apache.org/jira/browse/ATLAS-958
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Keval Bhatt
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-958.1.patch, ATLAS-958.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-962) Include Apache Incubator disclaimer text on website.
[ https://issues.apache.org/jira/browse/ATLAS-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-962: --- Fix Version/s: 0.7-incubating > Include Apache Incubator disclaimer text on website. > > > Key: ATLAS-962 > URL: https://issues.apache.org/jira/browse/ATLAS-962 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > Fix For: 0.7-incubating > > Attachments: ATLAS-962.patch > > > The Apache Incubator disclaimer is required to be included in the website on > the main page as per requirements of the Apache incubation process. Filing > this to make the change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-962) Include Apache Incubator disclaimer text on website.
[ https://issues.apache.org/jira/browse/ATLAS-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-962: --- Attachment: ATLAS-962.patch Attached patch file updates Index.twiki with the text from this link: http://incubator.apache.org/guides/branding.html > Include Apache Incubator disclaimer text on website. > > > Key: ATLAS-962 > URL: https://issues.apache.org/jira/browse/ATLAS-962 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > Attachments: ATLAS-962.patch > > > The Apache Incubator disclaimer is required to be included in the website on > the main page as per requirements of the Apache incubation process. Filing > this to make the change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-962) Include Apache Incubator disclaimer text on website.
[ https://issues.apache.org/jira/browse/ATLAS-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala reassigned ATLAS-962: -- Assignee: Hemanth Yamijala > Include Apache Incubator disclaimer text on website. > > > Key: ATLAS-962 > URL: https://issues.apache.org/jira/browse/ATLAS-962 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > > The Apache Incubator disclaimer is required to be included in the website on > the main page as per requirements of the Apache incubation process. Filing > this to make the change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-962) Include Apache Incubator disclaimer text on website.
Hemanth Yamijala created ATLAS-962: -- Summary: Include Apache Incubator disclaimer text on website. Key: ATLAS-962 URL: https://issues.apache.org/jira/browse/ATLAS-962 Project: Atlas Issue Type: Bug Reporter: Hemanth Yamijala The Apache Incubator disclaimer is required to be included in the website on the main page as per requirements of the Apache incubation process. Filing this to make the change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-431) Remove un-used licenses
[ https://issues.apache.org/jira/browse/ATLAS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354563#comment-15354563 ] Hemanth Yamijala commented on ATLAS-431: +1 for the change. > Remove un-used licenses > --- > > Key: ATLAS-431 > URL: https://issues.apache.org/jira/browse/ATLAS-431 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > Attachments: ATLAS-431-v2.patch, ATLAS-431.patch > > > From 0.6 voting thread: > On 26/12/15 5:14 am, "Justin Mclean" wrote: > Hi, > +1 binding > I checked: > - artefact contains “incubating” > - signatures and hashes correct > - DISCLAIMER exists > - LICENSE and NOTICE good, but license main contain too many things (see > below). > - no unexpected binaries in release > - all source files have Apache headers > - can compile from source > The license mentions Berkeley DB Java Edition and ASM but it doesn’t look > like these are bundled in the source release. If this is the case they should > be removed from the source LICENSE file. [1] > Thanks, > Justin > 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-431) Remove un-used licenses
[
https://issues.apache.org/jira/browse/ATLAS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352912#comment-15352912
]
Hemanth Yamijala commented on ATLAS-431:
I looked at the changes and also tried to verify this against the guidelines
listed here: http://www.apache.org/dev/licensing-howto.html. The only *doubt* I
have is whether we need to include these two lines from
https://github.com/thinkaurelius/titan/blob/titan05/NOTICE.txt in our NOTICE.
Other than this, it looks fine AFAIK. Of course, we need to wait for ATLAS-958
to make the whole thing complete.
{code}
==
Titan: Distributed Graph Database
Copyright 2012 and onwards Aurelius
==
{code}
> Remove un-used licenses
> ---
>
> Key: ATLAS-431
> URL: https://issues.apache.org/jira/browse/ATLAS-431
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-431.patch
>
>
> From 0.6 voting thread:
> On 26/12/15 5:14 am, "Justin Mclean" wrote:
> Hi,
> +1 binding
> I checked:
> - artefact contains “incubating”
> - signatures and hashes correct
> - DISCLAIMER exists
> - LICENSE and NOTICE good, but license main contain too many things (see
> below).
> - no unexpected binaries in release
> - all source files have Apache headers
> - can compile from source
> The license mentions Berkeley DB Java Edition and ASM but it doesn’t look
> like these are bundled in the source release. If this is the case they should
> be removed from the source LICENSE file. [1]
> Thanks,
> Justin
> 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-956) StormAtlasHook is not working for topologies that do not refer to Hadoop related bolts
[
https://issues.apache.org/jira/browse/ATLAS-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352509#comment-15352509
]
Hemanth Yamijala commented on ATLAS-956:
I had to copy at least these 3 jars for the issue to be resolved:
* hadoop-common.jar
* log4j-1.2.17.jar
* Gson-2.5.jar
* I suspect we may need hadoop-auth as well to work in secure environments
> StormAtlasHook is not working for topologies that do not refer to Hadoop
> related bolts
> --
>
> Key: ATLAS-956
> URL: https://issues.apache.org/jira/browse/ATLAS-956
> Project: Atlas
> Issue Type: Bug
>Reporter: Hemanth Yamijala
>Priority: Critical
>
> Submitting simple topologies that do not have any Hadoop specific bolts or
> functionality is causing exceptions in StormAtlas Hook, like below:
> {code}
> 684 [main] INFO o.a.s.StormSubmitter - Generated ZooKeeper secret payload
> for MD5-digest: -8572156748850444065:-7480695850066516712
> 776 [main] INFO o.a.s.s.a.AuthUtils - Got AutoCreds []
> 780 [main] WARN o.a.s.u.NimbusClient - Using deprecated config nimbus.host
> for backward compatibility. Please update your storm.yaml so it only has
> config nimbus.seeds
> 843 [main] WARN o.a.s.u.NimbusClient - Using deprecated config nimbus.host
> for backward compatibility. Please update your storm.yaml so it only has
> config nimbus.seeds
> 857 [main] INFO o.a.s.StormSubmitter - Uploading topology jar
> /tmp/1cb29a4a36b011e6a028080027f12dac.jar to assigned location:
> /hadoop/storm/nimbus/inbox/stormjar-f7558579-b946-4add-91c0-ad5a5177864c.jar
> 873 [main] INFO o.a.s.StormSubmitter - Successfully uploaded topology jar
> to assigned location:
> /hadoop/storm/nimbus/inbox/stormjar-f7558579-b946-4add-91c0-ad5a5177864c.jar
> 874 [main] INFO o.a.s.StormSubmitter - Submitting topology
> WordCountid007f0100_date271916 in distributed mode with conf
> {"storm.zookeeper.topology.auth.scheme":"digest","storm.zookeeper.topology.auth.payload":"-8572156748850444065:-7480695850066516712","topology.workers":3,"topology.debug":true}
> 874 [main] WARN o.a.s.u.NimbusClient - Using deprecated config nimbus.host
> for backward compatibility. Please update your storm.yaml so it only has
> config nimbus.seeds
> 1011 [main] INFO o.a.s.StormSubmitter - Finished submitting topology:
> WordCountid007f0100_date271916
> 1011 [main] INFO o.a.s.StormSubmitter - Initializing the registered
> ISubmitterHook [org.apache.atlas.storm.hook.StormAtlasHook]
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/hadoop/conf/Configuration
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.storm.StormSubmitter.invokeSubmitterHook(StormSubmitter.java:282)
> at
> org.apache.storm.StormSubmitter.submitTopologyAs(StormSubmitter.java:258)
> at
> org.apache.storm.StormSubmitter.submitTopology(StormSubmitter.java:311)
> at
> org.apache.storm.StormSubmitter.submitTopology(StormSubmitter.java:157)
> at storm.starter.WordCountTopology.main(WordCountTopology.java:77)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.conf.Configuration
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 7 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-957) Atlas is not capturing topologies that have $ in the data payload
Hemanth Yamijala created ATLAS-957:
--
Summary: Atlas is not capturing topologies that have $ in the data
payload
Key: ATLAS-957
URL: https://issues.apache.org/jira/browse/ATLAS-957
Project: Atlas
Issue Type: Bug
Reporter: Hemanth Yamijala
We found a topology that created a specific payload in Kafka ATLAS_HOOK topic,
that Atlas failed to process with an exception. The payload was:
{code}
{
"version": {
"version": "1.0.0"
},
"message": {
"entities": [{
"jsonClass":
"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
"id": {
"jsonClass":
"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id": "-12002007734454",
"version": 0,
"typeName": "storm_topology",
"state": "ACTIVE"
},
"typeName": "storm_topology",
"values": {
"name": "WordCountid007f0100_date381916",
"startTime": 1466404755258,
"outputs": [],
"id": "WordCountid007f0100_date381916-5-1466404754",
"inputs": [],
"qualifiedName": "WordCountid007f0100_date381916",
"nodes": [{
"jsonClass":
"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
"id": {
"jsonClass":
"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id": "-12002013206349",
"version": 0,
"typeName": "storm_bolt",
"state": "ACTIVE"
},
"typeName": "storm_bolt",
"values": {
"name": "split",
"outputs": ["count"],
"driverClass": "storm.starter.WordCountTopology$SplitSentence",
"conf": {
"SplitSentence._pendingWrites.takeLock.sync.state": "0",
"SplitSentence._running": "true",
"SplitSentence.workerTimeoutMills": "0",
"SplitSentence.sendHeartbeatFlag.value": "0",
"SplitSentence.lastHeartbeatTimestamp.value": "0",
"SplitSentence._pendingWrites.notEmpty.this$0.state": "0"
},
"inputs": ["spout"]
},
"traitNames": ["DataProcessor"],
"traits": {
"DataProcessor": {
"jsonClass":
"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
"typeName": "DataProcessor",
"values": {}
}
}
}, {
"jsonClass":
"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
"id": {
"jsonClass":
"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id": "-12002012737263",
"version": 0,
"typeName": "storm_spout",
"state": "ACTIVE"
},
"typeName": "storm_spout",
"values": {
"outputs": ["split"],
"name": "spout",
"driverClass": "storm.starter.spout.RandomSentenceSpout",
"conf": {}
},
"traitNames": ["DataProducer"],
"traits": {
"DataProducer": {
"jsonClass":
"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
"typeName": "DataProducer",
"values": {}
}
}
}, {
"jsonClass":
"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
"id": {
"jsonClass":
"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id": "-12002021428964",
"version": 0,
"typeName": "storm_bolt",
"state": "ACTIVE"
},
"typeName": "storm_bolt",
"values": {
"name": "count",
"driverClass": "org.apache.storm.topology.BasicBoltExecutor",
"conf": {},
"inputs": ["split"]
},
"traitNames": ["DataProcessor"],
"traits": {
"DataProcessor": {
"jsonClass":
"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
"typeName": "DataProcessor",
"values": {}
}
}
}],
"owner": "storm",
"clusterName": "cl1"
},
"traitNames": [],
"traits": {}
}],
"type": "ENTITY_CREATE",
"user": "storm"
}
}
{code}
The exception was
{code}
org.apache.atlas.AtlasServiceException: Metadata service API CREATE_ENTITY
failed with status 400(Bad Request) Response Body
(java.lang.IllegalArgumentException: Name can not contains reserved character
$: storm_node.conf.SplitSentence._pendingWrites.notEmpty.this$0.state
at
com.google.common.base.Preconditions.checkArgument(Preconditions.java:119)
at
com.thinkaurelius.titan.graphdb.types.StandardRelationTypeMaker.checkName(StandardRelationTypeMaker.java:70)
at
com.thinkaurelius.titan.graphdb.typ
[jira] [Created] (ATLAS-956) StormAtlasHook is not working for topologies that do not refer to Hadoop related bolts
Hemanth Yamijala created ATLAS-956:
--
Summary: StormAtlasHook is not working for topologies that do not
refer to Hadoop related bolts
Key: ATLAS-956
URL: https://issues.apache.org/jira/browse/ATLAS-956
Project: Atlas
Issue Type: Bug
Reporter: Hemanth Yamijala
Priority: Critical
Submitting simple topologies that do not have any Hadoop specific bolts or
functionality is causing exceptions in StormAtlas Hook, like below:
{code}
684 [main] INFO o.a.s.StormSubmitter - Generated ZooKeeper secret payload for
MD5-digest: -8572156748850444065:-7480695850066516712
776 [main] INFO o.a.s.s.a.AuthUtils - Got AutoCreds []
780 [main] WARN o.a.s.u.NimbusClient - Using deprecated config nimbus.host
for backward compatibility. Please update your storm.yaml so it only has config
nimbus.seeds
843 [main] WARN o.a.s.u.NimbusClient - Using deprecated config nimbus.host
for backward compatibility. Please update your storm.yaml so it only has config
nimbus.seeds
857 [main] INFO o.a.s.StormSubmitter - Uploading topology jar
/tmp/1cb29a4a36b011e6a028080027f12dac.jar to assigned location:
/hadoop/storm/nimbus/inbox/stormjar-f7558579-b946-4add-91c0-ad5a5177864c.jar
873 [main] INFO o.a.s.StormSubmitter - Successfully uploaded topology jar to
assigned location:
/hadoop/storm/nimbus/inbox/stormjar-f7558579-b946-4add-91c0-ad5a5177864c.jar
874 [main] INFO o.a.s.StormSubmitter - Submitting topology
WordCountid007f0100_date271916 in distributed mode with conf
{"storm.zookeeper.topology.auth.scheme":"digest","storm.zookeeper.topology.auth.payload":"-8572156748850444065:-7480695850066516712","topology.workers":3,"topology.debug":true}
874 [main] WARN o.a.s.u.NimbusClient - Using deprecated config nimbus.host
for backward compatibility. Please update your storm.yaml so it only has config
nimbus.seeds
1011 [main] INFO o.a.s.StormSubmitter - Finished submitting topology:
WordCountid007f0100_date271916
1011 [main] INFO o.a.s.StormSubmitter - Initializing the registered
ISubmitterHook [org.apache.atlas.storm.hook.StormAtlasHook]
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/hadoop/conf/Configuration
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at
org.apache.storm.StormSubmitter.invokeSubmitterHook(StormSubmitter.java:282)
at
org.apache.storm.StormSubmitter.submitTopologyAs(StormSubmitter.java:258)
at
org.apache.storm.StormSubmitter.submitTopology(StormSubmitter.java:311)
at
org.apache.storm.StormSubmitter.submitTopology(StormSubmitter.java:157)
at storm.starter.WordCountTopology.main(WordCountTopology.java:77)
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.conf.Configuration
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 7 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ATLAS-953) pyspark
[ https://issues.apache.org/jira/browse/ATLAS-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-953. Resolution: Invalid This is not an Apache Atlas issue. Please create a new issue by selecting the correct project. > pyspark > --- > > Key: ATLAS-953 > URL: https://issues.apache.org/jira/browse/ATLAS-953 > Project: Atlas > Issue Type: Bug >Reporter: Edward Ma > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-927) aboutAtlas_tmpl.html has hard-coded project version
[
https://issues.apache.org/jira/browse/ATLAS-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350971#comment-15350971
]
Hemanth Yamijala commented on ATLAS-927:
Looks good to me. I can see only one call now. +1.
> aboutAtlas_tmpl.html has hard-coded project version
> ---
>
> Key: ATLAS-927
> URL: https://issues.apache.org/jira/browse/ATLAS-927
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-927.1.patch, ATLAS-927.2.patch, ATLAS-927.patch
>
>
> dashboardv2/public/js/templates/common/aboutAtlas_tmpl.html has hard coded
> version:
> {code}
> Version :
> 0.7-incubating-SNAPSHOT-ra2cc01c4342ace7f7a3e3e254d7ede781f990318
> {code}
> Instead, it should use mvn resource filtering to set the version to project
> version
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-735) UI showing incorrect results if two queries are executed.(first query succeeds but second should fail)
[ https://issues.apache.org/jira/browse/ATLAS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350938#comment-15350938 ] Hemanth Yamijala commented on ATLAS-735: [~kevalbhatt18] / [~ayubkhan], I cannot reproduce this bug (without the patch) on my machine. I mean, if I perform these quick searches, the older results are not getting displayed, even if I fire two queries. Since [~ayubkhan] has a scenario where this is happening, can you probably take this for a spin? > UI showing incorrect results if two queries are executed.(first query > succeeds but second should fail) > -- > > Key: ATLAS-735 > URL: https://issues.apache.org/jira/browse/ATLAS-735 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Ayub Khan >Assignee: Keval Bhatt > Attachments: ATLAS-735.patch, DSL-query.gif > > > Steps to repro: > 1. Through search tab, fire a valid dsl search query(eg: hive_table) and make > sure this query response takes time(~30 seconds) > 2. Before the response comes for the first query, search for another invalid > query.(this will fail with 400 error). > 3. Now when the response for first query returns, the UI still renders the > first query's response as if it is a response to second query which seems > incorrect. And this might lead to a confusion from a customer's perspective. > This can be an issue from a customer's perspective and the probability of > happening in production is pretty high. > If the above steps are not clear, I am attaching a GIF which captures the > steps to repro. Please take a look. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-927) aboutAtlas_tmpl.html has hard-coded project version
[
https://issues.apache.org/jira/browse/ATLAS-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350896#comment-15350896
]
Hemanth Yamijala commented on ATLAS-927:
Overall functionality looks fine. Just one minor nit: I see that when I select
the About menu from the UI, it results in two calls being fired for the
/api/atlas/admin/version URL. This is not a big deal, but would be good to
avoid in case its hiding any other issue. Can you please check?
> aboutAtlas_tmpl.html has hard-coded project version
> ---
>
> Key: ATLAS-927
> URL: https://issues.apache.org/jira/browse/ATLAS-927
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-927.1.patch, ATLAS-927.patch
>
>
> dashboardv2/public/js/templates/common/aboutAtlas_tmpl.html has hard coded
> version:
> {code}
> Version :
> 0.7-incubating-SNAPSHOT-ra2cc01c4342ace7f7a3e3e254d7ede781f990318
> {code}
> Instead, it should use mvn resource filtering to set the version to project
> version
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ATLAS-624) UI: Clicking a tag hyperlink should always result in DSL search. In some cases, results in full-text search.
[ https://issues.apache.org/jira/browse/ATLAS-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-624. Resolution: Fixed Fix Version/s: 0.8-incubating I just committed this. Thanks, [~Kalyanikashikar] for the patch, and [~ayubkhan] for reporting it. > UI: Clicking a tag hyperlink should always result in DSL search. In some > cases, results in full-text search. > > > Key: ATLAS-624 > URL: https://issues.apache.org/jira/browse/ATLAS-624 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk >Reporter: Ayub Khan >Assignee: Kalyani Kashikar > Fix For: 0.8-incubating > > Attachments: ATLAS-624.1.patch, ATLAS-624.2.patch, ATLAS-624.patch > > > UI: Clicking a tag hyperlink should always result in DSL search. > 1. Create a hive table with a column, Attach a tag to the column. > 2. Now navigate to the schema tab of hive_table search result. > 3. Click on the attached tag - This will result in full-text query search of > that tag, which will always return empty response. This should be ideally a > DSL search query which will show all the entities associated with that tag. > Ideally, this should be true in all cases. i.e; Whenever a tag hyperlink is > clicked on atlas UI, this should result in DSL search only. > UI snapshot for reference: > https://monosnap.com/file/QKWcuSeG85UI3NDXakvR7iD9LJd1RC -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-624) UI: Clicking a tag hyperlink should always result in DSL search. In some cases, results in full-text search.
[ https://issues.apache.org/jira/browse/ATLAS-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350779#comment-15350779 ] Hemanth Yamijala commented on ATLAS-624: Looks good to me. I don't know why I saw the difference in the earlier patch, but it is working fine now. +1. Will commit. > UI: Clicking a tag hyperlink should always result in DSL search. In some > cases, results in full-text search. > > > Key: ATLAS-624 > URL: https://issues.apache.org/jira/browse/ATLAS-624 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk >Reporter: Ayub Khan >Assignee: Kalyani Kashikar > Attachments: ATLAS-624.1.patch, ATLAS-624.2.patch, ATLAS-624.patch > > > UI: Clicking a tag hyperlink should always result in DSL search. > 1. Create a hive table with a column, Attach a tag to the column. > 2. Now navigate to the schema tab of hive_table search result. > 3. Click on the attached tag - This will result in full-text query search of > that tag, which will always return empty response. This should be ideally a > DSL search query which will show all the entities associated with that tag. > Ideally, this should be true in all cases. i.e; Whenever a tag hyperlink is > clicked on atlas UI, this should result in DSL search only. > UI snapshot for reference: > https://monosnap.com/file/QKWcuSeG85UI3NDXakvR7iD9LJd1RC -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-951) GraphRepoMapperScaleTest is slower by about 20 seconds and is indicative of a performance regression
Hemanth Yamijala created ATLAS-951: -- Summary: GraphRepoMapperScaleTest is slower by about 20 seconds and is indicative of a performance regression Key: ATLAS-951 URL: https://issues.apache.org/jira/browse/ATLAS-951 Project: Atlas Issue Type: Bug Reporter: Hemanth Yamijala The GraphRepoMapperScaleTest usually takes around 80 seconds on my dev box. Currently is is taking about 100 seconds on my dev box. When there was a performance regression in Atlas, it took upto 5 minutes. This was eventually caught in performance tests [~ssainath] ran (ATLAS-690). [~shwethags], [~suma.shivaprasad] also noticed this regression. Filing this here so we can investigate closer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-950) Atlas should support Solr that requires Kerberos authentication
[ https://issues.apache.org/jira/browse/ATLAS-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350418#comment-15350418 ] Hemanth Yamijala commented on ATLAS-950: Changes look good to me. Have commented details of my review on review board. +1 > Atlas should support Solr that requires Kerberos authentication > --- > > Key: ATLAS-950 > URL: https://issues.apache.org/jira/browse/ATLAS-950 > Project: Atlas > Issue Type: Bug >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj > Attachments: ATLAS-950.patch > > > Currently Atlas uses Solr version 5.1.0 libraries, which does not support > Kerberos authentication. To support Solr instances that require Kerberos > authentication, Atlas should use recent Solr version libraries - like 5.5.1. > Details Solr Security can be found at: > https://cwiki.apache.org/confluence/display/solr/Securing+Solr -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-949) UI improvement
[ https://issues.apache.org/jira/browse/ATLAS-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348149#comment-15348149 ] Hemanth Yamijala commented on ATLAS-949: [~Kalyanikashikar], can you please expand of the JIRA title and provide some description about what improvements you are looking at? It would help later for reviews, etc. Thanks! > UI improvement > -- > > Key: ATLAS-949 > URL: https://issues.apache.org/jira/browse/ATLAS-949 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-806) Create default taxonomy at server startup
[ https://issues.apache.org/jira/browse/ATLAS-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-806: --- Attachment: ATLAS-806-2.patch Modified the default taxonomy name to "Catalog" > Create default taxonomy at server startup > - > > Key: ATLAS-806 > URL: https://issues.apache.org/jira/browse/ATLAS-806 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > Fix For: 0.8-incubating > > Attachments: ATLAS-806-1.patch, ATLAS-806-2.patch, ATLAS-806.patch > > > Currently, the UI is creating a default taxonomy object as the first call in > its flow. This would not work if used from an API. Hence, creating this > automatically at server startup time will help. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-806) Create default taxonomy at server startup
[
https://issues.apache.org/jira/browse/ATLAS-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated ATLAS-806:
---
Attachment: ATLAS-806-1.patch
Attaching a patch with the following changes:
* Addresses review comments I raised on the review board request.
* Sets default taxonomy name to "BusinessTaxonomy"
* One scenario uncovered during testing: The check for existence of taxonomies
was not setting the cached variable {{defaultTaxonomyInitialized}} to true.
Thus if a taxonomy is created externally, say via API or from another server,
there would be repeated checks for existence of taxonomy instances even if it
is not necessary. Fixed this issue.
> Create default taxonomy at server startup
> -
>
> Key: ATLAS-806
> URL: https://issues.apache.org/jira/browse/ATLAS-806
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-806-1.patch, ATLAS-806.patch
>
>
> Currently, the UI is creating a default taxonomy object as the first call in
> its flow. This would not work if used from an API. Hence, creating this
> automatically at server startup time will help.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-945) Minor typo in warning message while deleting terms
Hemanth Yamijala created ATLAS-945:
--
Summary: Minor typo in warning message while deleting terms
Key: ATLAS-945
URL: https://issues.apache.org/jira/browse/ATLAS-945
Project: Atlas
Issue Type: Bug
Reporter: Hemanth Yamijala
Priority: Minor
Create terms under Taxonomy tab on left pane. Select a term and delete. There
is an alert message that comes up saying:
{code}
"Delete: `BusinessTaxonomy.term1.term12`?
Assets map to this term will be unclassified
{code}
The 2nd line should read: Assets *mapped* to this term will be unclassified.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-943) ATlas Build failure: Storm Bridge
[
https://issues.apache.org/jira/browse/ATLAS-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346057#comment-15346057
]
Hemanth Yamijala commented on ATLAS-943:
[~jonesn], we had uncovered this as part of ATLAS-912. The documentation has
been updated to specify MAVEN_OPTS to 1.5GB:
https://github.com/apache/incubator-atlas/blob/0.7-incubating/docs/src/site/twiki/InstallationSteps.twiki
- when this is pushed to the website it will be public.
It appears there's something in Kafka 0.9.0.1+ that requires more memory
locally - we may need to investigate closer. But for now 1.5GB works. Can you
please let us know if that works for you?
> ATlas Build failure: Storm Bridge
> -
>
> Key: ATLAS-943
> URL: https://issues.apache.org/jira/browse/ATLAS-943
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
> Environment: CentOS 7.2.1511
> Maven 3.3.9
> OpenJDK 1.7.0_101
> *fresh atlas clone*
>Reporter: Nigel Jones
>
> [INFO] Apache Atlas Storm Bridge .. FAILURE [02:34
> min]
> [WARNING] FAILED
> o.e.j.m.p.JettyWebAppContext@17d43cec{/,file:/home/ibmcloud/src/atlas/webapp/target/atlas-webapp-0.8-incubating-SNAPSHOT/,STARTING}{/home/ibmcloud/src/atlas/webapp/target/atlas-webapp-0.8-incubating-SNAPSHOT.war}:
> java.lang.OutOfMemoryError: Java heap space
> java.lang.OutOfMemoryError: Java heap space
> at java.nio.HeapByteBuffer.(HeapByteBuffer.java:57)
> at java.nio.ByteBuffer.allocate(ByteBuffer.java:331)
> at kafka.log.SkimpyOffsetMap.(OffsetMap.scala:43)
> at kafka.log.LogCleaner$CleanerThread.(LogCleaner.scala:193)
> at kafka.log.LogCleaner$$anonfun$1.apply(LogCleaner.scala:83)
> at kafka.log.LogCleaner$$anonfun$1.apply(LogCleaner.scala:83)
> at
> etc.
> Heap Space likely needs increasing for clean build/test
> Log file to be attached...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ATLAS-806) Create default taxonomy at server startup
[ https://issues.apache.org/jira/browse/ATLAS-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala reassigned ATLAS-806: -- Assignee: Hemanth Yamijala (was: John Speidel) Assigning to self for completion. > Create default taxonomy at server startup > - > > Key: ATLAS-806 > URL: https://issues.apache.org/jira/browse/ATLAS-806 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > Fix For: 0.8-incubating > > Attachments: ATLAS-806.patch > > > Currently, the UI is creating a default taxonomy object as the first call in > its flow. This would not work if used from an API. Hence, creating this > automatically at server startup time will help. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-806) Create default taxonomy at server startup
[ https://issues.apache.org/jira/browse/ATLAS-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-806: --- Fix Version/s: 0.8-incubating > Create default taxonomy at server startup > - > > Key: ATLAS-806 > URL: https://issues.apache.org/jira/browse/ATLAS-806 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > Fix For: 0.8-incubating > > Attachments: ATLAS-806.patch > > > Currently, the UI is creating a default taxonomy object as the first call in > its flow. This would not work if used from an API. Hence, creating this > automatically at server startup time will help. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-939) apache-atlas-0.8-incubating-SNAPSHOT payload doesn't start
[
https://issues.apache.org/jira/browse/ATLAS-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344528#comment-15344528
]
Hemanth Yamijala commented on ATLAS-939:
{code}
Cannot connect to cluster at localhost:2181: cluster not found/not ready
{code}
Is Zookeeper, Solr running? Have the Solr indexes been created?
Can you please confirm if you have followed steps documented here:
http://atlas.incubator.apache.org/InstallationSteps.html for setting up the
cluster.
Unless the Atlas distribution is created with berkeleydb_elasticsearch profile,
a few manual steps are required to setup the dependencies like HBase and Solr.
Please do let us know if you can use those steps to set things up fine. Would
be happy to help if you are still facing issues.
> apache-atlas-0.8-incubating-SNAPSHOT payload doesn't start
> --
>
> Key: ATLAS-939
> URL: https://issues.apache.org/jira/browse/ATLAS-939
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
> Environment: Linux RH 7.2 Atlas used
> apache-atlas-0.8-incubating-SNAPSHOT
>Reporter: Ushma Dubal
>
> I tried to execute atlas payload as it is. i.e with Solr search
> configuration. When tried to access Atlas url it throws error.
> 2016-06-22 04:28:55,708 WARN - [main:] ~ FAILED
> o.e.j.w.WebAppContext@-33285a78{/,file:/opt/ushma/apache-atlas-0.8-incubating-SNAPSHOT/server/webapp/atlas/,STARTING}{/opt/ushma/apache-atlas-0.8-incubating-SNAPSHOT/server/webapp/atlas}:
> java.lang.ExceptionInInitializerError (AbstractLifeCycle:212)
> java.lang.ExceptionInInitializerError
> at java.lang.J9VMInternals.ensureError(J9VMInternals.java:137)
> at
> java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:126)
> at
> org.apache.atlas.repository.graph.DeleteHandler.(DeleteHandler.java:50)
> at java.lang.Class.forNameImpl(Native Method)
> at java.lang.Class.forName(Class.java:273)
> at
> org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
> at
> org.apache.atlas.RepositoryMetadataModule.getDeleteHandlerImpl(RepositoryMetadataModule.java:148)
> at
> org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:95)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
> at com.google.inject.spi.Elements.getElements(Elements.java:110)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
> at com.google.inject.Guice.createInjector(Guice.java:96)
> at com.google.inject.Guice.createInjector(Guice.java:73)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:78)
> at
> com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:132)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:93)
> at org.apache.atlas.Atlas.main(Atlas.java:113)
> Caused by: java.la
[jira] [Resolved] (ATLAS-938) I want to configure BA server for SAML authenticaion. Please let me know how to obtain pentaho-saml-sample.kar file?
[ https://issues.apache.org/jira/browse/ATLAS-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-938. Resolution: Invalid This is not an issue in the Atlas project. Can you please file it against the right project? > I want to configure BA server for SAML authenticaion. Please let me know how > to obtain pentaho-saml-sample.kar file? > > > Key: ATLAS-938 > URL: https://issues.apache.org/jira/browse/ATLAS-938 > Project: Atlas > Issue Type: Bug >Reporter: Gauri Shirsath > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-765) Need documentation for Authentication and Authorization features of Atlas
[ https://issues.apache.org/jira/browse/ATLAS-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-765: --- Attachment: ATLAS-765-1.patch The attached file makes editorial changes to the text provided in the original patch. It also adds a link to the new wiki page in Index.twiki. > Need documentation for Authentication and Authorization features of Atlas > - > > Key: ATLAS-765 > URL: https://issues.apache.org/jira/browse/ATLAS-765 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Nixon Rodrigues >Priority: Critical > Fix For: 0.7-incubating > > Attachments: ATLAS-765-1.patch, ATLAS-765.patch > > > Since authentication and authorization are incompatible changes to Atlas > source, it will be very helpful to have detailed user documentation on how to > set this up using various user / policy stores. The sooner we have this, the > better it will be for the community. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-904) Hive hook fails due to session state not being set
[
https://issues.apache.org/jira/browse/ATLAS-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated ATLAS-904:
---
Attachment: ATLAS-904.4.patch
There were minor import rebases in HiveHookIT
> Hive hook fails due to session state not being set
> --
>
> Key: ATLAS-904
> URL: https://issues.apache.org/jira/browse/ATLAS-904
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-904.1.patch, ATLAS-904.2.patch, ATLAS-904.3.patch,
> ATLAS-904.4.patch, ATLAS-904.patch
>
>
> {noformat}
> 2016-06-15 11:34:30,423 WARN [Atlas Logger 0]: hook.HiveHook
> (HiveHook.java:normalize(557)) - Could not rewrite query due to error.
> Proceeding with original query EXPORT TABLE test_export_table to
> 'hdfs://localhost:9000/hive_tables/test_path1'
> java.lang.NullPointerException: Conf non-local session path expected to be
> non-null
> at
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:204)
> at
> org.apache.hadoop.hive.ql.session.SessionState.getHDFSSessionPath(SessionState.java:641)
> at org.apache.hadoop.hive.ql.Context.(Context.java:133)
> at org.apache.hadoop.hive.ql.Context.(Context.java:120)
> at
> org.apache.atlas.hive.rewrite.HiveASTRewriter.(HiveASTRewriter.java:44)
> at org.apache.atlas.hive.hook.HiveHook.normalize(HiveHook.java:554)
> at
> org.apache.atlas.hive.hook.HiveHook.getProcessReferenceable(HiveHook.java:702)
> at
> org.apache.atlas.hive.hook.HiveHook.registerProcess(HiveHook.java:596)
> at org.apache.atlas.hive.hook.HiveHook.fireAndForget(HiveHook.java:222)
> at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:77)
> at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:182)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 2016-06-15 11:34:30,423 ERROR [Atlas Logger 0]: hook.HiveHook
> (HiveHook.java:run(184)) - Atlas hook failed due to error
> java.lang.NullPointerException
> at java.lang.StringBuilder.(StringBuilder.java:109)
> at
> org.apache.atlas.hive.hook.HiveHook.getProcessQualifiedName(HiveHook.java:738)
> at
> org.apache.atlas.hive.hook.HiveHook.getProcessReferenceable(HiveHook.java:703)
> at
> org.apache.atlas.hive.hook.HiveHook.registerProcess(HiveHook.java:596)
> at org.apache.atlas.hive.hook.HiveHook.fireAndForget(HiveHook.java:222)
> at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:77)
> at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:182)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-928) UI is not showing the name column for hive tables in the schema tab
[ https://issues.apache.org/jira/browse/ATLAS-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-928: --- Attachment: ATLAS-928.patch The right fix for this issue should probably come from the server side, but for now, I am attaching a temporary patch that fixes this on the UI side. Essentially, the attempt is for the UI to always include a name attribute if the returned superTypes contains 'Asset'. From my tests this is working for hive tables and quick start tables both. I will test more in detail, but putting this up in case someone can take a look. > UI is not showing the name column for hive tables in the schema tab > --- > > Key: ATLAS-928 > URL: https://issues.apache.org/jira/browse/ATLAS-928 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala >Priority: Critical > Fix For: 0.7-incubating > > Attachments: ATLAS-928.patch, hive_schema_response.json > > > * Create a hive table from the hive hook. > * Search for it in the UI, and select the schema tab > * There is no name shown for the columns of the table (although all other > attributes like comment, data type are present). > The same issue does not occur for quick_start Tables. > The reason seems to be that the UI is using the attributeDefinitions element > in the return of the schema API to decide what columns to show. With > ATLAS-819, the name attribute was made a common attribute via a supertype for > assets like hive tables. The Schema API does not return the super type > attributes in the attributeDefinitions. Hence, even though the response of > the schema API contains the name attribute, because it is missing from the > attributeDefinitions, it is not picked up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-928) UI is not showing the name column for hive tables in the schema tab
[ https://issues.apache.org/jira/browse/ATLAS-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala reassigned ATLAS-928: -- Assignee: Hemanth Yamijala (was: Kalyani Kashikar) > UI is not showing the name column for hive tables in the schema tab > --- > > Key: ATLAS-928 > URL: https://issues.apache.org/jira/browse/ATLAS-928 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala >Priority: Critical > Fix For: 0.7-incubating > > Attachments: hive_schema_response.json > > > * Create a hive table from the hive hook. > * Search for it in the UI, and select the schema tab > * There is no name shown for the columns of the table (although all other > attributes like comment, data type are present). > The same issue does not occur for quick_start Tables. > The reason seems to be that the UI is using the attributeDefinitions element > in the return of the schema API to decide what columns to show. With > ATLAS-819, the name attribute was made a common attribute via a supertype for > assets like hive tables. The Schema API does not return the super type > attributes in the attributeDefinitions. Hence, even though the response of > the schema API contains the name attribute, because it is missing from the > attributeDefinitions, it is not picked up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations
[
https://issues.apache.org/jira/browse/ATLAS-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated ATLAS-930:
---
Priority: Critical (was: Major)
> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
> Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-930.patch, application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805.
> However, I need a more complicated sequence of operations to reproduce the
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata
> service API CREATE_ENTITY failed with status 500(Internal Server Error)
> Response Body ({"error":"Could not commit transaction due to exception during
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could
> not commit transaction due to exception during persistence\n\tat
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:606)\n\tat
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\tat
> com.google.i
[jira] [Updated] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations
[
https://issues.apache.org/jira/browse/ATLAS-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated ATLAS-930:
---
Attachment: ATLAS-930.patch
Attaching a fairly simple patch. Verified the failing scenario works fine with
this patch. All existing tests pass.
> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
> Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-930.patch, application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805.
> However, I need a more complicated sequence of operations to reproduce the
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata
> service API CREATE_ENTITY failed with status 500(Internal Server Error)
> Response Body ({"error":"Could not commit transaction due to exception during
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could
> not commit transaction due to exception during persistence\n\tat
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:606)\n\tat
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>
> com.google.inject.servlet.Man
[jira] [Assigned] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations
[
https://issues.apache.org/jira/browse/ATLAS-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala reassigned ATLAS-930:
--
Assignee: Hemanth Yamijala
> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
> Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
> Fix For: 0.7-incubating
>
> Attachments: application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805.
> However, I need a more complicated sequence of operations to reproduce the
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata
> service API CREATE_ENTITY failed with status 500(Internal Server Error)
> Response Body ({"error":"Could not commit transaction due to exception during
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could
> not commit transaction due to exception during persistence\n\tat
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:606)\n\tat
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\tat
> com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.jav
[jira] [Updated] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations
[
https://issues.apache.org/jira/browse/ATLAS-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated ATLAS-930:
---
Fix Version/s: 0.7-incubating
> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
> Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
> Fix For: 0.7-incubating
>
> Attachments: application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805.
> However, I need a more complicated sequence of operations to reproduce the
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata
> service API CREATE_ENTITY failed with status 500(Internal Server Error)
> Response Body ({"error":"Could not commit transaction due to exception during
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could
> not commit transaction due to exception during persistence\n\tat
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:606)\n\tat
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\tat
> com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:13
[jira] [Commented] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations
[
https://issues.apache.org/jira/browse/ATLAS-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341709#comment-15341709
]
Hemanth Yamijala commented on ATLAS-930:
Right, so with more debugging, the case is narrowed to:
* Create a hive table
* Call the API api/atlas/lineage/{GUID}/inputs/graph
* Run quick start - the failure is seen
The reason for the failure seems to be that the new lineage APIs are missing
the {{GraphTransaction}} annotation. Hence the cause is similar to what we saw
in ATLAS-805, except it is happening at a different place.
I'll put up a patch that hopefully fixes this.
> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
> Issue Type: Bug
>Reporter: Hemanth Yamijala
> Attachments: application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805.
> However, I need a more complicated sequence of operations to reproduce the
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata
> service API CREATE_ENTITY failed with status 500(Internal Server Error)
> Response Body ({"error":"Could not commit transaction due to exception during
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could
> not commit transaction due to exception during persistence\n\tat
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:606)\n\tat
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>
> com.google.inject.servlet.FilterChainInvocation.doFilter(
[jira] [Commented] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations
[
https://issues.apache.org/jira/browse/ATLAS-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341613#comment-15341613
]
Hemanth Yamijala commented on ATLAS-930:
I tried the following sequences, which all seemed fine:
* Just creating hive tables and running quick start.
* Creating business taxonomy and running quick start.
* Creating hive table, default business taxonomy, search for hive_table and
running quick start.
I am not even sure if the sequence is relevant or its just a fluke. Would be
good if someone can replicate and confirm.
> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
> Issue Type: Bug
>Reporter: Hemanth Yamijala
> Attachments: application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805.
> However, I need a more complicated sequence of operations to reproduce the
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata
> service API CREATE_ENTITY failed with status 500(Internal Server Error)
> Response Body ({"error":"Could not commit transaction due to exception during
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could
> not commit transaction due to exception during persistence\n\tat
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:606)\n\tat
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
> org.apache.atl
[jira] [Updated] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations
[
https://issues.apache.org/jira/browse/ATLAS-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated ATLAS-930:
---
Attachment: application.log.qs-fail-after-hive
Application log file when I reproduced the problem for steps reported in
Description.
> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
> Issue Type: Bug
>Reporter: Hemanth Yamijala
> Attachments: application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805.
> However, I need a more complicated sequence of operations to reproduce the
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata
> service API CREATE_ENTITY failed with status 500(Internal Server Error)
> Response Body ({"error":"Could not commit transaction due to exception during
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could
> not commit transaction due to exception during persistence\n\tat
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:606)\n\tat
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\tat
> com.google.inject.servlet.GuiceFilter$1
