[jira] [Commented] (ATLAS-1875) Gremlin id is no longer returned for vertices in gremlin query

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-1875:
---

GitHub user cmar81 opened a pull request:

https://github.com/apache/incubator-atlas/pull/36

[ATLAS-1875] Adding the gremlin id for a vertex back into the search …

…result for a gremlin search. This functionality was present in Atlas 0.7 
but disappeared when an abstraction layer was introduced

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cmar81/incubator-atlas master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/36.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #36


commit 485775868dae4afb1a27fe9f0c2c5bb4074a0d93
Author: Christian Rieck 
Date:   2017-06-16T08:45:22Z

[ATLAS-1875] Adding the gremlin id for a vertex back into the search result 
for a gremlin search. This functionality was present in Atlas 0.7 but 
disappeared when an abstraction layer was introduced




> Gremlin id is no longer returned for vertices in gremlin query
> --
>
> Key: ATLAS-1875
> URL: https://issues.apache.org/jira/browse/ATLAS-1875
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk, 0.8-incubating
>Reporter: Christian R
>  Labels: dsl, gremlin
>
> Hi, 
> while investigating a move from atlas 0.7 to 0.8 (HDP 2.5 to HDP2.6) our 
> tests fail on gremlin queries. It turns out that the returned entities in a 
> gremlin search in 0.8 does not include the 'id' attribute. 
> I've built commit a0bd93945cd45457bbf34a8cb819d4fa4ba72964 (0.8-rc1) on linux 
> using berkely and elasticearch to test with. 
> The query 
> :21000/api/atlas/discovery/search/gremlin?g.V.has('__type.name', 
> 'Infrastructure').collect()
> on our 0.7 cluster gives
> {code:json}
> {
> __type.name: "Infrastructure",
> __type.category: "CLASS",
> __type: "typeSystem",
> id: "16640"
> }{code}
> while the same query on my 0.8-rc1 installation gives 
> {code:javascript}
> {
> __type.name: "Infrastructure",
> __version: "1",
> __type.category: "CLASS",
> __type.version: "1.0",
> __modificationTimestamp: "1497448424134",
> __type: "typeSystem",
> __type.options: "null",
> __type.description: "Infrastructure",
> __guid: "77d07283-7622-4305-9c0c-09ac5aee86c8",
> __timestamp: "1497448424134"
> }
> {code}
> Certainly more information, but id is missing. 
> The very poor DSL performance (see  ATLAS-1868) and a need for advanced 
> queries led us to base our queries on gremlin. This has worked very well so 
> far. We include both edges and nodes in the result set and use the inVertex, 
> outVertex and label info on the edges to rebuild our tree on the client side.
> I also see that gremlin has disappeared from version two of the API. Since 
> addE and addV lets you insert into the graph I can see how exposing a full 
> gremlin endpoint might not be wanted. 
> As an example of the queries we run that I haven't been able to express in 
> the DSL is 
> {noformat}
> query = g.V.has('__guid','').copySplit(
>   _().out('track'), 
>   _().as('x')
>   .out('functions', 'component')
>   .loop('x'){true}{true}
>   .copySplit(
>   _(),
>   _().in('part_of'),
>   _().outE('functions', 
> 'component'),
>   _().inE('part_of')
>   )
>   .exhaustMerge.dedup
>   )
>   .exhaustMerge
> .collect()
> {noformat}
> this might not be a normal usecase. 
> edit to add: 
> I looked at GraphBackedDiscoveryService.java and notice that:
> 0.7:
> {code:java}
> else if (r instanceof TitanVertex) {
> Iterable ps = ((TitanVertex) 
> r).getProperties();
> for (TitanProperty tP : ps) {
> String pName = tP.getPropertyKey().getName();
> Object pValue = ((TitanVertex) r).getProperty(pName);
> if (pValue != null) {
> oRow.put(pName, pValue.toString());
> }
> }
> {code}
> Vs 0.8 code: 
> {code:java}
> else if (value instanceof AtlasVertex) {
> AtlasVertex vertex = (AtlasVertex)value;
> for 

[jira] [Commented] (ATLAS-1826) UI Create Entity : Type doesn't list the inverseRef constrained attribute options when name length is less than 3.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-1826:
---

GitHub user qinglin opened a pull request:

https://github.com/apache/incubator-atlas/pull/31

fix-ATLAS-1826



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/qinglin/incubator-atlas fix-ATLAS-1826

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/31.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #31


commit 1390ae3a29f37087c5293cc7cd08ecb69524bb3c
Author: qinglin,xia 
Date:   2017-06-06T09:54:07Z

fix-ATLAS-1826




> UI Create Entity : Type doesn't list the inverseRef constrained attribute 
> options when name length is less than 3.
> --
>
> Key: ATLAS-1826
> URL: https://issues.apache.org/jira/browse/ATLAS-1826
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: qinglin,xia
> Fix For: 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1826.patch, fix-ATLAS-1826.png
>
>
> 1. Created a hbase_table h1.
> 2. Tried to create a hbase_column_family with hbase table as h1. Since "h1" 
> has only 2 characters , the drop down didn't display "h1" but displayed 
> "Please enter 1 or more characters".
> 3. When hbase_table name length is more than 2 , the drop down lists the name.
> Same happens when adding hbase_column_family with name "hf" to hbase_column.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1781) Atlas UI cannot show lineage pic when inputs and outputs of lineage are the same entity

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-1781:
---

GitHub user developersLxz opened a pull request:

https://github.com/apache/incubator-atlas/pull/30

fix ATLAS-1781

fix https://issues.apache.org/jira/browse/ATLAS-1781

work with qinglin,xia  

Thanks :)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/developersLxz/incubator-atlas fix-ATLAS-1781

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/30.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #30


commit 506e3623e4ae12ba3679b1bff6a30131c295acaa
Author: Linzs <850589...@qq.com>
Date:   2017-06-04T10:54:53Z

fix ATLAS-1781




> Atlas UI cannot show lineage pic when inputs and outputs of lineage are the 
> same entity
> ---
>
> Key: ATLAS-1781
> URL: https://issues.apache.org/jira/browse/ATLAS-1781
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: trunk, 0.7-incubating, 0.8-incubating, 0.7.1-incubating, 
> 0.9-incubating
>Reporter: qinglin,xia
>Assignee: Xinzhi,Luo
> Attachments: browser_error.png, 
> Lineage_Create_Successfully_when_inputs_outputs_different.png, 
> Lineage_keep_loading.png
>
>
> I was working with the lineage for hbase, when I added a column family in a 
> hbase table, I want to create a lineage for the table to show there is a 
> change within the table schema, yet when I create a process using the atlas 
> api, I found that the process entity is successfully created, but the lineage 
> is not shown on the atlas web page.
> Steps to Reproduce this issue is: 
> 1. build up an entity extends the DataSet Type
> 2. build up a lineage Process
> 3. set the process input and output to the same entity
> The code is like:
> Referenceable table1 = 
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME, 
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, input_table_name);
> Referenceable table2 = 
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME, 
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, output_table_name);
> HBaseProcess process = new HBaseProcess("process");
> process.setInput(table1.getId());
> process.setoutput(table2.getId());
> here I set the input_table_name and output_table_name the same string name, 
> when I set them different values, the lineage pic can be shown for table1 and 
> table2 successfully
> Screenshots are:
> 1) The lineage pic keep loading on the atlas UI 
> 2) The error log reported by the browser console
> 3) The lineage pic showed successfully when set the inputs and outputs of the 
> lineage to different entities.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1824) Cannot create hive lineage when using query "insert into table X select A.Y, B.Z from A,B"

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-1824:
---

GitHub user developersLxz opened a pull request:

https://github.com/apache/incubator-atlas/pull/29

fix ATLAS-1824

fix bug  
https://issues.apache.org/jira/browse/ATLAS-1824

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/developersLxz/incubator-atlas fix-ATLAS-1824

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/29.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #29


commit 30fc8ebe28b5d2c5d3c747ffcdd59ba0a0c938b4
Author: Linzs <850589...@qq.com>
Date:   2017-05-31T02:11:27Z

fix ATLAS-1824




> Cannot create hive lineage when using query "insert into table X select A.Y, 
> B.Z from A,B"
> --
>
> Key: ATLAS-1824
> URL: https://issues.apache.org/jira/browse/ATLAS-1824
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.7-incubating, 0.8-incubating, 0.7.1-incubating, 
> 0.9-incubating, 0.8.1-incubating
>Reporter: qinglin,xia
>  Labels: atlas
> Attachments: 0001-fix-ATLAS-1824.patch, 
> failed_lineage_input_output.png, failed_lineage.png
>
>
> Problem: 
> I am using atlas to create hive lineage, I found that when using the hive 
> query "insert into table A select B.name ,C.name from B, C", the lineage 
> between A, B and C cannot be created. 
> Steps to reproduce: 
> 1. log in to the hive shell
> 2. create hive table a, b,c and insert into data into a,b and c
> 3. using query "insert into table datalake_demo.d9 select a.id as key, a.id, 
> a.aname ,b.bname,c.cname from datalake_demo.a,datalake_demo.b,datalake_demo.c 
> where a.id = b.id and b.id = c.id" to create hive table d9
> Expected Result:
> hive_process is created , input of the process is a, b, c, output of the 
> process is datalake_demo.d9, and the process could be shown on atlas UI
> Actual Result: 
> hive_process is created, input of the process is a, b, b, d9, output of the 
> process is null, and the process could not be shown on atlas UI, according to 
> the attached pic "failed_lineage.png" and "failed_lineage_input_output.png"
> PS: We are working on fixing the issue!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1804) Allow PAM for authentication

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-1804:
---

GitHub user Wancy opened a pull request:

https://github.com/apache/incubator-atlas/pull/28

ATLAS-1804:Allow PAM for authentication

This patch added a new param atlas.authentication.method.pam to configure 
atlas login using pam authentication. 
The pam module name could be configured by setting the value of 
atlas.authentication.method.pam.service, without explicitly setting the name, 
it will call it "atlas-login" by default.
User can custom the pam module content under /etc/pam.d/atlas-login.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Wancy/incubator-atlas master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/28.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #28


commit 8ae01c91fa42b56a261a2ba19ea521fd253c1c4b
Author: shiwang 
Date:   2017-05-22T23:19:46Z

ATLAS-1804:Allow PAM for authentication




> Allow PAM for authentication
> 
>
> Key: ATLAS-1804
> URL: https://issues.apache.org/jira/browse/ATLAS-1804
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Shi Wang
>Assignee: Shi Wang
>
> Atlas currently support File, Kerberos and Ldap authentication. An 
> improvement feature will be adding PAM as another authentication type. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1341) Fix name of Credential Provider utility in documentation

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-1341:
---

GitHub user yogeshtewari opened a pull request:

https://github.com/apache/incubator-atlas/pull/27

ATLAS-1341: In Atlas security documentation page, Updated file cputil…

… (extension of Credential Provider Utility Script) from .sh to .py

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yogeshtewari/incubator-atlas ATLAS-1341

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/27.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #27


commit 430bbcf2945ccc27bb2f9953099657229f259a7d
Author: Yogesh Tewari 
Date:   2017-04-01T15:04:14Z

ATLAS-1341: In Atlas security documentation page, Updated file cputil 
(extension of Credential Provider Utility Script) from .sh to .py




> Fix name of Credential Provider utility in documentation
> 
>
> Key: ATLAS-1341
> URL: https://issues.apache.org/jira/browse/ATLAS-1341
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Vipin Rathor
>Priority: Trivial
>  Labels: docuentation
>
> At Atlas security page [here|http://atlas.apache.org/Security.html] & in the 
> section "Credential Provider Utility Script", the name of Credential Provider 
> utility is given incorrectly as "./cputil.sh".
> This should actually be "./cputil.py".



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-835) Falcon Integration with Atlas

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-835:
--

GitHub user sowmyaramesh opened a pull request:

https://github.com/apache/incubator-atlas/pull/26

ATLAS-835: Falcon Integration with Atlas



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sowmyaramesh/incubator-atlas ATLAS-835

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/26.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #26


commit 6b31a442c89f0f00b4836bfcd521667d378d8338
Author: Sowmya Ramesh 
Date:   2016-04-05T23:25:12Z

Atlas Falcon Integration

commit f0074948a3baffc795c4b9b91330a619361911ac
Author: Sowmya Ramesh 
Date:   2016-04-20T21:01:53Z

Merge remote-tracking branch 'upstream/master'

commit 85b3837a3417c95833d7b52fe3bbc28c7fc4e38c
Author: Sowmya Ramesh 
Date:   2016-05-03T22:25:54Z

Merge remote-tracking branch 'upstream/master'

commit 7971770bf662bd3b31a3142e00b71c754485e68b
Author: Sowmya Ramesh 
Date:   2016-05-18T22:56:00Z

Merged master fixed conflict.

commit f049dc858451636aaa46cbba638c6e7dbec996be
Author: Sowmya Ramesh 
Date:   2016-05-24T00:06:18Z

Merge remote-tracking branch 'upstream/master'

commit 5c5612205f579e5ed42fe00658f00379515b62cc
Author: Sowmya Ramesh 
Date:   2016-05-24T00:43:52Z

Falcon Integration with altest Atlas

commit b9aeb07d8221ec26717298104861d90a867b68cb
Author: Sowmya Ramesh 
Date:   2016-05-27T19:43:24Z

Merge remote-tracking branch 'upstream/master'

commit d1c4bdbf6024ce45e4cfa42081198e93f4b85158
Author: Sowmya Ramesh 
Date:   2016-05-27T19:56:57Z

ATLAS-835: Falcon Integration with Atlas




> Falcon Integration with Atlas
> -
>
> Key: ATLAS-835
> URL: https://issues.apache.org/jira/browse/ATLAS-835
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sowmya Ramesh
>Assignee: Sowmya Ramesh
> Fix For: trunk
>
>
> Currently only Falcon process registration is supported in Atlas. Extend this 
> to support Falcon feed, replication feed, cluster entity addition and updates.
> Here are the types to be defined:
> {noformat}
> falcon_cluster - models falcon cluster
> falcon_feed - extends Dataset - models falcon feed
> falcon_process - extends Process - models falcon process with inputs and 
> outputs as falcon_feed
> falcon_feed_creation - extends Process - input as hive_table or hdfs_path, 
> output as falcon_feed
> falcon_replication - extends Process - input as falcon_feed in source 
> cluster, output as falcon_feed in target cluster
> {noformat}



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

[jira] [Commented] (ATLAS-651) Add a atlas_status.py script

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-651:
--

GitHub user jbonofre opened a pull request:

https://github.com/apache/incubator-atlas/pull/25

[ATLAS-651] Add atlas_status.py script

Add atlas_status.py script

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jbonofre/incubator-atlas SPARK-651

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/25.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #25


commit 90db0e28e748344807d9822d6936f7ff161d81f2
Author: Jean-Baptiste Onofré 
Date:   2016-04-07T15:28:15Z

[ATLAS-651] Add atlas_status.py script




> Add a atlas_status.py script
> 
>
> Key: ATLAS-651
> URL: https://issues.apache.org/jira/browse/ATLAS-651
> Project: Atlas
>  Issue Type: Wish
>Reporter: Jean-Baptiste Onofré
>Priority: Minor
>
> In order to check if Atlas server is running, we could add a 
> bin/atlas_status.py.



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

[jira] [Commented] (ATLAS-650) Use Apache logo on the webapp

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-650:
--

GitHub user jbonofre opened a pull request:

https://github.com/apache/incubator-atlas/pull/24

[ATLAS-650] Use Apache small logo on the Atlas webapp

Replace hortonworks default logo by Apache logo in the Atlas webapp.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jbonofre/incubator-atlas ATLAS-650

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/24.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #24


commit f572ee357d87db62ea380a3dcea259f53e30a739
Author: Jean-Baptiste Onofré 
Date:   2016-04-07T12:28:00Z

[ATLAS-650] Use Apache small logo on the Atlas webapp




> Use Apache logo on the webapp
> -
>
> Key: ATLAS-650
> URL: https://issues.apache.org/jira/browse/ATLAS-650
> Project: Atlas
>  Issue Type: Wish
>Reporter: Jean-Baptiste Onofré
>Priority: Trivial
>
> My Apache member small heart would love to see the Apache logo on the Atlas 
> webapp ;)



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

[jira] [Commented] (ATLAS-421) typo in Architecture.twiki

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-421:
--

Github user dbist closed the pull request at:

https://github.com/apache/incubator-atlas/pull/22


> typo in Architecture.twiki
> --
>
> Key: ATLAS-421
> URL: https://issues.apache.org/jira/browse/ATLAS-421
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: trunk
> Environment: docs
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
>  Labels: starter
> Fix For: trunk
>
> Attachments: ATLAS-22.patch
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> typo on main page in the bridges section. Says "any failure in APIs because 
> of network issue etc can in result" and should be "any failure in APIs 
> because of network issue etc can result in".



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

[jira] [Commented] (ATLAS-136) Add trait API to org.apache.atlas.AtlasClient

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-136:
--

GitHub user rishabhbhardwaj opened a pull request:

https://github.com/apache/incubator-atlas/pull/20

ATLAS-136 Add trait API to org.apache.atlas.AtlasClient

Added the following trait API methods in AtlasClient
createTrait
addTrait
deleteTrait

I have tested the methods and they are working fine.
Kindly review the changes.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rishabhbhardwaj/incubator-atlas master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/20.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #20


commit fd23d4c998b1714a85479034c90b2d324b84ee81
Author: Rishabh Bhardwaj 
Date:   2015-10-13T13:06:14Z

Atlas-201 Renamed org.apache.atlas.Main to org.apache.atlas.Atlas.

commit 66fe404120a48a4af25b6aa4b1081b7c0f8cd155
Author: Rishabh Bhardwaj 
Date:   2015-10-15T06:07:40Z

Merge remote-tracking branch 'upstream/master'

commit 715401ae4d34e922753fc3356bd52ae04a2d875c
Author: Rishabh Bhardwaj 
Date:   2015-10-21T17:36:49Z

Merge remote-tracking branch 'upstream/master'

commit 071425baa7bab1c8d34e45cddad6df5357b91b57
Author: Rishabh Bhardwaj 
Date:   2015-10-26T06:06:17Z

Merge remote-tracking branch 'upstream/master'

commit a27fb7af29beafebcca8e1596a7ce4978badf8d2
Author: Rishabh Bhardwaj 
Date:   2015-10-28T10:36:54Z

Merge remote-tracking branch 'upstream/master'

commit aac3f83d9ee255e24fe92b56532772358b69d135
Author: Rishabh Bhardwaj 
Date:   2015-10-29T07:55:12Z

Merge remote-tracking branch 'upstream/master'

commit c31d5ed98a80b369c7855a65d9411a37637247cd
Author: Rishabh Bhardwaj 
Date:   2015-10-29T07:57:26Z

ATLAS-136 Add trait API to org.apache.atlas.AtlasClient




> Add trait API to org.apache.atlas.AtlasClient
> -
>
> Key: ATLAS-136
> URL: https://issues.apache.org/jira/browse/ATLAS-136
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Vladimir Antonevich`
> Fix For: 0.6-incubating
>
> Attachments: atlas.client.patch
>
>
> API to manipulate entity traits must be added to 
> org.apache.atlas.AtlasClient. These should include methods to add/remove a 
> trait POST/DELETE to /api/atlas/entities/{guid}/traits[/traitName], as 
> supported by exposed entities resource



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

[jira] [Commented] (ATLAS-201) Rename org.apache.atlas.Main to org.apache.atlas.Atlas

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-201:
--

Github user rishabhbhardwaj closed the pull request at:

https://github.com/apache/incubator-atlas/pull/15


> Rename org.apache.atlas.Main to org.apache.atlas.Atlas
> --
>
> Key: ATLAS-201
> URL: https://issues.apache.org/jira/browse/ATLAS-201
> Project: Atlas
>  Issue Type: Task
>Reporter: Shwetha G S
>Assignee: Rishabh Bhardwaj
>Priority: Minor
> Fix For: trunk
>
> Attachments: ATLAS-201-v2.patch, ATLAS-201.patch
>
>
> Rename org.apache.atlas.Main to org.apache.atlas.Atlas so that jps command 
> shows process running as Atlas



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

[jira] [Commented] (ATLAS-138) Combine Input/Output graph

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-138:
--

GitHub user AnilGayakwad opened a pull request:

https://github.com/apache/incubator-atlas/pull/12

[ATLAS-138 - HDPDGI-142] Combine Input/Output lineage graph



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MPR-Global/incubator-atlas HDPDGI-142

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/12.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #12


commit e5830233c95e2e859ed1fd62de82102c87633374
Author: DarshanKumar 
Date:   2015-09-12T06:15:00Z

[ATLAS-155,HDPDGI-154]- resolved merge conflict - image does not show up on 
dashboard

commit 3106ec6faadb42310f55ad40a18cd8a2d107824d
Author: babanb 
Date:   2015-09-13T02:37:15Z

[ATLAS-138 - HDPDGI-142]-- Combine Input/Output lineage  graph




> Combine Input/Output graph
> --
>
> Key: ATLAS-138
> URL: https://issues.apache.org/jira/browse/ATLAS-138
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.6-incubating
>Reporter: baban
>
> Combine the i/p and o/p graph so that there is only lineage graph. 



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

[jira] [Commented] (ATLAS-155) Images do not show up on the dashboard

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-155:
--

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-atlas/pull/9


> Images do not show up on the dashboard
> --
>
> Key: ATLAS-155
> URL: https://issues.apache.org/jira/browse/ATLAS-155
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Venkatesh Seetharam
>Assignee: Darshan Kumar
>Priority: Critical
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-155-v0.patch
>
>
> Post ATLAS-90 and ATLAS-109, the images do not show up, was not moved from v2 
> folder. I forced deleted v2 folder.



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

[jira] [Commented] (ATLAS-132) Search Controller Optimization

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-132:
--

Github user AnilGayakwad closed the pull request at:

https://github.com/apache/incubator-atlas/pull/11


> Search Controller Optimization
> --
>
> Key: ATLAS-132
> URL: https://issues.apache.org/jira/browse/ATLAS-132
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.5.1-incubating
>Reporter: Erik Bergenholtz
>Assignee: Rohit
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-132-v0.patch
>
>
> Search Controller currently makes multiple calls. This can and should be 
> optimized as a single API call.



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

[jira] [Commented] (ATLAS-156) Login Screen

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-156:
--

GitHub user AnilGayakwad opened a pull request:

https://github.com/apache/incubator-atlas/pull/10

[ATLAS-156, HDPDGI-88_1] Login Screen



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MPR-Global/incubator-atlas HDPDGI-88_1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/10.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #10


commit e5830233c95e2e859ed1fd62de82102c87633374
Author: DarshanKumar 
Date:   2015-09-12T06:15:00Z

[ATLAS-155,HDPDGI-154]- resolved merge conflict - image does not show up on 
dashboard

commit 6cd91bcdc9080065b424c5ea12e2f6ba1c9e4f1b
Author: Vishal Kadam 
Date:   2015-09-13T03:33:46Z

[ATLAS-156,HDPDGI-88_1] Login Screen




> Login Screen
> 
>
> Key: ATLAS-156
> URL: https://issues.apache.org/jira/browse/ATLAS-156
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.6-incubating
>Reporter: Anilsg
> Fix For: 0.6-incubating
>
>
> Login Screen



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

[jira] [Commented] (ATLAS-132) Search Controller Optimization

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-132:
--

GitHub user AnilGayakwad opened a pull request:

https://github.com/apache/incubator-atlas/pull/11

[ATLAS-132, HDPDGI-125] - Search Controller Optimization



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MPR-Global/incubator-atlas HDPDGI-125_1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/11.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #11


commit 1a458eecac69cc443383dc2c9f856b925481090d
Author: Anilsg 
Date:   2015-09-13T16:00:24Z

[ATLAS-132, HDPDGI-125] - Search Controller Optimization




> Search Controller Optimization
> --
>
> Key: ATLAS-132
> URL: https://issues.apache.org/jira/browse/ATLAS-132
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.5.1-incubating
>Reporter: Erik Bergenholtz
>Assignee: Rohit
> Fix For: 0.6-incubating
>
>
> Search Controller currently makes multiple calls. This can and should be 
> optimized as a single API call.



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

[jira] [Commented] (ATLAS-155) Images do not show up on the dashboard

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-155:
--

GitHub user DarshanKumar89 opened a pull request:

https://github.com/apache/incubator-atlas/pull/9

[ATLAS-155,HDPDGI-154]- resolved merge conflict - image does not show up on 
dashboard

[ATLAS-155,HDPDGI-154]- resolved merge conflict - image does not show up on 
dashboard

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MPR-Global/incubator-atlas master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/9.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #9


commit e5830233c95e2e859ed1fd62de82102c87633374
Author: DarshanKumar 
Date:   2015-09-12T06:15:00Z

[ATLAS-155,HDPDGI-154]- resolved merge conflict - image does not show up on 
dashboard




> Images do not show up on the dashboard
> --
>
> Key: ATLAS-155
> URL: https://issues.apache.org/jira/browse/ATLAS-155
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Venkatesh Seetharam
>Assignee: darshan kumar
>Priority: Critical
> Fix For: 0.6-incubating
>
>
> Post ATLAS-90 and ATLAS-109, the images do not show up, was not moved from v2 
> folder. I forced deleted v2 folder.



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

[jira] [Commented] (ATLAS-90) Support offline builds

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14717942#comment-14717942
 ] 

ASF GitHub Bot commented on ATLAS-90:
-

Github user vkadam commented on a diff in the pull request:

https://github.com/apache/incubator-atlas/pull/6#discussion_r38167128
  
--- Diff: dashboard/v2/.bowerrc ---
@@ -1,5 +1,5 @@
 {
-  directory: dist/lib,
+  directory: public/lib,
--- End diff --

Why it should be in target? Its required runtime and not only compile time 
like java classes. While creation of war dist folder gets added to it. Dist 
folder is create from public folder with minified files.
If we move it to target folder then every mvn clean it will get deleted and 
which will need bower to download it again. Which defeats the purpose of whole 
offline build support.


 Support offline builds
 --

 Key: ATLAS-90
 URL: https://issues.apache.org/jira/browse/ATLAS-90
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S
Assignee: Vishal Kadam
Priority: Minor
 Fix For: 0.6-incubating

 Attachments: 6.patch.txt, ATLAS-90.patch


 Currently, frontend-maven-plugin doesn't work without internet. Can we use 
 https://github.com/allegro/grunt-maven-plugin to support offline builds?



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

[jira] [Commented] (ATLAS-90) Support offline builds

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14710533#comment-14710533
 ] 

ASF GitHub Bot commented on ATLAS-90:
-

Github user sumashivaprasad commented on a diff in the pull request:

https://github.com/apache/incubator-atlas/pull/6#discussion_r37830439
  
--- Diff: pom.xml ---
@@ -1248,7 +1248,14 @@
 artifactIdbuildnumber-maven-plugin/artifactId
 version1.0/version
 /plugin
-
+   plugin
--- End diff --

correct indentation


 Support offline builds
 --

 Key: ATLAS-90
 URL: https://issues.apache.org/jira/browse/ATLAS-90
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S
Priority: Minor
 Fix For: 0.6-incubating

 Attachments: 6.patch.txt


 Currently, frontend-maven-plugin doesn't work without internet. Can we use 
 https://github.com/allegro/grunt-maven-plugin to support offline builds?



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

[jira] [Commented] (ATLAS-90) Support offline builds

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14706198#comment-14706198
 ] 

ASF GitHub Bot commented on ATLAS-90:
-

Github user vkadam closed the pull request at:

https://github.com/apache/incubator-atlas/pull/5


 Support offline builds
 --

 Key: ATLAS-90
 URL: https://issues.apache.org/jira/browse/ATLAS-90
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S
Priority: Minor
 Fix For: 0.6-incubating

 Attachments: 5.patch.txt


 Currently, frontend-maven-plugin doesn't work without internet. Can we use 
 https://github.com/allegro/grunt-maven-plugin to support offline builds?



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

[jira] [Commented] (ATLAS-90) Support offline builds

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14704231#comment-14704231
 ] 

ASF GitHub Bot commented on ATLAS-90:
-

GitHub user vkadam opened a pull request:

https://github.com/apache/incubator-atlas/pull/5

[ATLAS-90] Added profiles to support offline build

MPR jira ticket number HDPDGI-126, support for offline build

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MPR-Global/incubator-atlas master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/5.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5


commit 29c05b2ccc08ef09fffe4a0824047a352bd91a24
Author: Sanjay Patel sanj...@mprglobalsolutions.com
Date:   2015-08-05T02:03:03Z

[HDPDGI-126, ATLAS-90] Added profiles to support offline build

commit 7ad33bd0effc13fbc64dd7ca54df90998cbca726
Author: Vishal Kadam vishal.4ka...@gmail.com
Date:   2015-08-20T03:17:51Z

Merge pull request #5 from MPR-Global/HDPDGI-126

[HDPDGI-126, ATLAS-90] Added profiles to support offline build




 Support offline builds
 --

 Key: ATLAS-90
 URL: https://issues.apache.org/jira/browse/ATLAS-90
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S
Priority: Minor

 Currently, frontend-maven-plugin doesn't work without internet. Can we use 
 https://github.com/allegro/grunt-maven-plugin to support offline builds?



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