[jira] [Assigned] (ATLAS-540) API to retrieve entity version events

[Shwetha G S (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shwetha G S reassigned ATLAS-540:
-

Assignee: Shwetha G S

> API to retrieve entity version events
> -
>
> Key: ATLAS-540
> URL: https://issues.apache.org/jira/browse/ATLAS-540
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
>
> We will need an API that will take entity id as input and returns the events 
> in the decreasing order of timestamp. The API should return n events and 
> return the timestamp of the next event



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

[jira] [Created] (ATLAS-584) Integrate CSRF prevention filter

[Erik Bergenholtz (JIRA)]

Erik Bergenholtz created ATLAS-584:
--

 Summary: Integrate CSRF prevention filter
 Key: ATLAS-584
 URL: https://issues.apache.org/jira/browse/ATLAS-584
 Project: Atlas
  Issue Type: Task
Affects Versions: 0.7-incubating
Reporter: Erik Bergenholtz
 Fix For: 0.7-incubating


Atlas needs to provide protection for CSRF protection.



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

[jira] [Updated] (ATLAS-535) Support delete cascade efficiently

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad updated ATLAS-535:
---
Summary: Support delete cascade efficiently  (was: Support delete cascade 
efficently)

> Support delete cascade efficiently
> --
>
> Key: ATLAS-535
> URL: https://issues.apache.org/jira/browse/ATLAS-535
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Suma Shivaprasad
> Fix For: 0.7-incubating
>
>
> Currently there are some limitation in the typesystem and modelling to 
> support delete cascades at scale through the isComposite flag



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

[jira] [Updated] (ATLAS-553) Entity mutation - Fix issue with reordering of elements in array with composite references

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad updated ATLAS-553:
---
Summary: Entity mutation - Fix issue with reordering of elements in 
array with composite references  (was: Entity mutation - Fix issue with 
reordering of elements in array)

> Entity mutation - Fix issue with reordering of elements in array with 
> composite references
> -
>
> Key: ATLAS-553
> URL: https://issues.apache.org/jira/browse/ATLAS-553
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-553.1.patch, ATLAS-553.patch
>
>
> Currently, if theres an update on the entity to the order of elements in an 
> array/aray etc, it is not handled correctly since entity 
> mutation logic thinks that the element is deleted resulting in a deleted 
> vertex being referred later causing entity mutation to fail.



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

[jira] [Updated] (ATLAS-528) support drop table, view

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad updated ATLAS-528:
---
Description: 
Drop table and view requires soft deletes. The reason is whenever a table is 
dropped , it also may have an associated lineage which consists of a 
hive_process which N input tables and an output table. If the table is dropped, 
the lineage edge is also dropped resulting in incorrect lineage history. 

With soft deletes, the expected behaviour is to changes the table status to 
"deleted" and when the table is recreated through a create table statement, 
then create another vertex/entity for that table with the new state. Also,  the 
lineage for this newly recreated table should be a new hive_process and should 
not reuse the existing entity/vertex even though the hive statement for that 
process is the same.

  was:Drop table and view requires soft deletes. The reason is whenever a table 
is dropped , it also may have an associated lineage which consists of a 
hive_process which N input tables and an output table. If the table is dropped, 
the lineage edge is also dropped resulting in incorrect lineage history


> support drop table, view
> 
>
> Key: ATLAS-528
> URL: https://issues.apache.org/jira/browse/ATLAS-528
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Suma Shivaprasad
> Fix For: 0.7-incubating
>
>
> Drop table and view requires soft deletes. The reason is whenever a table is 
> dropped , it also may have an associated lineage which consists of a 
> hive_process which N input tables and an output table. If the table is 
> dropped, the lineage edge is also dropped resulting in incorrect lineage 
> history. 
> With soft deletes, the expected behaviour is to changes the table status to 
> "deleted" and when the table is recreated through a create table statement, 
> then create another vertex/entity for that table with the new state. Also,  
> the lineage for this newly recreated table should be a new hive_process and 
> should not reuse the existing entity/vertex even though the hive statement 
> for that process is the same.



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

[jira] [Updated] (ATLAS-528) support drop table, view

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad updated ATLAS-528:
---
Description: Drop table and view requires soft deletes. The reason is 
whenever a table is dropped , it also may have an associated lineage which 
consists of a hive_process which N input tables and an output table. If the 
table is dropped, the lineage edge is also dropped resulting in incorrect 
lineage history

> support drop table, view
> 
>
> Key: ATLAS-528
> URL: https://issues.apache.org/jira/browse/ATLAS-528
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Suma Shivaprasad
> Fix For: 0.7-incubating
>
>
> Drop table and view requires soft deletes. The reason is whenever a table is 
> dropped , it also may have an associated lineage which consists of a 
> hive_process which N input tables and an output table. If the table is 
> dropped, the lineage edge is also dropped resulting in incorrect lineage 
> history



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

[jira] [Resolved] (ATLAS-534) Verify free text search is able to surface search on table parameters

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad resolved ATLAS-534.

Resolution: Won't Fix
  Assignee: Suma Shivaprasad

Was able to verify that free text search is able to surface any parameters 
stored in the table/db parameters

> Verify free text search is able to surface search on table parameters
> -
>
> Key: ATLAS-534
> URL: https://issues.apache.org/jira/browse/ATLAS-534
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.7-incubating
>
>




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

[jira] [Created] (ATLAS-583) Rename table should retain traits/tags assigned to columns

[Suma Shivaprasad (JIRA)]

Suma Shivaprasad created ATLAS-583:
--

 Summary: Rename table should retain traits/tags assigned to columns
 Key: ATLAS-583
 URL: https://issues.apache.org/jira/browse/ATLAS-583
 Project: Atlas
  Issue Type: Sub-task
Reporter: Suma Shivaprasad


Currently rename changes the column qualifiedName in the renamed table 
resulting in the columns getting deleted and therefore the traits attached to 
these will also get deleted. We need to ensure  they are retained by ensuring 
columns are renamed first to the new qualified name and then table is renamed 
in the repository



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

[jira] [Resolved] (ATLAS-531) Remove isComposite on storageDescriptor.cols

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad resolved ATLAS-531.

Resolution: Fixed
  Assignee: Suma Shivaprasad

This is not required currently since the concerned attribute  has been removed 
from the model

> Remove isComposite on storageDescriptor.cols
> 
>
> Key: ATLAS-531
> URL: https://issues.apache.org/jira/browse/ATLAS-531
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.7-incubating
>
>
> This is causing issues since Table.cols and storageDesc.cols have isComposite 
> attributes and try to control the lifecycle causing issues



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

[jira] [Updated] (ATLAS-568) Parallelize Hive hook operations

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad updated ATLAS-568:
---
Description: 
Maintaining the same order of operations that were executed in hive is crucial 
also on top of ATLAS . This is because if they are not ordered, it could easily 
lead to correctness issues in the ATLAS repository. For eg: Table columns being 
dropped and then table is renamed , dropping tables, databases etc all need to 
be executed in the same order as they were in hive metastore. There are 
multiple issues that needs to be addressed here

1. How do we ensure order of messages on the producer/hook side?
2. Once producer/hook publishes these messages onto KAFKA, how do we ensure the 
order of processing is the same as it was published.

One suggested approach is to assign a timestamp to all the messages on the 
producer side and have a window/batch these messages on the consumer/ATLAS 
server side. 



  was:
Maintaining the same order of operations that were executed in hive is crucial 
also on top of ATLAS . This is because if they are not ordered, it could easily 
lead to correctness issues in the ATLAS repository. For eg: Table columns being 
dropped and then table is renamed , dropping tables, databases etc all need to 
be executed in the same order as they were in hive metastore. There are 
multiple issues that needs to be addressed here

1. How do we ensure order of messages on the producer/hook side?
2. Once producer/hook publishes these messages onto KAFKA, how do we ensure the 
order of processing is the same as it was published.

One suggested approach is to assign a timestamp to all the messages on the 
producer side and have a window/batch these messages on the consumer/ATLAS 
server side. Order these messages according to the timestamp within the window 
which is a configured time period and then execute these operations in that 
order.




>  Parallelize Hive hook operations
> -
>
> Key: ATLAS-568
> URL: https://issues.apache.org/jira/browse/ATLAS-568
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
> Fix For: 0.7-incubating
>
>
> Maintaining the same order of operations that were executed in hive is 
> crucial also on top of ATLAS . This is because if they are not ordered, it 
> could easily lead to correctness issues in the ATLAS repository. For eg: 
> Table columns being dropped and then table is renamed , dropping tables, 
> databases etc all need to be executed in the same order as they were in hive 
> metastore. There are multiple issues that needs to be addressed here
> 1. How do we ensure order of messages on the producer/hook side?
> 2. Once producer/hook publishes these messages onto KAFKA, how do we ensure 
> the order of processing is the same as it was published.
> One suggested approach is to assign a timestamp to all the messages on the 
> producer side and have a window/batch these messages on the consumer/ATLAS 
> server side. 



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

[jira] [Updated] (ATLAS-568) Parallelize Hive hook operations

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad updated ATLAS-568:
---
Description: 
Maintaining the same order of operations that were executed in hive is crucial 
also on top of ATLAS . This is because if they are not ordered, it could easily 
lead to correctness issues in the ATLAS repository. For eg: Table columns being 
dropped and then table is renamed , dropping tables, databases etc all need to 
be executed in the same order as they were in hive metastore. There are 
multiple issues that needs to be addressed here

1. How do we ensure order of messages on the producer/hook side?
2. Once producer/hook publishes these messages onto KAFKA, how do we ensure the 
order of processing is the same as it was published.

One suggested approach is to assign a timestamp to all the messages on the 
producer side and have a window/batch these messages on the consumer/ATLAS 
server side. Order these messages according to the timestamp within the window 
which is a configured time period and then execute these operations in that 
order.



  was:Currently, there are operations like rename which fire multiple messages 
to repository to accomplish the required task(create table by old name if it 
doesnt exist. This could lead to issues if there are multiple consumers running 
as kafka consumers since the order of messages could be executed in anyway in 
this case resulting in inconsistent behaviour.


>  Parallelize Hive hook operations
> -
>
> Key: ATLAS-568
> URL: https://issues.apache.org/jira/browse/ATLAS-568
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
> Fix For: 0.7-incubating
>
>
> Maintaining the same order of operations that were executed in hive is 
> crucial also on top of ATLAS . This is because if they are not ordered, it 
> could easily lead to correctness issues in the ATLAS repository. For eg: 
> Table columns being dropped and then table is renamed , dropping tables, 
> databases etc all need to be executed in the same order as they were in hive 
> metastore. There are multiple issues that needs to be addressed here
> 1. How do we ensure order of messages on the producer/hook side?
> 2. Once producer/hook publishes these messages onto KAFKA, how do we ensure 
> the order of processing is the same as it was published.
> One suggested approach is to assign a timestamp to all the messages on the 
> producer side and have a window/batch these messages on the consumer/ATLAS 
> server side. Order these messages according to the timestamp within the 
> window which is a configured time period and then execute these operations in 
> that order.



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

[jira] [Updated] (ATLAS-568) Parallelize Hive hook operations

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad updated ATLAS-568:
---
Summary:  Parallelize Hive hook operations  (was: Make hive hook 
multithreaded)

>  Parallelize Hive hook operations
> -
>
> Key: ATLAS-568
> URL: https://issues.apache.org/jira/browse/ATLAS-568
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
> Fix For: 0.7-incubating
>
>
> Currently, there are operations like rename which fire multiple messages to 
> repository to accomplish the required task(create table by old name if it 
> doesnt exist. This could lead to issues if there are multiple consumers 
> running as kafka consumers since the order of messages could be executed in 
> anyway in this case resulting in inconsistent behaviour.



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

[jira] [Commented] (ATLAS-575) jetty-maven-plugin fails with ShutdownMonitorThread already started

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-575:


+1

> jetty-maven-plugin fails with ShutdownMonitorThread already started
> ---
>
> Key: ATLAS-575
> URL: https://issues.apache.org/jira/browse/ATLAS-575
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-575-v2.patch, ATLAS-575.patch
>
>
> {noformat}
> [INFO] --- jetty-maven-plugin:9.2.12.v20150709:deploy-war (start-jetty) @ 
> falcon-bridge ---
> [INFO] Configuring Jetty for project: Apache Atlas Falcon Bridge
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Atlas UI  SUCCESS [01:04 
> min]
> [INFO] Apache Atlas Web Application ... SUCCESS [03:13 
> min]
> [INFO] Apache Atlas Documentation . SUCCESS [  4.433 
> s]
> [INFO] Apache Atlas Hive Bridge ... SUCCESS [01:31 
> min]
> [INFO] Apache Atlas Falcon Bridge . FAILURE [  3.805 
> s]
> [INFO] Apache Atlas Sqoop Bridge .. SKIPPED
> [INFO] Apache Atlas Storm Bridge .. SKIPPED
> [INFO] Apache Atlas Distribution .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 05:58 min
> [INFO] Finished at: 2016-03-18T12:42:32+05:30
> [INFO] Final Memory: 188M/687M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.eclipse.jetty:jetty-maven-plugin:9.2.12.v20150709:deploy-war 
> (start-jetty) on project falcon-bridge: Failure: ShutdownMonitorThread 
> already started -> [Help 1]
> {noformat}



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

[jira] [Updated] (ATLAS-575) jetty-maven-plugin fails with ShutdownMonitorThread already started

[Shwetha G S (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shwetha G S updated ATLAS-575:
--
Attachment: ATLAS-575-v2.patch

> jetty-maven-plugin fails with ShutdownMonitorThread already started
> ---
>
> Key: ATLAS-575
> URL: https://issues.apache.org/jira/browse/ATLAS-575
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-575-v2.patch, ATLAS-575.patch
>
>
> {noformat}
> [INFO] --- jetty-maven-plugin:9.2.12.v20150709:deploy-war (start-jetty) @ 
> falcon-bridge ---
> [INFO] Configuring Jetty for project: Apache Atlas Falcon Bridge
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Atlas UI  SUCCESS [01:04 
> min]
> [INFO] Apache Atlas Web Application ... SUCCESS [03:13 
> min]
> [INFO] Apache Atlas Documentation . SUCCESS [  4.433 
> s]
> [INFO] Apache Atlas Hive Bridge ... SUCCESS [01:31 
> min]
> [INFO] Apache Atlas Falcon Bridge . FAILURE [  3.805 
> s]
> [INFO] Apache Atlas Sqoop Bridge .. SKIPPED
> [INFO] Apache Atlas Storm Bridge .. SKIPPED
> [INFO] Apache Atlas Distribution .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 05:58 min
> [INFO] Finished at: 2016-03-18T12:42:32+05:30
> [INFO] Final Memory: 188M/687M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.eclipse.jetty:jetty-maven-plugin:9.2.12.v20150709:deploy-war 
> (start-jetty) on project falcon-bridge: Failure: ShutdownMonitorThread 
> already started -> [Help 1]
> {noformat}



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

Jenkins build is back to normal : apache-atlas-nightly #222

[Apache Jenkins Server]

See 

[jira] [Created] (ATLAS-582) Move Atlas UI to use backboneJS

[Erik Bergenholtz (JIRA)]

Erik Bergenholtz created ATLAS-582:
--

 Summary: Move Atlas UI to use backboneJS
 Key: ATLAS-582
 URL: https://issues.apache.org/jira/browse/ATLAS-582
 Project: Atlas
  Issue Type: Improvement
Affects Versions: 0.7-incubating
Reporter: Erik Bergenholtz
Assignee: keval bhatt
 Fix For: 0.7-incubating






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

[jira] [Created] (ATLAS-581) Atlas UI should show state of Entity

[Erik Bergenholtz (JIRA)]

Erik Bergenholtz created ATLAS-581:
--

 Summary: Atlas UI should show state of Entity
 Key: ATLAS-581
 URL: https://issues.apache.org/jira/browse/ATLAS-581
 Project: Atlas
  Issue Type: Improvement
Reporter: Erik Bergenholtz
Assignee: keval bhatt


Atlas will be introducing an attribute indicating whether or not an entity is 
deleted. In the search results page the UI should differentiate between a 
deleted entity and a non-deleted entity. The best way to do this is up for 
discussion, several options include:

- Introduce a separate 'deleted' column with a check mark for deleted Entities
- Show deleted Entities in muted gray text
- Show deleted Entities in -strikethrough- text



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

[jira] [Updated] (ATLAS-495) Atlas Ranger Authorization Plugin

[Erik Bergenholtz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik Bergenholtz updated ATLAS-495:
---
Assignee: Nixon Rodrigues

> Atlas Ranger Authorization Plugin
> -
>
> Key: ATLAS-495
> URL: https://issues.apache.org/jira/browse/ATLAS-495
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Nixon Rodrigues
> Fix For: 0.7-incubating
>
>
> Atlas must support an Authorization Plugin that leverage Ranger:
> Requirements
> - The Ranger Plugin will authorize all user actions against security policies 
> defined in Ranger
> Example of Policies include:
> - Restricting Access to specific actions based on user role i.e.
> - Ability to Tag
> - Ability to Delete
> - Ability to View
> - Ability to Modify / Update



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

[jira] [Commented] (ATLAS-497) Simple Authorization

[Erik Bergenholtz (JIRA)]

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

Erik Bergenholtz commented on ATLAS-497:


Determining if the store for persisting user/role mappings can be HBase - TBD.

> Simple Authorization
> 
>
> Key: ATLAS-497
> URL: https://issues.apache.org/jira/browse/ATLAS-497
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
> Fix For: 0.7-incubating
>
>
> Atlas needs to support a simple (out of box) authorization mechanism.
> Defined Roles:
> - Data Scientist: provides a read only view (GET)
> - Data Steward: provides a read/edit view (PUT, POST, DELETE)
> - Admin (can do anything)
> All can comment on entity
> Requirements
> - Atlas will implement a simple file based store for providing user to role 
> mapping
> - The out of box experience will be this file based mechanism for 
> authorization



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

[jira] [Updated] (ATLAS-497) Simple Authorization

[Erik Bergenholtz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik Bergenholtz updated ATLAS-497:
---
Assignee: Nixon Rodrigues

> Simple Authorization
> 
>
> Key: ATLAS-497
> URL: https://issues.apache.org/jira/browse/ATLAS-497
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Nixon Rodrigues
> Fix For: 0.7-incubating
>
>
> Atlas needs to support a simple (out of box) authorization mechanism.
> Defined Roles:
> - Data Scientist: provides a read only view (GET)
> - Data Steward: provides a read/edit view (PUT, POST, DELETE)
> - Admin (can do anything)
> All can comment on entity
> Requirements
> - Atlas will implement a simple file based store for providing user to role 
> mapping
> - The out of box experience will be this file based mechanism for 
> authorization



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

[jira] [Commented] (ATLAS-513) Admin support for HA

[Erik Bergenholtz (JIRA)]

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

Erik Bergenholtz commented on ATLAS-513:


This makes sense to me.

> Admin support for HA
> 
>
> Key: ATLAS-513
> URL: https://issues.apache.org/jira/browse/ATLAS-513
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>
> The following enhancements are proposed for the admin interface to manage HA:
> * Status of any atlas server instance via API and Atlas Admin UI.
> * Admin API to switch from active to passive.
> * Admin switch from passive to active - this must fail if there is another 
> active.



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

[jira] [Commented] (ATLAS-576) Build with Maven 3.0.5 fails

[Shwetha G S (JIRA)]

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

Shwetha G S commented on ATLAS-576:
---

Dashboard is failing on my box with any version, looks like an issue with my 
environment. I can't verify if this patch works with mvn 3.3.9. So, reverting 
to unblock development. Will check with mvn 3.3.9 later and commit

> Build with Maven 3.0.5 fails
> 
>
> Key: ATLAS-576
> URL: https://issues.apache.org/jira/browse/ATLAS-576
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
> Environment: Maven 3.0.5 on Mac OS X (10.10.5)
>Reporter: Rajendra Patil
>Assignee: Rajendra Patil
>Priority: Trivial
>  Labels: Maven, dashboard, front-end, frontend
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-576-1.patch, ATLAS-576-2.patch
>
>
> *Problem*:
> Atlast dashboard, the subproject fails due to maven frontend plugin version 
> 0.0.23 that needs maven 3.1.0
> --
> INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 2.598s
> [INFO] Finished at: Fri Mar 18 13:18:03 IST 2016
> [INFO] Final Memory: 14M/309M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> com.github.eirslett:frontend-maven-plugin:0.0.23:install-node-and-npm 
> (install node and npm) on project atlas-dashboard: The plugin 
> com.github.eirslett:frontend-maven-plugin:0.0.23 requires Maven version 3.1.0 
> -> [Help 1]
> --
> *Solution/Proposal*: frontend plugin  0.0.22 works absolutely fine and I 
> don't think we have any must have dependency on 0.0.23 or higher at this 
> time. 



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

[jira] [Reopened] (ATLAS-576) Build with Maven 3.0.5 fails

[Shwetha G S (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shwetha G S reopened ATLAS-576:
---

> Build with Maven 3.0.5 fails
> 
>
> Key: ATLAS-576
> URL: https://issues.apache.org/jira/browse/ATLAS-576
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
> Environment: Maven 3.0.5 on Mac OS X (10.10.5)
>Reporter: Rajendra Patil
>Assignee: Rajendra Patil
>Priority: Trivial
>  Labels: Maven, dashboard, front-end, frontend
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-576-1.patch, ATLAS-576-2.patch
>
>
> *Problem*:
> Atlast dashboard, the subproject fails due to maven frontend plugin version 
> 0.0.23 that needs maven 3.1.0
> --
> INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 2.598s
> [INFO] Finished at: Fri Mar 18 13:18:03 IST 2016
> [INFO] Final Memory: 14M/309M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> com.github.eirslett:frontend-maven-plugin:0.0.23:install-node-and-npm 
> (install node and npm) on project atlas-dashboard: The plugin 
> com.github.eirslett:frontend-maven-plugin:0.0.23 requires Maven version 3.1.0 
> -> [Help 1]
> --
> *Solution/Proposal*: frontend plugin  0.0.22 works absolutely fine and I 
> don't think we have any must have dependency on 0.0.23 or higher at this 
> time. 



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

[jira] [Commented] (ATLAS-513) Admin support for HA

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-513:


One of the main motivations for this requirement (other than providing 
operational status) was for supporting upgrades of components without any 
downtime (referred to as rolling upgrades) - something that is common in many 
Hadoop components. However, I realized that this is easily achieved just with 
the capabilities of ATLAS-511. Assuming only 2 instances:
* One can just shutdown a passive instance, upgrade and start. The new instance 
would join the leader election and be on standby. 
* This can be followed by shutting down the active instance cleanly. This will 
cause the newly upgraded instance to be elected active. With clean shutdown, 
the election of a new leader happens instantaneously in my tests.
* Then the older active instance can be upgraded and restarted. It will join 
the leader election and become standby.

So I propose we scope down this JIRA to be providing Admin status alone. If 
folks feel there is need for other actions like switch to passive, we can 
discuss them in some following jiras.

For providing admin status, I am thinking to do the following:
* Make sure that the Servlet Filter for Active status checks introduced in 
ATLAS-511 passes through all admin APIs.
* Add an admin/status command that provides required information about a server 
instance.

If required for convenience, we can have a script like {{atlas_admin.py 
-status}}, (similar to atlas_start.py and atlas_stop.py) that can provide the 
same information from command line.

> Admin support for HA
> 
>
> Key: ATLAS-513
> URL: https://issues.apache.org/jira/browse/ATLAS-513
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>
> The following enhancements are proposed for the admin interface to manage HA:
> * Status of any atlas server instance via API and Atlas Admin UI.
> * Admin API to switch from active to passive.
> * Admin switch from passive to active - this must fail if there is another 
> active.



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

[jira] [Commented] (ATLAS-576) Build with Maven 3.0.5 fails

[Shwetha G S (JIRA)]

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

Shwetha G S commented on ATLAS-576:
---

This looks like a bug in mvn 3.3.1 and 3.3.3 and affects other plugins as well 
- https://issues.apache.org/jira/browse/MNG-5787. Its fixed in mvn 3.3.9. But 
frontend-maven-plugin(with any version) didn't work with mvn 3.3.9. So, until 
we need some specific feature in higher version of frontend-maven-plugin, we 
should recommend max mvn version to be 3.2.x?

> Build with Maven 3.0.5 fails
> 
>
> Key: ATLAS-576
> URL: https://issues.apache.org/jira/browse/ATLAS-576
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
> Environment: Maven 3.0.5 on Mac OS X (10.10.5)
>Reporter: Rajendra Patil
>Assignee: Rajendra Patil
>Priority: Trivial
>  Labels: Maven, dashboard, front-end, frontend
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-576-1.patch, ATLAS-576-2.patch
>
>
> *Problem*:
> Atlast dashboard, the subproject fails due to maven frontend plugin version 
> 0.0.23 that needs maven 3.1.0
> --
> INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 2.598s
> [INFO] Finished at: Fri Mar 18 13:18:03 IST 2016
> [INFO] Final Memory: 14M/309M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> com.github.eirslett:frontend-maven-plugin:0.0.23:install-node-and-npm 
> (install node and npm) on project atlas-dashboard: The plugin 
> com.github.eirslett:frontend-maven-plugin:0.0.23 requires Maven version 3.1.0 
> -> [Help 1]
> --
> *Solution/Proposal*: frontend plugin  0.0.22 works absolutely fine and I 
> don't think we have any must have dependency on 0.0.23 or higher at this 
> time. 



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

[jira] [Commented] (ATLAS-576) Build with Maven 3.0.5 fails

[Shwetha G S (JIRA)]

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

Shwetha G S commented on ATLAS-576:
---

I have mvn 3.2.5, and 0.0.22 of frontend-maven-plugin worked for me. Will check

> Build with Maven 3.0.5 fails
> 
>
> Key: ATLAS-576
> URL: https://issues.apache.org/jira/browse/ATLAS-576
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
> Environment: Maven 3.0.5 on Mac OS X (10.10.5)
>Reporter: Rajendra Patil
>Assignee: Rajendra Patil
>Priority: Trivial
>  Labels: Maven, dashboard, front-end, frontend
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-576-1.patch, ATLAS-576-2.patch
>
>
> *Problem*:
> Atlast dashboard, the subproject fails due to maven frontend plugin version 
> 0.0.23 that needs maven 3.1.0
> --
> INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 2.598s
> [INFO] Finished at: Fri Mar 18 13:18:03 IST 2016
> [INFO] Final Memory: 14M/309M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> com.github.eirslett:frontend-maven-plugin:0.0.23:install-node-and-npm 
> (install node and npm) on project atlas-dashboard: The plugin 
> com.github.eirslett:frontend-maven-plugin:0.0.23 requires Maven version 3.1.0 
> -> [Help 1]
> --
> *Solution/Proposal*: frontend plugin  0.0.22 works absolutely fine and I 
> don't think we have any must have dependency on 0.0.23 or higher at this 
> time. 



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

[jira] [Commented] (ATLAS-576) Build with Maven 3.0.5 fails

[Rajendra Patil (JIRA)]

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

Rajendra Patil commented on ATLAS-576:
--

Looking at the issue mentioned by Hemanth, I think we need to revert the 
change. I will check maven profile to see if we can set the right version. For 
now, revert seems to be the quick fix.

> Build with Maven 3.0.5 fails
> 
>
> Key: ATLAS-576
> URL: https://issues.apache.org/jira/browse/ATLAS-576
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
> Environment: Maven 3.0.5 on Mac OS X (10.10.5)
>Reporter: Rajendra Patil
>Assignee: Rajendra Patil
>Priority: Trivial
>  Labels: Maven, dashboard, front-end, frontend
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-576-1.patch, ATLAS-576-2.patch
>
>
> *Problem*:
> Atlast dashboard, the subproject fails due to maven frontend plugin version 
> 0.0.23 that needs maven 3.1.0
> --
> INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 2.598s
> [INFO] Finished at: Fri Mar 18 13:18:03 IST 2016
> [INFO] Final Memory: 14M/309M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> com.github.eirslett:frontend-maven-plugin:0.0.23:install-node-and-npm 
> (install node and npm) on project atlas-dashboard: The plugin 
> com.github.eirslett:frontend-maven-plugin:0.0.23 requires Maven version 3.1.0 
> -> [Help 1]
> --
> *Solution/Proposal*: frontend plugin  0.0.22 works absolutely fine and I 
> don't think we have any must have dependency on 0.0.23 or higher at this 
> time. 



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

[jira] [Commented] (ATLAS-576) Build with Maven 3.0.5 fails

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-576:


[~rpatil], [~shwethags], I have Apache Maven 3.3.3 (always had). Did a mvn 
clean install today and got the following error in the atlas-dashboard module:

{code}
[ERROR] Failed to execute goal 
com.github.eirslett:frontend-maven-plugin:0.0.22:install-node-and-npm (install 
node and npm) on project atlas-dashboard: Execution install node and npm of 
goal com.github.eirslett:frontend-maven-plugin:0.0.22:install-node-and-npm 
failed: A required class was missing while executing 
com.github.eirslett:frontend-maven-plugin:0.0.22:install-node-and-npm: 
org/slf4j/helpers/MarkerIgnoringBase
[ERROR] -
[ERROR] realm =plugin>com.github.eirslett:frontend-maven-plugin:0.0.22
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = 
file:/Users/hyamijala/.m2/repository/com/github/eirslett/frontend-maven-plugin/0.0.22/frontend-maven-plugin-0.0.22.jar
[ERROR] urls[1] = 
file:/Users/hyamijala/.m2/repository/com/github/eirslett/frontend-plugin-core/0.0.22/frontend-plugin-core-0.0.22.jar
[ERROR] urls[2] = 
file:/Users/hyamijala/.m2/repository/org/codehaus/jackson/jackson-mapper-asl/1.9.13/jackson-mapper-asl-1.9.13.jar
[ERROR] urls[3] = 
file:/Users/hyamijala/.m2/repository/org/codehaus/jackson/jackson-core-asl/1.9.13/jackson-core-asl-1.9.13.jar
[ERROR] urls[4] = 
file:/Users/hyamijala/.m2/repository/org/apache/commons/commons-compress/1.5/commons-compress-1.5.jar
[ERROR] urls[5] = 
file:/Users/hyamijala/.m2/repository/org/tukaani/xz/1.2/xz-1.2.jar
[ERROR] urls[6] = 
file:/Users/hyamijala/.m2/repository/commons-io/commons-io/1.3.2/commons-io-1.3.2.jar
[ERROR] urls[7] = 
file:/Users/hyamijala/.m2/repository/org/apache/httpcomponents/httpclient/4.3.1/httpclient-4.3.1.jar
[ERROR] urls[8] = 
file:/Users/hyamijala/.m2/repository/org/apache/httpcomponents/httpcore/4.3/httpcore-4.3.jar
[ERROR] urls[9] = 
file:/Users/hyamijala/.m2/repository/commons-logging/commons-logging/1.1.3/commons-logging-1.1.3.jar
[ERROR] urls[10] = 
file:/Users/hyamijala/.m2/repository/commons-codec/commons-codec/1.6/commons-codec-1.6.jar
[ERROR] urls[11] = 
file:/Users/hyamijala/.m2/repository/javax/enterprise/cdi-api/1.0/cdi-api-1.0.jar
[ERROR] urls[12] = 
file:/Users/hyamijala/.m2/repository/javax/annotation/jsr250-api/1.0/jsr250-api-1.0.jar
[ERROR] urls[13] = 
file:/Users/hyamijala/.m2/repository/com/google/guava/guava/10.0.1/guava-10.0.1.jar
[ERROR] urls[14] = 
file:/Users/hyamijala/.m2/repository/com/google/code/findbugs/jsr305/1.3.9/jsr305-1.3.9.jar
[ERROR] urls[15] = 
file:/Users/hyamijala/.m2/repository/org/sonatype/sisu/sisu-guice/3.1.0/sisu-guice-3.1.0-no_aop.jar
[ERROR] urls[16] = 
file:/Users/hyamijala/.m2/repository/aopalliance/aopalliance/1.0/aopalliance-1.0.jar
[ERROR] urls[17] = 
file:/Users/hyamijala/.m2/repository/org/eclipse/sisu/org.eclipse.sisu.inject/0.0.0.M2a/org.eclipse.sisu.inject-0.0.0.M2a.jar
[ERROR] urls[18] = 
file:/Users/hyamijala/.m2/repository/asm/asm/3.3.1/asm-3.3.1.jar
[ERROR] urls[19] = 
file:/Users/hyamijala/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
[ERROR] urls[20] = 
file:/Users/hyamijala/.m2/repository/org/apache/maven/plugin-tools/maven-plugin-annotations/3.2/maven-plugin-annotations-3.2.jar
[ERROR] urls[21] = 
file:/Users/hyamijala/.m2/repository/com/googlecode/slf4j-maven-plugin-log/slf4j-maven-plugin-log/1.0.0/slf4j-maven-plugin-log-1.0.0.jar
[ERROR] urls[22] = 
file:/Users/hyamijala/.m2/repository/org/sonatype/plexus/plexus-build-api/0.0.7/plexus-build-api-0.0.7.jar
[ERROR] urls[23] = 
file:/Users/hyamijala/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.8/plexus-utils-1.5.8.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import  from realm 
ClassRealm[project>org.apache.atlas:apache-atlas:0.7-incubating-SNAPSHOT, 
parent: ClassRealm[maven.api, parent: null]]]
[ERROR] 
[ERROR] -: 
org.slf4j.helpers.MarkerIgnoringBase
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
{code}

This issue is referenced here: 
https://github.com/eirslett/frontend-maven-plugin/issues/179, where the fix was 
to use 0.0.23 of frontend-maven-plugin. So, it appears our code base does need 
0.0.23 (and therefore possibly maven 3.3.x). Can you please check this?

> Build with Maven 3.0.5 fails
> 
>

[jira] [Commented] (ATLAS-513) Admin support for HA

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-513:


[~jonesn], as described in ATLAS-511, the HA work overall is indeed a Zookeeper 
/ Curator based solution.

> Admin support for HA
> 
>
> Key: ATLAS-513
> URL: https://issues.apache.org/jira/browse/ATLAS-513
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>
> The following enhancements are proposed for the admin interface to manage HA:
> * Status of any atlas server instance via API and Atlas Admin UI.
> * Admin API to switch from active to passive.
> * Admin switch from passive to active - this must fail if there is another 
> active.



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

[jira] [Assigned] (ATLAS-513) Admin support for HA

[Hemanth Yamijala (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hemanth Yamijala reassigned ATLAS-513:
--

Assignee: Hemanth Yamijala

> Admin support for HA
> 
>
> Key: ATLAS-513
> URL: https://issues.apache.org/jira/browse/ATLAS-513
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>
> The following enhancements are proposed for the admin interface to manage HA:
> * Status of any atlas server instance via API and Atlas Admin UI.
> * Admin API to switch from active to passive.
> * Admin switch from passive to active - this must fail if there is another 
> active.



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