[jira] [Commented] (ATLAS-3766) Atlas Admin Audit UI pagination is not working

2020-05-01 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on ATLAS-3766:


Commit 2004bcd37d5de9c9d4031a16032989d174950520 in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2004bcd ]

ATLAS-3766:- UI:Atlas Admin Audit UI pagination is not working


> Atlas Admin Audit UI pagination is not working
> --
>
> Key: ATLAS-3766
> URL: https://issues.apache.org/jira/browse/ATLAS-3766
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3766-1.patch, ATLAS-3766.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3766) Atlas Admin Audit UI pagination is not working

2020-05-01 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on ATLAS-3766:


Commit 1c07f93b577d156ccf7c9adb75c447359002ed38 in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1c07f93 ]

ATLAS-3766:- UI:Atlas Admin Audit UI pagination is not working


> Atlas Admin Audit UI pagination is not working
> --
>
> Key: ATLAS-3766
> URL: https://issues.apache.org/jira/browse/ATLAS-3766
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3766-1.patch, ATLAS-3766.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3776) graph query fails when orderBy attribute is specified

2020-05-01 Thread Damian Warszawski (Jira) 


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

Damian Warszawski updated ATLAS-3776:
-
Description: 
EntitySearchProcessor fails when doing search by classification and specify 
orderBy attribute. The issue is that for graph query you cannot refer to 
attribute by name but need to provide absolute path to entity attribute e.g. 

 

```

{ "attributes": [ "description", "comment", "popularityScore" ], 
"classification": "customer_NON_PII", "excludeDeletedEntities": "False", 
"limit": "", "offset": 100, "sortBy": "Table.popularityScore", "sortOrder": 
"DESCENDING", "typeName": "hive_table" }

```

this query fails with following exception:

 

```

{"exception":{"message":"Provided key does not exist: 
Table.popularityScore","class":"java.lang.IllegalArgumentException","stacktrace":"java.lang.IllegalArgumentException:
 Provided key does not exist: hive_table.popularityScore\n\tat 
com.google.common.base.Preconditions.checkArgument(Preconditions.java:163)\n\tat
 org.janusgraph.graphdb.query.graph.GraphCentricQueryBuilder.
 orderBy(GraphCentricQueryBuilder.java:160)

```

 

When specify full reference to attribute e.g. 

 

```

{ "attributes": [ "description", "comment", "popularityScore" ], 
"classification": "customer_NON_PII", "excludeDeletedEntities": "False", 
"limit": "", "offset": 100, "sortBy": "Table.popularityScore", "sortOrder": 
"DESCENDING", "typeName": "hive_table" }

```

it fails on validation stage

 

```

{"exception":{"message":"Attribute Table.popularityScore not found for type 
Table","class":"org.apache.atlas.exception.AtlasBaseException","stacktrace":"org.apache.atlas.exception.AtlasBaseException:
 Attribute Table.popularityScore not found for type Table\n\tat 
org.apache.atlas.discovery.SearchContext.validateAttributes(SearchContext.java:288)

```

workaround is provided as a patch.

  was:
EntitySearchProcessor fails when doing search by classification and specify 
orderBy attribute. The issue is that for graph query you cannot refer to 
attribute by name but need to provide absolute path to entity attribute e.g. 

 

```

{
 "attributes": [
 "description",
 "comment",
 "popularityScore"
 ],
 "classification": "customer_NON_PII",
 "excludeDeletedEntities": "False",
 "limit": "",
 "offset": 100,
 "sortBy": "Table.popularityScore",
 "sortOrder": "DESCENDING",
 "typeName": "hive_table"
}

```

this query fails with following exception:

 

```

{"exception":{"message":"Provided key does not exist: 
hive_table.popularityScore","class":"java.lang.IllegalArgumentException","stacktrace":"java.lang.IllegalArgumentException:
 Provided key does not exist: hive_table.popularityScore\n\tat 
com.google.common.base.Preconditions.checkArgument(Preconditions.java:163)\n\tat
 org.janusgraph.graphdb.query.graph.GraphCentricQueryBuilder.
orderBy(GraphCentricQueryBuilder.java:160)

```

 

When specify full reference to attribute e.g. 

 

```

{
 "attributes": [
 "description",
 "comment",
 "popularityScore"
 ],
 "classification": "customer_NON_PII",
 "excludeDeletedEntities": "False",
 "limit": "",
 "offset": 100,
 "sortBy": "Table.popularityScore",
 "sortOrder": "DESCENDING",
 "typeName": "hive_table"
}

```

it fails on validation stage

 

```

{"exception":{"message":"Attribute Table.popularityScore not found for type 
Table","class":"org.apache.atlas.exception.AtlasBaseException","stacktrace":"org.apache.atlas.exception.AtlasBaseException:
 Attribute Table.popularityScore not found for type Table\n\tat 
org.apache.atlas.discovery.SearchContext.validateAttributes(SearchContext.java:288)

```

workaround is provided as a patch.


> graph query fails when orderBy attribute is specified
> -
>
> Key: ATLAS-3776
> URL: https://issues.apache.org/jira/browse/ATLAS-3776
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 3.0.0
>Reporter: Damian Warszawski
>Priority: Minor
>
> EntitySearchProcessor fails when doing search by classification and specify 
> orderBy attribute. The issue is that for graph query you cannot refer to 
> attribute by name but need to provide absolute path to entity attribute e.g. 
>  
> ```
> { "attributes": [ "description", "comment", "popularityScore" ], 
> "classification": "customer_NON_PII", "excludeDeletedEntities": "False", 
> "limit": "", "offset": 100, "sortBy": "Table.popularityScore", "sortOrder": 
> "DESCENDING", "typeName": "hive_table" }
> ```
> this query fails with following exception:
>  
> ```
> {"exception":{"message":"Provided key does not exist: 
> Table.popularityScore","class":"java.lang.IllegalArgumentException","stacktrace":"java.lang.IllegalArgumentException:
>  Provided key does not exist: hive_table.popularityScore\n\tat 
> com.google.common.base.Preconditions.checkA

Review Request 72459: EntitySearchProcessor is failing on graph query with sortBy attribute.

2020-05-01 Thread Damian Warszawski 

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

Review request for atlas, Bolke de Bruin, Madhan Neethiraj, and Nixon Rodrigues.


Repository: atlas


Description
---

EntitySearchProcessor fails when doing search by classification and specify 
orderBy attribute. The issue is that for graph query you cannot refer to 
attribute by name but need to provide absolute path to entity attribute e.g. 

 

```

{ "attributes": [ "description", "comment", "popularityScore" ], 
"classification": "customer_NON_PII", "excludeDeletedEntities": "False", 
"limit": "", "offset": 100, "sortBy": "Table.popularityScore", "sortOrder": 
"DESCENDING", "typeName": "hive_table" }
```

this query fails with following exception:

 

```

{"exception":{"message":"Provided key does not exist: 
hive_table.popularityScore","class":"java.lang.IllegalArgumentException","stacktrace":"java.lang.IllegalArgumentException:
 Provided key does not exist: hive_table.popularityScore\n\tat 
com.google.common.base.Preconditions.checkArgument(Preconditions.java:163)\n\tat
 org.janusgraph.graphdb.query.graph.GraphCentricQueryBuilder.
orderBy(GraphCentricQueryBuilder.java:160)

```

 

When specify full reference to attribute e.g. 

 

```

{ "attributes": [ "description", "comment", "popularityScore" ], 
"classification": "customer_NON_PII", "excludeDeletedEntities": "False", 
"limit": "", "offset": 100, "sortBy": "Table.popularityScore", "sortOrder": 
"DESCENDING", "typeName": "hive_table" }
```

it fails on validation stage

 

```

{"exception":{"message":"Attribute Table.popularityScore not found for type 
Table","class":"org.apache.atlas.exception.AtlasBaseException","stacktrace":"org.apache.atlas.exception.AtlasBaseException:
 Attribute Table.popularityScore not found for type Table\n\tat 
org.apache.atlas.discovery.SearchContext.validateAttributes(SearchContext.java:288)

```

Reference to JIRA https://issues.apache.org/jira/browse/ATLAS-3776


Diffs
-

  
repository/src/main/java/org/apache/atlas/discovery/EntitySearchProcessor.java 
1a7bf6b16 


Diff: https://reviews.apache.org/r/72459/diff/1/


Testing
---

tested on our dev env.


Thanks,

Damian Warszawski

[jira] [Created] (ATLAS-3776) graph query fails when orderBy attribute is specified

2020-05-01 Thread Damian Warszawski (Jira) 
Damian Warszawski created ATLAS-3776:


 Summary: graph query fails when orderBy attribute is specified
 Key: ATLAS-3776
 URL: https://issues.apache.org/jira/browse/ATLAS-3776
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 3.0.0
Reporter: Damian Warszawski


EntitySearchProcessor fails when doing search by classification and specify 
orderBy attribute. The issue is that for graph query you cannot refer to 
attribute by name but need to provide absolute path to entity attribute e.g. 

 

```

{
 "attributes": [
 "description",
 "comment",
 "popularityScore"
 ],
 "classification": "customer_NON_PII",
 "excludeDeletedEntities": "False",
 "limit": "",
 "offset": 100,
 "sortBy": "Table.popularityScore",
 "sortOrder": "DESCENDING",
 "typeName": "hive_table"
}

```

this query fails with following exception:

 

```

{"exception":{"message":"Provided key does not exist: 
hive_table.popularityScore","class":"java.lang.IllegalArgumentException","stacktrace":"java.lang.IllegalArgumentException:
 Provided key does not exist: hive_table.popularityScore\n\tat 
com.google.common.base.Preconditions.checkArgument(Preconditions.java:163)\n\tat
 org.janusgraph.graphdb.query.graph.GraphCentricQueryBuilder.
orderBy(GraphCentricQueryBuilder.java:160)

```

 

When specify full reference to attribute e.g. 

 

```

{
 "attributes": [
 "description",
 "comment",
 "popularityScore"
 ],
 "classification": "customer_NON_PII",
 "excludeDeletedEntities": "False",
 "limit": "",
 "offset": 100,
 "sortBy": "Table.popularityScore",
 "sortOrder": "DESCENDING",
 "typeName": "hive_table"
}

```

it fails on validation stage

 

```

{"exception":{"message":"Attribute Table.popularityScore not found for type 
Table","class":"org.apache.atlas.exception.AtlasBaseException","stacktrace":"org.apache.atlas.exception.AtlasBaseException:
 Attribute Table.popularityScore not found for type Table\n\tat 
org.apache.atlas.discovery.SearchContext.validateAttributes(SearchContext.java:288)

```

workaround is provided as a patch.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3775) Migration Import Display: Incorrect Status Display

2020-05-01 Thread Ashutosh Mestry (Jira) 


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

Ashutosh Mestry updated ATLAS-3775:
---
Attachment: ATLAS-3775-Migration-Import-Status-display-fix.patch

> Migration Import Display: Incorrect Status Display
> --
>
> Key: ATLAS-3775
> URL: https://issues.apache.org/jira/browse/ATLAS-3775
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk
>
> Attachments: ATLAS-3775-Migration-Import-Status-display-fix.patch
>
>
> *Background*
> Zip file based migration introduced _DataMigrationStatusService_. This class 
> is responsible for displaying the status.
> *Steps to Duplicate*
> Pre-requisites:
>  * Keep the REST http:///api/atlas/admin output open in a browser 
> window.
>  * Keep zip-file based migration import in progress.
>  * Ensure that you see the current status. Once migration progress, refresh 
> the REST API output to display the status. The status should be accurate.
>  * Refresh the REST API output after 5 mins. This will expire the status 
> cache and make a request to _DataMigrationService_ for status.
> _Expected results_
>  * Status returned by API should reflect the status logged.
>  
> _Actual results_
>  * There is a mismatch in the status.
>  * Additional information: The status is never updated for that session.
> Root cause:
> - _DataMigrationService_ maintains cached status object for each requestor. 
> This is not refreshed from the database status.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (ATLAS-3775) Migration Import Display: Incorrect Status Display

2020-05-01 Thread Ashutosh Mestry (Jira) 
Ashutosh Mestry created ATLAS-3775:
--

 Summary: Migration Import Display: Incorrect Status Display
 Key: ATLAS-3775
 URL: https://issues.apache.org/jira/browse/ATLAS-3775
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: trunk
Reporter: Ashutosh Mestry
Assignee: Ashutosh Mestry
 Fix For: trunk


*Background*

Zip file based migration introduced _DataMigrationStatusService_. This class is 
responsible for displaying the status.

*Steps to Duplicate*

Pre-requisites:
 * Keep the REST http:///api/atlas/admin output open in a browser 
window.
 * Keep zip-file based migration import in progress.
 * Ensure that you see the current status. Once migration progress, refresh the 
REST API output to display the status. The status should be accurate.
 * Refresh the REST API output after 5 mins. This will expire the status cache 
and make a request to _DataMigrationService_ for status.

_Expected results_
 * Status returned by API should reflect the status logged.

 

_Actual results_
 * There is a mismatch in the status.
 * Additional information: The status is never updated for that session.

Root cause:

- _DataMigrationService_ maintains cached status object for each requestor. 
This is not refreshed from the database status.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3773) Migration: From 0.8 to latest: Breaks Relationships

2020-05-01 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on ATLAS-3773:


Commit a43b5488fbd10c874d181bf27e076fd502693a93 in atlas's branch 
refs/heads/master from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=a43b548 ]

ATLAS-3773: Shadow Attributes Update Post-Migration from 0.8.


> Migration: From 0.8 to latest: Breaks Relationships
> ---
>
> Key: ATLAS-3773
> URL: https://issues.apache.org/jira/browse/ATLAS-3773
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk
>
> Attachments: 
> ATLAS-3773-Handling-shadow-attributes-for-indexType-.patch
>
>
> *Steps to Duplicate*
>  # Migrate data from 0.8 to latest. E.g. data containing hive db and tables.
>  # In the web UI, use a DSL search like: _hive_table 
> db.name="migration_database_8"_
> _**Expected results:_ The hive_table with for database _migration_database_8_ 
> should be displayed.
> **_Actual results_: No results are displayed. There are exceptions logged on 
> the server-side.
> *Root Cause*
> As part of implementation of ATLAS-3370, shadow properties were introduced 
> for index type STRING. These need to be set for data that is migrated.
> *Solution*
> Use patch handler to add these missing types.
> Rationale for the approach: The same problem would be observed when upgrading 
> from version of Atlas post 0.8 but before the change was introduced.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Review Request 72458: Shadow Attributes Update Post-Migration from 0.8

2020-05-01 Thread Sarath Subramanian 

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


Ship it!




Ship It!

- Sarath Subramanian


On May 1, 2020, 10:18 a.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72458/
> ---
> 
> (Updated May 1, 2020, 10:18 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Nikhil Bonte, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3773
> https://issues.apache.org/jira/browse/ATLAS-3773
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> Please refer to JIRA for details.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatch.java
>  2b5811919 
> 
> 
> Diff: https://reviews.apache.org/r/72458/diff/3/
> 
> 
> Testing
> ---
> 
> **Manual verification**
> Steps:
> - Imported dataset from 0.8 using migration import.
> - Let the patch handlers run.
> - Verified DSL queries and basic search functionality.
> 
> **Pre-commit**
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1862/
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

Re: Review Request 72458: Shadow Attributes Update Post-Migration from 0.8

2020-05-01 Thread Madhan Neethiraj 

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


Ship it!




Ship It!

- Madhan Neethiraj


On May 1, 2020, 5:18 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72458/
> ---
> 
> (Updated May 1, 2020, 5:18 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Nikhil Bonte, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3773
> https://issues.apache.org/jira/browse/ATLAS-3773
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> Please refer to JIRA for details.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatch.java
>  2b5811919 
> 
> 
> Diff: https://reviews.apache.org/r/72458/diff/3/
> 
> 
> Testing
> ---
> 
> **Manual verification**
> Steps:
> - Imported dataset from 0.8 using migration import.
> - Let the patch handlers run.
> - Verified DSL queries and basic search functionality.
> 
> **Pre-commit**
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1862/
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

Re: Review Request 72458: Shadow Attributes Update Post-Migration from 0.8

2020-05-01 Thread Ashutosh Mestry via Review Board 

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

(Updated May 1, 2020, 5:18 p.m.)


Review request for atlas, Madhan Neethiraj, Nikhil Bonte, Nixon Rodrigues, and 
Sarath Subramanian.


Changes
---

Updates include: Addressed review comments.


Bugs: ATLAS-3773
https://issues.apache.org/jira/browse/ATLAS-3773


Repository: atlas


Description
---

**Approach**
Please refer to JIRA for details.


Diffs (updated)
-

  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/events/BaseHiveEvent.java
 6986ba176 
  
repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatch.java
 2b5811919 


Diff: https://reviews.apache.org/r/72458/diff/2/

Changes: https://reviews.apache.org/r/72458/diff/1-2/


Testing
---

**Manual verification**
Steps:
- Imported dataset from 0.8 using migration import.
- Let the patch handlers run.
- Verified DSL queries and basic search functionality.

**Pre-commit**
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1862/


Thanks,

Ashutosh Mestry

Re: Review Request 72458: Shadow Attributes Update Post-Migration from 0.8

2020-05-01 Thread Madhan Neethiraj 

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


Fix it, then Ship it!





repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatch.java
Lines 162 (patched)


for clarity, I suggest the following:

   void processIndexStringAttributes(AtlasVertex vertex, AtlasEntityType 
entityType) {
 for (AtlasAttribute attribute : 
entityType.getAllAttributes().values()) {
if 
(AtlasAttributeDef.IndexType.STRING.equals(attribute.getIndexType()) {
  ...
}
 }
   }
   
   void processUniqueAttributes(AtlasVertex vertex, AtlasEntityType 
entityType) {
 for (AtlasAttribute attribute : 
entityType.getUniqAttributes().values()) {
   ..
 }
   }


- Madhan Neethiraj


On May 1, 2020, 4:31 a.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72458/
> ---
> 
> (Updated May 1, 2020, 4:31 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Nikhil Bonte, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3773
> https://issues.apache.org/jira/browse/ATLAS-3773
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> Please refer to JIRA for details.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatch.java
>  2b5811919 
> 
> 
> Diff: https://reviews.apache.org/r/72458/diff/1/
> 
> 
> Testing
> ---
> 
> **Manual verification**
> Steps:
> - Imported dataset from 0.8 using migration import.
> - Let the patch handlers run.
> - Verified DSL queries and basic search functionality.
> 
> **Pre-commit**
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1862/
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

[jira] [Resolved] (ATLAS-3774) Typo in authentication docs

2020-05-01 Thread Nixon Rodrigues (Jira) 


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

Nixon Rodrigues resolved ATLAS-3774.

Fix Version/s: 3.0.0
   Resolution: Fixed

> Typo in authentication docs
> ---
>
> Key: ATLAS-3774
> URL: https://issues.apache.org/jira/browse/ATLAS-3774
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Guido Aulisi
>Priority: Trivial
> Fix For: 3.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Docs about LDAP authentication contain a closing ] instead of a closing}.
> See pull request https://github.com/apache/atlas/pull/84



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [atlas] nixonrodrigues commented on pull request #84: ATLAS-3774 : Fix typo in authentication docs

2020-05-01 Thread GitBox 


nixonrodrigues commented on pull request #84:
URL: https://github.com/apache/atlas/pull/84#issuecomment-622397725


   +1 for the fix. thanks @tartina 



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [atlas] tartina commented on pull request #84: Fix typo in authentication docs

2020-05-01 Thread GitBox 


tartina commented on pull request #84:
URL: https://github.com/apache/atlas/pull/84#issuecomment-622384741


   Added https://issues.apache.org/jira/browse/ATLAS-3774



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Created] (ATLAS-3774) Typo in authentication docs

2020-05-01 Thread Guido Aulisi (Jira) 
Guido Aulisi created ATLAS-3774:
---

 Summary: Typo in authentication docs
 Key: ATLAS-3774
 URL: https://issues.apache.org/jira/browse/ATLAS-3774
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Guido Aulisi


Docs about LDAP authentication contain a closing ] instead of a closing}.

See pull request https://github.com/apache/atlas/pull/84



--
This message was sent by Atlassian Jira
(v8.3.4#803005)