[jira] [Updated] (ATLAS-3931) Basic Search: Get total count of referred entities

2020-08-27 Thread Pinal (Jira)


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

Pinal updated ATLAS-3931:
-
Affects Version/s: 2.0.0

> Basic Search: Get total count of referred entities
> --
>
> Key: ATLAS-3931
> URL: https://issues.apache.org/jira/browse/ATLAS-3931
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> With this feature, While searching the entities we will get information of 
> its referred entities like total count.
>  Example: on searching entities of hive_table, in addition with hive_table 
> details, we can also get total number of columns associated to particular 
> hive_table.



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


[jira] [Updated] (ATLAS-3780) Change 'Status' from Classification System Attributes to EntityStatus

2020-08-27 Thread Pinal (Jira)


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

Pinal updated ATLAS-3780:
-
Fix Version/s: 2.1.0

> Change 'Status' from Classification System Attributes to EntityStatus
> -
>
> Key: ATLAS-3780
> URL: https://issues.apache.org/jira/browse/ATLAS-3780
> Project: Atlas
>  Issue Type: Task
>  Components: atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0, 3.0.0
>
> Attachments: Screen Shot 2020-05-05 at 4.40.40 PM.png
>
>




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


[jira] [Updated] (ATLAS-3876) Relationship Search API not showing correct approximateCount

2020-08-27 Thread Pinal (Jira)


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

Pinal updated ATLAS-3876:
-
Fix Version/s: 2.2.0

> Relationship Search API not showing correct approximateCount
> 
>
> Key: ATLAS-3876
> URL: https://issues.apache.org/jira/browse/ATLAS-3876
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: Relationships
> Fix For: 3.0.0, 2.2.0
>
>
> Relationship Search API for hive columns showing *approximateCount* as -1 in 
> response.
>  E.g.
> {code:java}
> v2/search/relationship?limit=10=0=3e424245-0676-4d47-96a1-e17228b38367=__hive_table.columns=name=ASCENDING=true
> {code}
> *WorkAround:* 
> Added queryParam in REST api : *boolean getApproximateCount*
> To get approximate count, enable flag getApproximateCount = true



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


[jira] [Updated] (ATLAS-3652) Quick Search: API requirement for GET request on multiple entity types

2020-08-27 Thread Pinal (Jira)


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

Pinal updated ATLAS-3652:
-
Fix Version/s: 2.2.0

> Quick Search: API requirement for GET request on multiple entity types
> --
>
> Key: ATLAS-3652
> URL: https://issues.apache.org/jira/browse/ATLAS-3652
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: quicksearch
> Fix For: 3.0.0, 2.2.0
>
>
> Need an API that can be used to GET information of multiple selected entity 
> types. Currently it seems to support GET request for
>  # One type (typeName=someType)\{by specifying typeName in the call},
>  OR 
>  # All types (typeName= )\{by leaving out typeName empty}.
>   
>  Need an API that works for multiple selected types while also returning the 
> aggregationMetrics in the responseJSON as opposed to the POST call(where the 
> aggregationMetrics is left out as empty).
>  
> *UseCase:* Multiple Entity types with its attribute filters
> *How And Validations:*
> 1. Search Results can be filtered with multiple entity types by 'comma' 
> seperated string of entity typeName in the request
> Eg. "typeName": "hive_table,hive_db".
> 2. For the attribute filters, attribute in the criteria should be System 
> attribute like "created by user, last modified time" or the attribute should 
> present in both the typeDefs of the mentioned entity 'hive_table' and 
> 'hive_db'. (Common attributes like name).



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


[jira] [Updated] (ATLAS-3838) Support multiple tag/classification in basic/quick search API

2020-08-27 Thread Pinal (Jira)


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

Pinal updated ATLAS-3838:
-
Fix Version/s: 2.2.0

> Support multiple tag/classification in basic/quick search API
> -
>
> Key: ATLAS-3838
> URL: https://issues.apache.org/jira/browse/ATLAS-3838
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 3.0.0, 2.2.0
>
>
> it will allow user to search with multiple tags and the tag attribute filters 
> (attribute should System attributes or attribute which common for all the 
> mentioned tags)
>  
> *Use Case**: Multiple tags with its attribute filters*
> *How And Validations:*
>  # Search Results can be filtered with multiple tag by 'comma' seperated 
> string of tags in the request
> Eg. "classification": "tag1,tag2".
>  # For the attribute filters, attribute in the criteria should be System 
> attribute like "created by user, last modified time" or the attribute should 
> present in both the typeDefs of the mentioned classification 'tag1' and 
> 'tag2'. (Common attributes like name).
>  # Curently we support Classifications like _ALL_CLASSIFICATION_TYPES, 
> _NOT_CLASSIFIED So if the request have any builtin classifications with the 
> normal tags, preference will be given to it in the below order
> _NOT_CLASSIFIED > _ALL_CLASSIFICATION_TYPES = _CLASSIFIED = 
> WILDCARD_CLASSIFICATIONS(*) > tag1 = tag2
> Eg. "classification" : "tag1,_CLASSIFIED" , search results will be according 
> to _CLASSIFIED
>  # Classification supports wildcard search too Eg. tag*, So if the request 
> has wildcard tag , tag filters will not apply to it.



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


[jira] [Updated] (ATLAS-3888) BasicSearch: Multiple type/tag: [Regression], Restrict when tag filters and regex in tag

2020-08-27 Thread Pinal (Jira)


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

Pinal updated ATLAS-3888:
-
Fix Version/s: 2.2.0

> BasicSearch: Multiple type/tag: [Regression], Restrict when tag filters and 
> regex in tag 
> -
>
> Key: ATLAS-3888
> URL: https://issues.apache.org/jira/browse/ATLAS-3888
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch, MultipleType/Tag
> Fix For: 3.0.0, 2.2.0
>
>
> In Basic search ,
> tag : PII_*
> tag filter : sensitivity < 0.5 
> returns 200 OK with no entities in response though there are entities tagged 
> with PII_1 with sensitivity < 0.5
>  
> Expected is 400 Bad request , as tag filters are not allowed when the tag has 
> regex.
>  



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


[jira] [Updated] (ATLAS-3880) BasicSearch: Multiple type/tag: Log invalid and allow searching valid type/tag names

2020-08-27 Thread Pinal (Jira)


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

Pinal updated ATLAS-3880:
-
Fix Version/s: 2.2.0

> BasicSearch: Multiple type/tag: Log invalid and allow searching valid 
> type/tag names
> 
>
> Key: ATLAS-3880
> URL: https://issues.apache.org/jira/browse/ATLAS-3880
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch, MultipleType/Tag
> Fix For: 3.0.0, 2.2.0
>
>
> If in basic search, request has combination of valid and invalid 
> typename/tags, allow searching for valid type names/tag names.
> Example:
> typeName:"valid,invalid"
> Allow searching entities for valid type.



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


[jira] [Updated] (ATLAS-3782) Support NOT_CONTAINS operator in basic search with search parameters

2020-08-27 Thread Pinal (Jira)


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

Pinal updated ATLAS-3782:
-
Fix Version/s: 2.2.0

> Support NOT_CONTAINS operator in basic search with search parameters
> 
>
> Key: ATLAS-3782
> URL: https://issues.apache.org/jira/browse/ATLAS-3782
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Andreas Danckert
>Assignee: Pinal
>Priority: Minor
>  Labels: BasicSearch
> Fix For: 3.0.0, 2.2.0
>
>
> The operator 'SearchParameters.Operator.NOT_CONTAINS' is defined and 
> implemented in SearchProcessors. It would allow a search of entities that do 
> not contain in given string in a specified attribute (eg exclude entities 
> from search that contain 'temp' in the qualified name). 
> However, this operator is currently ignored when used in REST calls and thus 
> not effective. Presumably the reason for this behaviour is that the operator 
> is not listed as case value in any of the switch statements on the search 
> operator in SearchProcessor.java.
>  



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


[jira] [Updated] (ATLAS-3848) Quick Search : Incorrect aggregation metrics

2020-08-27 Thread Pinal (Jira)


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

Pinal updated ATLAS-3848:
-
Fix Version/s: 2.2.0

> Quick Search : Incorrect aggregation metrics
> 
>
> Key: ATLAS-3848
> URL: https://issues.apache.org/jira/browse/ATLAS-3848
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: quicksearch
> Fix For: 3.0.0, 2.2.0
>
>
> Below scenarios doesn't result correct aggregation metrics in quick search
>  * when filtered with System Attributes
>  * when filtered with more than one filters
>  * when filtered with negation operators
>  * need to support _customAttributes 



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


[jira] [Commented] (ATLAS-3844) Ignore relationship attributes while fetching entities in Import Hive bridge.

2020-08-27 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3844:


Commit 260f06645d95474209d433c78086c07e25c20dc2 in atlas's branch 
refs/heads/branch-2.0 from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=260f066 ]

ATLAS-3844 - Ignore relationship attributes while fetching entities in Import 
Hive bridge.

Change-Id: I1d0eeb478286e896af733b51fe4f7fc62c594899
(cherry picked from commit cea851c5513cede054bc7704ac24c04cc498cd32)


> Ignore relationship attributes while fetching entities in Import Hive bridge.
> -
>
> Key: ATLAS-3844
> URL: https://issues.apache.org/jira/browse/ATLAS-3844
> Project: Atlas
>  Issue Type: Improvement
>  Components: hive-integration
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 
> 0001-ATLAS-3844-Ignore-relationship-attributes-while-fetc.patch, 
> ATLAS-3844-Testcase-Fix-Ignore-relationship-attributes-while-fetc.patch
>
>
> Currently in Import Hive bridge, the hive_db and hive_table entities are 
> fetched along relationshipAttributes and related Attributes and this 
> attributes are cleared thereafter.
> Instead fetching relationshipAttributes and related Attributes in response, 
> it is will good to ignoreRelationship to reduce the size of response payload.



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


[jira] [Commented] (ATLAS-3892) Basic search enhanced Feature - Search history

2020-08-27 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3892:


Commit a89479e77c77d82810badc51115d59789ed35af4 in atlas's branch 
refs/heads/branch-2.0 from chaitali borole
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=a89479e ]

ATLAS-3892 : Basic search enhanced Feature - Search history

Signed-off-by: kevalbhatt 
(cherry picked from commit 1b41b980415961419bb4af8710bd82f34395779c)


> Basic search enhanced Feature - Search history 
> ---
>
> Key: ATLAS-3892
> URL: https://issues.apache.org/jira/browse/ATLAS-3892
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> Feature to provide filters for better searching abilities : 
> Date Range feature with 6 different filters :
> 1.last 7 days.
> 2.Last month.
> 3.Last 30 days.
> 4.Today.
> 5.Yesterday.
> 6.Custom Range.
> 7.This Month.



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


[jira] [Commented] (ATLAS-3724) Qualified name pattern for Column cause ambiguity in Quickstart data.

2020-08-27 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3724:


Commit 1105e23e63a7ed0f59ead5d4168523f41e8aff5f in atlas's branch 
refs/heads/branch-2.0 from chaitali borole
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1105e23 ]

ATLAS-3724 : Update Qualified name pattern for Column since it cause ambiguity 
in Quickstart data.

Signed-off-by: nixonrodrigues 
(cherry picked from commit 9d597f249bc222d362dd96921ed3254579e8fc1b)


> Qualified name pattern for Column cause ambiguity in Quickstart data.
> -
>
> Key: ATLAS-3724
> URL: https://issues.apache.org/jira/browse/ATLAS-3724
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0, 2.1.0, 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 2.0.0, 2.2.0
>
> Attachments: ATLAS-3724.patch
>
>
> 1) Create Entity of type Column name = app_id, qualified name = app_id@cl1
> assign Table - logging_fact_monthly_mv
> 2) Again Create same entity with same qualified name
> assign different Table - log_fact_daily_mv
> 3) Check Column Relationship, Only one Table relationship is seen
> 4) Check Table (logging_fact_monthly_mv,log_fact_daily_mv) In Both 
> Relationship, Column app_id is seen



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


[jira] [Commented] (ATLAS-3844) Ignore relationship attributes while fetching entities in Import Hive bridge.

2020-08-27 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3844:


Commit af8bd8a76e0f366f8fda2f46ab9a6257013fad06 in atlas's branch 
refs/heads/branch-2.0 from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=af8bd8a ]

ATLAS-3844 - Ignore relationship attributes while fetching entities in Import 
Hive bridge. (UT fix) #2

(cherry picked from commit 682d16dd19cb72d36af9798811ed701ecdc0dacf)


> Ignore relationship attributes while fetching entities in Import Hive bridge.
> -
>
> Key: ATLAS-3844
> URL: https://issues.apache.org/jira/browse/ATLAS-3844
> Project: Atlas
>  Issue Type: Improvement
>  Components: hive-integration
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 
> 0001-ATLAS-3844-Ignore-relationship-attributes-while-fetc.patch, 
> ATLAS-3844-Testcase-Fix-Ignore-relationship-attributes-while-fetc.patch
>
>
> Currently in Import Hive bridge, the hive_db and hive_table entities are 
> fetched along relationshipAttributes and related Attributes and this 
> attributes are cleared thereafter.
> Instead fetching relationshipAttributes and related Attributes in response, 
> it is will good to ignoreRelationship to reduce the size of response payload.



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


[jira] [Commented] (ATLAS-3833) Packaging for atlas index repair tool

2020-08-27 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3833:


Commit dbc1865a78138318a0753d4e7d52b5591796f4ff in atlas's branch 
refs/heads/branch-2.0 from chaitali borole
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=dbc1865 ]

ATLAS-3833 : Packaging for atlas index repair tool

Signed-off-by: nixonrodrigues 
(cherry picked from commit e691a32c2d3888c99757e6aa31694ec8d14c2d48)


> Packaging for atlas index repair tool 
> --
>
> Key: ATLAS-3833
> URL: https://issues.apache.org/jira/browse/ATLAS-3833
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Attachments: ATLAS-3833-1.patch
>
>
> Packaging for atlas repair index was missing in Apache master build:
> Added descriptor in pom.xml for atlas-repair-index-package.xml
> Added readme
> Added atlas-repair-index-package.xml



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


[jira] [Commented] (ATLAS-3855) Bulk entity tag association and bulk api enhancement

2020-08-27 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3855:


Commit df58d1ae782ede4b2ee69b1bf6cfba62c604d914 in atlas's branch 
refs/heads/branch-2.0 from chaitali borole
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=df58d1a ]

ATLAS-3855 :- Bulk entity tag association and bulk api enhancement, 
authorization fix.

Signed-off-by: nixonrodrigues 
(cherry picked from commit 06cd0cb35a285b3c4a7b0b3c662ce7263848f7b6)


> Bulk entity tag association and bulk api enhancement
> 
>
> Key: ATLAS-3855
> URL: https://issues.apache.org/jira/browse/ATLAS-3855
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>  Labels: api-change
> Fix For: 2.2.0
>
>
> API : /api/atlas/v2/entity/bulk/classification
> Body :
> {code:java}
> {"classification":{"typeName":"PII","attributes":{},"propagate":true,"removePropagationsOnEntityDelete":false,"validityPeriods":[]},"entityGuids":["guid1","guid2"]}
>  {code}
> when user doesn't have authorisation on either of guid1 or guid2 , the bulk 
> entity call fails with 403. 
> bulk api _v2/entity/bulk_ to retrieve a list of entities identified by its 
> guids.
> This bulk api fails with 403 if some guids belong to entities on which user 
> is *unauthorized* and other guids belong to entities on which user is 
> *authorized*.



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


[jira] [Commented] (ATLAS-3920) Harmonize joda-time to version 2.10.latest

2020-08-27 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3920:


Commit b18ebd26973d9cc0311511b7e7795175a63630a1 in atlas's branch 
refs/heads/branch-2.0 from mayanknj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b18ebd2 ]

ATLAS-3920 : Update joda-time to version 2.10.latest.

Signed-off-by: nixonrodrigues 
(cherry picked from commit 41e1039bd66829683e9b24f10186bde53a83d7ad)


> Harmonize joda-time to version 2.10.latest
> --
>
> Key: ATLAS-3920
> URL: https://issues.apache.org/jira/browse/ATLAS-3920
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mayank Jain
>Priority: Major
>
> Atlas currently uses outdated joda-time versions, which can cause issues. To 
> avoid issue we need to update it to the latest version of joda-time.



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


[jira] [Assigned] (ATLAS-2932) Update DSL to use Java Traversal API

2020-08-27 Thread Ashutosh Mestry (Jira)


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

Ashutosh Mestry reassigned ATLAS-2932:
--

Assignee: Ashutosh Mestry  (was: Apoorv Naik)

> Update DSL to use Java Traversal API
> 
>
> Key: ATLAS-2932
> URL: https://issues.apache.org/jira/browse/ATLAS-2932
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0, trunk
>Reporter: Apoorv Naik
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: 
> 0002-ATLAS-2932-Update-DSL-to-use-Tinkerpop-Java-APIs-ins.patch
>
>
> Change DSL code to use Java Tinkerpop Traversals instead of 
> GremlinScriptEngine



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


[jira] [Commented] (ATLAS-3880) BasicSearch: Multiple type/tag: Log invalid and allow searching valid type/tag names

2020-08-27 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3880:


Commit 2a7d321119cd60f5adb08ea9fa10d0baa3bd662b in atlas's branch 
refs/heads/branch-2.0 from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2a7d321 ]

ATLAS-3880 : BasicSearch: Multiple type/tag: Log invalid and allow searching 
valid type/tag names

Signed-off-by: nixonrodrigues 
(cherry picked from commit f690755f79f9696e3214b9a3f158977b3bd5f4a7)


> BasicSearch: Multiple type/tag: Log invalid and allow searching valid 
> type/tag names
> 
>
> Key: ATLAS-3880
> URL: https://issues.apache.org/jira/browse/ATLAS-3880
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch, MultipleType/Tag
> Fix For: 3.0.0
>
>
> If in basic search, request has combination of valid and invalid 
> typename/tags, allow searching for valid type names/tag names.
> Example:
> typeName:"valid,invalid"
> Allow searching entities for valid type.



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


[jira] [Commented] (ATLAS-3838) Support multiple tag/classification in basic/quick search API

2020-08-27 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3838:


Commit 01d8c3abffd053024ed530a4686812fe2de5777f in atlas's branch 
refs/heads/branch-2.0 from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=01d8c3a ]

ATLAS-3838: Support multiple tag/classification in basic/quick search API
ATLAS-3652: Quick Search: API requirement for GET request on multiple entity 
types

Signed-off-by: Sarath Subramanian 

both JIRA's addressed in the same commit.

(cherry picked from commit 8b5cb9d9aa9f977ba5dfc455dfe440dd55eace06)


> Support multiple tag/classification in basic/quick search API
> -
>
> Key: ATLAS-3838
> URL: https://issues.apache.org/jira/browse/ATLAS-3838
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 3.0.0
>
>
> it will allow user to search with multiple tags and the tag attribute filters 
> (attribute should System attributes or attribute which common for all the 
> mentioned tags)
>  
> *Use Case**: Multiple tags with its attribute filters*
> *How And Validations:*
>  # Search Results can be filtered with multiple tag by 'comma' seperated 
> string of tags in the request
> Eg. "classification": "tag1,tag2".
>  # For the attribute filters, attribute in the criteria should be System 
> attribute like "created by user, last modified time" or the attribute should 
> present in both the typeDefs of the mentioned classification 'tag1' and 
> 'tag2'. (Common attributes like name).
>  # Curently we support Classifications like _ALL_CLASSIFICATION_TYPES, 
> _NOT_CLASSIFIED So if the request have any builtin classifications with the 
> normal tags, preference will be given to it in the below order
> _NOT_CLASSIFIED > _ALL_CLASSIFICATION_TYPES = _CLASSIFIED = 
> WILDCARD_CLASSIFICATIONS(*) > tag1 = tag2
> Eg. "classification" : "tag1,_CLASSIFIED" , search results will be according 
> to _CLASSIFIED
>  # Classification supports wildcard search too Eg. tag*, So if the request 
> has wildcard tag , tag filters will not apply to it.



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


[jira] [Commented] (ATLAS-3652) Quick Search: API requirement for GET request on multiple entity types

2020-08-27 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3652:


Commit 01d8c3abffd053024ed530a4686812fe2de5777f in atlas's branch 
refs/heads/branch-2.0 from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=01d8c3a ]

ATLAS-3838: Support multiple tag/classification in basic/quick search API
ATLAS-3652: Quick Search: API requirement for GET request on multiple entity 
types

Signed-off-by: Sarath Subramanian 

both JIRA's addressed in the same commit.

(cherry picked from commit 8b5cb9d9aa9f977ba5dfc455dfe440dd55eace06)


> Quick Search: API requirement for GET request on multiple entity types
> --
>
> Key: ATLAS-3652
> URL: https://issues.apache.org/jira/browse/ATLAS-3652
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: quicksearch
> Fix For: 3.0.0
>
>
> Need an API that can be used to GET information of multiple selected entity 
> types. Currently it seems to support GET request for
>  # One type (typeName=someType)\{by specifying typeName in the call},
>  OR 
>  # All types (typeName= )\{by leaving out typeName empty}.
>   
>  Need an API that works for multiple selected types while also returning the 
> aggregationMetrics in the responseJSON as opposed to the POST call(where the 
> aggregationMetrics is left out as empty).
>  
> *UseCase:* Multiple Entity types with its attribute filters
> *How And Validations:*
> 1. Search Results can be filtered with multiple entity types by 'comma' 
> seperated string of entity typeName in the request
> Eg. "typeName": "hive_table,hive_db".
> 2. For the attribute filters, attribute in the criteria should be System 
> attribute like "created by user, last modified time" or the attribute should 
> present in both the typeDefs of the mentioned entity 'hive_table' and 
> 'hive_db'. (Common attributes like name).



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


[jira] [Commented] (ATLAS-3888) BasicSearch: Multiple type/tag: [Regression], Restrict when tag filters and regex in tag

2020-08-27 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3888:


Commit e97fb302231a3b452d99cd892a75a09b9499d24a in atlas's branch 
refs/heads/branch-2.0 from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e97fb30 ]

ATLAS-3888 : BasicSearch: Multiple type/tag: [Regression], Restrict when tag 
filters and regex in tag

Signed-off-by: nixonrodrigues 
(cherry picked from commit d9d0e8c2abe293a520f89b85015d9c52985e28cb)


> BasicSearch: Multiple type/tag: [Regression], Restrict when tag filters and 
> regex in tag 
> -
>
> Key: ATLAS-3888
> URL: https://issues.apache.org/jira/browse/ATLAS-3888
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch, MultipleType/Tag
> Fix For: 3.0.0
>
>
> In Basic search ,
> tag : PII_*
> tag filter : sensitivity < 0.5 
> returns 200 OK with no entities in response though there are entities tagged 
> with PII_1 with sensitivity < 0.5
>  
> Expected is 400 Bad request , as tag filters are not allowed when the tag has 
> regex.
>  



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


[jira] [Commented] (ATLAS-3782) Support NOT_CONTAINS operator in basic search with search parameters

2020-08-27 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3782:


Commit 897c2fc19f342d6fb8832734ac698e442bf85b58 in atlas's branch 
refs/heads/branch-2.0 from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=897c2fc ]

ATLAS-3782 : Support NOT_CONTAINS operator in basic search

Signed-off-by: nixonrodrigues 
(cherry picked from commit 9a067d38e27fc2255647133373b952a6a64ed1a4)


> Support NOT_CONTAINS operator in basic search with search parameters
> 
>
> Key: ATLAS-3782
> URL: https://issues.apache.org/jira/browse/ATLAS-3782
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Andreas Danckert
>Assignee: Pinal
>Priority: Minor
>  Labels: BasicSearch
> Fix For: 3.0.0
>
>
> The operator 'SearchParameters.Operator.NOT_CONTAINS' is defined and 
> implemented in SearchProcessors. It would allow a search of entities that do 
> not contain in given string in a specified attribute (eg exclude entities 
> from search that contain 'temp' in the qualified name). 
> However, this operator is currently ignored when used in REST calls and thus 
> not effective. Presumably the reason for this behaviour is that the operator 
> is not listed as case value in any of the switch statements on the search 
> operator in SearchProcessor.java.
>  



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


[jira] [Commented] (ATLAS-3848) Quick Search : Incorrect aggregation metrics

2020-08-27 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3848:


Commit 11b73ee0a58e93bb2df78d15dac7b850a60ac799 in atlas's branch 
refs/heads/branch-2.0 from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=11b73ee ]

ATLAS-3848 : Quick Search : Fixed incorrect aggregation metrics

Signed-off-by: nixonrodrigues 
(cherry picked from commit aa86d62c057d56f858dc7962aa158d23c82f972b)


> Quick Search : Incorrect aggregation metrics
> 
>
> Key: ATLAS-3848
> URL: https://issues.apache.org/jira/browse/ATLAS-3848
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: quicksearch
> Fix For: 3.0.0
>
>
> Below scenarios doesn't result correct aggregation metrics in quick search
>  * when filtered with System Attributes
>  * when filtered with more than one filters
>  * when filtered with negation operators
>  * need to support _customAttributes 



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


[jira] [Updated] (ATLAS-3931) Basic Search: Get total count of referred entities

2020-08-27 Thread Pinal (Jira)


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

Pinal updated ATLAS-3931:
-
Description: 
With this feature, While searching the entities we will get information of its 
referred entities like total count.
 Example: on searching entities of hive_table, in addition with hive_table 
details, we can also get total number of columns associated to particular 
hive_table.

  was:
With this feature, While searching the entities we will get information of its 
referred entities like total count.
Example: on searching entities of hive_table, in addition with hive_table 
metadata, we can also get total number of columns associated to particular 
hive_table.


> Basic Search: Get total count of referred entities
> --
>
> Key: ATLAS-3931
> URL: https://issues.apache.org/jira/browse/ATLAS-3931
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> With this feature, While searching the entities we will get information of 
> its referred entities like total count.
>  Example: on searching entities of hive_table, in addition with hive_table 
> details, we can also get total number of columns associated to particular 
> hive_table.



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


[jira] [Created] (ATLAS-3931) Basic Search: Get total count of referred entities

2020-08-27 Thread Pinal (Jira)
Pinal created ATLAS-3931:


 Summary: Basic Search: Get total count of referred entities
 Key: ATLAS-3931
 URL: https://issues.apache.org/jira/browse/ATLAS-3931
 Project: Atlas
  Issue Type: Improvement
Reporter: Pinal
Assignee: Pinal


With this feature, While searching the entities we will get information of its 
referred entities like total count.
Example: on searching entities of hive_table, in addition with hive_table 
metadata, we can also get total number of columns associated to particular 
hive_table.



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