[jira] [Updated] (ATLAS-3949) Relationship search API, add parameter to get classification attributes in search results

2020-09-27 Thread Pinal (Jira)


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

Pinal updated ATLAS-3949:
-
Fix Version/s: (was: 2.1.0)
   2.2.0
   3.0.0

> Relationship search API, add parameter to get classification attributes in 
> search results
> -
>
> Key: ATLAS-3949
> URL: https://issues.apache.org/jira/browse/ATLAS-3949
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> *Improvement:* Adding boolean parameter 'includeClassificationAttributes' in 
> Relationship search Api to get all attributes of the classification 
> associated to the entity.
> *Example Request api:* 
> /api/atlas/v2/search/relationship?guid=\{guid}=tables=10=true
> *Example Response api:* 
> {code:java}
> {
>"queryType":"RELATIONSHIP",
>"entities":[
>   {
>  "typeName":"hive_table",
>  "attributes":{
> "createTime":160062660,
> "qualifiedName":"table@db1",
> "name":"table1"
>  },
>  "guid":"9893504f-095d-47e3-abf8-fd79069252f7",
>  "status":"ACTIVE",
>  "displayText":"table1",
>  "classificationNames":[
> "Dimension"
>  ],
>  "classifications":[
> {
>"typeName":"Dimension",
>"entityGuid":"9893504f-095d-47e3-abf8-fd79069252f7",
>"entityStatus":"ACTIVE",
>"propagate":true,
>"validityPeriods":[
>   
>],
>"removePropagationsOnEntityDelete":false
> }
>  ],
>  "meaningNames":[
> 
>  ],
>  "meanings":[
> 
>  ],
>  "isIncomplete":false,
>  "labels":[
> 
>  ]
>   }
>],
>"approximateCount":-1
> }
> {code}



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


[jira] [Updated] (ATLAS-3949) Relationship search API, add parameter to get classification attributes in search results

2020-09-27 Thread Pinal (Jira)


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

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

> Relationship search API, add parameter to get classification attributes in 
> search results
> -
>
> Key: ATLAS-3949
> URL: https://issues.apache.org/jira/browse/ATLAS-3949
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0
>
>
> *Improvement:* Adding boolean parameter 'includeClassificationAttributes' in 
> Relationship search Api to get all attributes of the classification 
> associated to the entity.
> *Example Request api:* 
> /api/atlas/v2/search/relationship?guid=\{guid}=tables=10=true
> *Example Response api:* 
> {code:java}
> {
>"queryType":"RELATIONSHIP",
>"entities":[
>   {
>  "typeName":"hive_table",
>  "attributes":{
> "createTime":160062660,
> "qualifiedName":"table@db1",
> "name":"table1"
>  },
>  "guid":"9893504f-095d-47e3-abf8-fd79069252f7",
>  "status":"ACTIVE",
>  "displayText":"table1",
>  "classificationNames":[
> "Dimension"
>  ],
>  "classifications":[
> {
>"typeName":"Dimension",
>"entityGuid":"9893504f-095d-47e3-abf8-fd79069252f7",
>"entityStatus":"ACTIVE",
>"propagate":true,
>"validityPeriods":[
>   
>],
>"removePropagationsOnEntityDelete":false
> }
>  ],
>  "meaningNames":[
> 
>  ],
>  "meanings":[
> 
>  ],
>  "isIncomplete":false,
>  "labels":[
> 
>  ]
>   }
>],
>"approximateCount":-1
> }
> {code}



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


[jira] [Updated] (ATLAS-3949) Relationship search API, add parameter to get classification attributes in search results

2020-09-21 Thread Pinal (Jira)


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

Pinal updated ATLAS-3949:
-
Description: 
*Improvement:* Adding boolean parameter 'includeClassificationAttributes' in 
Relationship search Api to get all attributes of the classification associated 
to the entity.

*Example Request api:* 
/api/atlas/v2/search/relationship?guid=\{guid}=tables=10=true

*Example Response api:* 
{code:java}
{
   "queryType":"RELATIONSHIP",
   "entities":[
  {
 "typeName":"hive_table",
 "attributes":{
"createTime":160062660,
"qualifiedName":"table@db1",
"name":"table1"
 },
 "guid":"9893504f-095d-47e3-abf8-fd79069252f7",
 "status":"ACTIVE",
 "displayText":"table1",
 "classificationNames":[
"Dimension"
 ],
 "classifications":[
{
   "typeName":"Dimension",
   "entityGuid":"9893504f-095d-47e3-abf8-fd79069252f7",
   "entityStatus":"ACTIVE",
   "propagate":true,
   "validityPeriods":[
  
   ],
   "removePropagationsOnEntityDelete":false
}
 ],
 "meaningNames":[

 ],
 "meanings":[

 ],
 "isIncomplete":false,
 "labels":[

 ]
  }
   ],
   "approximateCount":-1
}
{code}

  was:
*Improvement:* Adding boolean parameter 'includeClassificationAttributes' in 
Relationship search Api to get all attributes of the classification associated 
to the entity.

*Example Request api:* 
/api/atlas/v2/search/relationship?guid=\{guid}=tables=10=true

Example Response api: 


{code:java}
{
   "queryType":"RELATIONSHIP",
   "entities":[
  {
 "typeName":"hive_table",
 "attributes":{
"createTime":160062660,
"qualifiedName":"table@db1",
"name":"table1"
 },
 "guid":"9893504f-095d-47e3-abf8-fd79069252f7",
 "status":"ACTIVE",
 "displayText":"table1",
 "classificationNames":[
"Dimension"
 ],
 "classifications":[
{
   "typeName":"Dimension",
   "entityGuid":"9893504f-095d-47e3-abf8-fd79069252f7",
   "entityStatus":"ACTIVE",
   "propagate":true,
   "validityPeriods":[
  
   ],
   "removePropagationsOnEntityDelete":false
}
 ],
 "meaningNames":[

 ],
 "meanings":[

 ],
 "isIncomplete":false,
 "labels":[

 ]
  }
   ],
   "approximateCount":-1
}
{code}


> Relationship search API, add parameter to get classification attributes in 
> search results
> -
>
> Key: ATLAS-3949
> URL: https://issues.apache.org/jira/browse/ATLAS-3949
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> *Improvement:* Adding boolean parameter 'includeClassificationAttributes' in 
> Relationship search Api to get all attributes of the classification 
> associated to the entity.
> *Example Request api:* 
> /api/atlas/v2/search/relationship?guid=\{guid}=tables=10=true
> *Example Response api:* 
> {code:java}
> {
>"queryType":"RELATIONSHIP",
>"entities":[
>   {
>  "typeName":"hive_table",
>  "attributes":{
> "createTime":160062660,
> "qualifiedName":"table@db1",
> "name":"table1"
>  },
>  "guid":"9893504f-095d-47e3-abf8-fd79069252f7",
>  "status":"ACTIVE",
>  "displayText":"table1",
>  "classificationNames":[
> "Dimension"
>  ],
>  "classifications":[
> {
>"typeName":"Dimension",
>"entityGuid":"9893504f-095d-47e3-abf8-fd79069252f7",
>"entityStatus":"ACTIVE",
>"propagate":true,
>"validityPeriods":[
>   
>],
>"removePropagationsOnEntityDelete":false
> }
>  ],
>  "meaningNames":[
> 
>  ],
>  "meanings":[
> 
>  ],
>  "isIncomplete":false,
>  "labels":[
> 
>  ]
>   }
>],
>"approximateCount":-1
> }
> {code}



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


[jira] [Updated] (ATLAS-3949) Relationship search API, add parameter to get classification attributes in search results

2020-09-21 Thread Pinal (Jira)


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

Pinal updated ATLAS-3949:
-
Description: 
*Improvement:* Adding boolean parameter 'includeClassificationAttributes' in 
Relationship search Api to get all attributes of the classification associated 
to the entity.

*Example Request api:* 
/api/atlas/v2/search/relationship?guid=\{guid}=tables=10=true

Example Response api: 


{code:java}
{
   "queryType":"RELATIONSHIP",
   "entities":[
  {
 "typeName":"hive_table",
 "attributes":{
"createTime":160062660,
"qualifiedName":"table@db1",
"name":"table1"
 },
 "guid":"9893504f-095d-47e3-abf8-fd79069252f7",
 "status":"ACTIVE",
 "displayText":"table1",
 "classificationNames":[
"Dimension"
 ],
 "classifications":[
{
   "typeName":"Dimension",
   "entityGuid":"9893504f-095d-47e3-abf8-fd79069252f7",
   "entityStatus":"ACTIVE",
   "propagate":true,
   "validityPeriods":[
  
   ],
   "removePropagationsOnEntityDelete":false
}
 ],
 "meaningNames":[

 ],
 "meanings":[

 ],
 "isIncomplete":false,
 "labels":[

 ]
  }
   ],
   "approximateCount":-1
}
{code}

> Relationship search API, add parameter to get classification attributes in 
> search results
> -
>
> Key: ATLAS-3949
> URL: https://issues.apache.org/jira/browse/ATLAS-3949
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> *Improvement:* Adding boolean parameter 'includeClassificationAttributes' in 
> Relationship search Api to get all attributes of the classification 
> associated to the entity.
> *Example Request api:* 
> /api/atlas/v2/search/relationship?guid=\{guid}=tables=10=true
> Example Response api: 
> {code:java}
> {
>"queryType":"RELATIONSHIP",
>"entities":[
>   {
>  "typeName":"hive_table",
>  "attributes":{
> "createTime":160062660,
> "qualifiedName":"table@db1",
> "name":"table1"
>  },
>  "guid":"9893504f-095d-47e3-abf8-fd79069252f7",
>  "status":"ACTIVE",
>  "displayText":"table1",
>  "classificationNames":[
> "Dimension"
>  ],
>  "classifications":[
> {
>"typeName":"Dimension",
>"entityGuid":"9893504f-095d-47e3-abf8-fd79069252f7",
>"entityStatus":"ACTIVE",
>"propagate":true,
>"validityPeriods":[
>   
>],
>"removePropagationsOnEntityDelete":false
> }
>  ],
>  "meaningNames":[
> 
>  ],
>  "meanings":[
> 
>  ],
>  "isIncomplete":false,
>  "labels":[
> 
>  ]
>   }
>],
>"approximateCount":-1
> }
> {code}



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


[jira] [Created] (ATLAS-3949) Relationship search API, add parameter to get classification attributes in search results

2020-09-21 Thread Pinal (Jira)
Pinal created ATLAS-3949:


 Summary: Relationship search API, add parameter to get 
classification attributes in search results
 Key: ATLAS-3949
 URL: https://issues.apache.org/jira/browse/ATLAS-3949
 Project: Atlas
  Issue Type: Improvement
  Components: atlas-intg
Reporter: Pinal
Assignee: Pinal






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


[jira] [Created] (ATLAS-3938) Import Hive Script: Support deletion of non existing database and table entities

2020-09-11 Thread Pinal (Jira)
Pinal created ATLAS-3938:


 Summary: Import Hive Script:  Support deletion of non existing 
database and table entities
 Key: ATLAS-3938
 URL: https://issues.apache.org/jira/browse/ATLAS-3938
 Project: Atlas
  Issue Type: Improvement
Reporter: Pinal
Assignee: Pinal


*Problem* : Whenever database or table is dropped in hive, and HiveHook is not 
enabled, we dont have anyway to get the database and table sync with hive.

*Workaround* : Added support to delete database and table entities present in 
Atlas, but not in Hive.

*Usage* : ./import-hive.sh -deleteNonExisting

*NOTE : atlas.hook.hive.page.limit* property is added to configure the 
pageSize/limit while fetching entities from Atlas



--
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:
-
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] [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)


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

2020-08-05 Thread Pinal (Jira)


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

Pinal updated ATLAS-3876:
-
Description: 
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

  was:
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}


> 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
>
>
> 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-3848) Quick Search : Incorrect aggregation metrics

2020-07-26 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: (was: 2.1.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
>
>
> 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] [Created] (ATLAS-3888) BasicSearch: Multiple type/tag: [Regression], Restrict when tag filters and regex in tag

2020-07-10 Thread Pinal (Jira)
Pinal created ATLAS-3888:


 Summary: 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
 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-3844) Ignore relationship attributes while fetching entities in Import Hive bridge.

2020-07-08 Thread Pinal (Jira)


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

Pinal commented on ATLAS-3844:
--

patch looks good, +1 for the patch.

> 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] [Created] (ATLAS-3880) BasicSearch: Multiple type/tag: Log invalid and allow searching valid type/tag names

2020-07-07 Thread Pinal (Jira)
Pinal created ATLAS-3880:


 Summary: 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


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-3876) Relationship Search API not showing correct approximateCount

2020-07-06 Thread Pinal (Jira)


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

Pinal updated ATLAS-3876:
-
Labels: Relationships  (was: )

> 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
>
> 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}



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


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

2020-07-05 Thread Pinal (Jira)
Pinal created ATLAS-3876:


 Summary: 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


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}



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


[jira] [Updated] (ATLAS-3867) Relationship search API should have a provision to fetch custom attributes in search results

2020-07-02 Thread Pinal (Jira)


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

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

> Relationship search API should have a provision to fetch custom attributes in 
> search results
> 
>
> Key: ATLAS-3867
> URL: https://issues.apache.org/jira/browse/ATLAS-3867
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: Relationships
> Fix For: 2.1.0, 3.0.0
>
>
> {code:java}
> /v2/search/relationship?guid=ac9e04cc-f927-4334-af08-c83bc3733f5b=__hive_table.columns=name=ASCENDING
> {code}
> The response of the  above API contains below attributes only:
> {code:java}
> "attributes": {
> "owner": "hive",
> "qualifiedName": "ho.us_customers.age@cm",
> "name": "age"
>   },{code}
>  Is it possible to fetch a custom attribute "*dcProfiledData*" present in 
> Technical properties of the entity detailed page.



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


[jira] [Updated] (ATLAS-3867) Relationship search API should have a provision to fetch custom attributes in search results

2020-07-01 Thread Pinal (Jira)


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

Pinal updated ATLAS-3867:
-
Fix Version/s: 3.0.0

> Relationship search API should have a provision to fetch custom attributes in 
> search results
> 
>
> Key: ATLAS-3867
> URL: https://issues.apache.org/jira/browse/ATLAS-3867
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: Relationships
> Fix For: 3.0.0
>
>
> {code:java}
> /v2/search/relationship?guid=ac9e04cc-f927-4334-af08-c83bc3733f5b=__hive_table.columns=name=ASCENDING
> {code}
> The response of the  above API contains below attributes only:
> {code:java}
> "attributes": {
> "owner": "hive",
> "qualifiedName": "ho.us_customers.age@cm",
> "name": "age"
>   },{code}
>  Is it possible to fetch a custom attribute "*dcProfiledData*" present in 
> Technical properties of the entity detailed page.



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


[jira] [Updated] (ATLAS-3867) Relationship search API should have a provision to fetch custom attributes in search results

2020-06-29 Thread Pinal (Jira)


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

Pinal updated ATLAS-3867:
-
Issue Type: Improvement  (was: Bug)

> Relationship search API should have a provision to fetch custom attributes in 
> search results
> 
>
> Key: ATLAS-3867
> URL: https://issues.apache.org/jira/browse/ATLAS-3867
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: Relationships
>
> {code:java}
> /v2/search/relationship?guid=ac9e04cc-f927-4334-af08-c83bc3733f5b=__hive_table.columns=name=ASCENDING
> {code}
> The response of the  above API contains below attributes only:
> {code:java}
> "attributes": {
> "owner": "hive",
> "qualifiedName": "ho.us_customers.age@cm",
> "name": "age"
>   },{code}
>  Is it possible to fetch a custom attribute "*dcProfiledData*" present in 
> Technical properties of the entity detailed page.



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


[jira] [Created] (ATLAS-3867) Relationship search API should have a provision to fetch all the attributes

2020-06-29 Thread Pinal (Jira)
Pinal created ATLAS-3867:


 Summary: Relationship search API should have a provision to fetch 
all the attributes
 Key: ATLAS-3867
 URL: https://issues.apache.org/jira/browse/ATLAS-3867
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core, atlas-intg
Affects Versions: 2.0.0
Reporter: Pinal
Assignee: Pinal


{code:java}
/v2/search/relationship?guid=ac9e04cc-f927-4334-af08-c83bc3733f5b=__hive_table.columns=name=ASCENDING
{code}
The response of the  above API contains below attributes only:
{code:java}
"attributes": {
"owner": "hive",
"qualifiedName": "ho.us_customers.age@cm",
"name": "age"
  },{code}
 Is it possible to fetch a custom attribute "*dcProfiledData*" present in 
Technical properties of the entity detailed page.



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


[jira] [Updated] (ATLAS-3867) Relationship search API should have a provision to fetch custom attributes in search results

2020-06-29 Thread Pinal (Jira)


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

Pinal updated ATLAS-3867:
-
Summary: Relationship search API should have a provision to fetch custom 
attributes in search results  (was: Relationship search API should have a 
provision to fetch all the attributes)

> Relationship search API should have a provision to fetch custom attributes in 
> search results
> 
>
> Key: ATLAS-3867
> URL: https://issues.apache.org/jira/browse/ATLAS-3867
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: Relationships
>
> {code:java}
> /v2/search/relationship?guid=ac9e04cc-f927-4334-af08-c83bc3733f5b=__hive_table.columns=name=ASCENDING
> {code}
> The response of the  above API contains below attributes only:
> {code:java}
> "attributes": {
> "owner": "hive",
> "qualifiedName": "ho.us_customers.age@cm",
> "name": "age"
>   },{code}
>  Is it possible to fetch a custom attribute "*dcProfiledData*" present in 
> Technical properties of the entity detailed page.



--
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-06-29 Thread Pinal (Jira)


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

Pinal updated ATLAS-3652:
-
Description: 
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).

  was:
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).
 


> 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] [Updated] (ATLAS-3838) Support multiple tag/classification in basic/quick search API

2020-06-29 Thread Pinal (Jira)


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

Pinal updated ATLAS-3838:
-
Description: 
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.

  was: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)


> 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-06-29 Thread Pinal (Jira)


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

Pinal commented on ATLAS-3652:
--

This patch is included in ATLAS-3838

> 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: 2.1.0, 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).
>  



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


[jira] [Updated] (ATLAS-3866) Relationship search API for hive storage desc throws error code 500

2020-06-28 Thread Pinal (Jira)


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

Pinal updated ATLAS-3866:
-
Description: 
Tried below API of ATLAS
{code:java}
v2/search/relationship?limit=10=0=3e424245-0676-4d47-96a1-e17228b38367=__hive_table.sd=name=ASCENDING=true{code}
error Response:
{code:java}
{
  "errorCode": "ATLAS-500-00-001",
  "errorMessage": "Internal server error Relationship search query failed"
}
{code}
 

*Cause of issue:* 
 Above Request contains sortBy=name, 'name' attribute is not in 
hive_storagedesc definition, hence the issue.
 Also if sortBy is not passed, default attribute is 'name'

  was:
Tried below API of ATLAS [CDH-7.2.0 runtime]
{code:java}
v2/search/relationship?limit=10=0=3e424245-0676-4d47-96a1-e17228b38367=__hive_table.sd=name=ASCENDING=true{code}
error Response:
{code:java}
{
  "errorCode": "ATLAS-500-00-001",
  "errorMessage": "Internal server error Relationship search query failed"
}
{code}
 

*Cause of issue:* 
 Above Request contains sortBy=name, 'name' attribute is not in 
hive_storagedesc definition, hence the issue.
 Also if sortBy is not passed, default attribute is 'name'


> Relationship search API for hive storage desc throws error code 500
> ---
>
> Key: ATLAS-3866
> URL: https://issues.apache.org/jira/browse/ATLAS-3866
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: Relationships
> Fix For: 2.1.0, 3.0.0
>
>
> Tried below API of ATLAS
> {code:java}
> v2/search/relationship?limit=10=0=3e424245-0676-4d47-96a1-e17228b38367=__hive_table.sd=name=ASCENDING=true{code}
> error Response:
> {code:java}
> {
>   "errorCode": "ATLAS-500-00-001",
>   "errorMessage": "Internal server error Relationship search query failed"
> }
> {code}
>  
> *Cause of issue:* 
>  Above Request contains sortBy=name, 'name' attribute is not in 
> hive_storagedesc definition, hence the issue.
>  Also if sortBy is not passed, default attribute is 'name'



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


[jira] [Created] (ATLAS-3866) Relationship search API for hive storage desc throws error code 500

2020-06-28 Thread Pinal (Jira)
Pinal created ATLAS-3866:


 Summary: Relationship search API for hive storage desc throws 
error code 500
 Key: ATLAS-3866
 URL: https://issues.apache.org/jira/browse/ATLAS-3866
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 2.0.0
Reporter: Pinal
Assignee: Pinal
 Fix For: 2.1.0, 3.0.0


Tried below API of ATLAS [CDH-7.2.0 runtime]
{code:java}
v2/search/relationship?limit=10=0=3e424245-0676-4d47-96a1-e17228b38367=__hive_table.sd=name=ASCENDING=true{code}
error Response:
{code:java}
{
  "errorCode": "ATLAS-500-00-001",
  "errorMessage": "Internal server error Relationship search query failed"
}
{code}
 

*Cause of issue:* 
 Above Request contains sortBy=name, 'name' attribute is not in 
hive_storagedesc definition, hence the issue.
 Also if sortBy is not passed, default attribute is 'name'



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


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

2020-06-25 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: 3.0.0
   2.1.0

> Quick Search : Incorrect aggregation metrics
> 
>
> Key: ATLAS-3848
> URL: https://issues.apache.org/jira/browse/ATLAS-3848
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: quicksearch
> Fix For: 2.1.0, 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-3848) Quick Search : Incorrect aggregation metrics

2020-06-25 Thread Pinal (Jira)


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

Pinal updated ATLAS-3848:
-
Component/s: atlas-intg
  atlas-core

> 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: 2.1.0, 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] [Created] (ATLAS-3850) Regression, Terms are not getting displayed

2020-06-19 Thread Pinal (Jira)
Pinal created ATLAS-3850:


 Summary: Regression, Terms are not getting displayed
 Key: ATLAS-3850
 URL: https://issues.apache.org/jira/browse/ATLAS-3850
 Project: Atlas
  Issue Type: Bug
Reporter: Pinal
Assignee: Pinal


For the entity E1 , if term T1@G1 is associated,

then while searching entity E1, Term is not displayed in the column of the 
basic search panel

"meanings":  in the response is empty



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


[jira] [Updated] (ATLAS-3850) Regression, Terms are not getting displayed

2020-06-19 Thread Pinal (Jira)


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

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

> Regression, Terms are not getting displayed
> ---
>
> Key: ATLAS-3850
> URL: https://issues.apache.org/jira/browse/ATLAS-3850
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> For the entity E1 , if term T1@G1 is associated,
> then while searching entity E1, Term is not displayed in the column of the 
> basic search panel
> "meanings":  in the response is empty



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


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

2020-06-18 Thread Pinal (Jira)
Pinal created ATLAS-3848:


 Summary: Quick Search : Incorrect aggregation metrics
 Key: ATLAS-3848
 URL: https://issues.apache.org/jira/browse/ATLAS-3848
 Project: Atlas
  Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Pinal
Assignee: Pinal


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-3838) Support multiple tag/classification in basic/quick search API

2020-06-15 Thread Pinal (Jira)


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

Pinal updated ATLAS-3838:
-
Description: 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)

> 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
>
> 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)



--
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-06-14 Thread Pinal (Jira)


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

Pinal updated ATLAS-3838:
-
Labels: BasicSearch  (was: )

> 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
>




--
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-06-14 Thread Pinal (Jira)


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

Pinal updated ATLAS-3838:
-
Affects Version/s: 2.0.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
>




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


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

2020-06-11 Thread Pinal (Jira)
Pinal created ATLAS-3838:


 Summary: 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
Reporter: Pinal
Assignee: Pinal






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


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

2020-06-09 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: (was: 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: 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-3823) BasicSearch: Incorrect warning for the Unsupported operator.

2020-06-03 Thread Pinal (Jira)


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

Pinal updated ATLAS-3823:
-
Summary: BasicSearch: Incorrect warning for the Unsupported operator.  
(was: BasicSearch: Warning for the Unsupported operator.)

> BasicSearch: Incorrect warning for the Unsupported operator.
> 
>
> Key: ATLAS-3823
> URL: https://issues.apache.org/jira/browse/ATLAS-3823
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0, 3.0.0
>
>
> For Some operator like notNull, isNull, there is incorrect warning message in 
> logs 'unsupported operator'.



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


[jira] [Updated] (ATLAS-3823) BasicSearch: Warning for the Unsupported operator.

2020-06-02 Thread Pinal (Jira)


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

Pinal updated ATLAS-3823:
-
Description: For Some operator like notNull, isNull, there is incorrect 
warning message in logs 'unsupported operator'.  (was: For Some operator like 
notNull, isNull, there is incorrect warning message 'unsupported operator'.)

> BasicSearch: Warning for the Unsupported operator.
> --
>
> Key: ATLAS-3823
> URL: https://issues.apache.org/jira/browse/ATLAS-3823
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0
>
>
> For Some operator like notNull, isNull, there is incorrect warning message in 
> logs 'unsupported operator'.



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


[jira] [Updated] (ATLAS-3823) BasicSearch: Warning for the Unsupported operator.

2020-06-02 Thread Pinal (Jira)


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

Pinal updated ATLAS-3823:
-
Description: For Some operator like notNull, isNull, there is incorrect 
warning message 'unsupported operator'.

> BasicSearch: Warning for the Unsupported operator.
> --
>
> Key: ATLAS-3823
> URL: https://issues.apache.org/jira/browse/ATLAS-3823
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0
>
>
> For Some operator like notNull, isNull, there is incorrect warning message 
> 'unsupported operator'.



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


[jira] [Updated] (ATLAS-3823) BasicSearch: Warning for the Unsupported operator.

2020-06-02 Thread Pinal (Jira)


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

Pinal updated ATLAS-3823:
-
Component/s:  atlas-core

> BasicSearch: Warning for the Unsupported operator.
> --
>
> Key: ATLAS-3823
> URL: https://issues.apache.org/jira/browse/ATLAS-3823
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
>




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


[jira] [Updated] (ATLAS-3823) BasicSearch: Warning for the Unsupported operator.

2020-06-02 Thread Pinal (Jira)


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

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

> BasicSearch: Warning for the Unsupported operator.
> --
>
> Key: ATLAS-3823
> URL: https://issues.apache.org/jira/browse/ATLAS-3823
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0
>
>




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


[jira] [Updated] (ATLAS-3823) BasicSearch: Warning for the Unsupported operator.

2020-06-02 Thread Pinal (Jira)


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

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

> BasicSearch: Warning for the Unsupported operator.
> --
>
> Key: ATLAS-3823
> URL: https://issues.apache.org/jira/browse/ATLAS-3823
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
>




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


[jira] [Updated] (ATLAS-3823) BasicSearch: Warning for the Unsupported operator.

2020-06-02 Thread Pinal (Jira)


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

Pinal updated ATLAS-3823:
-
Labels: BasicSearch  (was: )

> BasicSearch: Warning for the Unsupported operator.
> --
>
> Key: ATLAS-3823
> URL: https://issues.apache.org/jira/browse/ATLAS-3823
> Project: Atlas
>  Issue Type: Bug
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
>




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


[jira] [Created] (ATLAS-3823) BasicSearch: Warning for the Unsupported operator.

2020-06-02 Thread Pinal (Jira)
Pinal created ATLAS-3823:


 Summary: BasicSearch: Warning for the Unsupported operator.
 Key: ATLAS-3823
 URL: https://issues.apache.org/jira/browse/ATLAS-3823
 Project: Atlas
  Issue Type: Bug
Reporter: Pinal
Assignee: Pinal






--
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-05-22 Thread Pinal (Jira)


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

Pinal updated ATLAS-3782:
-
Labels: BasicSearch  (was: )

> 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
>Priority: Minor
>  Labels: BasicSearch
>
> 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] [Assigned] (ATLAS-3782) Support NOT_CONTAINS operator in basic search with search parameters

2020-05-22 Thread Pinal (Jira)


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

Pinal reassigned ATLAS-3782:


Assignee: Pinal

> 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
>
> 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-3615) Basic Search : Search with _ALL_ENTITY_TYPES and classification doesn't not fetch any entity associated to that classification

2020-05-22 Thread Pinal (Jira)


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

Pinal updated ATLAS-3615:
-
Labels: BasicSearch  (was: )

> Basic Search : Search with _ALL_ENTITY_TYPES and classification doesn't not 
> fetch any entity associated to that classification
> --
>
> Key: ATLAS-3615
> URL: https://issues.apache.org/jira/browse/ATLAS-3615
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0, 3.0.0
>
>
> 1. classification : tag1 returns all entities associated to tag1
> 2. typename : _ALL_ENTITY_TYPES returns all entities under all types.
> 3. classification : tag1 typename : hive_table returns all hive_table 
> entities associated to tag1
> 4. classification : tag1 typename : _ALL_ENTITY_TYPES doesn't return any 
> result. Expected it would return same results as query1.
> Basic search payload :
> {code:java}
> { 
> "excludeDeletedEntities":true,
> "includeSubClassifications":true,
> "includeSubTypes":true,
> "includeClassificationAttributes":true,
> "entityFilters":null,
> "tagFilters":null,
> "attributes":[
> ],
> "limit":25,
> "offset":0,
> "typeName":"_ALL_ENTITY_TYPES",
> "classification":"tag1",
> "termName":null
> }
> {code}
>  5. classification : tag1, typename : _ALL_ENTITY_TYPES, Search by text, this 
> combination doesn't return any result



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


[jira] [Updated] (ATLAS-3615) Basic Search : Search with _ALL_ENTITY_TYPES and classification doesn't not fetch any entity associated to that classification

2020-05-22 Thread Pinal (Jira)


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

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

> Basic Search : Search with _ALL_ENTITY_TYPES and classification doesn't not 
> fetch any entity associated to that classification
> --
>
> Key: ATLAS-3615
> URL: https://issues.apache.org/jira/browse/ATLAS-3615
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0, 3.0.0
>
>
> 1. classification : tag1 returns all entities associated to tag1
> 2. typename : _ALL_ENTITY_TYPES returns all entities under all types.
> 3. classification : tag1 typename : hive_table returns all hive_table 
> entities associated to tag1
> 4. classification : tag1 typename : _ALL_ENTITY_TYPES doesn't return any 
> result. Expected it would return same results as query1.
> Basic search payload :
> {code:java}
> { 
> "excludeDeletedEntities":true,
> "includeSubClassifications":true,
> "includeSubTypes":true,
> "includeClassificationAttributes":true,
> "entityFilters":null,
> "tagFilters":null,
> "attributes":[
> ],
> "limit":25,
> "offset":0,
> "typeName":"_ALL_ENTITY_TYPES",
> "classification":"tag1",
> "termName":null
> }
> {code}
>  5. classification : tag1, typename : _ALL_ENTITY_TYPES, Search by text, this 
> combination doesn't return any result



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


[jira] [Updated] (ATLAS-3600) Some System Attribute of Entity filter doesn't work

2020-05-22 Thread Pinal (Jira)


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

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

> Some System Attribute of Entity filter doesn't work
> ---
>
> Key: ATLAS-3600
> URL: https://issues.apache.org/jira/browse/ATLAS-3600
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Mayank Jain
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0, 3.0.0
>
>
> The new enhancement of System Attributes does not support's following 4 
> search ,
>  # classification search
>  # Propogated Classification Search
>  # User-Defined Attributes 
>  # Labels                                  



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


[jira] [Updated] (ATLAS-3600) Some System Attribute of Entity filter doesn't work

2020-05-22 Thread Pinal (Jira)


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

Pinal updated ATLAS-3600:
-
Labels: BasicSearch  (was: )

> Some System Attribute of Entity filter doesn't work
> ---
>
> Key: ATLAS-3600
> URL: https://issues.apache.org/jira/browse/ATLAS-3600
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mayank Jain
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0, 3.0.0
>
>
> The new enhancement of System Attributes does not support's following 4 
> search ,
>  # classification search
>  # Propogated Classification Search
>  # User-Defined Attributes 
>  # Labels                                  



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


[jira] [Updated] (ATLAS-3618) Entities with no guid appears in search result

2020-05-22 Thread Pinal (Jira)


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

Pinal updated ATLAS-3618:
-
Labels: BasicSearch  (was: )

> Entities with no guid appears in search result
> --
>
> Key: ATLAS-3618
> URL: https://issues.apache.org/jira/browse/ATLAS-3618
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0, 3.0.0
>
> Attachments: no_guid_entity.png
>
>
> entities with no guid is listed in search result, when _ALL_ENTITY_TYPES is 
> searched.
> !no_guid_entity.png!
> Also, Entites with internal type is listed in search result



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


[jira] [Updated] (ATLAS-3650) Basic Search: query of typeName doesn't apply when it has many subTypes(like Asset) in combination with attribute filter

2020-05-22 Thread Pinal (Jira)


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

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

> Basic Search: query of typeName doesn't apply when it has many subTypes(like 
> Asset) in combination with attribute filter
> 
>
> Key: ATLAS-3650
> URL: https://issues.apache.org/jira/browse/ATLAS-3650
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0, 3.0.0
>
>
> When Asset typeName, which has many subtypes, with some attribute filter is 
> searched ,
> query formed for typeName is not included in final query



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


[jira] [Updated] (ATLAS-3650) Basic Search: query of typeName doesn't apply when it has many subTypes(like Asset) in combination with attribute filter

2020-05-22 Thread Pinal (Jira)


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

Pinal updated ATLAS-3650:
-
Labels: BasicSearch  (was: )

> Basic Search: query of typeName doesn't apply when it has many subTypes(like 
> Asset) in combination with attribute filter
> 
>
> Key: ATLAS-3650
> URL: https://issues.apache.org/jira/browse/ATLAS-3650
> Project: Atlas
>  Issue Type: Bug
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0, 3.0.0
>
>
> When Asset typeName, which has many subtypes, with some attribute filter is 
> searched ,
> query formed for typeName is not included in final query



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


[jira] [Updated] (ATLAS-3680) Regression : _ALL_ENTITY_TYPES with any system attribute filter throws 500 exception

2020-05-22 Thread Pinal (Jira)


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

Pinal updated ATLAS-3680:
-
Labels: BasicSearch  (was: )

> Regression : _ALL_ENTITY_TYPES with any system attribute filter throws 500 
> exception
> 
>
> Key: ATLAS-3680
> URL: https://issues.apache.org/jira/browse/ATLAS-3680
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
>
> Search with specific type. such as hive_table and system attribute 
> __timestamp and conditions returns right results.
> with _ALL_ENTITY_TYPES and any system attribute say __timestamp , 500 
> Exception is thrown with stack trace:
> {code:java}
> 2020-03-23 12:54:05,247 ERROR - [pool-2-thread-10 - 
> 4cd9a02a-f62c-48bd-8a1d-973c5cdba474:] ~ Error handling a request: 
> 85f5f4278846ecae (ExceptionMapperUtil:32)
> java.lang.IllegalArgumentException: Predicate must not be null
>   at 
> org.apache.commons.collections.functors.AndPredicate.getInstance(AndPredicate.java:51)
>   at 
> org.apache.commons.collections.PredicateUtils.andPredicate(PredicateUtils.java:262)
>   at 
> org.apache.atlas.discovery.EntitySearchProcessor.(EntitySearchProcessor.java:122)
>   at 
> org.apache.atlas.discovery.SearchContext.(SearchContext.java:168)
>   at 
> org.apache.atlas.discovery.EntityDiscoveryService.searchWithParameters(EntityDiscoveryService.java:458)
>   at 
> org.apache.atlas.discovery.EntityDiscoveryService$$FastClassBySpringCGLIB$$1af2cf1f.invoke()
>   at 
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
>   at 
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736)
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
>   at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:82)
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>   at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671)
>   at 
> org.apache.atlas.discovery.EntityDiscoveryService$$EnhancerBySpringCGLIB$$912a463.searchWithParameters()
>   at 
> org.apache.atlas.web.rest.DiscoveryREST.searchWithParameters(DiscoveryREST.java:336)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>   at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> 

[jira] [Updated] (ATLAS-3703) BasicSearch: Search by terms/Search by text in combination of Classification filter, filter doesn't work

2020-05-22 Thread Pinal (Jira)


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

Pinal updated ATLAS-3703:
-
Labels: BasicSearch  (was: )

> BasicSearch: Search by terms/Search by text in combination of Classification 
> filter, filter doesn't work
> 
>
> Key: ATLAS-3703
> URL: https://issues.apache.org/jira/browse/ATLAS-3703
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0, 3.0.0
>
> Attachments: filter doesn't work.png, filter works.png
>
>
> Example of cases where Filters of classification doesn't work
> ClassificationType + Classification Filter + Term
> ClassificationType + Classification Filter + Text
> EntityType + Entity Filter + ClassificationType + Classification Filter + Term



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


[jira] [Updated] (ATLAS-3672) Search with Classification without filters and Entity with filters doesn't fetch expected results.

2020-05-22 Thread Pinal (Jira)


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

Pinal updated ATLAS-3672:
-
Labels: BasicSearch  (was: )

> Search with Classification without filters and Entity with filters doesn't 
> fetch expected results.
> --
>
> Key: ATLAS-3672
> URL: https://issues.apache.org/jira/browse/ATLAS-3672
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0, 3.0.0
>
> Attachments: entity_filter_no_tag_filter.png, 
> no_tag_filter_no_entity_filter.png, tag_filters_no_entity_filter.png, 
> tag_filters_with_entity_filters.png
>
>
> Attached screenshots for different scenarios:
> 1 . tag filters with entity filters - works
>  2. tag filters without entity filters - works
>  3. no tag filters with entity filters - doesn't work
>  3. no tag filters no entity filters - works



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


[jira] [Updated] (ATLAS-3703) BasicSearch: Search by terms/Search by text in combination of Classification filter, filter doesn't work

2020-05-22 Thread Pinal (Jira)


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

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

> BasicSearch: Search by terms/Search by text in combination of Classification 
> filter, filter doesn't work
> 
>
> Key: ATLAS-3703
> URL: https://issues.apache.org/jira/browse/ATLAS-3703
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: filter doesn't work.png, filter works.png
>
>
> Example of cases where Filters of classification doesn't work
> ClassificationType + Classification Filter + Term
> ClassificationType + Classification Filter + Text
> EntityType + Entity Filter + ClassificationType + Classification Filter + Term



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


[jira] [Updated] (ATLAS-3672) Search with Classification without filters and Entity with filters doesn't fetch expected results.

2020-05-22 Thread Pinal (Jira)


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

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

> Search with Classification without filters and Entity with filters doesn't 
> fetch expected results.
> --
>
> Key: ATLAS-3672
> URL: https://issues.apache.org/jira/browse/ATLAS-3672
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: entity_filter_no_tag_filter.png, 
> no_tag_filter_no_entity_filter.png, tag_filters_no_entity_filter.png, 
> tag_filters_with_entity_filters.png
>
>
> Attached screenshots for different scenarios:
> 1 . tag filters with entity filters - works
>  2. tag filters without entity filters - works
>  3. no tag filters with entity filters - doesn't work
>  3. no tag filters no entity filters - works



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


[jira] [Updated] (ATLAS-3746) _NOT_CLASSIFIED doesn't fetch right results

2020-05-22 Thread Pinal (Jira)


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

Pinal updated ATLAS-3746:
-
Labels: BasicSearch  (was: )

> _NOT_CLASSIFIED doesn't fetch right results
> ---
>
> Key: ATLAS-3746
> URL: https://issues.apache.org/jira/browse/ATLAS-3746
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0
>
>
> typename = hive_table
> classification = _NOT_CLASSIFIED
> fetches right results.
> But
> just classification = _NOT_CLASSIFIED
> doesn't fetch right results.



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


[jira] [Updated] (ATLAS-3746) _NOT_CLASSIFIED doesn't fetch right results

2020-05-22 Thread Pinal (Jira)


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

Pinal updated ATLAS-3746:
-
Component/s:  atlas-core

> _NOT_CLASSIFIED doesn't fetch right results
> ---
>
> Key: ATLAS-3746
> URL: https://issues.apache.org/jira/browse/ATLAS-3746
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0
>
>
> typename = hive_table
> classification = _NOT_CLASSIFIED
> fetches right results.
> But
> just classification = _NOT_CLASSIFIED
> doesn't fetch right results.



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


[jira] [Updated] (ATLAS-3746) _NOT_CLASSIFIED doesn't fetch right results

2020-05-22 Thread Pinal (Jira)


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

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

> _NOT_CLASSIFIED doesn't fetch right results
> ---
>
> Key: ATLAS-3746
> URL: https://issues.apache.org/jira/browse/ATLAS-3746
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0
>
>
> typename = hive_table
> classification = _NOT_CLASSIFIED
> fetches right results.
> But
> just classification = _NOT_CLASSIFIED
> doesn't fetch right results.



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


[jira] [Updated] (ATLAS-3753) Classification Search with wildcard in between strings causes issues.

2020-05-22 Thread Pinal (Jira)


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

Pinal updated ATLAS-3753:
-
Labels: BasicSearch  (was: )

> Classification Search with wildcard in between strings causes issues.
> -
>
> Key: ATLAS-3753
> URL: https://issues.apache.org/jira/browse/ATLAS-3753
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0
>
>
> Tag `tag_abc_test` is created and associated to an entity.
> Search with *test or tag* fetches the entity.
> But Search with tag*test doesn't fetch the entity.



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


[jira] [Updated] (ATLAS-3746) _NOT_CLASSIFIED doesn't fetch right results

2020-05-22 Thread Pinal (Jira)


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

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

> _NOT_CLASSIFIED doesn't fetch right results
> ---
>
> Key: ATLAS-3746
> URL: https://issues.apache.org/jira/browse/ATLAS-3746
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> typename = hive_table
> classification = _NOT_CLASSIFIED
> fetches right results.
> But
> just classification = _NOT_CLASSIFIED
> doesn't fetch right results.



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


[jira] [Updated] (ATLAS-3753) Classification Search with wildcard in between strings causes issues.

2020-05-22 Thread Pinal (Jira)


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

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

> Classification Search with wildcard in between strings causes issues.
> -
>
> Key: ATLAS-3753
> URL: https://issues.apache.org/jira/browse/ATLAS-3753
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> Tag `tag_abc_test` is created and associated to an entity.
> Search with *test or tag* fetches the entity.
> But Search with tag*test doesn't fetch the entity.



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


[jira] [Updated] (ATLAS-3753) Classification Search with wildcard in between strings causes issues.

2020-05-22 Thread Pinal (Jira)


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

Pinal updated ATLAS-3753:
-
Component/s:  atlas-core

> Classification Search with wildcard in between strings causes issues.
> -
>
> Key: ATLAS-3753
> URL: https://issues.apache.org/jira/browse/ATLAS-3753
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0
>
>
> Tag `tag_abc_test` is created and associated to an entity.
> Search with *test or tag* fetches the entity.
> But Search with tag*test doesn't fetch the entity.



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


[jira] [Updated] (ATLAS-3753) Classification Search with wildcard in between strings causes issues.

2020-05-22 Thread Pinal (Jira)


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

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

> Classification Search with wildcard in between strings causes issues.
> -
>
> Key: ATLAS-3753
> URL: https://issues.apache.org/jira/browse/ATLAS-3753
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0
>
>
> Tag `tag_abc_test` is created and associated to an entity.
> Search with *test or tag* fetches the entity.
> But Search with tag*test doesn't fetch the entity.



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


[jira] [Updated] (ATLAS-3802) BasicSearch: filter, attribute with NEQ operator doesn't match attribute having null values

2020-05-22 Thread Pinal (Jira)


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

Pinal updated ATLAS-3802:
-
Component/s:  atlas-core

> BasicSearch: filter, attribute with NEQ operator doesn't match attribute 
> having null values
> ---
>
> Key: ATLAS-3802
> URL: https://issues.apache.org/jira/browse/ATLAS-3802
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0
>
>
> When filter with 'attribute' != 'value' is searched, it doesn't fetch 
> entities where attribute is not present.
> Eg. propagatedClassification != tag1 is searched, it fetches all entities not 
> tagged to tag1 , but it will not match to entities which don't have *any* 
> propagated tags



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


[jira] [Updated] (ATLAS-3802) BasicSearch: filter, attribute with NEQ operator doesn't match attribute having null values

2020-05-22 Thread Pinal (Jira)


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

Pinal updated ATLAS-3802:
-
Labels: BasicSearch  (was: )

> BasicSearch: filter, attribute with NEQ operator doesn't match attribute 
> having null values
> ---
>
> Key: ATLAS-3802
> URL: https://issues.apache.org/jira/browse/ATLAS-3802
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0
>
>
> When filter with 'attribute' != 'value' is searched, it doesn't fetch 
> entities where attribute is not present.
> Eg. propagatedClassification != tag1 is searched, it fetches all entities not 
> tagged to tag1 , but it will not match to entities which don't have *any* 
> propagated tags



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


[jira] [Updated] (ATLAS-3802) BasicSearch: filter, attribute with NEQ operator doesn't match attribute having null values

2020-05-22 Thread Pinal (Jira)


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

Pinal updated ATLAS-3802:
-
Fix Version/s: (was: 2.0.0)
   2.1.0

> BasicSearch: filter, attribute with NEQ operator doesn't match attribute 
> having null values
> ---
>
> Key: ATLAS-3802
> URL: https://issues.apache.org/jira/browse/ATLAS-3802
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0
>
>
> When filter with 'attribute' != 'value' is searched, it doesn't fetch 
> entities where attribute is not present.
> Eg. propagatedClassification != tag1 is searched, it fetches all entities not 
> tagged to tag1 , but it will not match to entities which don't have *any* 
> propagated tags



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


[jira] [Updated] (ATLAS-3802) BasicSearch: filter, attribute with NEQ operator doesn't match attribute having null values

2020-05-22 Thread Pinal (Jira)


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

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

> BasicSearch: filter, attribute with NEQ operator doesn't match attribute 
> having null values
> ---
>
> Key: ATLAS-3802
> URL: https://issues.apache.org/jira/browse/ATLAS-3802
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.0.0
>
>
> When filter with 'attribute' != 'value' is searched, it doesn't fetch 
> entities where attribute is not present.
> Eg. propagatedClassification != tag1 is searched, it fetches all entities not 
> tagged to tag1 , but it will not match to entities which don't have *any* 
> propagated tags



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


[jira] [Updated] (ATLAS-3802) BasicSearch: filter, attribute with NEQ operator doesn't match attribute having null values

2020-05-20 Thread Pinal (Jira)


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

Pinal updated ATLAS-3802:
-
Description: 
When filter with 'attribute' != 'value' is searched, it doesn't fetch entities 
where attribute is not present.

Eg. propagatedClassification != tag1 is searched, it fetches all entities not 
tagged to tag1 , but it will not match to entities which don't have *any* 
propagated tags

  was:
When propagatedClassification != tag1 is searched, it fetches all entities not 
tagged to tag1

But it will not match to entities which don't have any propagated tags


> BasicSearch: filter, attribute with NEQ operator doesn't match attribute 
> having null values
> ---
>
> Key: ATLAS-3802
> URL: https://issues.apache.org/jira/browse/ATLAS-3802
> Project: Atlas
>  Issue Type: Bug
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> When filter with 'attribute' != 'value' is searched, it doesn't fetch 
> entities where attribute is not present.
> Eg. propagatedClassification != tag1 is searched, it fetches all entities not 
> tagged to tag1 , but it will not match to entities which don't have *any* 
> propagated tags



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


[jira] [Created] (ATLAS-3802) BasicSearch: filter, attribute with NEQ operator doesn't match attribute having null values

2020-05-20 Thread Pinal (Jira)
Pinal created ATLAS-3802:


 Summary: BasicSearch: filter, attribute with NEQ operator doesn't 
match attribute having null values
 Key: ATLAS-3802
 URL: https://issues.apache.org/jira/browse/ATLAS-3802
 Project: Atlas
  Issue Type: Bug
Reporter: Pinal
Assignee: Pinal


When propagatedClassification != tag1 is searched, it fetches all entities not 
tagged to tag1

But it will not match to entities which don't have any propagated tags



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


[jira] [Created] (ATLAS-3788) BasicSearch: Classification with System attribute(indexed) filters has pagination issue

2020-05-11 Thread Pinal (Jira)
Pinal created ATLAS-3788:


 Summary: BasicSearch: Classification with System 
attribute(indexed) filters has pagination issue
 Key: ATLAS-3788
 URL: https://issues.apache.org/jira/browse/ATLAS-3788
 Project: Atlas
  Issue Type: Bug
Reporter: Pinal
Assignee: Pinal


When selecting ALL_CLASSIFICATION_TYPES, with system attribute Created Time < 
currentTimeStamp , it results to less or zero number of entities than actual.



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


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

2020-05-08 Thread Pinal (Jira)


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

Pinal updated ATLAS-3780:
-
Summary: Change 'Status' from Classification System Attributes to 
EntityStatus  (was: Remove 'Status' from Classification System Attributes)

> 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
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> 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-3780) Remove 'Status' from Classification System Attributes

2020-05-05 Thread Pinal (Jira)


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

Pinal updated ATLAS-3780:
-
Attachment: Screen Shot 2020-05-05 at 4.40.40 PM.png

> Remove 'Status' from Classification System Attributes
> -
>
> Key: ATLAS-3780
> URL: https://issues.apache.org/jira/browse/ATLAS-3780
> Project: Atlas
>  Issue Type: Task
>  Components: atlas-intg
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> 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-3780) Remove 'Status' from Classification System Attributes

2020-05-05 Thread Pinal (Jira)


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

Pinal updated ATLAS-3780:
-
Attachment: Screen Shot 2020-05-05 at 4.40.40 PM.png

> Remove 'Status' from Classification System Attributes
> -
>
> Key: ATLAS-3780
> URL: https://issues.apache.org/jira/browse/ATLAS-3780
> Project: Atlas
>  Issue Type: Task
>  Components: atlas-intg
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>




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


[jira] [Updated] (ATLAS-3780) Remove 'Status' from Classification System Attributes

2020-05-05 Thread Pinal (Jira)


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

Pinal updated ATLAS-3780:
-
Attachment: (was: Screen Shot 2020-05-05 at 4.40.40 PM.png)

> Remove 'Status' from Classification System Attributes
> -
>
> Key: ATLAS-3780
> URL: https://issues.apache.org/jira/browse/ATLAS-3780
> Project: Atlas
>  Issue Type: Task
>  Components: atlas-intg
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>




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


[jira] [Created] (ATLAS-3780) Remove 'Status' from Classification System Attributes

2020-05-05 Thread Pinal (Jira)
Pinal created ATLAS-3780:


 Summary: Remove 'Status' from Classification System Attributes
 Key: ATLAS-3780
 URL: https://issues.apache.org/jira/browse/ATLAS-3780
 Project: Atlas
  Issue Type: Task
  Components: atlas-intg
Reporter: Pinal
Assignee: Pinal






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


[jira] [Resolved] (ATLAS-3753) Classification Search with wildcard in between strings causes issues.

2020-04-23 Thread Pinal (Jira)


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

Pinal resolved ATLAS-3753.
--
Resolution: Fixed

> Classification Search with wildcard in between strings causes issues.
> -
>
> Key: ATLAS-3753
> URL: https://issues.apache.org/jira/browse/ATLAS-3753
> Project: Atlas
>  Issue Type: Bug
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> Tag `tag_abc_test` is created and associated to an entity.
> Search with *test or tag* fetches the entity.
> But Search with tag*test doesn't fetch the entity.



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


[jira] [Resolved] (ATLAS-3746) _NOT_CLASSIFIED doesn't fetch right results

2020-04-23 Thread Pinal (Jira)


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

Pinal resolved ATLAS-3746.
--
Resolution: Fixed

> _NOT_CLASSIFIED doesn't fetch right results
> ---
>
> Key: ATLAS-3746
> URL: https://issues.apache.org/jira/browse/ATLAS-3746
> Project: Atlas
>  Issue Type: Bug
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> typename = hive_table
> classification = _NOT_CLASSIFIED
> fetches right results.
> But
> just classification = _NOT_CLASSIFIED
> doesn't fetch right results.



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


[jira] [Created] (ATLAS-3753) Classification Search with wildcard in between strings causes issues.

2020-04-22 Thread Pinal (Jira)
Pinal created ATLAS-3753:


 Summary: Classification Search with wildcard in between strings 
causes issues.
 Key: ATLAS-3753
 URL: https://issues.apache.org/jira/browse/ATLAS-3753
 Project: Atlas
  Issue Type: Bug
Reporter: Pinal
Assignee: Pinal


Tag `tag_abc_test` is created and associated to an entity.

Search with *test or tag* fetches the entity.

But Search with tag*test doesn't fetch the entity.



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


[jira] [Created] (ATLAS-3746) _NOT_CLASSIFIED doesn't fetch right results

2020-04-21 Thread Pinal (Jira)
Pinal created ATLAS-3746:


 Summary: _NOT_CLASSIFIED doesn't fetch right results
 Key: ATLAS-3746
 URL: https://issues.apache.org/jira/browse/ATLAS-3746
 Project: Atlas
  Issue Type: Bug
Reporter: Pinal
Assignee: Pinal


typename = hive_table

classification = _NOT_CLASSIFIED

fetches right results.

But

just classification = _NOT_CLASSIFIED

doesn't fetch right results.



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


[jira] [Assigned] (ATLAS-3696) [Business Metadata] No option to check/uncheck Business Metadata field in search results

2020-04-08 Thread Pinal (Jira)


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

Pinal reassigned ATLAS-3696:


Assignee: Keval Bhatt  (was: Pinal)

> [Business Metadata] No option to check/uncheck Business Metadata field in 
> search results
> 
>
> Key: ATLAS-3696
> URL: https://issues.apache.org/jira/browse/ATLAS-3696
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: Screenshot 2020-03-26 at 9.00.55 PM.png, Screenshot 
> 2020-03-26 at 9.04.22 PM.png
>
>
> For instance, there is no way to show "Business Metadata" column if Business 
> Metadata attribute filter is not applied while searching. Attached screenshots



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


[jira] [Assigned] (ATLAS-3682) Multivalued attributes are not listed under Business Metadata Attribute filter

2020-04-03 Thread Pinal (Jira)


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

Pinal reassigned ATLAS-3682:


Assignee: Pinal  (was: Keval Bhatt)

> Multivalued attributes are not listed under Business Metadata Attribute filter
> --
>
> Key: ATLAS-3682
> URL: https://issues.apache.org/jira/browse/ATLAS-3682
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Pinal
>Priority: Major
> Attachments: Screenshot 2020-03-24 at 1.01.54 AM.png, Screenshot 
> 2020-03-24 at 1.02.28 AM.png
>
>
> Added attributes of different types, noticed that the multi valued attributes 
> are bot being listed for an entity filter, even when the attribute is 
> applicable to that entity. Screenshots attached below.
> As you can see, the attribute "Reviewed by" which is of type "array" 
> is not being listed under the Business Metadata Attribute drop down.
> CC: [~kevalbhatt]



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


[jira] [Assigned] (ATLAS-3696) [Business Metadata] No option to check/uncheck Business Metadata field in search results

2020-03-31 Thread Pinal (Jira)


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

Pinal reassigned ATLAS-3696:


Assignee: Pinal

> [Business Metadata] No option to check/uncheck Business Metadata field in 
> search results
> 
>
> Key: ATLAS-3696
> URL: https://issues.apache.org/jira/browse/ATLAS-3696
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Pinal
>Priority: Major
> Attachments: Screenshot 2020-03-26 at 9.00.55 PM.png, Screenshot 
> 2020-03-26 at 9.04.22 PM.png
>
>
> For instance, there is no way to show "Business Metadata" column if Business 
> Metadata attribute filter is not applied while searching. Attached screenshots



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


[jira] [Resolved] (ATLAS-3672) Search with Classification without filters and Entity with filters doesn't fetch expected results.

2020-03-31 Thread Pinal (Jira)


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

Pinal resolved ATLAS-3672.
--
Fix Version/s: 3.0.0
   2.1.0
   Resolution: Fixed

> Search with Classification without filters and Entity with filters doesn't 
> fetch expected results.
> --
>
> Key: ATLAS-3672
> URL: https://issues.apache.org/jira/browse/ATLAS-3672
> Project: Atlas
>  Issue Type: Bug
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: entity_filter_no_tag_filter.png, 
> no_tag_filter_no_entity_filter.png, tag_filters_no_entity_filter.png, 
> tag_filters_with_entity_filters.png
>
>
> Attached screenshots for different scenarios:
> 1 . tag filters with entity filters - works
>  2. tag filters without entity filters - works
>  3. no tag filters with entity filters - doesn't work
>  3. no tag filters no entity filters - works



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


[jira] [Resolved] (ATLAS-3703) BasicSearch: Search by terms/Search by text in combination of Classification filter, filter doesn't work

2020-03-31 Thread Pinal (Jira)


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

Pinal resolved ATLAS-3703.
--
Fix Version/s: 3.0.0
   2.1.0
   Resolution: Fixed

> BasicSearch: Search by terms/Search by text in combination of Classification 
> filter, filter doesn't work
> 
>
> Key: ATLAS-3703
> URL: https://issues.apache.org/jira/browse/ATLAS-3703
> Project: Atlas
>  Issue Type: Bug
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: filter doesn't work.png, filter works.png
>
>
> Example of cases where Filters of classification doesn't work
> ClassificationType + Classification Filter + Term
> ClassificationType + Classification Filter + Text
> EntityType + Entity Filter + ClassificationType + Classification Filter + Term



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


[jira] [Resolved] (ATLAS-3680) Regression : _ALL_ENTITY_TYPES with any system attribute filter throws 500 exception

2020-03-30 Thread Pinal (Jira)


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

Pinal resolved ATLAS-3680.
--
Resolution: Fixed

> Regression : _ALL_ENTITY_TYPES with any system attribute filter throws 500 
> exception
> 
>
> Key: ATLAS-3680
> URL: https://issues.apache.org/jira/browse/ATLAS-3680
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Pinal
>Priority: Major
>
> Search with specific type. such as hive_table and system attribute 
> __timestamp and conditions returns right results.
> with _ALL_ENTITY_TYPES and any system attribute say __timestamp , 500 
> Exception is thrown with stack trace:
> {code:java}
> 2020-03-23 12:54:05,247 ERROR - [pool-2-thread-10 - 
> 4cd9a02a-f62c-48bd-8a1d-973c5cdba474:] ~ Error handling a request: 
> 85f5f4278846ecae (ExceptionMapperUtil:32)
> java.lang.IllegalArgumentException: Predicate must not be null
>   at 
> org.apache.commons.collections.functors.AndPredicate.getInstance(AndPredicate.java:51)
>   at 
> org.apache.commons.collections.PredicateUtils.andPredicate(PredicateUtils.java:262)
>   at 
> org.apache.atlas.discovery.EntitySearchProcessor.(EntitySearchProcessor.java:122)
>   at 
> org.apache.atlas.discovery.SearchContext.(SearchContext.java:168)
>   at 
> org.apache.atlas.discovery.EntityDiscoveryService.searchWithParameters(EntityDiscoveryService.java:458)
>   at 
> org.apache.atlas.discovery.EntityDiscoveryService$$FastClassBySpringCGLIB$$1af2cf1f.invoke()
>   at 
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
>   at 
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736)
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
>   at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:82)
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>   at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671)
>   at 
> org.apache.atlas.discovery.EntityDiscoveryService$$EnhancerBySpringCGLIB$$912a463.searchWithParameters()
>   at 
> org.apache.atlas.web.rest.DiscoveryREST.searchWithParameters(DiscoveryREST.java:336)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>   at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845)
>   at 
> 

[jira] [Updated] (ATLAS-3678) User defined properties are not listed under suggestions

2020-03-30 Thread Pinal (Jira)


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

Pinal updated ATLAS-3678:
-
Priority: Minor  (was: Major)

> User defined properties are not listed under suggestions
> 
>
> Key: ATLAS-3678
> URL: https://issues.apache.org/jira/browse/ATLAS-3678
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Pinal
>Priority: Minor
> Attachments: Screenshot 2020-03-23 at 2.56.49 PM.png, Screenshot 
> 2020-03-23 at 2.57.57 PM.png, Screenshot 2020-03-23 at 2.58.57 PM.png, 
> Screenshot 2020-03-23 at 3.00.27 PM.png, Screenshot 2020-03-23 at 3.00.39 
> PM.png
>
>
> When user-defined properties are added to an entity, and when we type the 
> "user-defined property" in the global search bar, the expectation is that 
>  # The corresponding entity appears in the quick search, entities dropdown. 
> This is working 
>  # The user-defined property itself should appear in the suggestions 
> dropdown. This is not working
> Tried similar tests with labels, entities that are tagged with labels appear 
> in the quick search drop down, and the labels itself appear as part of the 
> suggestions. Attached are the screenshots.
>  



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


[jira] [Updated] (ATLAS-3703) BasicSearch: Search by terms/Search by text in combination of Classification filter, filter doesn't work

2020-03-29 Thread Pinal (Jira)


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

Pinal updated ATLAS-3703:
-
Attachment: filter works.png
filter doesn't work.png

> BasicSearch: Search by terms/Search by text in combination of Classification 
> filter, filter doesn't work
> 
>
> Key: ATLAS-3703
> URL: https://issues.apache.org/jira/browse/ATLAS-3703
> Project: Atlas
>  Issue Type: Bug
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Attachments: filter doesn't work.png, filter works.png
>
>
> Example of cases where Filters of classification doesn't work
> ClassificationType + Classification Filter + Term
> ClassificationType + Classification Filter + Text
> EntityType + Entity Filter + ClassificationType + Classification Filter + Term



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


[jira] [Created] (ATLAS-3703) BasicSearch: Search by terms/Search by text in combination of Classification filter, filter doesn't work

2020-03-29 Thread Pinal (Jira)
Pinal created ATLAS-3703:


 Summary: BasicSearch: Search by terms/Search by text in 
combination of Classification filter, filter doesn't work
 Key: ATLAS-3703
 URL: https://issues.apache.org/jira/browse/ATLAS-3703
 Project: Atlas
  Issue Type: Bug
Reporter: Pinal
Assignee: Pinal


Example of cases where Filters of classification doesn't work
ClassificationType + Classification Filter + Term
ClassificationType + Classification Filter + Text
EntityType + Entity Filter + ClassificationType + Classification Filter + Term



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


[jira] [Assigned] (ATLAS-3678) User defined properties are not listed under suggestions

2020-03-24 Thread Pinal (Jira)


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

Pinal reassigned ATLAS-3678:


Assignee: Pinal  (was: Madhan Neethiraj)

> User defined properties are not listed under suggestions
> 
>
> Key: ATLAS-3678
> URL: https://issues.apache.org/jira/browse/ATLAS-3678
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Pinal
>Priority: Major
> Attachments: Screenshot 2020-03-23 at 2.56.49 PM.png, Screenshot 
> 2020-03-23 at 2.57.57 PM.png, Screenshot 2020-03-23 at 2.58.57 PM.png, 
> Screenshot 2020-03-23 at 3.00.27 PM.png, Screenshot 2020-03-23 at 3.00.39 
> PM.png
>
>
> When user-defined properties are added to an entity, and when we type the 
> "user-defined property" in the global search bar, the expectation is that 
>  # The corresponding entity appears in the quick search, entities dropdown. 
> This is working 
>  # The user-defined property itself should appear in the suggestions 
> dropdown. This is not working
> Tried similar tests with labels, entities that are tagged with labels appear 
> in the quick search drop down, and the labels itself appear as part of the 
> suggestions. Attached are the screenshots.
>  



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


  1   2   >