[jira] [Assigned] (ATLAS-4012) Atlas - Upgrade bootstrap to 3.4.1 or 4.3.1

2020-11-02 Thread chaitali borole (Jira) 


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

chaitali borole reassigned ATLAS-4012:
--

Assignee: Keval Bhatt  (was: chaitali borole)

> Atlas - Upgrade bootstrap to 3.4.1 or 4.3.1
> ---
>
> Key: ATLAS-4012
> URL: https://issues.apache.org/jira/browse/ATLAS-4012
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: Keval Bhatt
>Priority: Major
>




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

[jira] [Created] (ATLAS-4012) Atlas - Upgrade bootstrap to 3.4.1 or 4.3.1

2020-11-02 Thread chaitali borole (Jira) 
chaitali borole created ATLAS-4012:
--

 Summary: Atlas - Upgrade bootstrap to 3.4.1 or 4.3.1
 Key: ATLAS-4012
 URL: https://issues.apache.org/jira/browse/ATLAS-4012
 Project: Atlas
  Issue Type: Improvement
Affects Versions: 3.0.0
Reporter: chaitali borole
Assignee: chaitali borole






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

[jira] [Commented] (ATLAS-3030) UI : Allow to search the node in the lineage graph

2020-11-02 Thread Keval Bhatt (Jira) 


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

Keval Bhatt commented on ATLAS-3030:


for branch-0.8 fix has been committed using ATLAS-3259

> UI : Allow to search the node in the lineage graph
> --
>
> Key: ATLAS-3030
> URL: https://issues.apache.org/jira/browse/ATLAS-3030
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.4, 1.2.0, 2.0.0
>
> Attachments: ATLAS-3030-1.patch, ATLAS-3030.patch
>
>




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

Re: Review Request 72994: ATLAS-4010: Sort properties lexicographically in pom.xml for readability

2020-11-02 Thread Radhika Kundam 

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

(Updated Nov. 2, 2020, 12:08 p.m.)


Review request for atlas, Ashutosh Mestry and Madhan Neethiraj.


Changes
---

Removed the extra tab spaces for conf properties


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


Repository: atlas


Description
---

Properties are in random order under  section in pom.xml

For better readability, need to sort properties in lexicographic order.


Diffs (updated)
-

  distro/pom.xml db1f23acd 
  docs/pom.xml f22f9e2ff 
  pom.xml aca36aaee 
  webapp/pom.xml 5a8cfe616 


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

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


Testing
---

Build is successful.


File Attachments


Removing extra spaces
  
https://reviews.apache.org/media/uploaded/files/2020/10/30/40e165c6-985c-48e0-a61a-558ef4d9b2a3__0002-ATLAS-4010-Sort-properties-in-pom-removing-extra-spa.patch


Thanks,

Radhika Kundam

Re: Review Request 73000: ATLAS-4011: While running Atlas Docker container, data should be stored on host

2020-11-02 Thread Madhan Neethiraj 

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




dev-support/atlas-docker/README.md
Lines 42 (patched)


Instead of requiring users to create directory 'data', I suggest to create 
this directory and include with this patch. Please make sure to commit  
.gitignore file in this directory.

Once this is done, please remove 4.2 and 5.5.


- Madhan Neethiraj


On Nov. 2, 2020, 6:52 p.m., Jayendra Parab wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73000/
> ---
> 
> (Updated Nov. 2, 2020, 6:52 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-4011
> https://issues.apache.org/jira/browse/ATLAS-4011
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> - Mounting data directory from host machine into $ATLAS_HOME/data
> - To ensure solr collections are created in the data directory, setting the 
> SOLR_HOME using -s option. Also, copying solr.xml from the solr installation 
> directory to the solr home
> - Changed the command to keep the container from exiting when the container 
> runs in a pod in Kubernetes
> - Updated the documentation with new command for running docker container
> 
> 
> Diffs
> -
> 
>   dev-support/atlas-docker/Dockerfile.atlas e2dea7716 
>   dev-support/atlas-docker/README.md de644472b 
>   dev-support/atlas-docker/docker-compose.atlas.yml 92bd1edd0 
>   dev-support/atlas-docker/scripts/atlas.sh 0c4a4546a 
>   distro/src/bin/atlas_config.py bda8e2a10 
>   distro/src/bin/atlas_start.py 54fd2bd47 
>   distro/src/bin/atlas_stop.py 400a7d23d 
>   distro/src/test/python/scripts/TestMetadata.py f1235f747 
> 
> 
> Diff: https://reviews.apache.org/r/73000/diff/1/
> 
> 
> Testing
> ---
> 
> 1. Built the atlas container using `docker build -f Dockerfile.atlas 
> --build-arg ATLAS_VERSION=3.0.0-SNAPSHOT -t atlas .`
> 2. Ran the atlas container using `docker run -it -d --name atlas --hostname 
> localhost -p 21000:21000 -v $PWD/data:/home/atlas/data atlas`
> 3. Atlas was up and running, created some entities
> 4. Restarted the container. The entites created in step 3, were still there
> 5. Deleted the container using `docker rm -f atlas`
> 6. Created the conatiner again using the same command in step 2. The entities 
> created in step 3 were present.
> 
> 
> Thanks,
> 
> Jayendra Parab
> 
>

Review Request 73000: ATLAS-4011: While running Atlas Docker container, data should be stored on host

2020-11-02 Thread Jayendra Parab 

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

Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Nixon Rodrigues, 
and Sarath Subramanian.


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


Repository: atlas


Description
---

- Mounting data directory from host machine into $ATLAS_HOME/data
- To ensure solr collections are created in the data directory, setting the 
SOLR_HOME using -s option. Also, copying solr.xml from the solr installation 
directory to the solr home
- Changed the command to keep the container from exiting when the container 
runs in a pod in Kubernetes
- Updated the documentation with new command for running docker container


Diffs
-

  dev-support/atlas-docker/Dockerfile.atlas e2dea7716 
  dev-support/atlas-docker/README.md de644472b 
  dev-support/atlas-docker/docker-compose.atlas.yml 92bd1edd0 
  dev-support/atlas-docker/scripts/atlas.sh 0c4a4546a 
  distro/src/bin/atlas_config.py bda8e2a10 
  distro/src/bin/atlas_start.py 54fd2bd47 
  distro/src/bin/atlas_stop.py 400a7d23d 
  distro/src/test/python/scripts/TestMetadata.py f1235f747 


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


Testing
---

1. Built the atlas container using `docker build -f Dockerfile.atlas 
--build-arg ATLAS_VERSION=3.0.0-SNAPSHOT -t atlas .`
2. Ran the atlas container using `docker run -it -d --name atlas --hostname 
localhost -p 21000:21000 -v $PWD/data:/home/atlas/data atlas`
3. Atlas was up and running, created some entities
4. Restarted the container. The entites created in step 3, were still there
5. Deleted the container using `docker rm -f atlas`
6. Created the conatiner again using the same command in step 2. The entities 
created in step 3 were present.


Thanks,

Jayendra Parab

[jira] [Assigned] (ATLAS-4011) Docker: While running Atlas Docker container, data should be stored on host

2020-11-02 Thread Jayendra Parab (Jira) 


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

Jayendra Parab reassigned ATLAS-4011:
-

Assignee: Jayendra Parab

> Docker: While running Atlas Docker container, data should be stored on host
> ---
>
> Key: ATLAS-4011
> URL: https://issues.apache.org/jira/browse/ATLAS-4011
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Jayendra Parab
>Assignee: Jayendra Parab
>Priority: Major
>
> Currently, if Atlas is started with Embedded Solr and HBase in Docker 
> container, the data is persisted inside the container. So if the container is 
> destroyed and a new container is started, then its old data is lost.
> The data directory should be mounted as a volume, so that data can be 
> restored across container destroy and restore.
> To achieve this, Solr data directory should be configurable and by default it 
> should be $ATLAS_HOME/data/solr. HBase and Kafka data directory is already 
> configured to $ATLAS_HOME/data



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

[jira] [Created] (ATLAS-4011) Docker: While running Atlas Docker container, data should be stored on host

2020-11-02 Thread Jayendra Parab (Jira) 
Jayendra Parab created ATLAS-4011:
-

 Summary: Docker: While running Atlas Docker container, data should 
be stored on host
 Key: ATLAS-4011
 URL: https://issues.apache.org/jira/browse/ATLAS-4011
 Project: Atlas
  Issue Type: Improvement
Reporter: Jayendra Parab


Currently, if Atlas is started with Embedded Solr and HBase in Docker 
container, the data is persisted inside the container. So if the container is 
destroyed and a new container is started, then its old data is lost.

The data directory should be mounted as a volume, so that data can be restored 
across container destroy and restore.

To achieve this, Solr data directory should be configurable and by default it 
should be $ATLAS_HOME/data/solr. HBase and Kafka data directory is already 
configured to $ATLAS_HOME/data



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

[jira] [Updated] (ATLAS-3864) Atlas should use AdminClient where possible

2020-11-02 Thread Jayendra Parab (Jira) 


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

Jayendra Parab updated ATLAS-3864:
--
Affects Version/s: 2.1.0

> Atlas should use AdminClient where possible
> ---
>
> Key: ATLAS-3864
> URL: https://issues.apache.org/jira/browse/ATLAS-3864
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.1.0
>Reporter: Viktor Somogyi-Vass
>Assignee: Jayendra Parab
>Priority: Major
>
> Zookeeper access should be restricted wherever possible as going forward 
> Kafka won't use Zookeeper (see 
> [KIP-500|https://cwiki.apache.org/confluence/display/KAFKA/KIP-500%3A+Replace+ZooKeeper+with+a+Self-Managed+Metadata+Quorum]).
> Also the Zookeeper classes in Kafka aren't public apis so usage should be 
> avoided wherever possible. As a tactical fix (see ATLAS-3910) though it is 
> possible to continue using KafkaZkClient as that class likely won't change 
> much until the completion of KIP-500.



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

[jira] [Updated] (ATLAS-3864) Atlas should use AdminClient where possible

2020-11-02 Thread Jayendra Parab (Jira) 


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

Jayendra Parab updated ATLAS-3864:
--
Fix Version/s: 2.2.0
   3.0.0

> Atlas should use AdminClient where possible
> ---
>
> Key: ATLAS-3864
> URL: https://issues.apache.org/jira/browse/ATLAS-3864
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.1.0
>Reporter: Viktor Somogyi-Vass
>Assignee: Jayendra Parab
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> Zookeeper access should be restricted wherever possible as going forward 
> Kafka won't use Zookeeper (see 
> [KIP-500|https://cwiki.apache.org/confluence/display/KAFKA/KIP-500%3A+Replace+ZooKeeper+with+a+Self-Managed+Metadata+Quorum]).
> Also the Zookeeper classes in Kafka aren't public apis so usage should be 
> avoided wherever possible. As a tactical fix (see ATLAS-3910) though it is 
> possible to continue using KafkaZkClient as that class likely won't change 
> much until the completion of KIP-500.



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

[jira] [Resolved] (ATLAS-3864) Atlas should use AdminClient where possible

2020-11-02 Thread Jayendra Parab (Jira) 


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

Jayendra Parab resolved ATLAS-3864.
---
  Assignee: Jayendra Parab
Resolution: Fixed

Fixed as part of https://reviews.apache.org/r/72671/

> Atlas should use AdminClient where possible
> ---
>
> Key: ATLAS-3864
> URL: https://issues.apache.org/jira/browse/ATLAS-3864
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Viktor Somogyi-Vass
>Assignee: Jayendra Parab
>Priority: Major
>
> Zookeeper access should be restricted wherever possible as going forward 
> Kafka won't use Zookeeper (see 
> [KIP-500|https://cwiki.apache.org/confluence/display/KAFKA/KIP-500%3A+Replace+ZooKeeper+with+a+Self-Managed+Metadata+Quorum]).
> Also the Zookeeper classes in Kafka aren't public apis so usage should be 
> avoided wherever possible. As a tactical fix (see ATLAS-3910) though it is 
> possible to continue using KafkaZkClient as that class likely won't change 
> much until the completion of KIP-500.



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

[jira] [Commented] (ATLAS-3816) Backport: Basic search issue with IndexSerializer

2020-11-02 Thread Nikhil Bonte (Jira) 


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

Nikhil Bonte commented on ATLAS-3816:
-

committed to branch-0.8 - 63e3d5c9e5e74f1110d80c7bcfce970725504888

[https://github.com/apache/atlas/commit/63e3d5c9e5e74f1110d80c7bcfce970725504888]

 

> Backport: Basic search issue with IndexSerializer
> -
>
> Key: ATLAS-3816
> URL: https://issues.apache.org/jira/browse/ATLAS-3816
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.4
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: 0.8.4
>
> Attachments: 
> ATLAS-3816-Backport-Basic-search-issue-with-IndexSer-v2.patch
>
>
> *Background:*
> Atlas instance with property 
> _"atlas.use.index.query.to.find.entity.by.unique.attributes=true"_
> Direct index query which has pattern *"v."* throws exception, e.g.
>  
> v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
>  
> This will throw 
> {code:java}
> java.lang.IllegalArgumentException: Found reference to non-existant property 
> key in query at position...{code}
>  
> *Solution:*
> Backporting  ATLAS-2371.
> It is resolved with janusgraph, for titan implementation backporting required.
> Query will be :  
> *$v$*"Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
>  
> Default value for index search prefix is _"$v$"_
> Can be changed using the property _"atlas.graph.index.search.vertex.prefix"_
>  



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

[jira] [Updated] (ATLAS-3816) Backport: Basic search issue with IndexSerializer

2020-11-02 Thread Nikhil Bonte (Jira) 


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

Nikhil Bonte updated ATLAS-3816:

Fix Version/s: 0.8.4

> Backport: Basic search issue with IndexSerializer
> -
>
> Key: ATLAS-3816
> URL: https://issues.apache.org/jira/browse/ATLAS-3816
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.4
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: 0.8.4
>
> Attachments: 
> ATLAS-3816-Backport-Basic-search-issue-with-IndexSer-v2.patch
>
>
> *Background:*
> Atlas instance with property 
> _"atlas.use.index.query.to.find.entity.by.unique.attributes=true"_
> Direct index query which has pattern *"v."* throws exception, e.g.
>  
> v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
>  
> This will throw 
> {code:java}
> java.lang.IllegalArgumentException: Found reference to non-existant property 
> key in query at position...{code}
>  
> *Solution:*
> Backporting  ATLAS-2371.
> It is resolved with janusgraph, for titan implementation backporting required.
> Query will be :  
> *$v$*"Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
>  
> Default value for index search prefix is _"$v$"_
> Can be changed using the property _"atlas.graph.index.search.vertex.prefix"_
>  



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

[jira] [Commented] (ATLAS-3743) [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business Metadata attributes

2020-11-02 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on ATLAS-3743:


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

ATLAS-3743: Date type value is shown as timestamp instead of date, in BM 
audit/technical properties.

(cherry picked from commit 53ae712a095930ebf008e70ece4a7a351030acf3)


> [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business 
> Metadata attributes
> 
>
> Key: ATLAS-3743
> URL: https://issues.apache.org/jira/browse/ATLAS-3743
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3743.patch, Screenshot 2020-04-20 at 8.53.54 
> PM.png, Screenshot 2020-04-20 at 8.54.12 PM.png
>
>
>  Following are the issues observed:
>  # All the BM related operations on an entity are listed as 
> BUSINESS_ATTRIBUTE_UPDATE only. Right now, BUSINESS_ATTRIBUTE_UPDATE shows up 
> for all the operations.
>  ## When a BM attribute is added for the first time, ideally 
> BUSINESS_ATTRIBUTE_ADD action should show up.
>  ## On the same lines, when all the BM attributes are removed from entity, 
> BUSINESS_ATTRIBUTE_DELETE should show up.  
>  # Internal name, BUSINESS_ATTRIBUTE_UPDATE, is listed as action, instead of 
> plain text like "Business Attribute(s) Updated"
>  # Date type value is shown as timestamp instead of date, in audit/technical 
> properties. 
> Attached screenshots.



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

[jira] [Commented] (ATLAS-3743) [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business Metadata attributes

2020-11-02 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on ATLAS-3743:


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

ATLAS-3743: Date type value is shown as timestamp instead of date, in BM 
audit/technical properties.


> [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business 
> Metadata attributes
> 
>
> Key: ATLAS-3743
> URL: https://issues.apache.org/jira/browse/ATLAS-3743
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3743.patch, Screenshot 2020-04-20 at 8.53.54 
> PM.png, Screenshot 2020-04-20 at 8.54.12 PM.png
>
>
>  Following are the issues observed:
>  # All the BM related operations on an entity are listed as 
> BUSINESS_ATTRIBUTE_UPDATE only. Right now, BUSINESS_ATTRIBUTE_UPDATE shows up 
> for all the operations.
>  ## When a BM attribute is added for the first time, ideally 
> BUSINESS_ATTRIBUTE_ADD action should show up.
>  ## On the same lines, when all the BM attributes are removed from entity, 
> BUSINESS_ATTRIBUTE_DELETE should show up.  
>  # Internal name, BUSINESS_ATTRIBUTE_UPDATE, is listed as action, instead of 
> plain text like "Business Attribute(s) Updated"
>  # Date type value is shown as timestamp instead of date, in audit/technical 
> properties. 
> Attached screenshots.



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

[jira] [Updated] (ATLAS-3743) [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business Metadata attributes

2020-11-02 Thread Keval Bhatt (Jira) 


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

Keval Bhatt updated ATLAS-3743:
---
Attachment: ATLAS-3743.patch

> [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business 
> Metadata attributes
> 
>
> Key: ATLAS-3743
> URL: https://issues.apache.org/jira/browse/ATLAS-3743
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3743.patch, Screenshot 2020-04-20 at 8.53.54 
> PM.png, Screenshot 2020-04-20 at 8.54.12 PM.png
>
>
>  Following are the issues observed:
>  # All the BM related operations on an entity are listed as 
> BUSINESS_ATTRIBUTE_UPDATE only. Right now, BUSINESS_ATTRIBUTE_UPDATE shows up 
> for all the operations.
>  ## When a BM attribute is added for the first time, ideally 
> BUSINESS_ATTRIBUTE_ADD action should show up.
>  ## On the same lines, when all the BM attributes are removed from entity, 
> BUSINESS_ATTRIBUTE_DELETE should show up.  
>  # Internal name, BUSINESS_ATTRIBUTE_UPDATE, is listed as action, instead of 
> plain text like "Business Attribute(s) Updated"
>  # Date type value is shown as timestamp instead of date, in audit/technical 
> properties. 
> Attached screenshots.



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