[jira] [Commented] (ATLAS-4307) Atlas bulk clarification REST should be enhanced to associate classification to bulk entities with uniq attribute and type

2021-05-25 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra commented on ATLAS-4307:
--

With the change below three options will work -

Option 1 (Only with type name and list of uniq attributes)

curl --location --request POST 
'http://atlas-host:31000/api/atlas/v2/entity/bulk/classification?skipFailedEntities=True'
 \
--header 'Authorization: Basic YWRtaW46YWRtaW4xMjM=' \
--header 'Content-Type: application/json' \
--data-raw '{
 "classification" : {
 "propagate" : false,
 "attributes" : {
 "type" : "false"
 },
 "typeName" : "TEST_TAG_TABLE"
 },
 "entitiesUniqAttributes" : [
 \{"qualifiedName": "db1.table43@cm"},
 \{"qualifiedName": "db1.table7@cm"},
 \{"qualifiedName": "db1.table55@cm"}],
 "entityTypeName" : "hive_table"
}'

Option 2 (Only with entity Guids)
curl --location --request POST 
'http://atlas-host:31000/api/atlas/v2/entity/bulk/classification?skipFailedEntities=True'
 \
--header 'Authorization: Basic YWRtaW46YWRtaW4xMjM=' \
--header 'Content-Type: application/json' \
--data-raw '{
 "classification" : {
 "propagate" : false,
 "attributes" : {
 "type" : "false"
 },
 "typeName" : "TEST_TAG_TABLE"
 },
 "entityGuids" : ["f7288e81-46e4-4c88-b6c7-da092d6b6e35", 
"1793c6df-53a6-481b-a75c-c705f98d6900"],
 "entityTypeName" : "hive_table"
}'

Option 3 (With both entity GUIDs and type Name with list of uniq attributes)
curl --location --request POST 
'http://atlas-host:31000/api/atlas/v2/entity/bulk/classification?skipFailedEntities=True'
 \
--header 'Authorization: Basic YWRtaW46YWRtaW4xMjM=' \
--header 'Content-Type: application/json' \
--data-raw '{
 "classification" : {
 "propagate" : false,
 "attributes" : {
 "type" : "false"
 },
 "typeName" : "TEST_TAG_TABLE"
 },
 "entitiesUniqAttributes" : [
 \{"qualifiedName": "db1.table43@cm"},
 \{"qualifiedName": "db1.table8@cm"},
 \{"qualifiedName": "db1.table55@cm"}],
 "entityGuids" : [
 "6d6ab082-9a62-4aea-97b7-2b7337173631",
 "9a0d3275-eb42-4229-ac51-6db1ddf3ccc6"],
 "entityTypeName" : "hive_table"
}'

> Atlas bulk clarification REST should be enhanced to associate classification 
> to bulk entities with uniq attribute and type
> --
>
> Key: ATLAS-4307
> URL: https://issues.apache.org/jira/browse/ATLAS-4307
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-4307..patch
>
>
> Right now there is no REST to support this. The existing bulk add 
> classification takes a list of GUIDs and associates the classification to 
> them. The existing one should also take type name and list of unique 
> attribute values for entities and tag the classification if it finds entries.



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


[jira] [Updated] (ATLAS-4307) Atlas bulk clarification REST should be enhanced to associate classification to bulk entities with uniq attribute and type

2021-05-25 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-4307:
-
Summary: Atlas bulk clarification REST should be enhanced to associate 
classification to bulk entities with uniq attribute and type  (was: Atlas 
should have REST to add a classification to bulk entities with uniq attribute 
and type)

> Atlas bulk clarification REST should be enhanced to associate classification 
> to bulk entities with uniq attribute and type
> --
>
> Key: ATLAS-4307
> URL: https://issues.apache.org/jira/browse/ATLAS-4307
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Right now there is no REST to support this. The existing bulk add 
> classification takes a list of GUIDs and associates the classification to 
> them. The existing one should also take type name and list of unique 
> attribute values for entities and tag the classification if it finds entries.



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


[jira] [Commented] (ATLAS-4307) Atlas should have REST to add a classification to bulk entities with uniq attribute and type

2021-05-25 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra commented on ATLAS-4307:
--

In case there is no entity found for the specific unique attribute and type and 
skipFailedEntities flag is not set to True then it will fail even there will be 
more specified unique attributes for other enttities. If skipFailedEntities = 
True then it will continue even there are some error for some entity.

> Atlas should have REST to add a classification to bulk entities with uniq 
> attribute and type
> 
>
> Key: ATLAS-4307
> URL: https://issues.apache.org/jira/browse/ATLAS-4307
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Right now there is no REST to support this. The existing bulk add 
> classification takes a list of GUIDs and associates the classification to 
> them. The existing one should also take type name and list of unique 
> attribute values for entities and tag the classification if it finds entries.



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


[jira] [Updated] (ATLAS-4307) Atlas should have REST to add a classification to bulk entities with uniq attribute and type

2021-05-25 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-4307:
-
Description: Right now there is no REST to support this. The existing bulk 
add classification takes a list of GUIDs and associates the classification to 
them. The existing one should also take type name and list of unique attribute 
values for entities and tag the classification if it finds entries.  (was: 
Right now there is no REST to support this. The existing bulk add 
classification takes list of GUIDs and associate the classification to them. 
The new one will take type name and list of uniq attribute values for each 
entity and tag the classification.)

> Atlas should have REST to add a classification to bulk entities with uniq 
> attribute and type
> 
>
> Key: ATLAS-4307
> URL: https://issues.apache.org/jira/browse/ATLAS-4307
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Right now there is no REST to support this. The existing bulk add 
> classification takes a list of GUIDs and associates the classification to 
> them. The existing one should also take type name and list of unique 
> attribute values for entities and tag the classification if it finds entries.



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


[jira] [Updated] (ATLAS-4307) Atlas should have REST to add a classification to bulk entities with uniq attribute and type

2021-05-25 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-4307:
-
Description: Right now there is no REST to support this. The existing bulk 
add classification takes list of GUIDs and associate the classification to 
them. The new one will take type name and list of uniq attribute values for 
each entity and tag the classification.

> Atlas should have REST to add a classification to bulk entities with uniq 
> attribute and type
> 
>
> Key: ATLAS-4307
> URL: https://issues.apache.org/jira/browse/ATLAS-4307
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Right now there is no REST to support this. The existing bulk add 
> classification takes list of GUIDs and associate the classification to them. 
> The new one will take type name and list of uniq attribute values for each 
> entity and tag the classification.



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


[jira] [Created] (ATLAS-4307) Atlas should have REST to add a classification to bulk entities with uniq attribute and type

2021-05-25 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-4307:


 Summary: Atlas should have REST to add a classification to bulk 
entities with uniq attribute and type
 Key: ATLAS-4307
 URL: https://issues.apache.org/jira/browse/ATLAS-4307
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra






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


[jira] [Commented] (ATLAS-4288) [Atlas: Glossary Term Bulk Import] Will all the data populated, while performing bulk import, PreferredToTerms relationship alone is not created

2021-05-17 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra commented on ATLAS-4288:
--

Changed code to take care of preferredToTerms relation when it exists without 
any other relations. Below it has also self-reference so now its throwing error 
for self reference and then creating the remaining relations successfully. 
Check below error messages and response json.

!image-2021-05-17-16-43-31-487.png!

Response json:

{
"failedImportInfoList": [
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_1",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_2",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_3",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_4",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_5",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_6",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_7",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_8",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_9",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_10",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_11",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_12",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_13",
"importStatus": "FAILED",
"remarks": "Invalid Term relationship: Term cant have a relationship with self"
}
],
"successImportInfoList": [
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_1",
"importStatus": "SUCCESS",
"remarks": 
"\{\"termGuid\":\"a83cf35d-22f5-4b4c-8d4f-1d658c85b0ae\",\"qualifiedName\":\"term_1@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_2",
"importStatus": "SUCCESS",
"remarks": 
"\{\"termGuid\":\"77d08bd2-9cff-489e-9240-50f2c0f68d89\",\"qualifiedName\":\"term_2@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_3",
"importStatus": "SUCCESS",
"remarks": 
"\{\"termGuid\":\"10563ed5-c1fb-438e-bead-b6f0ccbd4d44\",\"qualifiedName\":\"term_3@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_4",
"importStatus": "SUCCESS",
"remarks": 
"\{\"termGuid\":\"0f1ec608-4692-4041-b7d4-e270032f2bac\",\"qualifiedName\":\"term_4@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_5",
"importStatus": "SUCCESS",
"remarks": 
"\{\"termGuid\":\"30728c5b-99f6-4f69-a54a-2b0d4d49acef\",\"qualifiedName\":\"term_5@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_6",
"importStatus": "SUCCESS",
"remarks": 
"\{\"termGuid\":\"b075398a-f845-42ca-90b0-e1362c5757c4\",\"qualifiedName\":\"term_6@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_7",
"importStatus": "SUCCESS",
"remarks": 
"\{\"termGuid\":\"0c75f006-9d29-49db-96bb-b9c7738eb155\",\"qualifiedName\":\"term_7@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_8",
"importStatus": "SUCCESS",
"remarks": 
"\{\"termGuid\":\"e3cee557-1017-44ed-bfd1-fa42bf9f2b51\",\"qualifiedName\":\"term_8@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_9",
"importStatus": "SUCCESS",
"remarks": 
"\{\"termGuid\":\"63635428-a966-4843-b8c8-97576fa349da\",\"qualifiedName\":\"term_9@dharshmk_11\"}"
},
{
"parentObjectName": "dharshmk_11",
"childObjectName": "term_10",
"importStatus": "SUCCESS",
"remarks": 

[jira] [Updated] (ATLAS-4288) [Atlas: Glossary Term Bulk Import] Will all the data populated, while performing bulk import, PreferredToTerms relationship alone is not created

2021-05-17 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-4288:
-
Attachment: image-2021-05-17-16-43-31-487.png

> [Atlas: Glossary Term Bulk Import] Will all the data populated, while 
> performing bulk import, PreferredToTerms relationship alone is not created
> 
>
> Key: ATLAS-4288
> URL: https://issues.apache.org/jira/browse/ATLAS-4288
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: image-2021-05-17-16-43-31-487.png
>
>
> Consider the following input, here all the relations are established except 
> the preferredToTerms (term_2)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, 
> PreferredTermsGlossaryName, TermName, ShortDescription, LongDescription, 
> Examples, Abbreviation, Usage, AdditionalAttributes, TranslationTerms, 
> ValidValuesFor, Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTermsd 
> ,term_1,"short desc","long description", "Example", "G1", "Usage", 
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"dharshmk_11,term_2,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%""glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",dharshmk_11,term_3,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%",,,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,dharshmk_11,term_4,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%",,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,,dharshmk_11,term_5,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"dharshmk_11,term_6,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%""glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",dharshmk_11,term_7,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%",,,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,dharshmk_11,term_8,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%",,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,,dharshmk_11,term_9,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"dharshmk_11,term_10,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%""glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",dharshmk_11,term_11,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%",,,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,dharshmk_11,term_12,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%",,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,,dharshmk_11,term_13,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"
>  {code}
>  
> Before the above import happens, please do the initial import of the related 
> terms with the following input
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossaryBulkImport_1,termBulkImport_1
> glossaryBulkImport_1,termBulkImport_2
> glossaryBulkImport_1,termBulkImport_3
> glossaryBulkImport_1,termBulkImport_4
> glossaryBulkImport_1,termBulkImport_5
> glossaryBulkImport_2,termBulkImport_1
> glossaryBulkImport_2,termBulkImport_2
> glossaryBulkImport_2,termBulkImport_3
> glossaryBulkImport_2,termBulkImport_4
> glossaryBulkImport_2,termBulkImport_5
> glossaryBulkImport_3,termBulkImport_1
> glossaryBulkImport_3,termBulkImport_2
> 

[jira] [Resolved] (ATLAS-4287) [Atlas: Glossary Term Bulk Import] When there is self-reference in the input, bulk import is broken

2021-05-17 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra resolved ATLAS-4287.
--
Resolution: Duplicate

> [Atlas: Glossary Term Bulk Import] When there is self-reference in the input, 
> bulk import is broken
> ---
>
> Key: ATLAS-4287
> URL: https://issues.apache.org/jira/browse/ATLAS-4287
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> This was working on the previous build before that latest fix, but broken now.
> Scenario 1: Self-reference and Failure (2 failures expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1|glossary_1:term_2",{code}
> Scenario 2: Self-reference and Success  (1 failure expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1|glossary_1:term_2",
> glossary_1,term_2 {code}
> Scenatio 3: Only self reference  (1 failures expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1", {code}
> In all these cases we expect failure message which mentions about self 
> reference, this is currently broken.
> What makes this important is, in case of self-reference and success scenario, 
> the relationship is not established
>  



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


[jira] [Commented] (ATLAS-4287) [Atlas: Glossary Term Bulk Import] When there is self-reference in the input, bulk import is broken

2021-05-17 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra commented on ATLAS-4287:
--

Before the next import happens, please do the initial import of the related 
terms with the following input
{code:java}
GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, TranslatedTerms, 
IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
glossaryBulkImport_1,termBulkImport_1
glossaryBulkImport_1,termBulkImport_2{code}
Now with the below payload I tested and self-reference gives error message as 
expected.
{code:java}
GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, TranslatedTerms, 
IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
dharshmk_11,term_2,"short desc","long description", "Example", "G1", "Usage", 
"glossary:100%","dharshmk_11:term_2|glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_1:termBulkImport_2"{code}
Response as expected:

{
   "failedImportInfoList": [
   

{    "parentObjectName": "dharshmk_11",    "childObjectName": "term_2",    
"importStatus": "FAILED",    "remarks": "Invalid Term relationship: Term cant 
have a relationship with self"    }

   ],
   "successImportInfoList": [
   

{     "parentObjectName": "dharshmk_11",     "childObjectName": "term_2",     
"importStatus": "SUCCESS",     "remarks": 
"\\{\"termGuid\":\"7e6e4be7-1dc3-43de-8c7b-5f853113e406\",\"qualifiedName\":\"term_2@dharshmk_11\"}

"
   }
   ]
}
For the mentioned csv payload where this doesn't work is due to the fact that 
PreferredToTerms relationship doesn't work as filed by 
https://issues.apache.org/jira/browse/ATLAS-4288 Jira. So closing this as 
duplicate of ATLAS-4288

> [Atlas: Glossary Term Bulk Import] When there is self-reference in the input, 
> bulk import is broken
> ---
>
> Key: ATLAS-4287
> URL: https://issues.apache.org/jira/browse/ATLAS-4287
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> This was working on the previous build before that latest fix, but broken now.
> Scenario 1: Self-reference and Failure (2 failures expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1|glossary_1:term_2",{code}
> Scenario 2: Self-reference and Success  (1 failure expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1|glossary_1:term_2",
> glossary_1,term_2 {code}
> Scenatio 3: Only self reference  (1 failures expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1", {code}
> In all these cases we expect failure message which mentions about self 
> reference, this is currently broken.
> What makes this important is, in case of self-reference and success scenario, 
> the relationship is not established
>  



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


[jira] [Assigned] (ATLAS-4288) [Atlas: Glossary Term Bulk Import] Will all the data populated, while performing bulk import, PreferredToTerms relationship alone is not created

2021-05-17 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra reassigned ATLAS-4288:


Assignee: Sidharth Kumar Mishra

> [Atlas: Glossary Term Bulk Import] Will all the data populated, while 
> performing bulk import, PreferredToTerms relationship alone is not created
> 
>
> Key: ATLAS-4288
> URL: https://issues.apache.org/jira/browse/ATLAS-4288
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Consider the following input, here all the relations are established except 
> the preferredToTerms (term_2)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, 
> PreferredTermsGlossaryName, TermName, ShortDescription, LongDescription, 
> Examples, Abbreviation, Usage, AdditionalAttributes, TranslationTerms, 
> ValidValuesFor, Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTermsd 
> ,term_1,"short desc","long description", "Example", "G1", "Usage", 
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"dharshmk_11,term_2,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%""glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",dharshmk_11,term_3,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%",,,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,dharshmk_11,term_4,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%",,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,,dharshmk_11,term_5,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"dharshmk_11,term_6,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%""glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",dharshmk_11,term_7,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%",,,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,dharshmk_11,term_8,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%",,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,,dharshmk_11,term_9,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"dharshmk_11,term_10,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%""glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",dharshmk_11,term_11,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%",,,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,dharshmk_11,term_12,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%",,"glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2",,,dharshmk_11,term_13,"short
>  desc","long description", "Example", "G1", "Usage", 
> "glossary:100%","glossaryBulkImport_1:termBulkImport_1|glossaryBulkImport_2:termBulkImport_2"
>  {code}
>  
> Before the above import happens, please do the initial import of the related 
> terms with the following input
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossaryBulkImport_1,termBulkImport_1
> glossaryBulkImport_1,termBulkImport_2
> glossaryBulkImport_1,termBulkImport_3
> glossaryBulkImport_1,termBulkImport_4
> glossaryBulkImport_1,termBulkImport_5
> glossaryBulkImport_2,termBulkImport_1
> glossaryBulkImport_2,termBulkImport_2
> glossaryBulkImport_2,termBulkImport_3
> glossaryBulkImport_2,termBulkImport_4
> glossaryBulkImport_2,termBulkImport_5
> glossaryBulkImport_3,termBulkImport_1
> glossaryBulkImport_3,termBulkImport_2
> glossaryBulkImport_3,termBulkImport_3
> 

[jira] [Assigned] (ATLAS-4287) [Atlas: Glossary Term Bulk Import] When there is self-reference in the input, bulk import is broken

2021-05-17 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra reassigned ATLAS-4287:


Assignee: Sidharth Kumar Mishra

> [Atlas: Glossary Term Bulk Import] When there is self-reference in the input, 
> bulk import is broken
> ---
>
> Key: ATLAS-4287
> URL: https://issues.apache.org/jira/browse/ATLAS-4287
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> This was working on the previous build before that latest fix, but broken now.
> Scenario 1: Self-reference and Failure (2 failures expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1|glossary_1:term_2",{code}
> Scenario 2: Self-reference and Success  (1 failure expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1|glossary_1:term_2",
> glossary_1,term_2 {code}
> Scenatio 3: Only self reference  (1 failures expected at failedinfolist)
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1,,"glossary_1:term_1", {code}
> In all these cases we expect failure message which mentions about self 
> reference, this is currently broken.
> What makes this important is, in case of self-reference and success scenario, 
> the relationship is not established
>  



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


[jira] [Resolved] (ATLAS-4273) [Atlas: Glossary Term Bulk Import] When there is only 1 term imported via bulk import and if it fails, no proper reason is mentioned in response

2021-05-13 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra resolved ATLAS-4273.
--
Resolution: Won't Fix

> [Atlas: Glossary Term Bulk Import] When there is only 1 term imported via 
> bulk import and if it fails, no proper reason is mentioned in response
> 
>
> Key: ATLAS-4273
> URL: https://issues.apache.org/jira/browse/ATLAS-4273
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> The following fails as we do not support @ in term name
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_l,term_@_1 {code}
> But the failure is
> {code:java}
> {"errorCode":"ATLAS-409-00-011","errorMessage":"Glossary import failed"} 
> {code}
> The code is 409 which mean a conflict but the reason is different



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


[jira] [Resolved] (ATLAS-4275) [Atlas: Glossary Term Bulk Import] When there an incorrect data in preferred term column, it is not considered while importing

2021-05-10 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra resolved ATLAS-4275.
--
Resolution: Duplicate

> [Atlas: Glossary Term Bulk Import] When there an incorrect data in preferred 
> term column, it is not considered while importing
> --
>
> Key: ATLAS-4275
> URL: https://issues.apache.org/jira/browse/ATLAS-4275
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
>
> When there is an error in the PreferredTerms of the input, error is not 
> considered
> Consider the following input. Here the provided term "abcd:efgh" does not 
> exists in the system. 
>  The error is thrown when it is provided as an input for "*PreferredToTerms*" 
> column but not for "*PreferredTerms*" column
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> dharsh,term_1,"short desc","long description", "Example", "G1", "Usage", 
> "glossary:100%","abcd:efgh"
> dharsh,term_2,"short desc","long description", "Example", "G1", "Usage", 
> "glossary:100%""abcd:efgh", {code}
>  
> *Expectation:*
>  2 failed message info should be thrown one for term_1(incorrect 
> PreferredTerms) and the other for term_2(incorrect PreferredToTerms), but 
> only 1 is thrown
>  
> *Current output:*
> {code:java}
> {
>   "failedImportInfoList": [
> {
>   "parentObjectName": "dharsh",
>   "childObjectName": "term_2",
>   "importStatus": "FAILED",
>   "remarks": "The provided Reference efgh@abcd does not exist at Atlas 
> referred at record with TermName  : term_2 and GlossaryName : dharsh"
> }
>   ],
>   "successImportInfoList": [
> {
>   "parentObjectName": "dharsh",
>   "childObjectName": "term_1",
>   "importStatus": "SUCCESS",
>   "remarks": 
> "{\"termGuid\":\"284fe9a7-911c-423a-90bf-adf8231afb27\",\"qualifiedName\":\"term_1@dharsh\"}"
> },
> {
>   "parentObjectName": "dharsh",
>   "childObjectName": "term_2",
>   "importStatus": "SUCCESS",
>   "remarks": 
> "{\"termGuid\":\"29a51c8a-ce92-4988-8fca-feaf683c58dd\",\"qualifiedName\":\"term_2@dharsh\"}"
> }
>   ]
> } {code}
>  
> *Expected output:*
> {code:java}
> {
>   "failedImportInfoList": [
> {
>   "parentObjectName": "dharsh",
>   "childObjectName": "term_1",
>   "importStatus": "FAILED",
>   "remarks": "The provided Reference efgh@abcd does not exist at Atlas 
> referred at record with TermName  : term_1 and GlossaryName : dharsh"
> },
> {
>   "parentObjectName": "dharsh",
>   "childObjectName": "term_2",
>   "importStatus": "FAILED",
>   "remarks": "The provided Reference efgh@abcd does not exist at Atlas 
> referred at record with TermName  : term_2 and GlossaryName : dharsh"
> }
>   ],
>   "successImportInfoList": [
> {
>   "parentObjectName": "dharsh",
>   "childObjectName": "term_1",
>   "importStatus": "SUCCESS",
>   "remarks": 
> "{\"termGuid\":\"284fe9a7-911c-423a-90bf-adf8231afb27\",\"qualifiedName\":\"term_1@dharsh\"}"
> },
> {
>   "parentObjectName": "dharsh",
>   "childObjectName": "term_2",
>   "importStatus": "SUCCESS",
>   "remarks": 
> "{\"termGuid\":\"29a51c8a-ce92-4988-8fca-feaf683c58dd\",\"qualifiedName\":\"term_2@dharsh\"}"
> }
>   ]
> }  {code}



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


[jira] [Assigned] (ATLAS-4274) [Atlas: Glossary] Non matching relation are created via bulk import

2021-05-08 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra reassigned ATLAS-4274:


Assignee: Sidharth Kumar Mishra

> [Atlas: Glossary] Non matching relation are created via bulk import
> ---
>
> Key: ATLAS-4274
> URL: https://issues.apache.org/jira/browse/ATLAS-4274
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-05-04 at 3.31.00 PM.png, Screenshot 
> 2021-05-04 at 3.34.03 PM.png, Screenshot 2021-05-04 at 3.34.21 PM.png, 
> Screenshot 2021-05-04 at 3.34.36 PM.png
>
>
> The related terms provided in the input does not match the relation created 
> via import
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> a_glossary_1,term_1,,,"a_glossary_1:term_2"
> a_glossary_1,term_2,"a_glossary_1:term_3",,
> a_glossary_1,term_3,,"a_glossary_1:term_1", {code}
> !Screenshot 2021-05-04 at 3.31.00 PM.png|width=1973,height=127!
> !Screenshot 2021-05-04 at 3.34.03 PM.png|width=1038,height=578!
> !Screenshot 2021-05-04 at 3.34.21 PM.png|width=1005,height=563!
> !Screenshot 2021-05-04 at 3.34.36 PM.png|width=541,height=303!
>  



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


[jira] [Assigned] (ATLAS-4272) [Atlas: Glossary Term Bulk Import] Re-importing after deleting a glossary fails

2021-05-03 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra reassigned ATLAS-4272:


Assignee: Sidharth Kumar Mishra

> [Atlas: Glossary Term Bulk Import] Re-importing after deleting a glossary 
> fails 
> 
>
> Key: ATLAS-4272
> URL: https://issues.apache.org/jira/browse/ATLAS-4272
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Scenario: Import a glossary, after import delete the glossary and its terms 
> and reimport the same input
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> abc_glossary,term_1
> abc_glossary,term_2
> abc_glossary,term_3{code}
> This throws the following error
> {code:java}
> errorCode: "ATLAS-404-00-005",
> errorMessage: "Given instance guid 6363d630-a96e-4c15-a3ae-d4812dd67aa2 is 
> invalid/not found" {code}
> {code:java}
> 2021-05-03 13:33:43,562 ERROR - [etp813603842-30 - 
> 8f83ce44-0c56-4224-9f57-8211b3435b2e:] ~ graph rollback due to exception 
> AtlasBaseException:Given instance guid 45163be7-377a-4b74-b977-75fa5a4b5a2e 
> is invalid/not found (GraphTransactionInterceptor:202) 
> {code}



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


[jira] [Updated] (ATLAS-4261) Bulk Glossary Import Response and Failed Error Message Improvements

2021-04-26 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-4261:
-
Description: 
1. For bulk glossary import, if we have relations and there is some error 
present then the failed error message contains duplicate messages. 

2. The success response doesn't contains information about the relations

3. The failed messages at response contains extra '\n' 

 

> Bulk Glossary Import Response and Failed Error Message Improvements 
> 
>
> Key: ATLAS-4261
> URL: https://issues.apache.org/jira/browse/ATLAS-4261
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> 1. For bulk glossary import, if we have relations and there is some error 
> present then the failed error message contains duplicate messages. 
> 2. The success response doesn't contains information about the relations
> 3. The failed messages at response contains extra '\n' 
>  



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


[jira] [Created] (ATLAS-4261) Bulk Glossary Import Response and Failed Error Message Improvements

2021-04-26 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-4261:


 Summary: Bulk Glossary Import Response and Failed Error Message 
Improvements 
 Key: ATLAS-4261
 URL: https://issues.apache.org/jira/browse/ATLAS-4261
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra






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


[jira] [Commented] (ATLAS-4231) UI: Create icons for new entity types for Google Cloud Storage

2021-03-31 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra commented on ATLAS-4231:
--

Thanks [~prasadpp13]. It would be good to include Google Cloud Storage inside 
the icon to make it consistent with AWS S3 and ADLS Gen 2. 

> UI: Create icons for new entity types for Google Cloud Storage
> --
>
> Key: ATLAS-4231
> URL: https://issues.apache.org/jira/browse/ATLAS-4231
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.1.0
>Reporter: Sidharth Kumar Mishra
>Assignee: Sameer Shaikh
>Priority: Major
>  Labels: entity-icons
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 
> 0001-ATLAS-4231-UI-Create-icons-for-new-entity-types-for-.patch
>
>
> The model changes are part of ATLAS-4226



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


[jira] [Commented] (ATLAS-4226) Add model types for Google cloud platform

2021-03-31 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra commented on ATLAS-4226:
--

!image.png!

> Add model types for Google cloud platform 
> --
>
> Key: ATLAS-4226
> URL: https://issues.apache.org/jira/browse/ATLAS-4226
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-4226_2.patch, image.png
>
>
> Right now Atlas has no entity type for gcp paths. We should have the all the 
> types like bucket, object, virtual directory etc. for google cloud storage.



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


[jira] [Updated] (ATLAS-4226) Add model types for Google cloud platform

2021-03-31 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-4226:
-
Attachment: image.png

> Add model types for Google cloud platform 
> --
>
> Key: ATLAS-4226
> URL: https://issues.apache.org/jira/browse/ATLAS-4226
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-4226_2.patch, image.png
>
>
> Right now Atlas has no entity type for gcp paths. We should have the all the 
> types like bucket, object, virtual directory etc. for google cloud storage.



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


[jira] [Commented] (ATLAS-4231) UI: Create icons for new entity types for Google Cloud Storage

2021-03-30 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra commented on ATLAS-4231:
--

cc: [~jayendrap] 

> UI: Create icons for new entity types for Google Cloud Storage
> --
>
> Key: ATLAS-4231
> URL: https://issues.apache.org/jira/browse/ATLAS-4231
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sameer Shaikh
>Priority: Major
>
> The model changes are part of ATLAS-4226



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


[jira] [Assigned] (ATLAS-4231) UI: Create icons for new entity types for Google Cloud Storage

2021-03-30 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra reassigned ATLAS-4231:


Assignee: Sameer Shaikh

> UI: Create icons for new entity types for Google Cloud Storage
> --
>
> Key: ATLAS-4231
> URL: https://issues.apache.org/jira/browse/ATLAS-4231
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sameer Shaikh
>Priority: Major
>
> The model changes are part of ATLAS-4226



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


[jira] [Created] (ATLAS-4231) UI: Create icons for new entity types for Google Cloud Storage

2021-03-30 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-4231:


 Summary: UI: Create icons for new entity types for Google Cloud 
Storage
 Key: ATLAS-4231
 URL: https://issues.apache.org/jira/browse/ATLAS-4231
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra


The model changes are part of ATLAS-4226



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


[jira] [Created] (ATLAS-4230) Create new entity for Google cloud storage location from hive

2021-03-30 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-4230:


 Summary: Create new entity for Google cloud storage location from 
hive
 Key: ATLAS-4230
 URL: https://issues.apache.org/jira/browse/ATLAS-4230
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra


When I try to run the below create command at hive with GCP cloud configured - 

create external table hive_table_cloud_external_test1 (student_roll int, 
student_name string, student_dob date);

We see a hdfs path entity - gs://gcp-daily-test/testdir1/hiveurltests

Instead we should have a Google cloud storage directory entity and bucket 
entity created.



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


[jira] [Created] (ATLAS-4227) Remove aws_s3_v2_directory.objectPrefix uniqueness

2021-03-29 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-4227:


 Summary: Remove aws_s3_v2_directory.objectPrefix uniqueness
 Key: ATLAS-4227
 URL: https://issues.apache.org/jira/browse/ATLAS-4227
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra


For aws_s3_v2_directory.objectPrefix, the isUnique property is true.

based on the test here: (see verifyS3V2PseudoDir)

[https://github.com/apache/atlas/blob/d27790dfdde09a58db15064bbdaf77d224f61ecc/common/src/test/java/org/apache/atlas/utils/AtlasPathExtractorUtilTest.java]

if we have 2 AWS S3 files from different buckets:
 # s3://aws_my_bucket*1/1234567890/test.csv*
 # s3://aws_my_bucket*2/1234567890/test.csv*

as you see there is 2 different directories from different buckets, but having 
same objectPrefix, and different qualified name.

object 1:
aws_s3_v2_directory: qualifiedName: "s3://*aws_my_bucket1*/1234567890/"
objectPrefix: "/1234567890/"

object 2:
aws_s3_v2_directory:
qualifiedName: "s3://*aws_my_bucket2*/1234567890/"

objectPrefix: "/1234567890/"  

So we should remove uniqueness
 



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


[jira] [Created] (ATLAS-4226) Add model types for Google cloud platform

2021-03-25 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-4226:


 Summary: Add model types for Google cloud platform 
 Key: ATLAS-4226
 URL: https://issues.apache.org/jira/browse/ATLAS-4226
 Project: Atlas
  Issue Type: Improvement
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra


Right now Atlas has no entity type for gcp paths. We should have the all the 
types like bucket, object, virtual directory etc. for google cloud storage.



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


[jira] [Created] (ATLAS-4191) Creation of relations does not work for glossary import

2021-03-08 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-4191:


 Summary: Creation of relations does not work for glossary import
 Key: ATLAS-4191
 URL: https://issues.apache.org/jira/browse/ATLAS-4191
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra
 Attachments: Atlas BG template - smallish.csv

When importing glossary data in CSV format, any relations within the imported 
data lead to an error; import can only find referenced Terms that already exist 
in Atlas.

Example:  Term GA -> T1 has a 'seeAlso' relation to GA -> T2 and vice versa.

(See also attached CSV file)

This makes using relations with larger glossaries almost impossible to use: 
there will be circular references (as with 'seeAlso'), so even a two-step 
approach to import will not work.



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


[jira] [Updated] (ATLAS-4170) v2/entity/bulk Entity GET API is able to read unauthorised entities too when skipFailedEntities is passed as True

2021-02-18 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-4170:
-
Attachment: (was: ATLAS-4170.patch)

> v2/entity/bulk Entity GET API is able to read unauthorised entities too when 
> skipFailedEntities is passed as True
> -
>
> Key: ATLAS-4170
> URL: https://issues.apache.org/jira/browse/ATLAS-4170
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-4170.patch
>
>
> As part of https://issues.apache.org/jira/browse/ATLAS-3855, 
> skipFailedEntities was introduced to ignore the entities where it fails to 
> read
> When skipFailedEntities is not passed or is passed as 
> skipFailedEntities=False, then we get 403 with below error as expected
> {code:java}
> {
> "errorCode": "ATLAS-403-00-001",
> "errorMessage": "hrt is not authorized to perform read entity: 
> guid=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c"
> } {code}
> But when we pass skipFailedEntities=True, then API is able to retrieve the 
> data for even those entities on which the user has explicit deny conditions. 
> Ideally, we should be ignoring these unauthorised entities and return data 
> only for authorised ones. 
>  



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


[jira] [Updated] (ATLAS-4170) v2/entity/bulk Entity GET API is able to read unauthorised entities too when skipFailedEntities is passed as True

2021-02-18 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-4170:
-
Attachment: ATLAS-4170.patch

> v2/entity/bulk Entity GET API is able to read unauthorised entities too when 
> skipFailedEntities is passed as True
> -
>
> Key: ATLAS-4170
> URL: https://issues.apache.org/jira/browse/ATLAS-4170
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-4170.patch
>
>
> As part of https://issues.apache.org/jira/browse/ATLAS-3855, 
> skipFailedEntities was introduced to ignore the entities where it fails to 
> read
> When skipFailedEntities is not passed or is passed as 
> skipFailedEntities=False, then we get 403 with below error as expected
> {code:java}
> {
> "errorCode": "ATLAS-403-00-001",
> "errorMessage": "hrt is not authorized to perform read entity: 
> guid=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c"
> } {code}
> But when we pass skipFailedEntities=True, then API is able to retrieve the 
> data for even those entities on which the user has explicit deny conditions. 
> Ideally, we should be ignoring these unauthorised entities and return data 
> only for authorised ones. 
>  



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


[jira] [Created] (ATLAS-4170) v2/entity/bulk Entity GET API is able to read unauthorised entities too when skipFailedEntities is passed as True

2021-02-18 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-4170:


 Summary: v2/entity/bulk Entity GET API is able to read 
unauthorised entities too when skipFailedEntities is passed as True
 Key: ATLAS-4170
 URL: https://issues.apache.org/jira/browse/ATLAS-4170
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra


As part of https://issues.apache.org/jira/browse/ATLAS-3855, skipFailedEntities 
was introduced to ignore the entities where it fails to read

When skipFailedEntities is not passed or is passed as skipFailedEntities=False, 
then we get 403 with below error as expected
{code:java}
{
"errorCode": "ATLAS-403-00-001",
"errorMessage": "hrt is not authorized to perform read entity: 
guid=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c"
} {code}
But when we pass skipFailedEntities=True, then API is able to retrieve the data 
for even those entities on which the user has explicit deny conditions. 
Ideally, we should be ignoring these unauthorised entities and return data only 
for authorised ones. 
 



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


[jira] [Assigned] (ATLAS-4126) Rewrite enable value is not present at Atlas for Materialized View metadata

2021-02-03 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra reassigned ATLAS-4126:


Assignee: Sidharth Kumar Mishra

> Rewrite enable value is not present at Atlas for Materialized View metadata
> ---
>
> Key: ATLAS-4126
> URL: https://issues.apache.org/jira/browse/ATLAS-4126
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Repro steps:
> create table test_1 (id integer);
> CREATE MATERIALIZED VIEW test_mv_ctas_1 as select * from test_1;
> ALTER MATERIALIZED VIEW test_mv_ctas_1 enable rewrite;
> After this go to Atlas and see the Rewrite enable value is not present at 
> Atlas for the Materialized View entity test_mv_ctas_1
> [https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.5/materialized-view/content/hive_alter_materialized_view_rewrite.html]
> Even checked  parameters like transient_lastDdlTime is not getting populated 
> at hive_table of type MATERIALIZED_VIEW



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


[jira] [Created] (ATLAS-4126) Rewrite enable value is not present at Atlas for Materialized View metadata

2021-02-03 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-4126:


 Summary: Rewrite enable value is not present at Atlas for 
Materialized View metadata
 Key: ATLAS-4126
 URL: https://issues.apache.org/jira/browse/ATLAS-4126
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra


Repro steps:

create table test_1 (id integer);

CREATE MATERIALIZED VIEW test_mv_ctas_1 as select * from test_1;
ALTER MATERIALIZED VIEW test_mv_ctas_1 enable rewrite;

After this go to Atlas and see the Rewrite enable value is not present at Atlas 
for the Materialized View entity test_mv_ctas_1

[https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.5/materialized-view/content/hive_alter_materialized_view_rewrite.html]

Even checked  parameters like transient_lastDdlTime is not getting populated at 
hive_table of type MATERIALIZED_VIEW



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


[jira] [Created] (ATLAS-4123) Lineage missing in case of CREATE MATERIALIZED VIEW query at Hive

2021-02-02 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-4123:


 Summary: Lineage missing in case of CREATE MATERIALIZED VIEW query 
at Hive
 Key: ATLAS-4123
 URL: https://issues.apache.org/jira/browse/ATLAS-4123
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra


Issue:

At hive run the below queries:

create table test_1 (id integer);
CREATE MATERIALIZED VIEW test_mv_ctas_1 as select * from test_1;

Expected behaviour:

At Atlas we should have the lineage created between hive_table entity test_1 
and test_mv_ctas_1

 



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


[jira] [Assigned] (ATLAS-4123) Lineage missing in case of CREATE MATERIALIZED VIEW query at Hive

2021-02-02 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra reassigned ATLAS-4123:


Assignee: Sidharth Kumar Mishra

> Lineage missing in case of CREATE MATERIALIZED VIEW query at Hive
> -
>
> Key: ATLAS-4123
> URL: https://issues.apache.org/jira/browse/ATLAS-4123
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Issue:
> At hive run the below queries:
> create table test_1 (id integer);
> CREATE MATERIALIZED VIEW test_mv_ctas_1 as select * from test_1;
> Expected behaviour:
> At Atlas we should have the lineage created between hive_table entity test_1 
> and test_mv_ctas_1
>  



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


[jira] [Updated] (ATLAS-4099) adls_gen2_directory, Hive Hook : An extra "/" is seen in adls_gen2_directory created by Hook

2021-01-12 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-4099:
-
Attachment: ATLAS-4099-Removed-slash-from-adls_gen2_directory_2.patch

> adls_gen2_directory, Hive Hook : An extra "/" is seen in adls_gen2_directory 
> created by Hook
> 
>
> Key: ATLAS-4099
> URL: https://issues.apache.org/jira/browse/ATLAS-4099
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-4099-Removed-slash-from-adls_gen2_directory_2.patch
>
>
> For the query :
> {code:java}
> create external table ext_table(id int) location 
> 'abfs://contai...@storageaccount.dfs.core.windows.net/test51' {code}
> adls_gen2_directory created by Hook has QualifiedName : 
> *abfs://container@storageaccount/test51/@cm*
> whereas , adls_gen2_directory created by Extractor has QualifiedName:
> *abfs://**container@storageaccount/test51**@cm*
> There is an extra "/" after storage account name which causes issue. Because 
> of this , duplicate entities are created.



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


[jira] [Updated] (ATLAS-4099) adls_gen2_directory, Hive Hook : An extra "/" is seen in adls_gen2_directory created by Hook

2021-01-12 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-4099:
-
Attachment: (was: 
ATLAS-4099-Removed-slash-from-adls_gen2_directory.patch)

> adls_gen2_directory, Hive Hook : An extra "/" is seen in adls_gen2_directory 
> created by Hook
> 
>
> Key: ATLAS-4099
> URL: https://issues.apache.org/jira/browse/ATLAS-4099
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-4099-Removed-slash-from-adls_gen2_directory_2.patch
>
>
> For the query :
> {code:java}
> create external table ext_table(id int) location 
> 'abfs://contai...@storageaccount.dfs.core.windows.net/test51' {code}
> adls_gen2_directory created by Hook has QualifiedName : 
> *abfs://container@storageaccount/test51/@cm*
> whereas , adls_gen2_directory created by Extractor has QualifiedName:
> *abfs://**container@storageaccount/test51**@cm*
> There is an extra "/" after storage account name which causes issue. Because 
> of this , duplicate entities are created.



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


[jira] [Created] (ATLAS-4099) adls_gen2_directory, Hive Hook : An extra "/" is seen in adls_gen2_directory created by Hook

2021-01-12 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-4099:


 Summary: adls_gen2_directory, Hive Hook : An extra "/" is seen in 
adls_gen2_directory created by Hook
 Key: ATLAS-4099
 URL: https://issues.apache.org/jira/browse/ATLAS-4099
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra


For the query :
{code:java}
create external table ext_table(id int) location 
'abfs://contai...@storageaccount.dfs.core.windows.net/test51' {code}
adls_gen2_directory created by Hook has QualifiedName : 

*abfs://container@storageaccount/test51/@cm*

whereas , adls_gen2_directory created by Extractor has QualifiedName:

*abfs://**container@storageaccount/test51**@cm*

There is an extra "/" after storage account name which causes issue. Because of 
this , duplicate entities are created.



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


[jira] [Assigned] (ATLAS-4083) Change the existing ADLS Gen2 type with new attributes

2020-12-15 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra reassigned ATLAS-4083:


Assignee: Sidharth Kumar Mishra

> Change the existing ADLS Gen2 type with new attributes
> --
>
> Key: ATLAS-4083
> URL: https://issues.apache.org/jira/browse/ATLAS-4083
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> We should change the existing ADLS Gen2 type with new attributes as per the 
> 005-azure_adls_add_attributes.json patch



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


[jira] [Created] (ATLAS-4083) Change the existing ADLS Gen2 type with new attributes

2020-12-15 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-4083:


 Summary: Change the existing ADLS Gen2 type with new attributes
 Key: ATLAS-4083
 URL: https://issues.apache.org/jira/browse/ATLAS-4083
 Project: Atlas
  Issue Type: Improvement
Reporter: Sidharth Kumar Mishra


We should change the existing ADLS Gen2 type with new attributes as per the 
005-azure_adls_add_attributes.json patch



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


[jira] [Assigned] (ATLAS-4082) Add more attributes like create or last modify time, contentLength etc. to ADLS Gen2 types

2020-12-15 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra reassigned ATLAS-4082:


Assignee: Sidharth Kumar Mishra

> Add more attributes like create or last modify time, contentLength etc. to 
> ADLS Gen2 types
> --
>
> Key: ATLAS-4082
> URL: https://issues.apache.org/jira/browse/ATLAS-4082
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> We need more attributes to existing ADLS Gen2 types like 
> contentLength
> creationTime
> lastModifiedTime
> type
> etc.



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


[jira] [Created] (ATLAS-4082) Add more attributes like create or last modify time, contentLength etc. to ADLS Gen2 types

2020-12-15 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-4082:


 Summary: Add more attributes like create or last modify time, 
contentLength etc. to ADLS Gen2 types
 Key: ATLAS-4082
 URL: https://issues.apache.org/jira/browse/ATLAS-4082
 Project: Atlas
  Issue Type: Improvement
Reporter: Sidharth Kumar Mishra


We need more attributes to existing ADLS Gen2 types like 

contentLength

creationTime

lastModifiedTime

type

etc.



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


[jira] [Updated] (ATLAS-4081) Atlas incorrectly reports successful change to glossary term

2020-12-14 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-4081:
-
Description: When I log into Atlas as a user that does not have permissions 
to change the description for a glossary term (entity-type 
{{AtlasGlossaryTerm}}), and I try to make such a change, I get the message that 
it has successfully updated. It has not been, which is the correct thing, but I 
should get a message that this user does not have permission to make the 
change. (This is what happens when I try to change the glossary description, 
entity-type {{AtlasGlossary}})

> Atlas incorrectly reports successful change to glossary term
> 
>
> Key: ATLAS-4081
> URL: https://issues.apache.org/jira/browse/ATLAS-4081
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> When I log into Atlas as a user that does not have permissions to change the 
> description for a glossary term (entity-type {{AtlasGlossaryTerm}}), and I 
> try to make such a change, I get the message that it has successfully 
> updated. It has not been, which is the correct thing, but I should get a 
> message that this user does not have permission to make the change. (This is 
> what happens when I try to change the glossary description, entity-type 
> {{AtlasGlossary}})



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


[jira] [Assigned] (ATLAS-4081) Atlas incorrectly reports successful change to glossary term

2020-12-14 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra reassigned ATLAS-4081:


Assignee: Sidharth Kumar Mishra

> Atlas incorrectly reports successful change to glossary term
> 
>
> Key: ATLAS-4081
> URL: https://issues.apache.org/jira/browse/ATLAS-4081
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>




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


[jira] [Created] (ATLAS-4081) Atlas incorrectly reports successful change to glossary term

2020-12-14 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-4081:


 Summary: Atlas incorrectly reports successful change to glossary 
term
 Key: ATLAS-4081
 URL: https://issues.apache.org/jira/browse/ATLAS-4081
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra






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


[jira] [Updated] (ATLAS-3921) Need migration path from AWS s3 v1 to v2 entities

2020-08-13 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3921:
-
Issue Type: Improvement  (was: Bug)

> Need migration path from AWS s3 v1 to v2 entities
> -
>
> Key: ATLAS-3921
> URL: https://issues.apache.org/jira/browse/ATLAS-3921
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> We have introduced the new AWS S3 V2 entity at Atlas. After upgrade the 
> service like Hive will create the new V2 entities at Atlas, but the old v1 
> Aws S3 entity will not be migrated to new one. This will cause missing 
> relationship and/or lineage. We should have a migration path from the old v1 
> entity to new v2 entity .



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


[jira] [Created] (ATLAS-3921) Need migration path from AWS s3 v1 to v2 entities

2020-08-13 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3921:


 Summary: Need migration path from AWS s3 v1 to v2 entities
 Key: ATLAS-3921
 URL: https://issues.apache.org/jira/browse/ATLAS-3921
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra


We have introduced the new AWS S3 V2 entity at Atlas. After upgrade the service 
like Hive will create the new V2 entities at Atlas, but the old v1 Aws S3 
entity will not be migrated to new one. This will cause missing relationship 
and/or lineage. We should have a migration path from the old v1 entity to new 
v2 entity .



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


[jira] [Assigned] (ATLAS-3877) Purged entity audit throws 404 Entity not found error

2020-07-08 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra reassigned ATLAS-3877:


Assignee: Sidharth Kumar Mishra

> Purged entity audit throws 404 Entity not found error
> -
>
> Key: ATLAS-3877
> URL: https://issues.apache.org/jira/browse/ATLAS-3877
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Sharmadha S
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: rc2.png
>
>
> 1. Create an hdfs_path entity.
> 2. Delete the entity using DELETE: /api/atlas/v2/entity/guid/. The 
> entity is soft deleted
> 3. Purge the entity using PUT : /api/atlas/admin/purge with body [""]
> 4. Go to admin -> Administration -> Audits
> 5. Click on the GUID of purged entity. 
> The purged entity details window opens but Atlas throws a 404 error "Given 
> entity GUID is invalid/not found" . Attached screenshot.



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


[jira] [Updated] (ATLAS-3806) Classifications information missing in notification events during entity create/update/delete

2020-05-22 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3806:
-
Summary: Classifications information missing in notification events during 
entity create/update/delete  (was: Classifications information missing in 
notification events during entity update/delete)

> Classifications information missing in notification events during entity 
> create/update/delete
> -
>
> Key: ATLAS-3806
> URL: https://issues.apache.org/jira/browse/ATLAS-3806
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-3806.patch
>
>




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


[jira] [Updated] (ATLAS-3806) Classifications information missing in notification events during entity create/update

2020-05-22 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3806:
-
Summary: Classifications information missing in notification events during 
entity create/update  (was: Classifications information missing in notification 
events during entity create/update/delete)

> Classifications information missing in notification events during entity 
> create/update
> --
>
> Key: ATLAS-3806
> URL: https://issues.apache.org/jira/browse/ATLAS-3806
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-3806.patch
>
>




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


[jira] [Created] (ATLAS-3806) Classifications information missing in notification events during entity update/delete

2020-05-22 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3806:


 Summary: Classifications information missing in notification 
events during entity update/delete
 Key: ATLAS-3806
 URL: https://issues.apache.org/jira/browse/ATLAS-3806
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra






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


[jira] [Created] (ATLAS-3785) Modify the aws s3 v2 model to make relationship def end points as legacy attributes and objectPrefix as optional

2020-05-07 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3785:


 Summary: Modify the aws s3 v2 model to make relationship def end 
points as legacy attributes and objectPrefix as optional
 Key: ATLAS-3785
 URL: https://issues.apache.org/jira/browse/ATLAS-3785
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra


Modify the aws s3 v2 model to make relationship def end points as legacy 
attributes and objectPrefix as optional



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


[jira] [Commented] (ATLAS-3781) update authorization to admin-purge for admin entity purge Rest

2020-05-05 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra commented on ATLAS-3781:
--

Duplicate to https://issues.apache.org/jira/browse/ATLAS-3575

> update authorization to admin-purge for admin entity purge Rest
> ---
>
> Key: ATLAS-3781
> URL: https://issues.apache.org/jira/browse/ATLAS-3781
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>




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


[jira] [Resolved] (ATLAS-3781) update authorization to admin-purge for admin entity purge Rest

2020-05-05 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra resolved ATLAS-3781.
--
Resolution: Duplicate

> update authorization to admin-purge for admin entity purge Rest
> ---
>
> Key: ATLAS-3781
> URL: https://issues.apache.org/jira/browse/ATLAS-3781
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>




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


[jira] [Created] (ATLAS-3781) update authorization to admin-purge for admin entity purge Rest

2020-05-05 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3781:


 Summary: update authorization to admin-purge for admin entity 
purge Rest
 Key: ATLAS-3781
 URL: https://issues.apache.org/jira/browse/ATLAS-3781
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra






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


[jira] [Updated] (ATLAS-3747) Atlas Admin Purge API should take list of guids as body with operation Put instead of Delete

2020-04-21 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3747:
-
Summary: Atlas Admin Purge API should take list of guids as body with 
operation Put instead of Delete  (was: Atlas Admin Purge API should take list 
of guids as query param instead of body)

> Atlas Admin Purge API should take list of guids as body with operation Put 
> instead of Delete
> 
>
> Key: ATLAS-3747
> URL: https://issues.apache.org/jira/browse/ATLAS-3747
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-3747.patch
>
>




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


[jira] [Created] (ATLAS-3747) Atlas Admin Purge API should take list of guids as query param instead of body

2020-04-21 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3747:


 Summary: Atlas Admin Purge API should take list of guids as query 
param instead of body
 Key: ATLAS-3747
 URL: https://issues.apache.org/jira/browse/ATLAS-3747
 Project: Atlas
  Issue Type: New Feature
Reporter: Sidharth Kumar Mishra






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


[jira] [Assigned] (ATLAS-3747) Atlas Admin Purge API should take list of guids as query param instead of body

2020-04-21 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra reassigned ATLAS-3747:


Assignee: Sidharth Kumar Mishra

> Atlas Admin Purge API should take list of guids as query param instead of body
> --
>
> Key: ATLAS-3747
> URL: https://issues.apache.org/jira/browse/ATLAS-3747
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>




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


[jira] [Updated] (ATLAS-3730) In case Hard delete or Purge of an Entity we should make the entity status as purged instead of deleted at classification

2020-04-13 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3730:
-
Description: Right now if we do hard delete or purge of an entity the 
status for the entity is still deleted at classification. Due to this it's hard 
to know if any entity is really purged from classification  (was: Right now if 
we do hard delete or purge of an entity the status for the entity is still 
deleted. Due to this it's hard to know if any entity is really purged from the 
header which we keep.)

> In case Hard delete or Purge of an Entity we should make the entity status as 
> purged instead of deleted at classification
> -
>
> Key: ATLAS-3730
> URL: https://issues.apache.org/jira/browse/ATLAS-3730
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-3730.patch
>
>
> Right now if we do hard delete or purge of an entity the status for the 
> entity is still deleted at classification. Due to this it's hard to know if 
> any entity is really purged from classification



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


[jira] [Updated] (ATLAS-3730) In case Hard delete or Purge of an Entity we should make the entity status as purged instead of deleted at classification

2020-04-13 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3730:
-
Summary: In case Hard delete or Purge of an Entity we should make the 
entity status as purged instead of deleted at classification  (was: In case 
Hard delete and Purge of an Entity we should make the entity status as purged 
instead of deleted)

> In case Hard delete or Purge of an Entity we should make the entity status as 
> purged instead of deleted at classification
> -
>
> Key: ATLAS-3730
> URL: https://issues.apache.org/jira/browse/ATLAS-3730
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-3730.patch
>
>
> Right now if we do hard delete or purge of an entity the status for the 
> entity is still deleted. Due to this it's hard to know if any entity is 
> really purged from the header which we keep.



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


[jira] [Created] (ATLAS-3730) In case Hard delete and Purge of an Entity we should make the entity status as purged instead of deleted

2020-04-13 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3730:


 Summary: In case Hard delete and Purge of an Entity we should make 
the entity status as purged instead of deleted
 Key: ATLAS-3730
 URL: https://issues.apache.org/jira/browse/ATLAS-3730
 Project: Atlas
  Issue Type: New Feature
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra


Right now if we do hard delete or purge of an entity the status for the entity 
is still deleted. Due to this it's hard to know if any entity is really purged 
from the header which we keep.



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


[jira] [Commented] (ATLAS-3729) Add audit operation as a parameter to v2/entity/{guid}/audit

2020-04-13 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra commented on ATLAS-3729:
--

We should be able to filter the entity audit records based on audit operations 
which can be used by GUI in case of purge entity.

> Add audit operation as a parameter to v2/entity/{guid}/audit
> 
>
> Key: ATLAS-3729
> URL: https://issues.apache.org/jira/browse/ATLAS-3729
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>




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


[jira] [Created] (ATLAS-3729) Add audit operation as a parameter to v2/entity/{guid}/audit

2020-04-13 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3729:


 Summary: Add audit operation as a parameter to 
v2/entity/{guid}/audit
 Key: ATLAS-3729
 URL: https://issues.apache.org/jira/browse/ATLAS-3729
 Project: Atlas
  Issue Type: New Feature
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra






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


[jira] [Updated] (ATLAS-3727) Add get result details REST for admin audit record

2020-04-10 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3727:
-
Summary: Add get result details REST for admin audit record  (was: Add get 
purge result summary REST for admin audit record)

> Add get result details REST for admin audit record
> --
>
> Key: ATLAS-3727
> URL: https://issues.apache.org/jira/browse/ATLAS-3727
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Right now purge admin audit result stores purged entities guids. We need a 
> separate REST call to get more details summary of the entities purged.



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


[jira] [Updated] (ATLAS-3727) Add get purge result summary REST for admin audit record

2020-04-10 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3727:
-
Issue Type: New Feature  (was: Bug)

> Add get purge result summary REST for admin audit record
> 
>
> Key: ATLAS-3727
> URL: https://issues.apache.org/jira/browse/ATLAS-3727
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Right now purge admin audit result stores purged entities guids. We need a 
> separate REST call to get more details summary of the entities purged.



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


[jira] [Assigned] (ATLAS-3727) Add get purge result summary REST for admin audit record

2020-04-10 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra reassigned ATLAS-3727:


Assignee: Sidharth Kumar Mishra

> Add get purge result summary REST for admin audit record
> 
>
> Key: ATLAS-3727
> URL: https://issues.apache.org/jira/browse/ATLAS-3727
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Right now purge admin audit result stores purged entities guids. We need a 
> separate REST call to get more details summary of the entities purged.



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


[jira] [Created] (ATLAS-3727) Add get purge result summary REST for admin audit record

2020-04-08 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3727:


 Summary: Add get purge result summary REST for admin audit record
 Key: ATLAS-3727
 URL: https://issues.apache.org/jira/browse/ATLAS-3727
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sidharth Kumar Mishra


Right now purge admin audit result stores purged entities guids. We need a 
separate REST call to get more details summary of the entities purged.



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


[jira] [Created] (ATLAS-3726) Add result count to Atlas Admin Audit and enable filters on count for get audit

2020-04-08 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3726:


 Summary: Add result count to Atlas Admin Audit and enable filters 
on count for get audit
 Key: ATLAS-3726
 URL: https://issues.apache.org/jira/browse/ATLAS-3726
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra






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


[jira] [Created] (ATLAS-3719) Tag and Type search is not doing index search

2020-04-06 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3719:


 Summary: Tag and Type search is not doing index search
 Key: ATLAS-3719
 URL: https://issues.apache.org/jira/browse/ATLAS-3719
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra






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


[jira] [Created] (ATLAS-3707) Atlas Purge entity is generating both purge and delete audit

2020-03-30 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3707:


 Summary: Atlas Purge entity is generating both purge and delete 
audit 
 Key: ATLAS-3707
 URL: https://issues.apache.org/jira/browse/ATLAS-3707
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra


It should generate only purge audit



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


[jira] [Created] (ATLAS-3684) Atlas glossary get is taking more time when number of terms increase

2020-03-24 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3684:


 Summary: Atlas glossary get is taking more time when number of 
terms increase
 Key: ATLAS-3684
 URL: https://issues.apache.org/jira/browse/ATLAS-3684
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra


If we create a glossary Item and create around 3k terms inside it, get glossary 
takes around 25-30 seconds which is a lot. 



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


[jira] [Commented] (ATLAS-3518) Create Audit Framework for Atlas Purge Entity

2020-02-27 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra commented on ATLAS-3518:
--

The distro (TestMetaDate.py) test case failure is not related to my changes and 
been confirmed

> Create Audit Framework for Atlas Purge Entity
> -
>
> Key: ATLAS-3518
> URL: https://issues.apache.org/jira/browse/ATLAS-3518
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 2.0.0
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3518-16.patch
>
>
> Right now for purge, delete entity, etc. at Atlas we create audit entry at 
> HBase. User can go to entity and click on audit to see the audit information 
> for that particular entity. But if user purge one entity there will not be 
> any vertex at Janus graph and user will not able to get the purge audit which 
> is important for governance purpose.



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


[jira] [Updated] (ATLAS-3518) Create Audit Framework for Atlas Purge Entity

2020-02-27 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3518:
-
Attachment: ATLAS-3518-16.patch

> Create Audit Framework for Atlas Purge Entity
> -
>
> Key: ATLAS-3518
> URL: https://issues.apache.org/jira/browse/ATLAS-3518
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 2.0.0
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3518-16.patch
>
>
> Right now for purge, delete entity, etc. at Atlas we create audit entry at 
> HBase. User can go to entity and click on audit to see the audit information 
> for that particular entity. But if user purge one entity there will not be 
> any vertex at Janus graph and user will not able to get the purge audit which 
> is important for governance purpose.



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


[jira] [Updated] (ATLAS-3518) Create Audit Framework for Atlas Purge Entity

2020-02-27 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3518:
-
Attachment: (was: ATLAS-3518.patch)

> Create Audit Framework for Atlas Purge Entity
> -
>
> Key: ATLAS-3518
> URL: https://issues.apache.org/jira/browse/ATLAS-3518
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 2.0.0
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3518-16.patch
>
>
> Right now for purge, delete entity, etc. at Atlas we create audit entry at 
> HBase. User can go to entity and click on audit to see the audit information 
> for that particular entity. But if user purge one entity there will not be 
> any vertex at Janus graph and user will not able to get the purge audit which 
> is important for governance purpose.



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


[jira] [Created] (ATLAS-3605) Test case failure due to addition of two fields displayName and userDescription to base model

2020-01-31 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3605:


 Summary: Test case failure due to addition of two fields 
displayName and userDescription to base model 
 Key: ATLAS-3605
 URL: https://issues.apache.org/jira/browse/ATLAS-3605
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra


As Part of ATLAS_3559 we have added two new fields and duw to that there are 
test case failures at EntityJerseyResourceIT.java.

 

The failure details:

[https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1616/console]



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


[jira] [Assigned] (ATLAS-3500) Implement S3 Bulk Extraction

2020-01-21 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra reassigned ATLAS-3500:


Assignee: Sidharth Kumar Mishra  (was: Sridhar)

> Implement S3 Bulk Extraction
> 
>
> Key: ATLAS-3500
> URL: https://issues.apache.org/jira/browse/ATLAS-3500
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Sridhar
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>




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


[jira] [Created] (ATLAS-3564) New AWS S3 model addition

2019-12-17 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3564:


 Summary: New AWS S3 model addition
 Key: ATLAS-3564
 URL: https://issues.apache.org/jira/browse/ATLAS-3564
 Project: Atlas
  Issue Type: New Feature
  Components:  atlas-core
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra






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


[jira] [Commented] (ATLAS-2985) Fix delete handlers and relationship store

2019-12-03 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra commented on ATLAS-2985:
--

Hi [~alollo],

This is been resolved as part of ATLAS-3477. There is one more follow up 
feature for auditing the purge which is being tracked as part of ATLAS-3518.

> Fix delete handlers and relationship store
> --
>
> Key: ATLAS-2985
> URL: https://issues.apache.org/jira/browse/ATLAS-2985
> Project: Atlas
>  Issue Type: Bug
>Reporter: Graham Wallis
>Assignee: Graham Wallis
>Priority: Critical
> Attachments: ATLAS-2985-2018-11-30.patch
>
>
> The problems this fixes are as follows:
>  * following a soft delete, a hard delete is not possible because the entity 
> or relationship will have status DELETED, and prior to this Jira and patch 
> the abstract delete handler skips the delete. 
>  * during a soft delete the modified-time, modified-by and version number 
> attributes on the entity or relationship should be updated, but 
> updateRelationship does not update system attributes - this Jira and patch 
> updates the system attributes that will need to be updated during a delete or 
> other update operations.
>  * also fixes a minor copy-paste debug logging error.



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


[jira] [Created] (ATLAS-3524) Add new privilege - admin-purge at ranger

2019-11-14 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3524:


 Summary: Add new privilege - admin-purge at ranger
 Key: ATLAS-3524
 URL: https://issues.apache.org/jira/browse/ATLAS-3524
 Project: Atlas
  Issue Type: New Feature
  Components:  atlas-core
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra


For Atlas Admin Purge we need to add new privilege - admin-purge at ranger and 
change the atlas purge to verifyAccess accordingly.



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


[jira] [Updated] (ATLAS-3522) Add new REST API to purge an entity at Atlas using typeName/uniqueAttributes

2019-11-12 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3522:
-
Description: Add new method that take List as parameter for 
purge. Such method can be useful in purging entities using 
typeName/uniqueAttributes.

> Add new REST API to purge an entity at Atlas using typeName/uniqueAttributes
> 
>
> Key: ATLAS-3522
> URL: https://issues.apache.org/jira/browse/ATLAS-3522
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Add new method that take List as parameter for purge. Such 
> method can be useful in purging entities using typeName/uniqueAttributes.



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


[jira] [Created] (ATLAS-3522) Add new REST API to purge an entity at Atlas using typeName/uniqueAttributes

2019-11-12 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3522:


 Summary: Add new REST API to purge an entity at Atlas using 
typeName/uniqueAttributes
 Key: ATLAS-3522
 URL: https://issues.apache.org/jira/browse/ATLAS-3522
 Project: Atlas
  Issue Type: New Feature
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra






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


[jira] [Updated] (ATLAS-3518) Create Audit Framework for Atlas Purge Entity

2019-11-07 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3518:
-
Issue Type: New Feature  (was: Bug)

> Create Audit Framework for Atlas Purge Entity
> -
>
> Key: ATLAS-3518
> URL: https://issues.apache.org/jira/browse/ATLAS-3518
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Right now for purge, delete entity, etc. at Atlas we create audit entry at 
> HBase. User can go to entity and click on audit to see the audit information 
> for that particular entity. But if user purge one entity there will not be 
> any vertex at Janus graph and user will not able to get the purge audit which 
> is important for governance purpose.



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


[jira] [Created] (ATLAS-3518) Create Audit Framework for Atlas Purge Entity

2019-11-07 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3518:


 Summary: Create Audit Framework for Atlas Purge Entity
 Key: ATLAS-3518
 URL: https://issues.apache.org/jira/browse/ATLAS-3518
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra


Right now for purge, delete entity, etc. at Atlas we create audit entry at 
HBase. User can go to entity and click on audit to see the audit information 
for that particular entity. But if user purge one entity there will not be any 
vertex at Janus graph and user will not able to get the purge audit which is 
important for governance purpose.



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


[jira] [Updated] (ATLAS-3477) Introduce purging of entity in Atlas

2019-11-07 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3477:
-
Attachment: (was: ATLAS-3477.patch)

> Introduce purging of entity in Atlas
> 
>
> Key: ATLAS-3477
> URL: https://issues.apache.org/jira/browse/ATLAS-3477
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 2.0.0
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3477.patch
>
>
> In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there 
> is no way to do cleanup if user wants to delete those permanently. Right now 
> we can change the configuration 
> atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.
> HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
> desired. But what happens to existing soft deleted Entities. There is no way 
> in that case.
> As part of this issue solution we should be able to purge the entities which 
> are already soft deleted. This will be useful to users who is interested to 
> purge some list of soft deleted entities from Atlas. Due to governance 
> compliances, only admin can perform purge of entities.
> Purge should have separate Audit similar to delete entity.



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


[jira] [Updated] (ATLAS-3477) Introduce purging of entity in Atlas

2019-11-07 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3477:
-
Attachment: ATLAS-3477.patch

> Introduce purging of entity in Atlas
> 
>
> Key: ATLAS-3477
> URL: https://issues.apache.org/jira/browse/ATLAS-3477
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-3477.patch
>
>
> In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there 
> is no way to do cleanup if user wants to delete those permanently. Right now 
> we can change the configuration 
> atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.
> HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
> desired. But what happens to existing soft deleted Entities. There is no way 
> in that case.
> As part of this issue solution we should be able to purge the entities which 
> are already soft deleted. This will be useful to users who is interested to 
> purge some list of soft deleted entities from Atlas. Due to governance 
> compliances, only admin can perform purge of entities.
> Purge should have separate Audit similar to delete entity.



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


[jira] [Updated] (ATLAS-3477) Introduce purging of entity in Atlas

2019-11-07 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3477:
-
Description: 
In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there is 
no way to do cleanup if user wants to delete those permanently. Right now we 
can change the configuration 

atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.

HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
desired. But what happens to existing soft deleted Entities. There is no way in 
that case.

As part of this issue solution we should be able to purge the entities which 
are already soft deleted. This will be useful to users who is interested to 
purge some list of soft deleted entities from Atlas. Due to governance 
compliances, only admin can perform purge of entities.

Purge should have separate Audit similar to delete entity.

  was:
In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there is 
no way to do cleanup if user wants to delete those permanently. Right now we 
can change the configuration 

atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.

HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
desired. But what happens to existing soft deleted Entities. There is no way in 
that case.

There are two cases which needs to be addressed as part of this problem.
 # There is an active entity which has to be purged in case the entity is 
dropped.
 # There might be existing soft deleted entities and which has to be purge 
deleted if user desires

In both the above cases we also need to think about the auditing and its impact.


> Introduce purging of entity in Atlas
> 
>
> Key: ATLAS-3477
> URL: https://issues.apache.org/jira/browse/ATLAS-3477
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there 
> is no way to do cleanup if user wants to delete those permanently. Right now 
> we can change the configuration 
> atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.
> HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
> desired. But what happens to existing soft deleted Entities. There is no way 
> in that case.
> As part of this issue solution we should be able to purge the entities which 
> are already soft deleted. This will be useful to users who is interested to 
> purge some list of soft deleted entities from Atlas. Due to governance 
> compliances, only admin can perform purge of entities.
> Purge should have separate Audit similar to delete entity.



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


[jira] [Updated] (ATLAS-3461) Impala process and lineage is not getting created appropriately if query contains variation like comment or extra spaces

2019-10-22 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3461:
-
Attachment: ATLAS-3461-3.patch

> Impala process and lineage is not getting created appropriately if query 
> contains variation like comment or extra spaces
> 
>
> Key: ATLAS-3461
> URL: https://issues.apache.org/jira/browse/ATLAS-3461
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3461-3.patch
>
>
> Some examples of such queries are at Impala:
> creAted external table /*test*/ impala1 aS – temp  fff
>       /* temp */ – sdfrnfkjef select
>       select * from t1;
> Create /*dd*/ table impala2 aS select * from t1;
>  
> From JDBC:
> If we add more spaces in between create and table as shown below and use jdbc 
> to execute the query then the impala process is not getting created at Atlas.
> create table testSun2 as select * from t1;



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


[jira] [Updated] (ATLAS-3461) Impala process and lineage is not getting created appropriately if query contains variation like comment or extra spaces

2019-10-22 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3461:
-
Attachment: (was: ATLAS-3461-1.patch)

> Impala process and lineage is not getting created appropriately if query 
> contains variation like comment or extra spaces
> 
>
> Key: ATLAS-3461
> URL: https://issues.apache.org/jira/browse/ATLAS-3461
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3461-3.patch
>
>
> Some examples of such queries are at Impala:
> creAted external table /*test*/ impala1 aS – temp  fff
>       /* temp */ – sdfrnfkjef select
>       select * from t1;
> Create /*dd*/ table impala2 aS select * from t1;
>  
> From JDBC:
> If we add more spaces in between create and table as shown below and use jdbc 
> to execute the query then the impala process is not getting created at Atlas.
> create table testSun2 as select * from t1;



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


[jira] [Updated] (ATLAS-3477) Introduce purging of entity in Atlas

2019-10-17 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3477:
-
Description: 
In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there is 
no way to do cleanup if user wants to delete those permanently. Right now we 
can change the configuration 

atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.

HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
desired. But what happens to existing soft deleted Entities. There is no way in 
that case.

There are two cases which needs to be addressed as part of this problem.
 # There is an active entity which has to be purged in case the entity is 
dropped.
 # There might be existing soft deleted entities and which has to be purge 
deleted if user desires

In both the above cases we also need to think about the auditing and its impact.

  was:
In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there is 
no way to do cleanup if user wants to delete those permanently. Right now we 
can change the configuration 

atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.

HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
desired. But what happens to existing soft deleted Entities. There is no way in 
that case.

There are two cases which needs to be addressed as part of this problem.
 # There are active entity which has to be purged in case the entity is dropped.
 # There might be existing soft deleted entities and which has to be purge 
deleted

In both the above cases we also need to think about the auditing and its impact.


> Introduce purging of entity in Atlas
> 
>
> Key: ATLAS-3477
> URL: https://issues.apache.org/jira/browse/ATLAS-3477
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there 
> is no way to do cleanup if user wants to delete those permanently. Right now 
> we can change the configuration 
> atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.
> HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
> desired. But what happens to existing soft deleted Entities. There is no way 
> in that case.
> There are two cases which needs to be addressed as part of this problem.
>  # There is an active entity which has to be purged in case the entity is 
> dropped.
>  # There might be existing soft deleted entities and which has to be purge 
> deleted if user desires
> In both the above cases we also need to think about the auditing and its 
> impact.



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


[jira] [Updated] (ATLAS-3477) Introduce purging of entity in Atlas

2019-10-17 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3477:
-
Description: 
In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there is 
no way to do cleanup if user wants to delete those permanently. Right now we 
can change the configuration 

atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.

HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
desired. But what happens to existing soft deleted Entities. There is no way in 
that case.

There are two cases which needs to be addressed as part of this problem.
 # There are active entity which has to be purged in case the entity is dropped.
 # There might be existing soft deleted entities and which has to be purge 
deleted

In both the above cases we also need to think about the auditing and its impact.

  was:
In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there is 
no way to do cleanup if user wants to delete those permanently. Right now we 
can change the configuration 

atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.

HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
desired. But what happens to existing soft deleted Entities. There is no way in 
that case.


> Introduce purging of entity in Atlas
> 
>
> Key: ATLAS-3477
> URL: https://issues.apache.org/jira/browse/ATLAS-3477
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there 
> is no way to do cleanup if user wants to delete those permanently. Right now 
> we can change the configuration 
> atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.
> HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
> desired. But what happens to existing soft deleted Entities. There is no way 
> in that case.
> There are two cases which needs to be addressed as part of this problem.
>  # There are active entity which has to be purged in case the entity is 
> dropped.
>  # There might be existing soft deleted entities and which has to be purge 
> deleted
> In both the above cases we also need to think about the auditing and its 
> impact.



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


[jira] [Updated] (ATLAS-3477) Introduce purging of entity in Atlas

2019-10-17 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3477:
-
Summary: Introduce purging of entity in Atlas  (was: No way to purge the 
soft deleted entity from Atlas)

> Introduce purging of entity in Atlas
> 
>
> Key: ATLAS-3477
> URL: https://issues.apache.org/jira/browse/ATLAS-3477
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there 
> is no way to do cleanup if user wants to delete those permanently. Right now 
> we can change the configuration 
> atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.
> HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
> desired. But what happens to existing soft deleted Entities. There is no way 
> in that case.



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


[jira] [Updated] (ATLAS-3477) No way to purge the soft deleted entity from Atlas

2019-10-17 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra updated ATLAS-3477:
-
Issue Type: New Feature  (was: Bug)

> No way to purge the soft deleted entity from Atlas
> --
>
> Key: ATLAS-3477
> URL: https://issues.apache.org/jira/browse/ATLAS-3477
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there 
> is no way to do cleanup if user wants to delete those permanently. Right now 
> we can change the configuration 
> atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.
> HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
> desired. But what happens to existing soft deleted Entities. There is no way 
> in that case.



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


[jira] [Assigned] (ATLAS-3477) No way to purge the soft deleted entity from Atlas

2019-10-17 Thread Sidharth Kumar Mishra (Jira)


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

Sidharth Kumar Mishra reassigned ATLAS-3477:


Assignee: Sidharth Kumar Mishra

> No way to purge the soft deleted entity from Atlas
> --
>
> Key: ATLAS-3477
> URL: https://issues.apache.org/jira/browse/ATLAS-3477
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there 
> is no way to do cleanup if user wants to delete those permanently. Right now 
> we can change the configuration 
> atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.
> HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
> desired. But what happens to existing soft deleted Entities. There is no way 
> in that case.



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


[jira] [Created] (ATLAS-3477) No way to purge the soft deleted entity from Atlas

2019-10-17 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3477:


 Summary: No way to purge the soft deleted entity from Atlas
 Key: ATLAS-3477
 URL: https://issues.apache.org/jira/browse/ATLAS-3477
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra


In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there is 
no way to do cleanup if user wants to delete those permanently. Right now we 
can change the configuration 

atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.

HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
desired. But what happens to existing soft deleted Entities. There is no way in 
that case.



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


[jira] [Created] (ATLAS-3461) Impala process and lineage is not getting created appropriately if query contains variation like comment or extra spaces

2019-10-13 Thread Sidharth Kumar Mishra (Jira)
Sidharth Kumar Mishra created ATLAS-3461:


 Summary: Impala process and lineage is not getting created 
appropriately if query contains variation like comment or extra spaces
 Key: ATLAS-3461
 URL: https://issues.apache.org/jira/browse/ATLAS-3461
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra


Some examples of such queries are at Impala:

creAted external table /*test*/ impala1 aS – temp  fff

      /* temp */ – sdfrnfkjef select

      select * from t1;

Create /*dd*/ table impala2 aS select * from t1;

 

>From JDBC:

If we add more spaces in between create and table as shown below and use jdbc 
to execute the query then the impala process is not getting created at Atlas.

create table testSun2 as select * from t1;



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