[jira] [Created] (ATLAS-3978) In Administration, Audits filter for 'OR' condition does not work
Durga Kadam created ATLAS-3978: -- Summary: In Administration, Audits filter for 'OR' condition does not work Key: ATLAS-3978 URL: https://issues.apache.org/jira/browse/ATLAS-3978 Project: Atlas Issue Type: Bug Reporter: Durga Kadam Attachments: OR condition not working.mkv Description:: When user uses OR condition it does not apply on filter, results are listed with AND condition. PFA evidence file [OR condition not working.mkv] Steps to regenerate:: # Go to Administration- Audits # Select the OR condition filter # Check the console for response # Results are listed with 'AND' operator instead of 'OR' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3967) On creating a type with a type_name of a different category, 409 conflict error is thrown
[
https://issues.apache.org/jira/browse/ATLAS-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dharshana M Krishnamoorthy resolved ATLAS-3967.
---
Resolution: Not A Bug
As per: [http://atlas.apache.org/#/TypeSystem] ";
* A type in Atlas is identified uniquely by a ‘name’
> On creating a type with a type_name of a different category, 409 conflict
> error is thrown
> -
>
> Key: ATLAS-3967
> URL: https://issues.apache.org/jira/browse/ATLAS-3967
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Dharshana M Krishnamoorthy
>Priority: Major
>
> On creating a classification with a name same as business_metadata type, 409
> is thrown
>
> Existing business metadata:
> {code:java|title=business_metadata details}
> {"category":"BUSINESS_METADATA","guid":"-416986733842","createdBy":"hrt_qa","updatedBy":"hrt_qa","createTime":1601466038742,"updateTime":1601466038742,"version":1,"name":"read_auth_business_metadata_WXuUg","description":"bm
> description","typeVersion":"1.0","attributeDefs":[]}
> {code}
>
> create a classification with name "*read_auth_business_metadata_WXuUg*"
> this gives a conflict error
> Create request payload: to endpoint
> *api/atlas/v2/types/typedefs?type=classification*
> {code}
> {"classificationDefs":[\{"name":"read_auth_business_metadata_WXuUg","description":"","superTypes":[],"attributeDefs":[]}],"entityDefs":[],"enumDefs":[],"structDefs":[]}
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-3967) On creating a type with a type_name of a different category, 409 conflict error is thrown
[
https://issues.apache.org/jira/browse/ATLAS-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dharshana M Krishnamoorthy reassigned ATLAS-3967:
-
Assignee: Dharshana M Krishnamoorthy
> On creating a type with a type_name of a different category, 409 conflict
> error is thrown
> -
>
> Key: ATLAS-3967
> URL: https://issues.apache.org/jira/browse/ATLAS-3967
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Dharshana M Krishnamoorthy
>Priority: Major
>
> On creating a classification with a name same as business_metadata type, 409
> is thrown
>
> Existing business metadata:
> {code:java|title=business_metadata details}
> {"category":"BUSINESS_METADATA","guid":"-416986733842","createdBy":"hrt_qa","updatedBy":"hrt_qa","createTime":1601466038742,"updateTime":1601466038742,"version":1,"name":"read_auth_business_metadata_WXuUg","description":"bm
> description","typeVersion":"1.0","attributeDefs":[]}
> {code}
>
> create a classification with name "*read_auth_business_metadata_WXuUg*"
> this gives a conflict error
> Create request payload: to endpoint
> *api/atlas/v2/types/typedefs?type=classification*
> {code}
> {"classificationDefs":[\{"name":"read_auth_business_metadata_WXuUg","description":"","superTypes":[],"attributeDefs":[]}],"entityDefs":[],"enumDefs":[],"structDefs":[]}
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3976) On creating a type with a type_name that already exists as a read-only user 409 is thrown instead on 403
[ https://issues.apache.org/jira/browse/ATLAS-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dharshana M Krishnamoorthy updated ATLAS-3976: -- Description: hrt_qa has crud permission on classification PII is created by hrt_qa hrt_1 has read-only permission on classification PII When hrt_1 is trying to create PII again, since its a read-only user 403- unauthorised to create should be thrown, instead 409 conflict is thrown > On creating a type with a type_name that already exists as a read-only user > 409 is thrown instead on 403 > - > > Key: ATLAS-3976 > URL: https://issues.apache.org/jira/browse/ATLAS-3976 > Project: Atlas > Issue Type: Bug >Reporter: Dharshana M Krishnamoorthy >Assignee: Nixon Rodrigues >Priority: Major > > hrt_qa has crud permission on classification > PII is created by hrt_qa > hrt_1 has read-only permission on classification PII > When hrt_1 is trying to create PII again, since its a read-only user 403- > unauthorised to create should be thrown, instead 409 conflict is thrown -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3977) Migration Script: Deleted entities in Atlas1.0 miss few attributes after migrated to Atlas2.0
[ https://issues.apache.org/jira/browse/ATLAS-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208482#comment-17208482 ] Ashutosh Mestry commented on ATLAS-3977: [~sarath] / [~nixon] / [~nikhilbonte] Can you please review. > Migration Script: Deleted entities in Atlas1.0 miss few attributes after > migrated to Atlas2.0 > - > > Key: ATLAS-3977 > URL: https://issues.apache.org/jira/browse/ATLAS-3977 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sharmadha S >Assignee: Ashutosh Mestry >Priority: Major > Attachments: ATLAS-3977-Addressed-patch-processing-for.patch, > am2cm_deleted_active_entity.png > > > table6 is DELETED in Atlas1.0 and it is migrated to Atals2.0 > Attributes like name , db , owner are missing in DELETED entities whereas > they are populated correctly in ACTIVE entities. > Attaching the screenshot. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3977) Migration Script: Deleted entities in Atlas1.0 miss few attributes after migrated to Atlas2.0
[ https://issues.apache.org/jira/browse/ATLAS-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry reassigned ATLAS-3977: -- Attachment: ATLAS-3977-Addressed-patch-processing-for.patch Assignee: Ashutosh Mestry > Migration Script: Deleted entities in Atlas1.0 miss few attributes after > migrated to Atlas2.0 > - > > Key: ATLAS-3977 > URL: https://issues.apache.org/jira/browse/ATLAS-3977 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sharmadha S >Assignee: Ashutosh Mestry >Priority: Major > Attachments: ATLAS-3977-Addressed-patch-processing-for.patch, > am2cm_deleted_active_entity.png > > > table6 is DELETED in Atlas1.0 and it is migrated to Atals2.0 > Attributes like name , db , owner are missing in DELETED entities whereas > they are populated correctly in ACTIVE entities. > Attaching the screenshot. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Review Request 72932: ATLAS-3964: Fix for regression caused by earlier patch
> On Oct. 6, 2020, 2:13 a.m., Ashutosh Mestry wrote: > > LGTM. I will let Keval review it. Perhaps there is some JS where all these > > re-usable methods are kept. Right now there is duplication of code. Its not duplication of code. There are two codebases for UI. DashboardV2 and DashboardV3. We need to commit at both the places as only one of it gets loaded at a time. - Deep --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72932/#review221994 --- On Oct. 6, 2020, 2:05 a.m., Deep Singh wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/72932/ > --- > > (Updated Oct. 6, 2020, 2:05 a.m.) > > > Review request for atlas, keval bhatt, Madhan Neethiraj, and Sarath > Subramanian. > > > Bugs: ATLAS-3964 > https://issues.apache.org/jira/browse/ATLAS-3964 > > > Repository: atlas > > > Description > --- > > Regression was observed in counts of entities. > With earlier patch all sorts of numbers were parsed into string. > Only those numbers where information is being lost must be passed into a > string. > > > Diffs > - > > dashboardv2/public/js/utils/Overrides.js 63770b5c3 > dashboardv3/public/js/utils/Overrides.js 63770b5c3 > > > Diff: https://reviews.apache.org/r/72932/diff/1/ > > > Testing > --- > > Testing was done on Atlas loaded with 3738 entities (2057 active and 1681 > deleted) > > > Thanks, > > Deep Singh > >
[jira] [Created] (ATLAS-3977) Migration Script: Deleted entities in Atlas1.0 miss few attributes after migrated to Atlas2.0
Sharmadha S created ATLAS-3977: -- Summary: Migration Script: Deleted entities in Atlas1.0 miss few attributes after migrated to Atlas2.0 Key: ATLAS-3977 URL: https://issues.apache.org/jira/browse/ATLAS-3977 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Sharmadha S Attachments: am2cm_deleted_active_entity.png table6 is DELETED in Atlas1.0 and it is migrated to Atals2.0 Attributes like name , db , owner are missing in DELETED entities whereas they are populated correctly in ACTIVE entities. Attaching the screenshot. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Review Request 72932: ATLAS-3964: Fix for regression caused by earlier patch
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72932/#review221994 --- LGTM. I will let Keval review it. Perhaps there is some JS where all these re-usable methods are kept. Right now there is duplication of code. - Ashutosh Mestry On Oct. 6, 2020, 2:05 a.m., Deep Singh wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/72932/ > --- > > (Updated Oct. 6, 2020, 2:05 a.m.) > > > Review request for atlas, keval bhatt, Madhan Neethiraj, and Sarath > Subramanian. > > > Bugs: ATLAS-3964 > https://issues.apache.org/jira/browse/ATLAS-3964 > > > Repository: atlas > > > Description > --- > > Regression was observed in counts of entities. > With earlier patch all sorts of numbers were parsed into string. > Only those numbers where information is being lost must be passed into a > string. > > > Diffs > - > > dashboardv2/public/js/utils/Overrides.js 63770b5c3 > dashboardv3/public/js/utils/Overrides.js 63770b5c3 > > > Diff: https://reviews.apache.org/r/72932/diff/1/ > > > Testing > --- > > Testing was done on Atlas loaded with 3738 entities (2057 active and 1681 > deleted) > > > Thanks, > > Deep Singh > >
[jira] [Commented] (ATLAS-3964) Atlas UI displays large numbers incorrectly
[ https://issues.apache.org/jira/browse/ATLAS-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208454#comment-17208454 ] Deep Singh commented on ATLAS-3964: --- Review request raised. https://reviews.apache.org/r/72932 > Atlas UI displays large numbers incorrectly > --- > > Key: ATLAS-3964 > URL: https://issues.apache.org/jira/browse/ATLAS-3964 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Deep Singh >Assignee: Deep Singh >Priority: Major > Attachments: details.doc > > > In the case of a type that has an attribute of type Long, and it contains a > very large number, the Atlas UI does not show the correct number. > Steps to reproduce: > From the command line: > # create an entity type which has a field of type long > # create an entity of this same type and the value of the field should be > "1085741226505763426" > # Atlas will respond with the created entity, you will see that the field > value is correct > # now open the Atlas website and search for this same entity; you will see > the value displayed is "1085741226505763500" -- This message was sent by Atlassian Jira (v8.3.4#803005)
Review Request 72932: ATLAS-3964: Fix for regression caused by earlier patch
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72932/ --- Review request for atlas, keval bhatt, Madhan Neethiraj, and Sarath Subramanian. Bugs: ATLAS-3964 https://issues.apache.org/jira/browse/ATLAS-3964 Repository: atlas Description --- Regression was observed in counts of entities. With earlier patch all sorts of numbers were parsed into string. Only those numbers where information is being lost must be passed into a string. Diffs - dashboardv2/public/js/utils/Overrides.js 63770b5c3 dashboardv3/public/js/utils/Overrides.js 63770b5c3 Diff: https://reviews.apache.org/r/72932/diff/1/ Testing --- Testing was done on Atlas loaded with 3738 entities (2057 active and 1681 deleted) Thanks, Deep Singh
[jira] [Created] (ATLAS-3976) On creating a type with a type_name that already exists as a read-only user 409 is thrown instead on 403
Dharshana M Krishnamoorthy created ATLAS-3976: - Summary: On creating a type with a type_name that already exists as a read-only user 409 is thrown instead on 403 Key: ATLAS-3976 URL: https://issues.apache.org/jira/browse/ATLAS-3976 Project: Atlas Issue Type: Bug Reporter: Dharshana M Krishnamoorthy Assignee: Nixon Rodrigues -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3975) User is allowed to create an entity with non-readable entity type
Dharshana M Krishnamoorthy created ATLAS-3975: - Summary: User is allowed to create an entity with non-readable entity type Key: ATLAS-3975 URL: https://issues.apache.org/jira/browse/ATLAS-3975 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Dharshana M Krishnamoorthy When a user tries to create an entity with non-readable entity-type it succeeds without throwing error -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3974) User is able to associate non-readable classification to entity
Dharshana M Krishnamoorthy created ATLAS-3974: - Summary: User is able to associate non-readable classification to entity Key: ATLAS-3974 URL: https://issues.apache.org/jira/browse/ATLAS-3974 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Dharshana M Krishnamoorthy When a user tries to assign a non-readable classification to an entity, it succeeds, without throwing error -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (ATLAS-3964) Atlas UI displays large numbers incorrectly
[ https://issues.apache.org/jira/browse/ATLAS-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deep Singh reopened ATLAS-3964: --- Regression was observed in counts of entities. That was because all sorts of numbers were parsed into string. Only those numbers where information is being lost must be passed into a string. > Atlas UI displays large numbers incorrectly > --- > > Key: ATLAS-3964 > URL: https://issues.apache.org/jira/browse/ATLAS-3964 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Deep Singh >Assignee: Deep Singh >Priority: Major > Attachments: details.doc > > > In the case of a type that has an attribute of type Long, and it contains a > very large number, the Atlas UI does not show the correct number. > Steps to reproduce: > From the command line: > # create an entity type which has a field of type long > # create an entity of this same type and the value of the field should be > "1085741226505763426" > # Atlas will respond with the created entity, you will see that the field > value is correct > # now open the Atlas website and search for this same entity; you will see > the value displayed is "1085741226505763500" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3973) Inappropriate message on performing create with non-readable super type
[
https://issues.apache.org/jira/browse/ATLAS-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dharshana M Krishnamoorthy updated ATLAS-3973:
--
Description:
Received message
{code:java}
{u'errorCode': u'ATLAS-403-00-001', u'errorMessage': u'hrt_qa is not authorized
to perform read type-def of
categoryCLASSIFICATIONnon_read_classification_ufvQK'}
{code}
Expected message
{code:java}
hrt_qa is not authorized to perform create classification-def with
non-readable classification
{code}
or something similar, that conveys the right message. The current error message
seems very confusing. It conveys about read when performing a create operation
Also the message has incorrect spacing
was:
Received message
{code}
{u'errorCode': u'ATLAS-403-00-001', u'errorMessage': u'hrt_qa is not authorized
to perform read type-def of
categoryCLASSIFICATIONnon_read_classification_ufvQK'}
{code}
Expected message
{code}
hrt_qa is not authorized to perform create classification-def with
non-readable classification
{code}
or something similar, that conveys the right message. The correct error message
seems very confusing. It conveys about read when performing a create operation
Also the message has incorrect spacing
> Inappropriate message on performing create with non-readable super type
> ---
>
> Key: ATLAS-3973
> URL: https://issues.apache.org/jira/browse/ATLAS-3973
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Priority: Major
>
> Received message
> {code:java}
> {u'errorCode': u'ATLAS-403-00-001', u'errorMessage': u'hrt_qa is not
> authorized to perform read type-def of
> categoryCLASSIFICATIONnon_read_classification_ufvQK'}
> {code}
>
> Expected message
> {code:java}
> hrt_qa is not authorized to perform create classification-def
> with non-readable classification
> {code}
> or something similar, that conveys the right message. The current error
> message seems very confusing. It conveys about read when performing a create
> operation
> Also the message has incorrect spacing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-3973) Inappropriate message on performing create with non-readable super type
Dharshana M Krishnamoorthy created ATLAS-3973:
-
Summary: Inappropriate message on performing create with
non-readable super type
Key: ATLAS-3973
URL: https://issues.apache.org/jira/browse/ATLAS-3973
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Dharshana M Krishnamoorthy
Received message
{code}
{u'errorCode': u'ATLAS-403-00-001', u'errorMessage': u'hrt_qa is not authorized
to perform read type-def of
categoryCLASSIFICATIONnon_read_classification_ufvQK'}
{code}
Expected message
{code}
hrt_qa is not authorized to perform create classification-def with
non-readable classification
{code}
or something similar, that conveys the right message. The correct error message
seems very confusing. It conveys about read when performing a create operation
Also the message has incorrect spacing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
org.apache.maven.plugins:maven-failsafe-plugin:2.18.1:verify
I am getting the below error trying to build Atlas 2.0 branch with mvn clean install. 2020-10-05T04:30:00.7494932Z [ [1;34mINFO [m] Apache Atlas Plugin Classloader 2.1.0 .. [1;32mSUCCESS [m [ 4.905 s] 2020-10-05T04:30:00.7496134Z [ [1;34mINFO [m] Apache Atlas Hive Bridge Shim 2.1.0 [1;32mSUCCESS [m [ 5.403 s] 2020-10-05T04:30:00.7496963Z [ [1;34mINFO [m] Apache Atlas Hive Bridge 2.1.0 . [1;31mFAILURE [m [49:06 min] 2020-10-05T04:30:00.7498393Z [ [1;34mINFO [m] Apache Atlas Falcon Bridge Shim 2.1.0 .. [1;33mSKIPPED [m 2020-10-05T04:30:00.7500497Z [ [1;34mINFO [m] Apache Atlas Falcon Bridge 2.1.0 ... [1;33mSKIPPED [m 2020-10-05T04:30:00.7502928Z [ [1;34mINFO [m] Apache Atlas Sqoop Bridge Shim 2.1.0 ... [1;33mSKIPPED [m 2020-10-05T04:30:00.7504223Z [ [1;34mINFO [m] Apache Atlas Sqoop Bridge 2.1.0 [1;33mSKIPPED [m 2020-10-05T04:30:00.7506613Z [ [1;34mINFO [m] Apache Atlas Storm Bridge Shim 2.1.0 ... [1;33mSKIPPED [m 2020-10-05T04:30:00.7507945Z [ [1;34mINFO [m] Apache Atlas Storm Bridge 2.1.0 [1;33mSKIPPED [m 2020-10-05T04:30:00.7509463Z [ [1;34mINFO [m] Apache Atlas Hbase Bridge Shim 2.1.0 ... [1;33mSKIPPED [m 2020-10-05T04:30:00.7510425Z [ [1;34mINFO [m] Apache Atlas Hbase Bridge 2.1.0 [1;33mSKIPPED [m 2020-10-05T04:30:00.7511715Z [ [1;34mINFO [m] Apache HBase - Testing Util 2.1.0 .. [1;33mSKIPPED [m 2020-10-05T04:30:00.7513793Z [ [1;34mINFO [m] Apache Atlas Kafka Bridge 2.1.0 [1;33mSKIPPED [m 2020-10-05T04:30:00.7522095Z [ [1;34mINFO [m] Apache Atlas classification updater 2.1.0 .. [1;33mSKIPPED [m 2020-10-05T04:30:00.7530585Z [ [1;34mINFO [m] Apache Atlas Impala Hook API 2.1.0 . [1;33mSKIPPED [m 2020-10-05T04:30:00.7531346Z [ [1;34mINFO [m] Apache Atlas Impala Bridge Shim 2.1.0 .. [1;33mSKIPPED [m 2020-10-05T04:30:00.7532025Z [ [1;34mINFO [m] Apache Atlas Impala Bridge 2.1.0 ... [1;33mSKIPPED [m 2020-10-05T04:30:00.7535746Z [ [1;34mINFO [m] Apache Atlas Distribution 2.1.0 [1;33mSKIPPED [m 2020-10-05T04:30:00.7542883Z [ [1;34mINFO [m] [1m [m 2020-10-05T04:30:00.7543561Z [ [1;34mINFO [m] [1;31mBUILD FAILURE [m 2020-10-05T04:30:00.7544607Z [ [1;34mINFO [m] [1m [m 2020-10-05T04:30:00.7545314Z [ [1;34mINFO [m] Total time: 01:23 h 2020-10-05T04:30:00.7547545Z [ [1;34mINFO [m] Finished at: 2020-10-05T04:30:00Z 2020-10-05T04:30:00.7548327Z [ [1;34mINFO [m] [1m [m 2020-10-05T04:30:00.7576508Z [ [1;31mERROR [m] Failed to execute goal [32morg.apache.maven.plugins:maven-failsafe-plugin:2.18.1:verify [m [1m(verify) [m on project [36mhive-bridge [m: [1;31mThere are test failures. [m Any recommendation to get past this error?
[jira] [Created] (ATLAS-3972) Apache atlas 2.1.0
Frédéric Comte created ATLAS-3972: - Summary: Apache atlas 2.1.0 Key: ATLAS-3972 URL: https://issues.apache.org/jira/browse/ATLAS-3972 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 2.1.0 Reporter: Frédéric Comte I am using keycloak integration for authentication. Atlas is behind a reverse proxy (HAProxy) that doing SSL termination. HAProxy send the header X-Forwarded-Proto : https but Atlas does't not create an URL with https scheme when constructing a redirect uri -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3965) Relationships with null values are missing in entity relationshipAttributes
[
https://issues.apache.org/jira/browse/ATLAS-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deep Singh resolved ATLAS-3965.
---
Resolution: Fixed
> Relationships with null values are missing in entity relationshipAttributes
> ---
>
> Key: ATLAS-3965
> URL: https://issues.apache.org/jira/browse/ATLAS-3965
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Reporter: Deep Singh
>Assignee: Deep Singh
>Priority: Major
> Attachments:
> 0002-ATLAS-3965-Relationships-with-null-values-are-missin.patch
>
>
> kafka_topic typedef has relationship attributes:
> {code:java}
> inputToProcesses
> pipeline
> schema
> model
> avroSchema
> meanings
> outputFromProcesses{code}
> When a kafka topic entity is created using import-kafka.sh script, the entity
> doesn't have all relationship attributes :
> {code:java}
> "relationshipAttributes": {
> "inputToProcesses": [ ],
> "schema": [ ],
> "avroSchema": [ ],
> "meanings": [ ],
> "outputFromProcesses": [ ]}, {code}
> The missing ones are "pipeline" and "model" .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3971) Move authorization check for Business Metadata before type exist check
[ https://issues.apache.org/jira/browse/ATLAS-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-3971: --- Attachment: ATLAS-3971.patch > Move authorization check for Business Metadata before type exist check > -- > > Key: ATLAS-3971 > URL: https://issues.apache.org/jira/browse/ATLAS-3971 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Attachments: ATLAS-3971.patch > > > Refactor authorization check for Business Metadata before type exist check, > so that enduser is aware that a duplicate type creation is being attempted > which exist he is authorized to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3971) Move authorization check for Business Metadata before type exist check
[ https://issues.apache.org/jira/browse/ATLAS-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-3971: --- Summary: Move authorization check for Business Metadata before type exist check (was: Refactor authorization check for Business Metadata before type exist check) > Move authorization check for Business Metadata before type exist check > -- > > Key: ATLAS-3971 > URL: https://issues.apache.org/jira/browse/ATLAS-3971 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > > Refactor authorization check for Business Metadata before type exist check, > so that enduser is aware that a duplicate type creation is being attempted > which exist he is authorized to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3971) Refactor authorization check for Business Metadata before type exist check
Nixon Rodrigues created ATLAS-3971: -- Summary: Refactor authorization check for Business Metadata before type exist check Key: ATLAS-3971 URL: https://issues.apache.org/jira/browse/ATLAS-3971 Project: Atlas Issue Type: Bug Reporter: Nixon Rodrigues Refactor authorization check for Business Metadata before type exist check, so that enduser is aware that a duplicate type creation is being attempted which exist he is authorized to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3971) Refactor authorization check for Business Metadata before type exist check
[ https://issues.apache.org/jira/browse/ATLAS-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues reassigned ATLAS-3971: -- Assignee: Nixon Rodrigues > Refactor authorization check for Business Metadata before type exist check > -- > > Key: ATLAS-3971 > URL: https://issues.apache.org/jira/browse/ATLAS-3971 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > > Refactor authorization check for Business Metadata before type exist check, > so that enduser is aware that a duplicate type creation is being attempted > which exist he is authorized to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3970) When the search button is hit on the atlas entity page, show the match count near "Results for: "
[ https://issues.apache.org/jira/browse/ATLAS-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dharshana M Krishnamoorthy updated ATLAS-3970: -- Description: Eg: When we fire a search with *Type: _ALL_ENTITY_TYPES* and *Classification: _NOT_CLASSIFIED* all the results are displayed but it is difficult to know the result count of the search criteria, unless we calculate it manually. It will be better of the result count is also displayed !image-2020-10-05-16-43-15-155.png|width=553,height=104! was: Eg: When we fire a search with *Type: _ALL_ENTITY_TYPES* and *Classification: _NOT_CLASSIFIED* all the results are displayed but it is8nnn difficult to know the result count of the search criteria, unless we calculate it manually. It will be better of the result count is also displayed !image-2020-10-05-16-43-15-155.png|width=553,height=104! > When the search button is hit on the atlas entity page, show the match count > near "Results for: " > - > > Key: ATLAS-3970 > URL: https://issues.apache.org/jira/browse/ATLAS-3970 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Priority: Major > Attachments: image-2020-10-05-16-43-15-155.png > > > Eg: When we fire a search with *Type: _ALL_ENTITY_TYPES* and *Classification: > _NOT_CLASSIFIED* all the results are displayed but it is difficult to know > the result count of the search criteria, unless we calculate it manually. It > will be better of the result count is also displayed > !image-2020-10-05-16-43-15-155.png|width=553,height=104! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3970) When the search button is hit on the atlas entity page, show the match count near "Results for: "
Dharshana M Krishnamoorthy created ATLAS-3970: - Summary: When the search button is hit on the atlas entity page, show the match count near "Results for: " Key: ATLAS-3970 URL: https://issues.apache.org/jira/browse/ATLAS-3970 Project: Atlas Issue Type: Improvement Components: atlas-webui Reporter: Dharshana M Krishnamoorthy Attachments: image-2020-10-05-16-43-15-155.png Eg: When we fire a search with *Type: _ALL_ENTITY_TYPES* and *Classification: _NOT_CLASSIFIED* all the results are displayed but it is8nnn difficult to know the result count of the search criteria, unless we calculate it manually. It will be better of the result count is also displayed !image-2020-10-05-16-43-15-155.png|width=553,height=104! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-2893) Atlas Column Lineage of Hive Hook to support the hive old version (before hive version 1.2.1 after the patch for HIVE-13112)
[ https://issues.apache.org/jira/browse/ATLAS-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17207908#comment-17207908 ] zhangsan commented on ATLAS-2893: - hi After adding the patch as you did, you still cannot get CREATE_AS_SELECT Lineage > Atlas Column Lineage of Hive Hook to support the hive old version (before > hive version 1.2.1 after the patch for HIVE-13112) > > > Key: ATLAS-2893 > URL: https://issues.apache.org/jira/browse/ATLAS-2893 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: aflyary >Priority: Major > Attachments: ATLAS-2893.001.patch > > > Right now atlas hook for apache hive of column lineage is limited, > only "Column level lineage works with Hive version 1.2.1 after the patch for > HIVE-13112 is applied to Hive source" could support the hive column lineage. > In some product env, hive version still very old, but we should also > support the hive column lineage. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3969) Atlas1.2.0INSERT_SELECT Lineage can be retrieved but not CREATE_TABLE_AS_SELECT
zhangsan created ATLAS-3969: --- Summary: Atlas1.2.0INSERT_SELECT Lineage can be retrieved but not CREATE_TABLE_AS_SELECT Key: ATLAS-3969 URL: https://issues.apache.org/jira/browse/ATLAS-3969 Project: Atlas Issue Type: Bug Components: hive-integration Affects Versions: 1.2.0 Reporter: zhangsan CREATE TABLE test.t5( id String, name String ) CREATE TABLE test.t6 AS SELECT id,name,age,phone FROM test.t5; The above operation cannot obtain the lineage INSERT OVERWRITE TABLE test.t6 SELECT id,name FROM test.t5; The above operation can obtain the Lineage -- This message was sent by Atlassian Jira (v8.3.4#803005)
