[jira] [Commented] (ATLAS-1016) Support for composite unique attributes for a type.

2016-10-10 Thread David Radley (JIRA) 

[ 
https://issues.apache.org/jira/browse/ATLAS-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15561749#comment-15561749
 ] 

David Radley commented on ATLAS-1016:
-

I read this as introducing something that would mean that the combination of 
more than one fields would need to be unique; even though the individual fields 
may not be unique. This can be used to define a more meaningful business key 
and can be used in master data management. 

Can we do this with the current support for structures? [~zhangqiangzte]

> Support for composite unique attributes for a type.
> ---
>
> Key: ATLAS-1016
> URL: https://issues.apache.org/jira/browse/ATLAS-1016
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8-incubating
>Reporter: Satish Duggana
> Fix For: 0.8-incubating
>
>
> Currently atlas types support attributes containing unique attributes. 
> Enhance this to support composite unique attributes. 
> For example,
> DeviceInfo has attributes like name, model, version and timestamp. Any of 
> these attributes can be configured unique constraint. There should be a way 
> to set composite unique constraint on both model and version fields so that 
> it should not allow storing entities having same set of values for both model 
> and version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-1218) Atlas says it is started but does not accept REST requests

2016-10-10 Thread David Radley (JIRA) 
David Radley created ATLAS-1218:
---

 Summary: Atlas says it is started but does not accept REST requests
 Key: ATLAS-1218
 URL: https://issues.apache.org/jira/browse/ATLAS-1218
 Project: Atlas
  Issue Type: Bug
Reporter: David Radley


I start Atlas on the command line and it tells me is started - but REST 
requests are not accepted immediately. There appears to be asynchronous 
background processes that have not yet initialized. I feel that when Atlas says 
it is started it should be open for business and accept REST requests.  a few 
seconds later REST requests are accepted. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-1182) Hive Column level lineage docs

2016-10-10 Thread zhangqiang2 (JIRA) 

[ 
https://issues.apache.org/jira/browse/ATLAS-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562034#comment-15562034
 ] 

zhangqiang2 commented on ATLAS-1182:


I also want to know if i want to built and install and use atlas and other  
Component, 
i find when i git clone the latest code from github  if i use maven3.3.9 then i 
can build it sucess ,as i use maven3.2.3.it build fail

whats version for atlas and other Component combination  good
for example atlas ,hive ,hadoop ,storm ，sqoop ，maven，and so on


> Hive Column level lineage docs
> --
>
> Key: ATLAS-1182
> URL: https://issues.apache.org/jira/browse/ATLAS-1182
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1182.patch, column_lineage_ex1.png
>
>
> Add column level lineage details to Atlas documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-1218) Atlas says it is started but does not accept REST requests

2016-10-10 Thread Nigel Jones (JIRA) 

[ 
https://issues.apache.org/jira/browse/ATLAS-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562387#comment-15562387
 ] 

Nigel Jones commented on ATLAS-1218:


I like this suggestion. 

I was setting up Cassandra to run under docker using docker-compose, and hit a 
similar issue whereby I wanted the client to wait until the server was ready. I 
ended up using a script that polled the relevant port. 

We may be able to do better in the atlas startup script with a check 
knowledgeable of atlas, but if not the one I used was at 
https://github.com/vishnubob/wait-for-it . That could also be useful in a 
similar situation. Indeed we could maybe have a "wait for atlas" or "is atlas 
running" script too as they can also help with automation. One less job for the 
integrator to do?

> Atlas says it is started but does not accept REST requests
> --
>
> Key: ATLAS-1218
> URL: https://issues.apache.org/jira/browse/ATLAS-1218
> Project: Atlas
>  Issue Type: Bug
>Reporter: David Radley
>
> I start Atlas on the command line and it tells me is started - but REST 
> requests are not accepted immediately. There appears to be asynchronous 
> background processes that have not yet initialized. I feel that when Atlas 
> says it is started it should be open for business and accept REST requests.  
> a few seconds later REST requests are accepted. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-1016) Support for composite unique attributes for a type.

2016-10-10 Thread Nigel Jones (JIRA) 

[ 
https://issues.apache.org/jira/browse/ATLAS-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562396#comment-15562396
 ] 

Nigel Jones commented on ATLAS-1016:


I'm not a titan expert, but an index can include multiple properties. An index 
can be unique. (not checked tinkerpop abstraction). I assume therefore that the 
underlying graph can do this... though I think in attribute it's single 
property only?

> Support for composite unique attributes for a type.
> ---
>
> Key: ATLAS-1016
> URL: https://issues.apache.org/jira/browse/ATLAS-1016
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8-incubating
>Reporter: Satish Duggana
> Fix For: 0.8-incubating
>
>
> Currently atlas types support attributes containing unique attributes. 
> Enhance this to support composite unique attributes. 
> For example,
> DeviceInfo has attributes like name, model, version and timestamp. Any of 
> these attributes can be configured unique constraint. There should be a way 
> to set composite unique constraint on both model and version fields so that 
> it should not allow storing entities having same set of values for both model 
> and version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 47810: ATLAS-694: Update Atlas to use Graph DB abstraction layer

2016-10-10 Thread Suma Shivaprasad 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/47810/#review152059
---


Ship it!




Ship It!

- Suma Shivaprasad


On Oct. 7, 2016, 9:28 p.m., Jeff Hagelberg wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47810/
> ---
> 
> (Updated Oct. 7, 2016, 9:28 p.m.)
> 
> 
> Review request for atlas, David Kantor and Neeru Gupta.
> 
> 
> Bugs: ATLAS-694
> https://issues.apache.org/jira/browse/ATLAS-694
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-694: Update Atlas to use abstraction layer.  All of the Atlas code 
> (with the exception of the catalog, which was only updated minimally) has 
> been updated to use the graph database abstraction layer.  In addition, there 
> is now an optional Atlas configuration property that specifies the class of 
> the abstraction layer database to use.  I basically put all of the changes in 
> here with the exception of the actual Titan 1 implementation of code.  This 
> includes the changes to support Tinkerpop 3 syntax.  This is mostly to 
> expedite getting the changes into Atlas.  Originally the TP3 changes were 
> going to be brought in as part of the Titan 1 implementation task.
> 
> Change Summary:
> 
>- change Atlas classes to use AtlasGraph,AtlasVertex,AtlasEdge, etc 
> instead of TitanGraph/Vertex/Edge, etc
>- compile time dependency on titan 0.5.4/TP 2 removed (except in Catalog, 
> which was only changed to use AtlasGraphProvider/AtlasGraph) - see 
> repository\pom.xml, other pom.xmls
>- updated DSL translation to generate Gremlin that is compliant with TP3 
> when TP3 is being used.  See GremlinQuery.scala, 
> GraphPersistenceStrategies.scala
>- TitanGraphProvider replaced by AtlasGraphProvider.  Graph database 
> implementation is determined from a new optional configuration property
>- HiveTitanSample is no longer used by tests.  It has been replaced by 
> hive-instances.json (which uses normal Atlas json syntax).  The data is saved 
> with a new JSONImporter class.  This was needed because the graphson syntax 
> used by HiveTitanSample is not compatible with TP3.  
> 
> Last rebase: 10/3/2016
> 
> 
> Diffs
> -
> 
>   .gitignore e10adbc4457f6297600f0feb01eb54718b8ec406 
>   addons/falcon-bridge/pom.xml 44dacb8ff8d8b9fbf61a1e1deecd4fe684a3c720 
>   addons/hdfs-model/pom.xml bd1debe8f6f0e8bbc1d0192808a6a0205e650491 
>   
> addons/hdfs-model/src/test/java/org/apache/atlas/fs/model/HDFSModelTest.java 
> ac60294e328835ba0340e150799ddfb348ccdb52 
>   addons/hive-bridge/pom.xml 3b8f576428f08d76b503b9f735fb2d0dddc01955 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/bridge/HiveMetaStoreBridge.java
>  ad7a4a5d09d8542a841701dfe04981f65f767c14 
>   addons/sqoop-bridge/pom.xml fa5bd8f04f26b386ba36b64efd8f510e16f2eefd 
>   addons/storm-bridge/pom.xml 4b3816f089bb4001b4aea8132dbff8f56617d537 
>   catalog/pom.xml 2f58a8f0748de65ab78eab35df6abd2fe7c336af 
>   catalog/src/main/java/org/apache/atlas/catalog/query/BaseQuery.java 
> e7bb505075983371ca12d9bc1d8c6eb240c3d134 
>   distro/src/conf/atlas-application.properties 
> d334600dc5534840409b586157799ef3abf9abf2 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasEdge.java 
> dd4b7e614cdd9bf30f957fb6a839d8c60f3e1701 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasElement.java
>  1bc0fc38c0802897f32260520770a16795474d04 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraph.java 
> 995c5457ac7f807172f367cc8e3348b3a98dd6f3 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraphIndex.java
>  41194d34f079842db0d95c73a8b099459f76ff2f 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraphManagement.java
>  c8cd2842ca3090b6bbd384c773b4eb45aff149ce 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraphQuery.java
>  93447495bcf18e9f19df9df68fd1cbe1427fc462 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasIndexQuery.java
>  e719d306ffe9f68e3ac6f7406baaf60a12390c34 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasPropertyKey.java
>  315ecddb861e1a1be6e0ab9b36fe4c0a52486ae8 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasVertex.java
>  fff6fb79247e7d0615ce83c4cbbd93d1bf8cf29c 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasVertexQuery.java
>  366cfe131512f36c02f59ad7e969ff94dfb0e12c 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/GraphDatabase.java
>  37acda5f6ddb883ee364d08a31251b071e6a89a5 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/GremlinVersion.java

[jira] [Created] (ATLAS-1219) AtlasGraphManagement should allow for edge label indexes to be created

2016-10-10 Thread Suma Shivaprasad (JIRA) 
Suma Shivaprasad created ATLAS-1219:
---

 Summary: AtlasGraphManagement should allow for edge label indexes 
to be created
 Key: ATLAS-1219
 URL: https://issues.apache.org/jira/browse/ATLAS-1219
 Project: Atlas
  Issue Type: Bug
Reporter: Suma Shivaprasad
Assignee: Jeffrey Hagelberg


The interface should provide a method for edge labels to be indexed by and 
should accept the edge label as a parameter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-694) Update Atlas code to use abstraction layer

2016-10-10 Thread Jeffrey Hagelberg (JIRA) 

[ 
https://issues.apache.org/jira/browse/ATLAS-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563448#comment-15563448
 ] 

Jeffrey Hagelberg commented on ATLAS-694:
-

[~suma.shivaprasad] - Dave just called me, the patch attached here represents 
that latest version of the ATLAS-694 code.  Please feel free to commit it, and 
definitely let me know if you find any problems.


> Update Atlas code to use abstraction layer
> --
>
> Key: ATLAS-694
> URL: https://issues.apache.org/jira/browse/ATLAS-694
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Jeffrey Hagelberg
>Assignee: Jeffrey Hagelberg
> Attachments: ATLAS-694.patch, rb47810.patch
>
>
> In this task, we will update Atlas to replace the direct usage of titan 
> classes with usage of the equivalent interfaces in the abstraction layer.  At 
> this point, there will be no options to configure the abstraction layer 
> implementation that gets used.  Atlas will be hard-coded to use the titan 
> 0.5.4 implementation.  It will also continue to have a compile time 
> dependency on the titan 0.5.4 graph database implementation.  When this task 
> is complete, Atlas will only be accessing titan through the abstraction layer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-694) Update Atlas code to use abstraction layer

2016-10-10 Thread Suma Shivaprasad (JIRA) 

[ 
https://issues.apache.org/jira/browse/ATLAS-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563455#comment-15563455
 ] 

Suma Shivaprasad commented on ATLAS-694:


+1. Ran tests and the unit tests are all passing. 

> Update Atlas code to use abstraction layer
> --
>
> Key: ATLAS-694
> URL: https://issues.apache.org/jira/browse/ATLAS-694
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Jeffrey Hagelberg
>Assignee: Jeffrey Hagelberg
> Attachments: ATLAS-694.patch, rb47810.patch
>
>
> In this task, we will update Atlas to replace the direct usage of titan 
> classes with usage of the equivalent interfaces in the abstraction layer.  At 
> this point, there will be no options to configure the abstraction layer 
> implementation that gets used.  Atlas will be hard-coded to use the titan 
> 0.5.4 implementation.  It will also continue to have a compile time 
> dependency on the titan 0.5.4 graph database implementation.  When this task 
> is complete, Atlas will only be accessing titan through the abstraction layer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 47810: ATLAS-694: Update Atlas to use Graph DB abstraction layer

2016-10-10 Thread Suma Shivaprasad 


> On Oct. 4, 2016, 9 p.m., Suma Shivaprasad wrote:
> > graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraphManagement.java,
> >  line 130
> > 
> >
> > Does the index here refer to the edgeLabel we are trying to create an 
> > idex for? Do we have everything we need in this interface to index an edge 
> > label?
> 
> Suma Shivaprasad wrote:
> I see that the index here refers to the indexName and not the edgeLabel. 
> We need to provide for indexing edge labels as well even though we dont use 
> that currently

Raised https://issues.apache.org/jira/browse/ATLAS-1219 for this


- Suma


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/47810/#review151393
---


On Oct. 7, 2016, 9:28 p.m., Jeff Hagelberg wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47810/
> ---
> 
> (Updated Oct. 7, 2016, 9:28 p.m.)
> 
> 
> Review request for atlas, David Kantor and Neeru Gupta.
> 
> 
> Bugs: ATLAS-694
> https://issues.apache.org/jira/browse/ATLAS-694
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-694: Update Atlas to use abstraction layer.  All of the Atlas code 
> (with the exception of the catalog, which was only updated minimally) has 
> been updated to use the graph database abstraction layer.  In addition, there 
> is now an optional Atlas configuration property that specifies the class of 
> the abstraction layer database to use.  I basically put all of the changes in 
> here with the exception of the actual Titan 1 implementation of code.  This 
> includes the changes to support Tinkerpop 3 syntax.  This is mostly to 
> expedite getting the changes into Atlas.  Originally the TP3 changes were 
> going to be brought in as part of the Titan 1 implementation task.
> 
> Change Summary:
> 
>- change Atlas classes to use AtlasGraph,AtlasVertex,AtlasEdge, etc 
> instead of TitanGraph/Vertex/Edge, etc
>- compile time dependency on titan 0.5.4/TP 2 removed (except in Catalog, 
> which was only changed to use AtlasGraphProvider/AtlasGraph) - see 
> repository\pom.xml, other pom.xmls
>- updated DSL translation to generate Gremlin that is compliant with TP3 
> when TP3 is being used.  See GremlinQuery.scala, 
> GraphPersistenceStrategies.scala
>- TitanGraphProvider replaced by AtlasGraphProvider.  Graph database 
> implementation is determined from a new optional configuration property
>- HiveTitanSample is no longer used by tests.  It has been replaced by 
> hive-instances.json (which uses normal Atlas json syntax).  The data is saved 
> with a new JSONImporter class.  This was needed because the graphson syntax 
> used by HiveTitanSample is not compatible with TP3.  
> 
> Last rebase: 10/3/2016
> 
> 
> Diffs
> -
> 
>   .gitignore e10adbc4457f6297600f0feb01eb54718b8ec406 
>   addons/falcon-bridge/pom.xml 44dacb8ff8d8b9fbf61a1e1deecd4fe684a3c720 
>   addons/hdfs-model/pom.xml bd1debe8f6f0e8bbc1d0192808a6a0205e650491 
>   
> addons/hdfs-model/src/test/java/org/apache/atlas/fs/model/HDFSModelTest.java 
> ac60294e328835ba0340e150799ddfb348ccdb52 
>   addons/hive-bridge/pom.xml 3b8f576428f08d76b503b9f735fb2d0dddc01955 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/bridge/HiveMetaStoreBridge.java
>  ad7a4a5d09d8542a841701dfe04981f65f767c14 
>   addons/sqoop-bridge/pom.xml fa5bd8f04f26b386ba36b64efd8f510e16f2eefd 
>   addons/storm-bridge/pom.xml 4b3816f089bb4001b4aea8132dbff8f56617d537 
>   catalog/pom.xml 2f58a8f0748de65ab78eab35df6abd2fe7c336af 
>   catalog/src/main/java/org/apache/atlas/catalog/query/BaseQuery.java 
> e7bb505075983371ca12d9bc1d8c6eb240c3d134 
>   distro/src/conf/atlas-application.properties 
> d334600dc5534840409b586157799ef3abf9abf2 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasEdge.java 
> dd4b7e614cdd9bf30f957fb6a839d8c60f3e1701 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasElement.java
>  1bc0fc38c0802897f32260520770a16795474d04 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraph.java 
> 995c5457ac7f807172f367cc8e3348b3a98dd6f3 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraphIndex.java
>  41194d34f079842db0d95c73a8b099459f76ff2f 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraphManagement.java
>  c8cd2842ca3090b6bbd384c773b4eb45aff149ce 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraphQuery.java
>  93447495bcf18e9f19df9df68fd1cbe1427fc462 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasIndexQuery.java
>  e719d306ff

[jira] [Comment Edited] (ATLAS-694) Update Atlas code to use abstraction layer

2016-10-10 Thread Jeffrey Hagelberg (JIRA) 

[ 
https://issues.apache.org/jira/browse/ATLAS-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563448#comment-15563448
 ] 

Jeffrey Hagelberg edited comment on ATLAS-694 at 10/10/16 9:02 PM:
---

[~suma.shivaprasad] - Dave just called me, the patch attached here represents 
the latest version of the ATLAS-694 code.  Please feel free to commit it, and 
definitely let me know if you find any problems.



was (Author: jnhagelb):
[~suma.shivaprasad] - Dave just called me, the patch attached here represents 
that latest version of the ATLAS-694 code.  Please feel free to commit it, and 
definitely let me know if you find any problems.


> Update Atlas code to use abstraction layer
> --
>
> Key: ATLAS-694
> URL: https://issues.apache.org/jira/browse/ATLAS-694
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Jeffrey Hagelberg
>Assignee: Jeffrey Hagelberg
> Attachments: ATLAS-694.patch, rb47810.patch
>
>
> In this task, we will update Atlas to replace the direct usage of titan 
> classes with usage of the equivalent interfaces in the abstraction layer.  At 
> this point, there will be no options to configure the abstraction layer 
> implementation that gets used.  Atlas will be hard-coded to use the titan 
> 0.5.4 implementation.  It will also continue to have a compile time 
> dependency on the titan 0.5.4 graph database implementation.  When this task 
> is complete, Atlas will only be accessing titan through the abstraction layer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-694) Update Atlas code to use abstraction layer

2016-10-10 Thread Suma Shivaprasad (JIRA) 

[ 
https://issues.apache.org/jira/browse/ATLAS-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563455#comment-15563455
 ] 

Suma Shivaprasad edited comment on ATLAS-694 at 10/10/16 10:40 PM:
---

+1. Ran tests and the unit tests are all passing. Ran quick start as well and 
that worked fine.


was (Author: suma.shivaprasad):
+1. Ran tests and the unit tests are all passing. 

> Update Atlas code to use abstraction layer
> --
>
> Key: ATLAS-694
> URL: https://issues.apache.org/jira/browse/ATLAS-694
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Jeffrey Hagelberg
>Assignee: Jeffrey Hagelberg
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-694.patch, rb47810.patch
>
>
> In this task, we will update Atlas to replace the direct usage of titan 
> classes with usage of the equivalent interfaces in the abstraction layer.  At 
> this point, there will be no options to configure the abstraction layer 
> implementation that gets used.  Atlas will be hard-coded to use the titan 
> 0.5.4 implementation.  It will also continue to have a compile time 
> dependency on the titan 0.5.4 graph database implementation.  When this task 
> is complete, Atlas will only be accessing titan through the abstraction layer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-1220) when i execute bin/atlas_start.py found HTTP ERROR: 503

2016-10-10 Thread zhangqiang2 (JIRA) 
zhangqiang2 created ATLAS-1220:
--

 Summary: when i execute bin/atlas_start.py   found HTTP ERROR: 503
 Key: ATLAS-1220
 URL: https://issues.apache.org/jira/browse/ATLAS-1220
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
 Environment:  
hadoop2.6.0+hbase1.1.5+solr5.5.2+zookeeper3.4.8+hive1.2.1+redhat6.5
Reporter: zhangqiang2


2016-10-11 10:01:06,739 INFO  - [main:] ~ Initializing type system for the 
first time. (DefaultMetadataService:162)
2016-10-11 10:01:07,495 WARN  - [main:] ~ class fs_path already registered, 
ignoring types in /home/hong/atlas/atlas-0.7/models/fs_model.json 
(ReservedTypesRegistrar:89)
2016-10-11 10:01:07,615 WARN  - [main:] ~ class hive_process already 
registered, ignoring types in /home/hong/atlas/atlas-0.7/models/hive_model.json 
(ReservedTypesRegistrar:89)
2016-10-11 10:01:07,654 WARN  - [main:] ~ class falcon_feed_replication already 
registered, ignoring types in 
/home/hong/atlas/atlas-0.7/models/falcon_model.json (ReservedTypesRegistrar:89)
2016-10-11 10:01:07,675 WARN  - [main:] ~ class sqoop_process already 
registered, ignoring types in 
/home/hong/atlas/atlas-0.7/models/sqoop_model.json (ReservedTypesRegistrar:89)
2016-10-11 10:01:07,707 WARN  - [main:] ~ class storm_topology already 
registered, ignoring types in 
/home/hong/atlas/atlas-0.7/models/storm_model.json (ReservedTypesRegistrar:89)
2016-10-11 10:01:07,707 INFO  - [main:] ~ Restored type system from the store 
(DefaultMetadataService:173)
2016-10-11 10:01:07,709 INFO  - [main:] ~ Guice modules loaded 
(GuiceServletConfig:120)
2016-10-11 10:01:07,714 INFO  - [main:] ~ Starting services 
(GuiceServletConfig:140)
2016-10-11 10:01:07,764 WARN  - [main-SendThread(dap241:9026):] ~ Session 0x0 
for server null, unexpected error, closing socket connection and attempting 
reconnect (ClientCnxn$SendThread:1102)
java.net.ConnectException: 拒绝连接
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
2016-10-11 10:01:07,803 INFO  - [main:] ~ HA is disabled. Hence creating table 
on startup. (HBaseBasedAuditRepository:287)
2016-10-11 10:01:07,803 INFO  - [main:] ~ Checking if table 
apache_atlas_entity_audit exists (HBaseBasedAuditRepository:249)
2016-10-11 10:01:07,816 INFO  - [main:] ~ Table apache_atlas_entity_audit 
exists (HBaseBasedAuditRepository:258)
2016-10-11 10:01:07,816 INFO  - [main:] ~ HA is not enabled, no need to start 
leader election service (ActiveInstanceElectorService:101)
2016-10-11 10:01:08,875 WARN  - 
[NIOServerCxn.Factory:dap241/10.43.182.241:9026:] ~ Exception causing close of 
session 0x0 due to java.io.IOException: ZooKeeperServer not running 
(NIOServerCnxn:362)
2016-10-11 10:01:10,139 WARN  - 
[NIOServerCxn.Factory:dap241/10.43.182.241:9026:] ~ Exception causing close of 
session 0x0 due to java.io.IOException: ZooKeeperServer not running 
(NIOServerCnxn:362)
2016-10-11 10:01:12,293 WARN  - 
[NIOServerCxn.Factory:dap241/10.43.182.241:9026:] ~ Exception causing close of 
session 0x0 due to java.io.IOException: ZooKeeperServer not running 
(NIOServerCnxn:362)
2016-10-11 10:01:14,756 FATAL - [main:] ~ Fatal error during KafkaServer 
startup. Prepare to shutdown (Logging$class:116)
org.I0Itec.zkclient.exception.ZkTimeoutException: Unable to connect to 
zookeeper server within timeout: 500
at org.I0Itec.zkclient.ZkClient.connect(ZkClient.java:1232)
at org.I0Itec.zkclient.ZkClient.(ZkClient.java:156)
at org.I0Itec.zkclient.ZkClient.(ZkClient.java:130)
at kafka.utils.ZkUtils$.createZkClientAndConnection(ZkUtils.scala:75)
at kafka.utils.ZkUtils$.apply(ZkUtils.scala:57)
at kafka.server.KafkaServer.initZk(KafkaServer.scala:294)
at kafka.server.KafkaServer.startup(KafkaServer.scala:180)
at 
org.apache.atlas.kafka.KafkaNotification.startKafka(KafkaNotification.java:352)
at 
org.apache.atlas.kafka.KafkaNotification.start(KafkaNotification.java:145)
at org.apache.atlas.service.Services.start(Services.java:45)
at 
org.apache.atlas.web.listeners.GuiceServletConfig.startServices(GuiceServletConfig.java:142)
at 
org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:136)
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(ServletContextHan