[jira] [Commented] (ATLAS-4473) Glossary Terms Bulk Create Performance Improvement
[ https://issues.apache.org/jira/browse/ATLAS-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17451505#comment-17451505 ] ASF subversion and git services commented on ATLAS-4473: Commit 8810c4477037dafbb518df57ff823c70127052d6 in atlas's branch refs/heads/branch-2.0 from Mandar Ambawane [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8810c44 ] ATLAS-4473: GlossaryTerms Bulk Create Performance Improvement Signed-off-by: Pinal Shah > Glossary Terms Bulk Create Performance Improvement > -- > > Key: ATLAS-4473 > URL: https://issues.apache.org/jira/browse/ATLAS-4473 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > Attachments: ATLAS-4473.patch > > > While creating GlossaryTerms we need information about Glossary and > GlossaryCategory (if present) > As per current design, > When every Term is created, respective Glossary and Category objects are > fetched from db and they are populated with unwanted information. > In case of bulk creation, > Even if multiple Terms have same Glossary and Category associated with them, > every time these objects are fetched from db and they are populated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4473) Glossary Terms Bulk Create Performance Improvement
[ https://issues.apache.org/jira/browse/ATLAS-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17451503#comment-17451503 ] ASF subversion and git services commented on ATLAS-4473: Commit 1db78435f48f2f2f6cff5d1daf1fd8d3deea3068 in atlas's branch refs/heads/master from Mandar Ambawane [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1db7843 ] ATLAS-4473: GlossaryTerms Bulk Create Performance Improvement Signed-off-by: Pinal Shah > Glossary Terms Bulk Create Performance Improvement > -- > > Key: ATLAS-4473 > URL: https://issues.apache.org/jira/browse/ATLAS-4473 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > Attachments: ATLAS-4473.patch > > > While creating GlossaryTerms we need information about Glossary and > GlossaryCategory (if present) > As per current design, > When every Term is created, respective Glossary and Category objects are > fetched from db and they are populated with unwanted information. > In case of bulk creation, > Even if multiple Terms have same Glossary and Category associated with them, > every time these objects are fetched from db and they are populated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4498) Incorrect atlas-buildtools version in pom.xml results in failed build
Greg created ATLAS-4498:
---
Summary: Incorrect atlas-buildtools version in pom.xml results in
failed build
Key: ATLAS-4498
URL: https://issues.apache.org/jira/browse/ATLAS-4498
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 2.2.0
Environment: Redhat UBI (Universal Base Image) 8.5
Reporter: Greg
Attachments: buildtools.patch
The apache-buildtools version specified in /pom.xml is incorrect and results in
Atlas failing to build. The project.version results in a 2.2.0 version and the
plugin version is 1.0 – both of which do not appear to exist:
[https://repo1.maven.org/maven2/org/apache/atlas/atlas-buildtools/]
Patching ${project.version} and 1.0 to 0.8.1 (only version available from link
above) allows Atlas to build successfully.
in /pom.xml
{code:java}
org.apache.atlas
atlas-buildtools
${project.version}
{code}
and
{code:java}
org.apache.maven.plugins
maven-checkstyle-plugin
org.apache.atlas
atlas-buildtools
1.0
{code}
A patch is attached to remedy this issue.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (ATLAS-4497) Large number of CVE's (vulnerabilities) when building 2.2.0 from source
Greg created ATLAS-4497: --- Summary: Large number of CVE's (vulnerabilities) when building 2.2.0 from source Key: ATLAS-4497 URL: https://issues.apache.org/jira/browse/ATLAS-4497 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 2.2.0 Environment: Redhat UBI (Universal Base Image) 8.5 Reporter: Greg Atlas 2.2.0 when built from source has a large number of jar packages that suffer from known exploits / vulnerabilities. I've performed an Anchore and a Twistlock scan of the compiled application and here's the list of the High and Critical vulnerabilities found: [https://pastebin.com/raw/t59rcyH8] I am attempting to put together a public docker image of Atlas compiled from source. You can see my build process here to see how I arrived at the compiled build that I performed the scans on: [https://github.com/589290/docker-apache-atlas-ubi8/blob/main/Dockerfile] I'm not a Java developer, but I would think that a different version of Maven (I'm using 3.6.3) or an updated pom.xml that has more current (vulnerability free) versions of packages may help remedy my findings. I am not sure whether or not this has to do with my downgrading the pom.xml file to use buildtools 0.8.1 since the packages for 1.0 do not seem to be available. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4496) Atlas - Upgrade elasticsearch to 7.14.0
chaitali borole created ATLAS-4496: -- Summary: Atlas - Upgrade elasticsearch to 7.14.0 Key: ATLAS-4496 URL: https://issues.apache.org/jira/browse/ATLAS-4496 Project: Atlas Issue Type: Improvement Components: atlas-core Affects Versions: 2.0.0, 3.0.0 Reporter: chaitali borole Assignee: chaitali borole Fix For: 3.0.0, 2.0.0 Currently Atlas is using elasticsearch version 7.6.0 upgrading it to 7.14.0. -- This message was sent by Atlassian Jira (v8.20.1#820001)
