[jira] [Commented] (ATLAS-4713) docker setup - update component versions
[ https://issues.apache.org/jira/browse/ATLAS-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635112#comment-17635112 ] ASF subversion and git services commented on ATLAS-4713: Commit 887ef24c5069c91fd1fb118d63c8ebca7f2978d5 in atlas's branch refs/heads/branch-2.0 from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=887ef24c5 ] ATLAS-4713: docker setup updates to be in sync with component versions in project pom.xml > docker setup - update component versions > > > Key: ATLAS-4713 > URL: https://issues.apache.org/jira/browse/ATLAS-4713 > Project: Atlas > Issue Type: Bug > Components: atlas-docker >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 2.3.0 > > Attachments: ATLAS-4713.patch > > > Docker setup needs updates to be in sync with component versions in project > pom.xml file. For example: > * ATLAS_VERSION=2.2.0 should be 2.3.0-SNAPSHOT > * KAFKA_VERSION=2.5.0 should be 2.8.1 > * HIVE_HADOOP_VERSION=3.1.0 should be 3.1.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-3820) run import-kafka.sh throws Expection
[ https://issues.apache.org/jira/browse/ATLAS-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635114#comment-17635114 ] ASF subversion and git services commented on ATLAS-3820: Commit 2c2d9197e68b809198d6e9f1232473d1c2d9e960 in atlas's branch refs/heads/branch-2.0 from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2c2d9197e ] ATLAS-3820: fix import-kafka.sh failures; updated docker setup for Kafka bridge > run import-kafka.sh throws Expection > > > Key: ATLAS-3820 > URL: https://issues.apache.org/jira/browse/ATLAS-3820 > Project: Atlas > Issue Type: Bug > Components: kafka-integration >Affects Versions: 1.0.0 > Environment: Kafka version: 1.1.0 >Reporter: fa >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 2.3.0 > > Attachments: ATLAS-3820.patch > > > maven build command: mvn clean -DskipTests package -Pdist,embedded-hbase-solr > I run `bin/atlas_stat.py`, and I can see the web-ui. > Then I run > apache-atlas-1.0.0-kafka-hook/apache-atlas-kafka-hook-1.0.0/hook-bin/import-kafka.sh. > stack trace > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/commons/lang/exception/NestableRuntimeExceptionException in thread > "main" java.lang.NoClassDefFoundError: > org/apache/commons/lang/exception/NestableRuntimeException at > java.lang.ClassLoader.defineClass1(Native Method) at > java.lang.ClassLoader.defineClass(ClassLoader.java:763) at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at > java.net.URLClassLoader.defineClass(URLClassLoader.java:468) at > java.net.URLClassLoader.access$100(URLClassLoader.java:74) at > java.net.URLClassLoader$1.run(URLClassLoader.java:369) at > java.net.URLClassLoader$1.run(URLClassLoader.java:363) at > java.security.AccessController.doPrivileged(Native Method) at > java.net.URLClassLoader.findClass(URLClassLoader.java:362) at > java.lang.ClassLoader.loadClass(ClassLoader.java:424) at > sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at > java.lang.ClassLoader.loadClass(ClassLoader.java:357) at > java.lang.ClassLoader.defineClass1(Native Method) at > java.lang.ClassLoader.defineClass(ClassLoader.java:763) at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at > java.net.URLClassLoader.defineClass(URLClassLoader.java:468) at > java.net.URLClassLoader.access$100(URLClassLoader.java:74) at > java.net.URLClassLoader$1.run(URLClassLoader.java:369) at > java.net.URLClassLoader$1.run(URLClassLoader.java:363) at > java.security.AccessController.doPrivileged(Native Method) at > java.net.URLClassLoader.findClass(URLClassLoader.java:362) at > java.lang.ClassLoader.loadClass(ClassLoader.java:424) at > sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at > java.lang.ClassLoader.loadClass(ClassLoader.java:357) at > org.apache.atlas.kafka.bridge.KafkaBridge.main(KafkaBridge.java:100)Caused > by: java.lang.ClassNotFoundException: > org.apache.commons.lang.exception.NestableRuntimeException at > java.net.URLClassLoader.findClass(URLClassLoader.java:382) at > java.lang.ClassLoader.loadClass(ClassLoader.java:424) at > sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at > java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 25 more -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4241) import-hbase.sh get map error
[ https://issues.apache.org/jira/browse/ATLAS-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635113#comment-17635113 ] ASF subversion and git services commented on ATLAS-4241: Commit da27bb1b497db7f234c66203255a3ded37af3631 in atlas's branch refs/heads/branch-2.0 from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=da27bb1b4 ] ATLAS-4241: fix import-hbase errors > import-hbase.sh get map error > - > > Key: ATLAS-4241 > URL: https://issues.apache.org/jira/browse/ATLAS-4241 > Project: Atlas > Issue Type: Bug > Components: hbase-integration >Affects Versions: 2.1.0 >Reporter: junsionzhang >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 2.3.0 > > Attachments: ATLAS-4241.patch > > > when run import-hbase.sh ,errors is as follows: > 2021-04-12 14:34:25,865 ERROR - [main:] ~ ImportHBaseEntities failed > (HBaseBridge:197) > org.apache.atlas.AtlasException: Failed to load application properties > at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:147) > at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:100) > at org.apache.atlas.hbase.bridge.HBaseBridge.main(HBaseBridge.java:139) > Caused by: org.apache.commons.configuration.ConversionException: > 'atlas.graph.index.search.solr.wait-searcher' doesn't map to a List object: > true, a java.lang.Boolean > at > org.apache.commons.configuration.AbstractConfiguration.getList(AbstractConfiguration.java:1144) > at > org.apache.commons.configuration.AbstractConfiguration.getList(AbstractConfiguration.java:1109) > at > org.apache.commons.configuration.AbstractConfiguration.interpolatedConfiguration(AbstractConfiguration.java:1274) > at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:142) > ... 2 more > > It seems the common-configuration does not work correctly . the hbasebridge > use common-configuration 1.10 ,but the version also exists. could somebody > upgrade from 1.x to 2.x > > https://commons.apache.org/proper/commons-configuration/userguide/upgradeto2_0.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4445) unable to run import-hive.sh successfully
[
https://issues.apache.org/jira/browse/ATLAS-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635111#comment-17635111
]
ASF subversion and git services commented on ATLAS-4445:
Commit 1a5bf676218d371398e700c1a348a60c11c52867 in atlas's branch
refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1a5bf6762 ]
ATLAS-4445: fix import-hive.sh failure; updated hive version from 3.1.0 to 3.1.2
> unable to run import-hive.sh successfully
> -
>
> Key: ATLAS-4445
> URL: https://issues.apache.org/jira/browse/ATLAS-4445
> Project: Atlas
> Issue Type: Bug
> Components: hive-integration
>Affects Versions: 2.2.0
> Environment: RHEL 7.x
>Reporter: Tim Hunter
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 2.3.0
>
> Attachments: ATLAS-4445.patch
>
>
> Same configuration this worked in 2.1.0, unable to figure out why it doesn't
> in 2.2.0
>
> {{$ ./import-hive.sh $ ./import-hive.sh Using Hive configuration directory
> [/usr/local/hive/conf]Log file for import is
> /var/log/atlas/import-hive.logSLF4J: Class path contains multiple SLF4J
> bindings.SLF4J: Found binding in
> [jar:file:/usr/local/hive/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]SLF4J:
> Found binding in
> [jar:file:/home/ec2-user/hadoop-3.3.1/share/hadoop/common/lib/slf4j-log4j12-1.7.30.jar!/org/slf4j/impl/StaticLoggerBinder.class]SLF4J:
> See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.SLF4J: Actual binding is of type
> [org.apache.logging.slf4j.Log4jLoggerFactory]2021-10-05T12:57:32,810 INFO
> [main] org.apache.atlas.hive.bridge.HiveMetaStoreBridge - delete non existing
> flag : false 2021-10-05T12:57:32,841 INFO [main]
> org.apache.atlas.ApplicationProperties - Looking for
> atlas-application.properties in classpath2021-10-05T12:57:32,843 INFO [main]
> org.apache.atlas.ApplicationProperties - Loading atlas-application.properties
> from
> file:/opt/atlas/apache-atlas-2.2.0/conf/atlas-application.properties2021-10-05T12:57:32,903
> INFO [main] org.apache.atlas.ApplicationProperties - Using graphdb backend
> 'janus'2021-10-05T12:57:32,903 INFO [main]
> org.apache.atlas.ApplicationProperties - Using storage backend
> 'hbase2'2021-10-05T12:57:32,903 INFO [main]
> org.apache.atlas.ApplicationProperties - Using index backend
> 'solr'2021-10-05T12:57:32,903 INFO [main]
> org.apache.atlas.ApplicationProperties - Atlas is running in MODE:
> PROD.2021-10-05T12:57:32,904 INFO [main]
> org.apache.atlas.ApplicationProperties - Setting solr.wait-searcher property
> 'false'2021-10-05T12:57:32,904 INFO [main]
> org.apache.atlas.ApplicationProperties - Setting index.search.map-name
> property 'false'2021-10-05T12:57:32,904 INFO [main]
> org.apache.atlas.ApplicationProperties - Setting
> atlas.graph.index.search.max-result-set-size = 1502021-10-05T12:57:32,904
> INFO [main] org.apache.atlas.ApplicationProperties - Setting
> atlas.graph.index.search.solr.wait-searcher = false2021-10-05T12:57:32,905
> INFO [main] org.apache.atlas.ApplicationProperties - Property (set to
> default) atlas.graph.cache.db-cache = true2021-10-05T12:57:32,905 INFO [main]
> org.apache.atlas.ApplicationProperties - Property (set to default)
> atlas.graph.cache.db-cache-clean-wait = 202021-10-05T12:57:32,905 INFO [main]
> org.apache.atlas.ApplicationProperties - Property (set to default)
> atlas.graph.cache.db-cache-size = 0.52021-10-05T12:57:32,905 INFO [main]
> org.apache.atlas.ApplicationProperties - Property (set to default)
> atlas.graph.cache.tx-cache-size = 150002021-10-05T12:57:32,905 INFO [main]
> org.apache.atlas.ApplicationProperties - Property (set to default)
> atlas.graph.cache.tx-dirty-size = 120Enter username for atlas :- adminEnter
> password for atlas :- Exception in thread "main"
> java.lang.NoClassDefFoundError: javax/ws/rs/core/Link$Builder at
> java.lang.Class.getDeclaredConstructors0(Native Method) at
> java.lang.Class.privateGetDeclaredConstructors(Class.java:2671) at
> java.lang.Class.getConstructor0(Class.java:3075) at
> java.lang.Class.newInstance(Class.java:412) at
> javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:65) at
> javax.ws.rs.ext.FactoryFinder.find(FactoryFinder.java:117) at
> javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:105) at
> javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:91) at
> javax.ws.rs.core.MediaType.(MediaType.java:44) at
> com.sun.jersey.core.header.MediaTypes.(MediaTypes.java:65) at
> com.sun.jersey.core.spi.factory.MessageBodyFactory.initReaders(MessageBodyFactory.java:182)
> at
> com.sun.jersey.core.spi.factory.MessageBodyFactory.initReaders(MessageBodyFac
[jira] [Commented] (ATLAS-2388) Disabled Unit Test: InMemoryJAASConfigurationTest.java:31
[ https://issues.apache.org/jira/browse/ATLAS-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631461#comment-17631461 ] ASF subversion and git services commented on ATLAS-2388: Commit 8ca041c982968fb1e769cd7ba20f9d342adebba3 in atlas's branch refs/heads/branch-2.0 from Peter Gergo Barna [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8ca041c98 ] ATLAS-2388: enabled InMemoryJAASConfigurationTest Signed-off-by: Madhan Neethiraj (cherry picked from commit d7a6242442085032a17bc60fd0b13bf62c3ebc1c) > Disabled Unit Test: InMemoryJAASConfigurationTest.java:31 > - > > Key: ATLAS-2388 > URL: https://issues.apache.org/jira/browse/ATLAS-2388 > Project: Atlas > Issue Type: Bug >Reporter: Graham Wallis >Priority: Blocker > Fix For: 1.0.0 > > > The above test needs to be reviewed and should probably be re-enabled -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-2388) Disabled Unit Test: InMemoryJAASConfigurationTest.java:31
[ https://issues.apache.org/jira/browse/ATLAS-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631459#comment-17631459 ] ASF subversion and git services commented on ATLAS-2388: Commit d7a6242442085032a17bc60fd0b13bf62c3ebc1c in atlas's branch refs/heads/master from Peter Gergo Barna [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d7a624244 ] ATLAS-2388: enabled InMemoryJAASConfigurationTest Signed-off-by: Madhan Neethiraj > Disabled Unit Test: InMemoryJAASConfigurationTest.java:31 > - > > Key: ATLAS-2388 > URL: https://issues.apache.org/jira/browse/ATLAS-2388 > Project: Atlas > Issue Type: Bug >Reporter: Graham Wallis >Priority: Blocker > Fix For: 1.0.0 > > > The above test needs to be reviewed and should probably be re-enabled -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4707) update UI component version for scss-tokenizer, node-sass and loader-utils
[ https://issues.apache.org/jira/browse/ATLAS-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631191#comment-17631191 ] ASF subversion and git services commented on ATLAS-4707: Commit 5af98986722e382a0d7dc6c4ed88a9869385d120 in atlas's branch refs/heads/branch-2.0 from dependabot[bot] [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5af989867 ] ATLAS-4707: updated loader-utils version from 1.4.0 to 1.4.1 - #2 Signed-off-by: Madhan Neethiraj (cherry picked from commit 2135188cc8a6f24e4a879b1783433c9945fe7ec2) > update UI component version for scss-tokenizer, node-sass and loader-utils > -- > > Key: ATLAS-4707 > URL: https://issues.apache.org/jira/browse/ATLAS-4707 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > This Jira tracks version updates in following pull requests: > - [pull request #202|https://github.com/apache/atlas/pull/202] > - [pull request #201|https://github.com/apache/atlas/pull/201] > - [pull request #205|https://github.com/apache/atlas/pull/205] > - [pull request #206|https://github.com/apache/atlas/pull/206] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4707) update UI component version for scss-tokenizer, node-sass and loader-utils
[ https://issues.apache.org/jira/browse/ATLAS-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631190#comment-17631190 ] ASF subversion and git services commented on ATLAS-4707: Commit 2135188cc8a6f24e4a879b1783433c9945fe7ec2 in atlas's branch refs/heads/master from dependabot[bot] [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2135188cc ] ATLAS-4707: updated loader-utils version from 1.4.0 to 1.4.1 - #2 Signed-off-by: Madhan Neethiraj > update UI component version for scss-tokenizer, node-sass and loader-utils > -- > > Key: ATLAS-4707 > URL: https://issues.apache.org/jira/browse/ATLAS-4707 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > This Jira tracks version updates in following pull requests: > - [pull request #202|https://github.com/apache/atlas/pull/202] > - [pull request #201|https://github.com/apache/atlas/pull/201] > - [pull request #205|https://github.com/apache/atlas/pull/205] > - [pull request #206|https://github.com/apache/atlas/pull/206] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4710) [Atlas][UI]Relationship Attribute Filter button keeps loading
[ https://issues.apache.org/jira/browse/ATLAS-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631068#comment-17631068 ] ASF subversion and git services commented on ATLAS-4710: Commit 48cbd799d89e6797e7c2a65658419082ce1e6cc0 in atlas's branch refs/heads/branch-2.0 from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=48cbd799d ] ATLAS-4710 : (UI)Relationship Attribute Filter button keeps loading Signed-off-by: Prasad Pawar > [Atlas][UI]Relationship Attribute Filter button keeps loading > - > > Key: ATLAS-4710 > URL: https://issues.apache.org/jira/browse/ATLAS-4710 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 3.0.0, 2.3.0 >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4710-UI-Relationship-Attribute-Filter-button-k.patch > > > The Relationship Attribute Filter button is stuck on the loading icon loop > and filters don't appear. > This is working on the Entity Attribute Filter button and via the API call, > but not on the UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4710) [Atlas][UI]Relationship Attribute Filter button keeps loading
[ https://issues.apache.org/jira/browse/ATLAS-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631066#comment-17631066 ] ASF subversion and git services commented on ATLAS-4710: Commit 953ce61db16457334e65c6f82bd49accaa649a00 in atlas's branch refs/heads/master from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=953ce61db ] ATLAS-4710 : (UI)Relationship Attribute Filter button keeps loading Signed-off-by: Prasad Pawar > [Atlas][UI]Relationship Attribute Filter button keeps loading > - > > Key: ATLAS-4710 > URL: https://issues.apache.org/jira/browse/ATLAS-4710 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 3.0.0, 2.3.0 >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4710-UI-Relationship-Attribute-Filter-button-k.patch > > > The Relationship Attribute Filter button is stuck on the loading icon loop > and filters don't appear. > This is working on the Entity Attribute Filter button and via the API call, > but not on the UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4709) Python client version 0.0.12
[ https://issues.apache.org/jira/browse/ATLAS-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17630568#comment-17630568 ] ASF subversion and git services commented on ATLAS-4709: Commit 6490db743c148a6fbb57ef6c114d1584eb0cf0ed in atlas's branch refs/heads/branch-2.0 from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=6490db743 ] ATLAS-4709: Python client 0.0.12 release (cherry picked from commit d40c1b09f533bce6fd27e97489885c10887fe4ec) > Python client version 0.0.12 > > > Key: ATLAS-4709 > URL: https://issues.apache.org/jira/browse/ATLAS-4709 > Project: Atlas > Issue Type: Task > Components: atlas-intg >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > > Following fixes were added since Apache Atlas Python client release - 0.0.11 : > * ATLAS-4205: fixes in Python sample-app and Python client > * ATLAS-4318 : fix python client api url concatenation > * ATLAS-4318 : Fixed bug in entity.py > * ATLAS-4590: fix minor problem in list_attributes_to_params() > * ATLAS-4676: do not expect response body to be a valid JSON > * ATLAS-4704: Remove os.path.join causing incorrect windows path > This Jira tracks release of Apache Atlas Python client version 0.0.12 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4709) Python client version 0.0.12
[ https://issues.apache.org/jira/browse/ATLAS-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17630567#comment-17630567 ] ASF subversion and git services commented on ATLAS-4709: Commit d40c1b09f533bce6fd27e97489885c10887fe4ec in atlas's branch refs/heads/master from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d40c1b09f ] ATLAS-4709: Python client 0.0.12 release > Python client version 0.0.12 > > > Key: ATLAS-4709 > URL: https://issues.apache.org/jira/browse/ATLAS-4709 > Project: Atlas > Issue Type: Task > Components: atlas-intg >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > > Following fixes were added since Apache Atlas Python client release - 0.0.11 : > * ATLAS-4205: fixes in Python sample-app and Python client > * ATLAS-4318 : fix python client api url concatenation > * ATLAS-4318 : Fixed bug in entity.py > * ATLAS-4590: fix minor problem in list_attributes_to_params() > * ATLAS-4676: do not expect response body to be a valid JSON > * ATLAS-4704: Remove os.path.join causing incorrect windows path > This Jira tracks release of Apache Atlas Python client version 0.0.12 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4707) update UI component version for scss-tokenizer and node-sass
[ https://issues.apache.org/jira/browse/ATLAS-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17630496#comment-17630496 ] ASF subversion and git services commented on ATLAS-4707: Commit 73e5c845662b16eeb3be8d00d9ae32d84f8b9c67 in atlas's branch refs/heads/branch-2.0 from dependabot[bot] [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=73e5c8456 ] ATLAS-4707: updated versions of scss-tokenizer 0.2.3 to 0.4.3, node-sass 4.13.1 to 7.0.3 Signed-off-by: Madhan Neethiraj (cherry picked from commit fbdf7863d59d04f8437c07d5bfd20fe1cbf4) > update UI component version for scss-tokenizer and node-sass > - > > Key: ATLAS-4707 > URL: https://issues.apache.org/jira/browse/ATLAS-4707 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > This Jira tracks version updates in following pull requests: > - [pull request #202|https://github.com/apache/atlas/pull/202] > - [pull request #201|https://github.com/apache/atlas/pull/201] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4707) update UI component version for scss-tokenizer and node-sass
[ https://issues.apache.org/jira/browse/ATLAS-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17630495#comment-17630495 ] ASF subversion and git services commented on ATLAS-4707: Commit fbdf7863d59d04f8437c07d5bfd20fe1cbf4 in atlas's branch refs/heads/master from dependabot[bot] [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=fbdf7 ] ATLAS-4707: updated versions of scss-tokenizer 0.2.3 to 0.4.3, node-sass 4.13.1 to 7.0.3 Signed-off-by: Madhan Neethiraj > update UI component version for scss-tokenizer and node-sass > - > > Key: ATLAS-4707 > URL: https://issues.apache.org/jira/browse/ATLAS-4707 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > This Jira tracks version updates in following pull requests: > - [pull request #202|https://github.com/apache/atlas/pull/202] > - [pull request #201|https://github.com/apache/atlas/pull/201] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4706) avoid duplicate call to retrieve entity-type in AtlasEntityStoreV2.java
[ https://issues.apache.org/jira/browse/ATLAS-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629674#comment-17629674 ] ASF subversion and git services commented on ATLAS-4706: Commit 7cb38028564bdc4bb799e0c022504cbb574a562e in atlas's branch refs/heads/branch-2.0 from zhuangchong [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=7cb380285 ] ATLAS-4706: code clean in the entity store v2 class Signed-off-by: Madhan Neethiraj (cherry picked from commit f497d7224f5dd1fcb73c8523a800e2b6ae26c274) > avoid duplicate call to retrieve entity-type in AtlasEntityStoreV2.java > --- > > Key: ATLAS-4706 > URL: https://issues.apache.org/jira/browse/ATLAS-4706 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: zhuangchong >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > from [pull request #178|https://github.com/apache/atlas/pull/178]: code clean > in the entity store v2 class -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4676) Atlas 401 response make Python client fail with JSON decode error
[
https://issues.apache.org/jira/browse/ATLAS-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629672#comment-17629672
]
ASF subversion and git services commented on ATLAS-4676:
Commit 0ccd96aa047a95fa754e0893d9b829c74c9a5e15 in atlas's branch
refs/heads/branch-2.0 from Maxim Martynov
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=0ccd96aa0 ]
ATLAS-4676: do not expect response body to be a valid JSON
Signed-off-by: Madhan Neethiraj
(cherry picked from commit a43ed6c11d3ca3c8a63b86981c3241365eb60b79)
> Atlas 401 response make Python client fail with JSON decode error
> -
>
> Key: ATLAS-4676
> URL: https://issues.apache.org/jira/browse/ATLAS-4676
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 2.1.0
>Reporter: Maxim Martynov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I've tried to use apache-atlas Python client to get an entity via API, but
> passed wrong password. Instead of 401 HTTP error I've got:
> {code:java}
> ~/.local/lib/python3.7/site-packages/apache_atlas/client/entity.py in
> get_entity_by_attribute(self, type_name, uniq_attributes, min_ext_info,
> ignore_relationships)
> 123
> 124 return
> self.client.call_api(EntityClient.GET_ENTITY_BY_UNIQUE_ATTRIBUTE.format_path_with_params(type_name),
> --> 125 AtlasEntityWithExtInfo,
> query_params)
> 126
> 127 def get_entities_by_guids(self, guids, min_ext_info=False,
> ignore_relationships=False):
> ~/.local/lib/python3.7/site-packages/apache_atlas/client/base_client.py in
> call_api(self, api, response_type, query_params, request_obj)
> 116 return None
> 117 else:
> --> 118 raise AtlasServiceException(api, response)
> ~/.local/lib/python3.7/site-packages/apache_atlas/exceptions.py in
> __init__(self, api, response)
> 36 msg = "Metadata service API with url {url} and method
> {method} : failed with status {status} and " \
> 37 "Response Body is :{response}". \
> ---> 38 format(**{'url': response.url, 'method': api.method,
> 'status': status, 'response': response.json()})
> 39
> 40 Exception.__init__(self, msg)
> /opt/anaconda/envs/jh-py37-conda/lib/python3.7/site-packages/requests/models.py
> in json(self, **kwargs)
> 898 # used.
> 899 pass
> --> 900 return complexjson.loads(self.text, **kwargs)
> 901
> 902 @property
> /opt/anaconda/envs/jh-py37-conda/lib/python3.7/json/__init__.py in loads(s,
> encoding, cls, object_hook, parse_float, parse_int, parse_constant,
> object_pairs_hook, **kw)
> 346 parse_int is None and parse_float is None and
> 347 parse_constant is None and object_pairs_hook is None and
> not kw):
> --> 348 return _default_decoder.decode(s)
> 349 if cls is None:
> 350 cls = JSONDecoder
> /opt/anaconda/envs/jh-py37-conda/lib/python3.7/json/decoder.py in
> decode(self, s, _w)
> 335
> 336 """
> --> 337 obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> 338 end = _w(s, end).end()
> 339 if end != len(s):
> /opt/anaconda/envs/jh-py37-conda/lib/python3.7/json/decoder.py in
> raw_decode(self, s, idx)
> 353 obj, end = self.scan_once(s, idx)
> 354 except StopIteration as err:
> --> 355 raise JSONDecodeError("Expecting value", s, err.value)
> from None
> 356 return obj, end
> JSONDecodeError: Expecting value: line 1 column 1 (char 0) {code}
> This is caused by this line:
> https://github.com/apache/atlas/blob/146835ef03158d87defa1ef082decf9e05becbb0/intg/src/main/python/apache_atlas/exceptions.py#L38
> Client can get not only JSON, but an empty string, or HTML page (if Atlas is
> running behind nginx as a reverse proxy).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4705) Remove unnecessary single quote at the end of flink_model.json
[ https://issues.apache.org/jira/browse/ATLAS-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629673#comment-17629673 ] ASF subversion and git services commented on ATLAS-4705: Commit 5c2434ca396108378bd6c04e9ab8efc07f02fca1 in atlas's branch refs/heads/branch-2.0 from yanxu3 [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5c2434ca3 ] ATLAS-4705: Remove unnecessary single quote at the end of flink_model.json Signed-off-by: Madhan Neethiraj (cherry picked from commit 4774ed61d5de579d3c9bad9162115e8c6cbb57a6) > Remove unnecessary single quote at the end of flink_model.json > -- > > Key: ATLAS-4705 > URL: https://issues.apache.org/jira/browse/ATLAS-4705 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: zhuangchong >Priority: Minor > Fix For: 3.0.0, 2.3.0 > > > from [pull request #183|https://github.com/apache/atlas/pull/183]: Remove > unnecessary single quote at the end of flink_model.json -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4704) Remove os.path.join causing incorrect windows path
[ https://issues.apache.org/jira/browse/ATLAS-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629671#comment-17629671 ] ASF subversion and git services commented on ATLAS-4704: Commit 956cac4b783741f4db93ce9bbeea99c6e49e2806 in atlas's branch refs/heads/branch-2.0 from Dov Benyomin Sohacheski [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=956cac4b7 ] ATLAS-4704: Remove os.path.join causing incorrect windows path Signed-off-by: Madhan Neethiraj (cherry picked from commit b9ff08fee7646f10083da2f8672b932a34aa4a7f) > Remove os.path.join causing incorrect windows path > -- > > Key: ATLAS-4704 > URL: https://issues.apache.org/jira/browse/ATLAS-4704 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 2.2.0 >Reporter: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > from [pull request #203|https://github.com/apache/atlas/pull/203]: > When running on Windows the os.path.join using the operating systems os.sep=\ > which causing the full url to be incorrect. > Using urllib.parse might be a little bit slower, but is less error-prone. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4706) avoid duplicate call to retrieve entity-type in AtlasEntityStoreV2.java
[ https://issues.apache.org/jira/browse/ATLAS-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629668#comment-17629668 ] ASF subversion and git services commented on ATLAS-4706: Commit 4774ed61d5de579d3c9bad9162115e8c6cbb57a6 in atlas's branch refs/heads/master from yanxu3 [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4774ed61d ] ATLAS-4706: Remove unnecessary single quote at the end of flink_model.json Signed-off-by: Madhan Neethiraj > avoid duplicate call to retrieve entity-type in AtlasEntityStoreV2.java > --- > > Key: ATLAS-4706 > URL: https://issues.apache.org/jira/browse/ATLAS-4706 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: zhuangchong >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > from [pull request #178|https://github.com/apache/atlas/pull/178]: code clean > in the entity store v2 class -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4706) avoid duplicate call to retrieve entity-type in AtlasEntityStoreV2.java
[ https://issues.apache.org/jira/browse/ATLAS-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629669#comment-17629669 ] ASF subversion and git services commented on ATLAS-4706: Commit f497d7224f5dd1fcb73c8523a800e2b6ae26c274 in atlas's branch refs/heads/master from zhuangchong [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f497d7224 ] ATLAS-4706: code clean in the entity store v2 class Signed-off-by: Madhan Neethiraj > avoid duplicate call to retrieve entity-type in AtlasEntityStoreV2.java > --- > > Key: ATLAS-4706 > URL: https://issues.apache.org/jira/browse/ATLAS-4706 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: zhuangchong >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > from [pull request #178|https://github.com/apache/atlas/pull/178]: code clean > in the entity store v2 class -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4676) Atlas 401 response make Python client fail with JSON decode error
[
https://issues.apache.org/jira/browse/ATLAS-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629667#comment-17629667
]
ASF subversion and git services commented on ATLAS-4676:
Commit a43ed6c11d3ca3c8a63b86981c3241365eb60b79 in atlas's branch
refs/heads/master from Maxim Martynov
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=a43ed6c11 ]
ATLAS-4676: do not expect response body to be a valid JSON
Signed-off-by: Madhan Neethiraj
> Atlas 401 response make Python client fail with JSON decode error
> -
>
> Key: ATLAS-4676
> URL: https://issues.apache.org/jira/browse/ATLAS-4676
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 2.1.0
>Reporter: Maxim Martynov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I've tried to use apache-atlas Python client to get an entity via API, but
> passed wrong password. Instead of 401 HTTP error I've got:
> {code:java}
> ~/.local/lib/python3.7/site-packages/apache_atlas/client/entity.py in
> get_entity_by_attribute(self, type_name, uniq_attributes, min_ext_info,
> ignore_relationships)
> 123
> 124 return
> self.client.call_api(EntityClient.GET_ENTITY_BY_UNIQUE_ATTRIBUTE.format_path_with_params(type_name),
> --> 125 AtlasEntityWithExtInfo,
> query_params)
> 126
> 127 def get_entities_by_guids(self, guids, min_ext_info=False,
> ignore_relationships=False):
> ~/.local/lib/python3.7/site-packages/apache_atlas/client/base_client.py in
> call_api(self, api, response_type, query_params, request_obj)
> 116 return None
> 117 else:
> --> 118 raise AtlasServiceException(api, response)
> ~/.local/lib/python3.7/site-packages/apache_atlas/exceptions.py in
> __init__(self, api, response)
> 36 msg = "Metadata service API with url {url} and method
> {method} : failed with status {status} and " \
> 37 "Response Body is :{response}". \
> ---> 38 format(**{'url': response.url, 'method': api.method,
> 'status': status, 'response': response.json()})
> 39
> 40 Exception.__init__(self, msg)
> /opt/anaconda/envs/jh-py37-conda/lib/python3.7/site-packages/requests/models.py
> in json(self, **kwargs)
> 898 # used.
> 899 pass
> --> 900 return complexjson.loads(self.text, **kwargs)
> 901
> 902 @property
> /opt/anaconda/envs/jh-py37-conda/lib/python3.7/json/__init__.py in loads(s,
> encoding, cls, object_hook, parse_float, parse_int, parse_constant,
> object_pairs_hook, **kw)
> 346 parse_int is None and parse_float is None and
> 347 parse_constant is None and object_pairs_hook is None and
> not kw):
> --> 348 return _default_decoder.decode(s)
> 349 if cls is None:
> 350 cls = JSONDecoder
> /opt/anaconda/envs/jh-py37-conda/lib/python3.7/json/decoder.py in
> decode(self, s, _w)
> 335
> 336 """
> --> 337 obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> 338 end = _w(s, end).end()
> 339 if end != len(s):
> /opt/anaconda/envs/jh-py37-conda/lib/python3.7/json/decoder.py in
> raw_decode(self, s, idx)
> 353 obj, end = self.scan_once(s, idx)
> 354 except StopIteration as err:
> --> 355 raise JSONDecodeError("Expecting value", s, err.value)
> from None
> 356 return obj, end
> JSONDecodeError: Expecting value: line 1 column 1 (char 0) {code}
> This is caused by this line:
> https://github.com/apache/atlas/blob/146835ef03158d87defa1ef082decf9e05becbb0/intg/src/main/python/apache_atlas/exceptions.py#L38
> Client can get not only JSON, but an empty string, or HTML page (if Atlas is
> running behind nginx as a reverse proxy).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4704) Remove os.path.join causing incorrect windows path
[ https://issues.apache.org/jira/browse/ATLAS-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629666#comment-17629666 ] ASF subversion and git services commented on ATLAS-4704: Commit b9ff08fee7646f10083da2f8672b932a34aa4a7f in atlas's branch refs/heads/master from Dov Benyomin Sohacheski [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b9ff08fee ] ATLAS-4704: Remove os.path.join causing incorrect windows path Signed-off-by: Madhan Neethiraj > Remove os.path.join causing incorrect windows path > -- > > Key: ATLAS-4704 > URL: https://issues.apache.org/jira/browse/ATLAS-4704 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 2.2.0 >Reporter: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > from [pull request #203|https://github.com/apache/atlas/pull/203]: > When running on Windows the os.path.join using the operating systems os.sep=\ > which causing the full url to be incorrect. > Using urllib.parse might be a little bit slower, but is less error-prone. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4642) remove unnecessary static members from plugin class loaders
[ https://issues.apache.org/jira/browse/ATLAS-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629559#comment-17629559 ] ASF subversion and git services commented on ATLAS-4642: Commit 5ff630a0b6dd5a1a35b75bc4cf8c0213ee341d0a in atlas's branch refs/heads/branch-2.0 from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5ff630a0b ] ATLAS-4642: replace use of static volatile member from plugin classloader (cherry picked from commit 218dd81db9f3ea87f75833bee6acee1c70e2b1df) > remove unnecessary static members from plugin class loaders > --- > > Key: ATLAS-4642 > URL: https://issues.apache.org/jira/browse/ATLAS-4642 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: ATLAS-4642.patch > > > Plugin class loader uses static class member, which can/should be replaced > with non-static equivalent. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4692) Upgrade Apache Commons Text to 1.10.0
[ https://issues.apache.org/jira/browse/ATLAS-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629557#comment-17629557 ] ASF subversion and git services commented on ATLAS-4692: Commit 47b645e5e5a08bb267088793846fe01362c34901 in atlas's branch refs/heads/branch-2.0 from Jayendra Parab [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=47b645e5e ] ATLAS-4692: upgraded Apache Commons Text to 1.10.0 Signed-off-by: Madhan Neethiraj (cherry picked from commit a0a5c596f6a551c4612b3063ad96b000374f46ff) > Upgrade Apache Commons Text to 1.10.0 > - > > Key: ATLAS-4692 > URL: https://issues.apache.org/jira/browse/ATLAS-4692 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 2.2.0 >Reporter: Jayendra Parab >Assignee: Jayendra Parab >Priority: Major > > Upgrade Apache Commons Text to 1.10.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4692) Upgrade Apache Commons Text to 1.10.0
[ https://issues.apache.org/jira/browse/ATLAS-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629556#comment-17629556 ] ASF subversion and git services commented on ATLAS-4692: Commit a0a5c596f6a551c4612b3063ad96b000374f46ff in atlas's branch refs/heads/master from Jayendra Parab [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=a0a5c596f ] ATLAS-4692: upgraded Apache Commons Text to 1.10.0 Signed-off-by: Madhan Neethiraj > Upgrade Apache Commons Text to 1.10.0 > - > > Key: ATLAS-4692 > URL: https://issues.apache.org/jira/browse/ATLAS-4692 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 2.2.0 >Reporter: Jayendra Parab >Assignee: Jayendra Parab >Priority: Major > > Upgrade Apache Commons Text to 1.10.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4677) Atlas - Upgrade commons-configuration to 2.8.0
[ https://issues.apache.org/jira/browse/ATLAS-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627154#comment-17627154 ] ASF subversion and git services commented on ATLAS-4677: Commit e71708f5fbbf9fe518835a7c1e8cc4501810273c in atlas's branch refs/heads/master from chaitali borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e71708f5f ] ATLAS-4677 : Upgrade commons-configuration to 2.8.0 Signed-off-by: Pinal Shah > Atlas - Upgrade commons-configuration to 2.8.0 > -- > > Key: ATLAS-4677 > URL: https://issues.apache.org/jira/browse/ATLAS-4677 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 2.0.0, 3.0.0 > > > Current version for commons-configuration2 is 2.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4677) Atlas - Upgrade commons-configuration to 2.8.0
[ https://issues.apache.org/jira/browse/ATLAS-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627155#comment-17627155 ] ASF subversion and git services commented on ATLAS-4677: Commit def9427507a88749aaecdb1ec1f9bf09e1568dd0 in atlas's branch refs/heads/branch-2.0 from chaitali borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=def942750 ] ATLAS-4677 : Upgrade commons-configuration to 2.8.0 Signed-off-by: Pinal Shah (cherry picked from commit e71708f5fbbf9fe518835a7c1e8cc4501810273c) > Atlas - Upgrade commons-configuration to 2.8.0 > -- > > Key: ATLAS-4677 > URL: https://issues.apache.org/jira/browse/ATLAS-4677 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 2.0.0, 3.0.0 > > > Current version for commons-configuration2 is 2.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4613) UI: After selecting checkboxes from Term page and then switching UI, page gets stuck in endless loading state.
[ https://issues.apache.org/jira/browse/ATLAS-4613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626497#comment-17626497 ] ASF subversion and git services commented on ATLAS-4613: Commit d821c879b3967a7980d43fc89e59e5ff4e23af6c in atlas's branch refs/heads/branch-2.0 from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d821c879b ] ATLAS-4693,ATLAS-4661,ATLAS-4613 : (UI)Switching within Terms page does not land you in the same tab Signed-off-by: Mandar Ambawane > UI: After selecting checkboxes from Term page and then switching UI, page > gets stuck in endless loading state. > -- > > Key: ATLAS-4613 > URL: https://issues.apache.org/jira/browse/ATLAS-4613 > Project: Atlas > Issue Type: Sub-task >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > > Steps: > # In classic UI, Create a term > # Assign a term to any entity > # Go to the term page > # Mark all the checkboxes > # Perform switch to new UI > You will notice that the page gets stuck in endless loading accompanied by an > error : "expected type AtlasGlossaryCategory; found AtlasGlossaryTerm". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4693) UI: Redundant basic search filters in Terms page and classification page on both UIs
[ https://issues.apache.org/jira/browse/ATLAS-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626495#comment-17626495 ] ASF subversion and git services commented on ATLAS-4693: Commit d821c879b3967a7980d43fc89e59e5ff4e23af6c in atlas's branch refs/heads/branch-2.0 from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d821c879b ] ATLAS-4693,ATLAS-4661,ATLAS-4613 : (UI)Switching within Terms page does not land you in the same tab Signed-off-by: Mandar Ambawane > UI: Redundant basic search filters in Terms page and classification page on > both UIs > > > Key: ATLAS-4693 > URL: https://issues.apache.org/jira/browse/ATLAS-4693 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > > 1. When you view the terms page on either UI, you can see that the 'Exclude > Sub-classifications' and 'Exclude sub-types' basic search filters are > present, which are redundant as you are searching by term. They should be > removed from the Terms page to avoid confusion. > 2. Classification page in new UI should have the "Exclude Sub-types" filter > removed so as to maintain consistency. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4661) UI: Switching within Terms page does not land you in the same tab.
[ https://issues.apache.org/jira/browse/ATLAS-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626496#comment-17626496 ] ASF subversion and git services commented on ATLAS-4661: Commit d821c879b3967a7980d43fc89e59e5ff4e23af6c in atlas's branch refs/heads/branch-2.0 from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d821c879b ] ATLAS-4693,ATLAS-4661,ATLAS-4613 : (UI)Switching within Terms page does not land you in the same tab Signed-off-by: Mandar Ambawane > UI: Switching within Terms page does not land you in the same tab. > -- > > Key: ATLAS-4661 > URL: https://issues.apache.org/jira/browse/ATLAS-4661 > Project: Atlas > Issue Type: Sub-task >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4693-ATLAS-4661-ATLAS-4613-UI-Switching-within.patch > > > There are 4 tabs in a Terms Page: Entities, Properties, Classifications and > Related Terms. When the user attempts to switch from any of these tabs to the > other UI, the user always lands on the Entities tab. > This is inconsistent with the behaviour in Entities Details page where on UI > switch the user lands in the corresponding tab within the target UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4661) UI: Switching within Terms page does not land you in the same tab.
[ https://issues.apache.org/jira/browse/ATLAS-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626492#comment-17626492 ] ASF subversion and git services commented on ATLAS-4661: Commit 3022242bb00b27c298c953d63256f237e15f3256 in atlas's branch refs/heads/master from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3022242bb ] ATLAS-4693,ATLAS-4661,ATLAS-4613 : (UI)Switching within Terms page does not land you in the same tab Signed-off-by: Mandar Ambawane > UI: Switching within Terms page does not land you in the same tab. > -- > > Key: ATLAS-4661 > URL: https://issues.apache.org/jira/browse/ATLAS-4661 > Project: Atlas > Issue Type: Sub-task >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4693-ATLAS-4661-ATLAS-4613-UI-Switching-within.patch > > > There are 4 tabs in a Terms Page: Entities, Properties, Classifications and > Related Terms. When the user attempts to switch from any of these tabs to the > other UI, the user always lands on the Entities tab. > This is inconsistent with the behaviour in Entities Details page where on UI > switch the user lands in the corresponding tab within the target UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4613) UI: After selecting checkboxes from Term page and then switching UI, page gets stuck in endless loading state.
[ https://issues.apache.org/jira/browse/ATLAS-4613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626493#comment-17626493 ] ASF subversion and git services commented on ATLAS-4613: Commit 3022242bb00b27c298c953d63256f237e15f3256 in atlas's branch refs/heads/master from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3022242bb ] ATLAS-4693,ATLAS-4661,ATLAS-4613 : (UI)Switching within Terms page does not land you in the same tab Signed-off-by: Mandar Ambawane > UI: After selecting checkboxes from Term page and then switching UI, page > gets stuck in endless loading state. > -- > > Key: ATLAS-4613 > URL: https://issues.apache.org/jira/browse/ATLAS-4613 > Project: Atlas > Issue Type: Sub-task >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > > Steps: > # In classic UI, Create a term > # Assign a term to any entity > # Go to the term page > # Mark all the checkboxes > # Perform switch to new UI > You will notice that the page gets stuck in endless loading accompanied by an > error : "expected type AtlasGlossaryCategory; found AtlasGlossaryTerm". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4693) UI: Redundant basic search filters in Terms page and classification page on both UIs
[ https://issues.apache.org/jira/browse/ATLAS-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626491#comment-17626491 ] ASF subversion and git services commented on ATLAS-4693: Commit 3022242bb00b27c298c953d63256f237e15f3256 in atlas's branch refs/heads/master from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3022242bb ] ATLAS-4693,ATLAS-4661,ATLAS-4613 : (UI)Switching within Terms page does not land you in the same tab Signed-off-by: Mandar Ambawane > UI: Redundant basic search filters in Terms page and classification page on > both UIs > > > Key: ATLAS-4693 > URL: https://issues.apache.org/jira/browse/ATLAS-4693 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > > 1. When you view the terms page on either UI, you can see that the 'Exclude > Sub-classifications' and 'Exclude sub-types' basic search filters are > present, which are redundant as you are searching by term. They should be > removed from the Terms page to avoid confusion. > 2. Classification page in new UI should have the "Exclude Sub-types" filter > removed so as to maintain consistency. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4689) UI: Basic Search: Invalid attributes passed in request
[ https://issues.apache.org/jira/browse/ATLAS-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17624940#comment-17624940 ] ASF subversion and git services commented on ATLAS-4689: Commit af6b54d1c4b08e24ba0f9e3d63731428d82e10b7 in atlas's branch refs/heads/branch-2.0 from Prasad Pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=af6b54d1c ] ATLAS-4689:UI: Basic Search: Invalid attributes passed in request Signed-off-by: Prasad Pawar > UI: Basic Search: Invalid attributes passed in request > --- > > Key: ATLAS-4689 > URL: https://issues.apache.org/jira/browse/ATLAS-4689 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Pinal Shah >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4689-UI-Basic-Search-Invalid-attributes-passed.patch > > > Steps to Reproduce: > Basic Search: > # Search with typeName hive_db, attribute filter clusterName. > # Search with typeName hive_table > The request sent will have the 'clusterName' in 'attributes' field. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4689) UI: Basic Search: Invalid attributes passed in request
[ https://issues.apache.org/jira/browse/ATLAS-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17624938#comment-17624938 ] ASF subversion and git services commented on ATLAS-4689: Commit 5a55dbdf1c9d306ef4b1c0e6d8e846eb1a688bad in atlas's branch refs/heads/master from Prasad Pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5a55dbdf1 ] ATLAS-4689:UI: Basic Search: Invalid attributes passed in request Signed-off-by: Prasad Pawar > UI: Basic Search: Invalid attributes passed in request > --- > > Key: ATLAS-4689 > URL: https://issues.apache.org/jira/browse/ATLAS-4689 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Pinal Shah >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4689-UI-Basic-Search-Invalid-attributes-passed.patch > > > Steps to Reproduce: > Basic Search: > # Search with typeName hive_db, attribute filter clusterName. > # Search with typeName hive_table > The request sent will have the 'clusterName' in 'attributes' field. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4691) Discrepancy in the atlas debug metrics between the active and the not active servers
[ https://issues.apache.org/jira/browse/ATLAS-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623277#comment-17623277 ] ASF subversion and git services commented on ATLAS-4691: Commit faf9da84bbf55cf46bce275ad1488333d71629cb in atlas's branch refs/heads/branch-2.0 from Jayendra Parab [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=faf9da84b ] ATLAS-4691: Discrepancy in the atlas debug metrics between the active and the not active servers Signed-off-by: Pinal Shah (cherry picked from commit 1c7e59478c8d2905f732c1d87da5e8fd940637b8) > Discrepancy in the atlas debug metrics between the active and the not active > servers > > > Key: ATLAS-4691 > URL: https://issues.apache.org/jira/browse/ATLAS-4691 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.2.0 >Reporter: Jayendra Parab >Assignee: Jayendra Parab >Priority: Major > > There is a discrepancy in the atlas debug metrics between the active and the > not active servers. > Steps to reproduce: > - Setup Atlas in HA mode with two instances of Atlas > - add "atlas.debug.metrics.enabled=true" to the Atlas configuration > (conf/atlas-application.properties) > - restart Atlas > - open Atlas and create a new entity (e.g. hdfs_path) > - check the debug metrics on both atlas instances using API call: > https://:/api/atlas/admin/debug/metrics > - The active instance returns correct metrics, whereas passive instance > returns empty metrics > The reason for this is that the debug metrics are maintained in-memory in the > active server. When "admin/debug/metrics" API call is accessed on the passive > server, the request isn't redirected to the active server like it does for > the other APIs, hence the passive node returns empty metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4691) Discrepancy in the atlas debug metrics between the active and the not active servers
[ https://issues.apache.org/jira/browse/ATLAS-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623276#comment-17623276 ] ASF subversion and git services commented on ATLAS-4691: Commit 1c7e59478c8d2905f732c1d87da5e8fd940637b8 in atlas's branch refs/heads/master from Jayendra Parab [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1c7e59478 ] ATLAS-4691: Discrepancy in the atlas debug metrics between the active and the not active servers Signed-off-by: Pinal Shah > Discrepancy in the atlas debug metrics between the active and the not active > servers > > > Key: ATLAS-4691 > URL: https://issues.apache.org/jira/browse/ATLAS-4691 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.2.0 >Reporter: Jayendra Parab >Assignee: Jayendra Parab >Priority: Major > > There is a discrepancy in the atlas debug metrics between the active and the > not active servers. > Steps to reproduce: > - Setup Atlas in HA mode with two instances of Atlas > - add "atlas.debug.metrics.enabled=true" to the Atlas configuration > (conf/atlas-application.properties) > - restart Atlas > - open Atlas and create a new entity (e.g. hdfs_path) > - check the debug metrics on both atlas instances using API call: > https://:/api/atlas/admin/debug/metrics > - The active instance returns correct metrics, whereas passive instance > returns empty metrics > The reason for this is that the debug metrics are maintained in-memory in the > active server. When "admin/debug/metrics" API call is accessed on the passive > server, the request isn't redirected to the active server like it does for > the other APIs, hence the passive node returns empty metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4655) Add Glossary details in Entity - Basic search, DSL search, Entity details and Related terms
[ https://issues.apache.org/jira/browse/ATLAS-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17621223#comment-17621223 ] ASF subversion and git services commented on ATLAS-4655: Commit c7f07ba8ec150bcecb8f3485d11eaa8a99d86bcb in atlas's branch refs/heads/branch-2.0 from Prasad Pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=c7f07ba8e ] ATLAS-4610: ATLAS-4655: Classification/ Term: Add parent name for classification & name Signed-off-by: Pinal Shah (cherry picked from commit f2293acf0d1ea720de17c345b518d64f324ba1f6) > Add Glossary details in Entity - Basic search, DSL search, Entity details and > Related terms > --- > > Key: ATLAS-4655 > URL: https://issues.apache.org/jira/browse/ATLAS-4655 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Sheetal Shah >Priority: Major > Attachments: ATLAS-4610_ATLAS-4655.diff > > > To show DSL and Basic search pages: > AtlasTermAssignmentHeader modified to include qualifiedName for associated > term(s) > To show glossary details on entity search page : > AtlasRelatedObjectId modified to include qualifiedName for associated term(s) > To show glossary details for related terms: > AtlasRelatedTermHeader modified to include qualifiedName for associated > term(s) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4610) ATLAS UI : Classification/ Term: Add parent name for classification & name
[ https://issues.apache.org/jira/browse/ATLAS-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17621222#comment-17621222 ] ASF subversion and git services commented on ATLAS-4610: Commit c7f07ba8ec150bcecb8f3485d11eaa8a99d86bcb in atlas's branch refs/heads/branch-2.0 from Prasad Pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=c7f07ba8e ] ATLAS-4610: ATLAS-4655: Classification/ Term: Add parent name for classification & name Signed-off-by: Pinal Shah (cherry picked from commit f2293acf0d1ea720de17c345b518d64f324ba1f6) > ATLAS UI : Classification/ Term: Add parent name for classification & name > --- > > Key: ATLAS-4610 > URL: https://issues.apache.org/jira/browse/ATLAS-4610 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4610-ATLAS-4655-Classification-Term-Add-parent.patch, > ATLAS-4610_ATLAS-4655.patch > > > The classification and term assignment section should display their parents > if present, on the detail page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4610) ATLAS UI : Classification/ Term: Add parent name for classification & name
[ https://issues.apache.org/jira/browse/ATLAS-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17621218#comment-17621218 ] ASF subversion and git services commented on ATLAS-4610: Commit f2293acf0d1ea720de17c345b518d64f324ba1f6 in atlas's branch refs/heads/master from Prasad Pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f2293acf0 ] ATLAS-4610: ATLAS-4655: Classification/ Term: Add parent name for classification & name Signed-off-by: Pinal Shah > ATLAS UI : Classification/ Term: Add parent name for classification & name > --- > > Key: ATLAS-4610 > URL: https://issues.apache.org/jira/browse/ATLAS-4610 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4610-ATLAS-4655-Classification-Term-Add-parent.patch, > ATLAS-4610_ATLAS-4655.patch > > > The classification and term assignment section should display their parents > if present, on the detail page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4655) Add Glossary details in Entity - Basic search, DSL search, Entity details and Related terms
[ https://issues.apache.org/jira/browse/ATLAS-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17621219#comment-17621219 ] ASF subversion and git services commented on ATLAS-4655: Commit f2293acf0d1ea720de17c345b518d64f324ba1f6 in atlas's branch refs/heads/master from Prasad Pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f2293acf0 ] ATLAS-4610: ATLAS-4655: Classification/ Term: Add parent name for classification & name Signed-off-by: Pinal Shah > Add Glossary details in Entity - Basic search, DSL search, Entity details and > Related terms > --- > > Key: ATLAS-4655 > URL: https://issues.apache.org/jira/browse/ATLAS-4655 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Sheetal Shah >Priority: Major > Attachments: ATLAS-4610_ATLAS-4655.diff > > > To show DSL and Basic search pages: > AtlasTermAssignmentHeader modified to include qualifiedName for associated > term(s) > To show glossary details on entity search page : > AtlasRelatedObjectId modified to include qualifiedName for associated term(s) > To show glossary details for related terms: > AtlasRelatedTermHeader modified to include qualifiedName for associated > term(s) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4677) Atlas - Upgrade commons-configuration to 2.8.0
[ https://issues.apache.org/jira/browse/ATLAS-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620852#comment-17620852 ] ASF subversion and git services commented on ATLAS-4677: Commit fe930d70130f3ac4cbdcdfd2fcbad575d33e818b in atlas's branch refs/heads/branch-2.0 from prasad.pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=fe930d701 ] ATLAS-4677 : Upgrade commons-configuration to 2.8.0 Signed-off-by: Pinal Shah (cherry picked from commit e98c398e622fa0d3bc57cb48ef77295d04b120b4) > Atlas - Upgrade commons-configuration to 2.8.0 > -- > > Key: ATLAS-4677 > URL: https://issues.apache.org/jira/browse/ATLAS-4677 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 2.0.0, 3.0.0 > > > Current version for commons-configuration2 is 2.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4677) Atlas - Upgrade commons-configuration to 2.8.0
[ https://issues.apache.org/jira/browse/ATLAS-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620850#comment-17620850 ] ASF subversion and git services commented on ATLAS-4677: Commit e98c398e622fa0d3bc57cb48ef77295d04b120b4 in atlas's branch refs/heads/master from prasad.pawar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e98c398e6 ] ATLAS-4677 : Upgrade commons-configuration to 2.8.0 Signed-off-by: Pinal Shah > Atlas - Upgrade commons-configuration to 2.8.0 > -- > > Key: ATLAS-4677 > URL: https://issues.apache.org/jira/browse/ATLAS-4677 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 2.0.0, 3.0.0 > > > Current version for commons-configuration2 is 2.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4686) UI improvements to support Atlas Relationship Search
[ https://issues.apache.org/jira/browse/ATLAS-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620729#comment-17620729 ] ASF subversion and git services commented on ATLAS-4686: Commit 88b2815b67259fa6765ceec38353cb8cc099b09a in atlas's branch refs/heads/branch-2.0 from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=88b2815b6 ] ATLAS-4686 : UI improvements to support Atlas Relationship Search Signed-off-by: Pinal Shah (cherry picked from commit cb0bde41d5b7a33e83d47e9f53aa24d53dd9a803) > UI improvements to support Atlas Relationship Search > > > Key: ATLAS-4686 > URL: https://issues.apache.org/jira/browse/ATLAS-4686 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0, 2.3.0 >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4686-UI-improvements-to-support-Atlas-Relation.patch > > > *Current Working :* > Atlas is entirely entity-based – it is not possible to search for > relationships. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4686) UI improvements to support Atlas Relationship Search
[ https://issues.apache.org/jira/browse/ATLAS-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620728#comment-17620728 ] ASF subversion and git services commented on ATLAS-4686: Commit cb0bde41d5b7a33e83d47e9f53aa24d53dd9a803 in atlas's branch refs/heads/master from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=cb0bde41d ] ATLAS-4686 : UI improvements to support Atlas Relationship Search Signed-off-by: Pinal Shah > UI improvements to support Atlas Relationship Search > > > Key: ATLAS-4686 > URL: https://issues.apache.org/jira/browse/ATLAS-4686 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0, 2.3.0 >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4686-UI-improvements-to-support-Atlas-Relation.patch > > > *Current Working :* > Atlas is entirely entity-based – it is not possible to search for > relationships. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4666) Intermittently, the audits for creation of hive_db registered are different than expected.
[ https://issues.apache.org/jira/browse/ATLAS-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620112#comment-17620112 ] ASF subversion and git services commented on ATLAS-4666: Commit 28186992318e996341cf516daefa652df1abd1cb in atlas's branch refs/heads/branch-2.0 from Mandar Ambawane [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=281869923 ] ATLAS-4666 : Intermittently, the audits for creation of hive_db registered are different than expected Signed-off-by: Pinal Shah (cherry picked from commit a5eb426263632034513ba7013913b57875ec7c5f) > Intermittently, the audits for creation of hive_db registered are different > than expected. > -- > > Key: ATLAS-4666 > URL: https://issues.apache.org/jira/browse/ATLAS-4666 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Mandar Ambawane >Priority: Major > > Sometimes, when I create a hive database and then check for the same in > Atlas, the audits tab shows unexpected audit entries: it shows two audit > entries both marked as 'Entity Updated' rather than showing a 'Entity > Created' audit entry anywhere. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4666) Intermittently, the audits for creation of hive_db registered are different than expected.
[ https://issues.apache.org/jira/browse/ATLAS-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620109#comment-17620109 ] ASF subversion and git services commented on ATLAS-4666: Commit a5eb426263632034513ba7013913b57875ec7c5f in atlas's branch refs/heads/master from Mandar Ambawane [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=a5eb42626 ] ATLAS-4666 : Intermittently, the audits for creation of hive_db registered are different than expected Signed-off-by: Pinal Shah > Intermittently, the audits for creation of hive_db registered are different > than expected. > -- > > Key: ATLAS-4666 > URL: https://issues.apache.org/jira/browse/ATLAS-4666 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Mandar Ambawane >Priority: Major > > Sometimes, when I create a hive database and then check for the same in > Atlas, the audits tab shows unexpected audit entries: it shows two audit > entries both marked as 'Entity Updated' rather than showing a 'Entity > Created' audit entry anywhere. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4674) Regression: Classification tagging is not sending appropriate notification to ATLAS_ENTITIES
[
https://issues.apache.org/jira/browse/ATLAS-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620002#comment-17620002
]
ASF subversion and git services commented on ATLAS-4674:
Commit dbc3302ef3bcbf3b90aef156f99348d9de70c897 in atlas's branch
refs/heads/branch-2.0 from Disha Talreja
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=dbc3302ef ]
ATLAS-4674 - Regression: Classification tagging is not sending appropriate
notification to ATLAS_ENTITIES
Signed-off-by: radhikakundam
> Regression: Classification tagging is not sending appropriate notification to
> ATLAS_ENTITIES
>
>
> Key: ATLAS-4674
> URL: https://issues.apache.org/jira/browse/ATLAS-4674
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Disha Talreja
>Assignee: Disha Talreja
>Priority: Major
> Attachments: ATLAS-4674.patch
>
>
> When we add/delete a classification from an entity, we send notification to
> ATLAS_ENTITIES so ranger tag sync works appropriately to facilitate Tag-based
> policy. This functionally seems to be broken and is a regression.
> On further investigation, it is seen that the issue is caused by deferred
> action for classification propagation as the right notifications are sent
> when deferred action is disabled.
> Considering the following example:
> 1. Create two table as shown below at Hive:
> =
> create table parent_table(ssn varchar(100));
> create table child_table as select * from parent_table;
> 2. Created two classification: "PII" and "sensitive"
>
> 3. Tagged PII to parent_table and notification received at ATLAS_ENTITIES
> topic:
> ---
> {code:java}
> {
> "source": {},
> "version":
> { "version": "1.0.0", "versionParts": [ 1 ] }
> ,
> "msgCompressionKind": "NONE",
> "msgSplitIdx": 1,
> "msgSplitCount": 1,
> "msgSourceIP": "172.27.40.5",
> "msgCreatedBy": "",
> "msgCreationTime": 1662660308744,
> "spooled": false,
> "message": {
> "type": "ENTITY_NOTIFICATION_V2",
> "entity": {
> "typeName": "hive_table",
> "attributes":
> { "owner": "admin", "createTime": 1662602695000,
> "qualifiedName": "default.parent_table@cm", "name": "parent_table"
> }
> ,
> "guid": "04ff79d7-b1ff-4354-ba75-a35b28d2f53f",
> "status": "ACTIVE",
> "displayText": "parent_table",
> "classificationNames": [
> "PII" ],
> "classifications": [
>
> { "typeName": "PII", "entityGuid":
> "04ff79d7-b1ff-4354-ba75-a35b28d2f53f", "entityStatus": "ACTIVE",
> "propagate": true, "validityPeriods": [],
> "removePropagationsOnEntityDelete": false }
> ],
> "isIncomplete": false },
> "operationType": "CLASSIFICATION_ADD",
> "eventTime": 1662660307360
> }
> }
> {
> "source": {},
> "version":
> { "version": "1.0.0", "versionParts": [ 1 ] }
> ,
> "msgCompressionKind": "NONE",
> "msgSplitIdx": 1,
> "msgSplitCount": 1,
> "msgSourceIP": "172.27.40.5",
> "msgCreatedBy": "",
> "msgCreationTime": 1662660309419,
> "spooled": false,
> "message": {
> "type": "ENTITY_NOTIFICATION_V2",
> "entity": {
> "typeName": "hive_process",
> "attributes":
> { "qualifiedName": "default.child_table@cm:1662602726000",
> "clusterName": "cm", "name": "default.child_table@cm:1662602726000"
> }
> ,
> "guid": "0e180d04-79ed-4cab-bbc3-76af4b876a5b",
> "status": "ACTIVE",
> "displayText": "default.child_table@cm:1662602726000",
> "classificationNames": [
> "PII" ],
> "classifications": [
>
> { "typeName": "PII", "entityGuid":
> "04ff79d7-b1ff-4354-ba75-a35b28d2f53f", "entityStatus": "ACTIVE",
> "propagate": true, "validityPeriods": [],
> "removePropagationsOnEntityDelete": false }
> ],
> "isIncomplete": false },
> "operationType": "CLASSIFICATION_ADD",
> "eventTime": 1662660308935
> }
> }
> {
> "source": {},
> "version":
> { "version": "1.0.0", "versionParts": [ 1 ] }
> ,
> "msgCompressionKind": "NONE",
> "msgSplitIdx": 1,
> "msgSplitCount": 1,
> "msgSourceIP": "172.27.40.5",
> "msgCreatedBy": "",
> "msgCreationTime": 1662660309419,
> "spooled": false,
> "message": {
> "type": "ENTITY_NOTIFICATION_V2",
> "entity": {
> "typeName": "hive_table",
> "attributes":
> { "owner": "adm
[jira] [Commented] (ATLAS-4674) Regression: Classification tagging is not sending appropriate notification to ATLAS_ENTITIES
[
https://issues.apache.org/jira/browse/ATLAS-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620001#comment-17620001
]
ASF subversion and git services commented on ATLAS-4674:
Commit 17c78bac3bfd9c8e7c12548b044b9d747704a973 in atlas's branch
refs/heads/master from Disha Talreja
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=17c78bac3 ]
ATLAS-4674 - Regression: Classification tagging is not sending appropriate
notification to ATLAS_ENTITIES
Signed-off-by: radhikakundam
> Regression: Classification tagging is not sending appropriate notification to
> ATLAS_ENTITIES
>
>
> Key: ATLAS-4674
> URL: https://issues.apache.org/jira/browse/ATLAS-4674
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Disha Talreja
>Assignee: Disha Talreja
>Priority: Major
> Attachments: ATLAS-4674.patch
>
>
> When we add/delete a classification from an entity, we send notification to
> ATLAS_ENTITIES so ranger tag sync works appropriately to facilitate Tag-based
> policy. This functionally seems to be broken and is a regression.
> On further investigation, it is seen that the issue is caused by deferred
> action for classification propagation as the right notifications are sent
> when deferred action is disabled.
> Considering the following example:
> 1. Create two table as shown below at Hive:
> =
> create table parent_table(ssn varchar(100));
> create table child_table as select * from parent_table;
> 2. Created two classification: "PII" and "sensitive"
>
> 3. Tagged PII to parent_table and notification received at ATLAS_ENTITIES
> topic:
> ---
> {code:java}
> {
> "source": {},
> "version":
> { "version": "1.0.0", "versionParts": [ 1 ] }
> ,
> "msgCompressionKind": "NONE",
> "msgSplitIdx": 1,
> "msgSplitCount": 1,
> "msgSourceIP": "172.27.40.5",
> "msgCreatedBy": "",
> "msgCreationTime": 1662660308744,
> "spooled": false,
> "message": {
> "type": "ENTITY_NOTIFICATION_V2",
> "entity": {
> "typeName": "hive_table",
> "attributes":
> { "owner": "admin", "createTime": 1662602695000,
> "qualifiedName": "default.parent_table@cm", "name": "parent_table"
> }
> ,
> "guid": "04ff79d7-b1ff-4354-ba75-a35b28d2f53f",
> "status": "ACTIVE",
> "displayText": "parent_table",
> "classificationNames": [
> "PII" ],
> "classifications": [
>
> { "typeName": "PII", "entityGuid":
> "04ff79d7-b1ff-4354-ba75-a35b28d2f53f", "entityStatus": "ACTIVE",
> "propagate": true, "validityPeriods": [],
> "removePropagationsOnEntityDelete": false }
> ],
> "isIncomplete": false },
> "operationType": "CLASSIFICATION_ADD",
> "eventTime": 1662660307360
> }
> }
> {
> "source": {},
> "version":
> { "version": "1.0.0", "versionParts": [ 1 ] }
> ,
> "msgCompressionKind": "NONE",
> "msgSplitIdx": 1,
> "msgSplitCount": 1,
> "msgSourceIP": "172.27.40.5",
> "msgCreatedBy": "",
> "msgCreationTime": 1662660309419,
> "spooled": false,
> "message": {
> "type": "ENTITY_NOTIFICATION_V2",
> "entity": {
> "typeName": "hive_process",
> "attributes":
> { "qualifiedName": "default.child_table@cm:1662602726000",
> "clusterName": "cm", "name": "default.child_table@cm:1662602726000"
> }
> ,
> "guid": "0e180d04-79ed-4cab-bbc3-76af4b876a5b",
> "status": "ACTIVE",
> "displayText": "default.child_table@cm:1662602726000",
> "classificationNames": [
> "PII" ],
> "classifications": [
>
> { "typeName": "PII", "entityGuid":
> "04ff79d7-b1ff-4354-ba75-a35b28d2f53f", "entityStatus": "ACTIVE",
> "propagate": true, "validityPeriods": [],
> "removePropagationsOnEntityDelete": false }
> ],
> "isIncomplete": false },
> "operationType": "CLASSIFICATION_ADD",
> "eventTime": 1662660308935
> }
> }
> {
> "source": {},
> "version":
> { "version": "1.0.0", "versionParts": [ 1 ] }
> ,
> "msgCompressionKind": "NONE",
> "msgSplitIdx": 1,
> "msgSplitCount": 1,
> "msgSourceIP": "172.27.40.5",
> "msgCreatedBy": "",
> "msgCreationTime": 1662660309419,
> "spooled": false,
> "message": {
> "type": "ENTITY_NOTIFICATION_V2",
> "entity": {
> "typeName": "hive_table",
> "attributes":
> { "owner": "admin",
[jira] [Commented] (ATLAS-4681) Relationship Search : SortBy is not working
[ https://issues.apache.org/jira/browse/ATLAS-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618426#comment-17618426 ] ASF subversion and git services commented on ATLAS-4681: Commit 36fd6c52cc88092630373eb909240cfdbc831cba in atlas's branch refs/heads/branch-2.0 from Pinal Shah [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=36fd6c52c ] ATLAS-4681: Relationship Search : SortBy is not working Signed-off-by: Pinal Shah (cherry picked from commit 66ed196766ddfbca745acfe044118d4174d57206) > Relationship Search : SortBy is not working > --- > > Key: ATLAS-4681 > URL: https://issues.apache.org/jira/browse/ATLAS-4681 > Project: Atlas > Issue Type: Bug >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > > Currently Relationship Search supports filtering results. There is a sortBy > and sortOrder param that is supposed to sort according to the arguments > provided. > However currently it is return a random order of results even though the > filter is applied. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4681) Relationship Search : SortBy is not working
[ https://issues.apache.org/jira/browse/ATLAS-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618424#comment-17618424 ] ASF subversion and git services commented on ATLAS-4681: Commit 66ed196766ddfbca745acfe044118d4174d57206 in atlas's branch refs/heads/master from Pinal Shah [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=66ed19676 ] ATLAS-4681: Relationship Search : SortBy is not working Signed-off-by: Pinal Shah > Relationship Search : SortBy is not working > --- > > Key: ATLAS-4681 > URL: https://issues.apache.org/jira/browse/ATLAS-4681 > Project: Atlas > Issue Type: Bug >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > > Currently Relationship Search supports filtering results. There is a sortBy > and sortOrder param that is supposed to sort according to the arguments > provided. > However currently it is return a random order of results even though the > filter is applied. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4688) Atlas - Upgrade Snake-yaml to 1.32
[ https://issues.apache.org/jira/browse/ATLAS-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616904#comment-17616904 ] ASF subversion and git services commented on ATLAS-4688: Commit f58fa0e84fa6976131ccf74b3225769518a9c83d in atlas's branch refs/heads/branch-2.0 from chaitali.borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f58fa0e84 ] ATLAS-4688 : Upgrade Snake-yaml to 1.32 Signed-off-by: Pinal Shah (cherry picked from commit c232484a52d32deea1e8ce3f659e9c7d2dc36256) > Atlas - Upgrade Snake-yaml to 1.32 > -- > > Key: ATLAS-4688 > URL: https://issues.apache.org/jira/browse/ATLAS-4688 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Currently Snake-yaml uses 1.26 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4688) Atlas - Upgrade Snake-yaml to 1.32
[ https://issues.apache.org/jira/browse/ATLAS-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616902#comment-17616902 ] ASF subversion and git services commented on ATLAS-4688: Commit da257fd133efa7b930e9bede002bbcdaead56b1e in atlas's branch refs/heads/master from chaitali.borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=da257fd13 ] ATLAS-4688 : Upgrade Snake-yaml to 1.32 Signed-off-by: Pinal Shah > Atlas - Upgrade Snake-yaml to 1.32 > -- > > Key: ATLAS-4688 > URL: https://issues.apache.org/jira/browse/ATLAS-4688 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Currently Snake-yaml uses 1.26 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4685) Advanced Search : Not Equals operator doesn't work for String type
[ https://issues.apache.org/jira/browse/ATLAS-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616901#comment-17616901 ] ASF subversion and git services commented on ATLAS-4685: Commit 876a4da3a2ca4e452b121a2baa6ff13cb5d29a89 in atlas's branch refs/heads/branch-2.0 from Pinal Shah [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=876a4da3a ] ATLAS-4685: Advanced Search : Not Equals operator doesn't work for String type Signed-off-by: Pinal Shah (cherry picked from commit 392f8b4a38bcb18a684f21127594afa74e10ee47) > Advanced Search : Not Equals operator doesn't work for String type > -- > > Key: ATLAS-4685 > URL: https://issues.apache.org/jira/browse/ATLAS-4685 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > > from hive_table where name != 'authors' select name, owner > If use the "!=" operator in where clause, it is not working as expected and > it still returns the row which has the value 'authors' -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4685) Advanced Search : Not Equals operator doesn't work for String type
[ https://issues.apache.org/jira/browse/ATLAS-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616899#comment-17616899 ] ASF subversion and git services commented on ATLAS-4685: Commit 392f8b4a38bcb18a684f21127594afa74e10ee47 in atlas's branch refs/heads/master from Pinal Shah [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=392f8b4a3 ] ATLAS-4685: Advanced Search : Not Equals operator doesn't work for String type Signed-off-by: Pinal Shah > Advanced Search : Not Equals operator doesn't work for String type > -- > > Key: ATLAS-4685 > URL: https://issues.apache.org/jira/browse/ATLAS-4685 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > > from hive_table where name != 'authors' select name, owner > If use the "!=" operator in where clause, it is not working as expected and > it still returns the row which has the value 'authors' -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4442) Support Relationship search
[
https://issues.apache.org/jira/browse/ATLAS-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615755#comment-17615755
]
ASF subversion and git services commented on ATLAS-4442:
Commit 9fb5467089d08bff16d3a3031178ade93b3a1852 in atlas's branch
refs/heads/branch-2.0 from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9fb546708 ]
ATLAS-4442: Support Relationship search
Signed-off-by: Pinal Shah
(cherry picked from commit 9e6fc31ce8450f784515e57c7df3d7fa57f216de)
> Support Relationship search
> ---
>
> Key: ATLAS-4442
> URL: https://issues.apache.org/jira/browse/ATLAS-4442
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
>
> *Current Working :*
> Atlas is entirely entity-based – it is not possible to search for
> relationships.
> *Improvement :*
> Get all relationships (edges) for particular relationship type, having some
> criteria on its properties
> *Example :*
> Get all the relations matching
> {code:java}
> type = rel_type and edge_property1 = edge_value1
> {code}
> *Request Payload :*
> {"relationshipName" : "rel_type",
> "relationshipFilters": { "condition": "OR", "criterion": [
> { "attributeName": "{{edge_property1}}", "operator": "eq",
> "attributeValue": "{{edge_value1}}" }
> ] },
> "limit":25,
> "offset":0 }
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4442) Support Relationship search
[
https://issues.apache.org/jira/browse/ATLAS-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615754#comment-17615754
]
ASF subversion and git services commented on ATLAS-4442:
Commit 9e6fc31ce8450f784515e57c7df3d7fa57f216de in atlas's branch
refs/heads/master from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9e6fc31ce ]
ATLAS-4442: Support Relationship search
Signed-off-by: Pinal Shah
> Support Relationship search
> ---
>
> Key: ATLAS-4442
> URL: https://issues.apache.org/jira/browse/ATLAS-4442
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
>
> *Current Working :*
> Atlas is entirely entity-based – it is not possible to search for
> relationships.
> *Improvement :*
> Get all relationships (edges) for particular relationship type, having some
> criteria on its properties
> *Example :*
> Get all the relations matching
> {code:java}
> type = rel_type and edge_property1 = edge_value1
> {code}
> *Request Payload :*
> {"relationshipName" : "rel_type",
> "relationshipFilters": { "condition": "OR", "criterion": [
> { "attributeName": "{{edge_property1}}", "operator": "eq",
> "attributeValue": "{{edge_value1}}" }
> ] },
> "limit":25,
> "offset":0 }
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4668) When classification is created with multiple super types having same attributes , Atlas doesn't throw an exception
[ https://issues.apache.org/jira/browse/ATLAS-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615479#comment-17615479 ] ASF subversion and git services commented on ATLAS-4668: Commit 06dca95849f72d31c85eb9a517f08f9336e3a74e in atlas's branch refs/heads/branch-2.0 from Mandar Ambawane [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=06dca9584 ] ATLAS-4668 : When classification is created with multiple super types having same attributes , Atlas doesn't throw an exception Signed-off-by: Pinal Shah (cherry picked from commit 956f1728bab8b8224554cb76a8810e2f3816662f) > When classification is created with multiple super types having same > attributes , Atlas doesn't throw an exception > -- > > Key: ATLAS-4668 > URL: https://issues.apache.org/jira/browse/ATLAS-4668 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > Attachments: ATLAS-4668.patch > > > When an entity type is created with multiple super types having same > attribute name, Atlas throws exception. > Ex: > if there are 2 types: > type1 - attr1, attr2 > type2- attr1, attr2 > Both types cant be added to super type to type3 since both type1 and type2 > have same attribute - attr1 > > But it is not the case with classification. Atlas allows to create a > classification with multiple super types having same attribute. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4668) When classification is created with multiple super types having same attributes , Atlas doesn't throw an exception
[ https://issues.apache.org/jira/browse/ATLAS-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615478#comment-17615478 ] ASF subversion and git services commented on ATLAS-4668: Commit 956f1728bab8b8224554cb76a8810e2f3816662f in atlas's branch refs/heads/master from Mandar Ambawane [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=956f1728b ] ATLAS-4668 : When classification is created with multiple super types having same attributes , Atlas doesn't throw an exception Signed-off-by: Pinal Shah > When classification is created with multiple super types having same > attributes , Atlas doesn't throw an exception > -- > > Key: ATLAS-4668 > URL: https://issues.apache.org/jira/browse/ATLAS-4668 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > Attachments: ATLAS-4668.patch > > > When an entity type is created with multiple super types having same > attribute name, Atlas throws exception. > Ex: > if there are 2 types: > type1 - attr1, attr2 > type2- attr1, attr2 > Both types cant be added to super type to type3 since both type1 and type2 > have same attribute - attr1 > > But it is not the case with classification. Atlas allows to create a > classification with multiple super types having same attribute. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4678) Restrict Relationship Typedef creation if "relationshipCategory" value is not provided
[ https://issues.apache.org/jira/browse/ATLAS-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615476#comment-17615476 ] ASF subversion and git services commented on ATLAS-4678: Commit 9ad4120371545d9281c3fd0a4a8b78a2b54e490b in atlas's branch refs/heads/branch-2.0 from Mandar Ambawane [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9ad412037 ] ATLAS-4678 : Restrict Relationship Typedef creation if relationshipCategory value is not provided Signed-off-by: Pinal Shah (cherry picked from commit d2f8933843ebdb64f29d13212065e71a6d3df6cd) > Restrict Relationship Typedef creation if "relationshipCategory" value is not > provided > -- > > Key: ATLAS-4678 > URL: https://issues.apache.org/jira/browse/ATLAS-4678 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4678) Restrict Relationship Typedef creation if "relationshipCategory" value is not provided
[ https://issues.apache.org/jira/browse/ATLAS-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615474#comment-17615474 ] ASF subversion and git services commented on ATLAS-4678: Commit d2f8933843ebdb64f29d13212065e71a6d3df6cd in atlas's branch refs/heads/master from Mandar Ambawane [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d2f893384 ] ATLAS-4678 : Restrict Relationship Typedef creation if relationshipCategory value is not provided Signed-off-by: Pinal Shah > Restrict Relationship Typedef creation if "relationshipCategory" value is not > provided > -- > > Key: ATLAS-4678 > URL: https://issues.apache.org/jira/browse/ATLAS-4678 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Mandar Ambawane >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4684) UI dependent components version update
[ https://issues.apache.org/jira/browse/ATLAS-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17614910#comment-17614910 ] ASF subversion and git services commented on ATLAS-4684: Commit 25329ef10c7a373917636bc07fab9957edc25e9a in atlas's branch refs/heads/master from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=25329ef10 ] ATLAS-4684: UI dependent components version update > UI dependent components version update > -- > > Key: ATLAS-4684 > URL: https://issues.apache.org/jira/browse/ATLAS-4684 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: ATLAS-4684.patch > > > This Jira is to track following pull requests containing updates to UI > component versions: > * [https://github.com/apache/atlas/pull/162] > * [https://github.com/apache/atlas/pull/164] > * [https://github.com/apache/atlas/pull/165] > * [https://github.com/apache/atlas/pull/166] > * [https://github.com/apache/atlas/pull/167] > * [https://github.com/apache/atlas/pull/168] > * [https://github.com/apache/atlas/pull/179] > * [https://github.com/apache/atlas/pull/180] > * [https://github.com/apache/atlas/pull/186] > * [https://github.com/apache/atlas/pull/188] > * [https://github.com/apache/atlas/pull/189] > * [https://github.com/apache/atlas/pull/190] > * [https://github.com/apache/atlas/pull/191] > * [https://github.com/apache/atlas/pull/194] > * https://github.com/apache/atlas/pull/195 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4684) UI dependent components version update
[ https://issues.apache.org/jira/browse/ATLAS-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17614912#comment-17614912 ] ASF subversion and git services commented on ATLAS-4684: Commit 400f732702f65a7fc6562984c4ee7de174acbbdf in atlas's branch refs/heads/branch-2.0 from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=400f73270 ] ATLAS-4684: UI dependent components version update (cherry picked from commit 25329ef10c7a373917636bc07fab9957edc25e9a) > UI dependent components version update > -- > > Key: ATLAS-4684 > URL: https://issues.apache.org/jira/browse/ATLAS-4684 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: ATLAS-4684.patch > > > This Jira is to track following pull requests containing updates to UI > component versions: > * [https://github.com/apache/atlas/pull/162] > * [https://github.com/apache/atlas/pull/164] > * [https://github.com/apache/atlas/pull/165] > * [https://github.com/apache/atlas/pull/166] > * [https://github.com/apache/atlas/pull/167] > * [https://github.com/apache/atlas/pull/168] > * [https://github.com/apache/atlas/pull/179] > * [https://github.com/apache/atlas/pull/180] > * [https://github.com/apache/atlas/pull/186] > * [https://github.com/apache/atlas/pull/188] > * [https://github.com/apache/atlas/pull/189] > * [https://github.com/apache/atlas/pull/190] > * [https://github.com/apache/atlas/pull/191] > * [https://github.com/apache/atlas/pull/194] > * https://github.com/apache/atlas/pull/195 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4652) Missing null check leading to NPE in isSoftReferenced method in AtlasStructDef
[
https://issues.apache.org/jira/browse/ATLAS-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17613364#comment-17613364
]
ASF subversion and git services commented on ATLAS-4652:
Commit 596a0af385459770aff330053ac2154dd1763496 in atlas's branch
refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=596a0af38 ]
ATLAS-4652: fix to address potential NPE in AtlasAttributeDef.isSoftReferenced()
(cherry picked from commit 43daa256dd04a2e9167de6749f34e262b8216de3)
> Missing null check leading to NPE in isSoftReferenced method in
> AtlasStructDef
> ---
>
> Key: ATLAS-4652
> URL: https://issues.apache.org/jira/browse/ATLAS-4652
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.2.0
>Reporter: Srikanth Venkat
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 3.0.0, 2.3.0
>
> Attachments: ATLAS-4652.patch
>
>
> The code inside isSoftReferenced method in AtlasStructDef class below:
> *{{}}* {{@JsonIgnore}}
> {{ public boolean isSoftReferenced() {}}
> {{ return this.options != null && }}{{
> getOptions().containsKey(AtlasAttributeDef.ATTRDEF_OPTION_SOFT_REFERENCE) &&}}
> {{
> getOptions().get(AtlasAttributeDef.ATTRDEF_OPTION_SOFT_REFERENCE){color:#de350b}.equals(STRING_TRUE){color};}}
> {{ }}}
>
> Since the null check is not performed, it can lead to NPE in typedef
> resolution.
>
> A sample typedef payload like the following can potentially trigger the NPE
> error in attribute resolution, i.e.
> EntityGraphRetriever.mapVertexToAttribute, where
> attribute.getAttributeDef().isSoftReferenced() is called
> {
> "businessMetadataDefs": [
> {
> "category": "BUSINESS_METADATA",
> "name": "bizType1",
> "description": "test",
> "attributeDefs": [
> {
> "name": "bizAttr1",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "options": {
> *"isSoftReference": null,*
> "maxStrLength": "50",
> "applicableEntityTypes": "[\"Asset\"]"
> }
> }
> ]
> }
> ]
> }
>
> It would be furthermore helpful to run SonarCube or FindBugs to determine any
> other incidences where this pattern of missing null check exists in Atlas
> codebase and address them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4652) Missing null check leading to NPE in isSoftReferenced method in AtlasStructDef
[
https://issues.apache.org/jira/browse/ATLAS-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17613363#comment-17613363
]
ASF subversion and git services commented on ATLAS-4652:
Commit 43daa256dd04a2e9167de6749f34e262b8216de3 in atlas's branch
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=43daa256d ]
ATLAS-4652: fix to address potential NPE in AtlasAttributeDef.isSoftReferenced()
> Missing null check leading to NPE in isSoftReferenced method in
> AtlasStructDef
> ---
>
> Key: ATLAS-4652
> URL: https://issues.apache.org/jira/browse/ATLAS-4652
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.2.0
>Reporter: Srikanth Venkat
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 3.0.0, 2.3.0
>
> Attachments: ATLAS-4652.patch
>
>
> The code inside isSoftReferenced method in AtlasStructDef class below:
> *{{}}* {{@JsonIgnore}}
> {{ public boolean isSoftReferenced() {}}
> {{ return this.options != null && }}{{
> getOptions().containsKey(AtlasAttributeDef.ATTRDEF_OPTION_SOFT_REFERENCE) &&}}
> {{
> getOptions().get(AtlasAttributeDef.ATTRDEF_OPTION_SOFT_REFERENCE){color:#de350b}.equals(STRING_TRUE){color};}}
> {{ }}}
>
> Since the null check is not performed, it can lead to NPE in typedef
> resolution.
>
> A sample typedef payload like the following can potentially trigger the NPE
> error in attribute resolution, i.e.
> EntityGraphRetriever.mapVertexToAttribute, where
> attribute.getAttributeDef().isSoftReferenced() is called
> {
> "businessMetadataDefs": [
> {
> "category": "BUSINESS_METADATA",
> "name": "bizType1",
> "description": "test",
> "attributeDefs": [
> {
> "name": "bizAttr1",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "options": {
> *"isSoftReference": null,*
> "maxStrLength": "50",
> "applicableEntityTypes": "[\"Asset\"]"
> }
> }
> ]
> }
> ]
> }
>
> It would be furthermore helpful to run SonarCube or FindBugs to determine any
> other incidences where this pattern of missing null check exists in Atlas
> codebase and address them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4671) Basic Search : Exclude Header attributes of entities from the response
[ https://issues.apache.org/jira/browse/ATLAS-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609993#comment-17609993 ] ASF subversion and git services commented on ATLAS-4671: Commit dff0fcb88a7b34365b1262f71e71f68749fbd35f in atlas's branch refs/heads/branch-2.0 from Pinal Shah [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=dff0fcb88 ] ATLAS-4671: Basic Search : Exclude Header attributes of entities from the response Signed-off-by: Pinal Shah (cherry picked from commit 37c242755cdf5320c2eafce925d613061e584e6a) > Basic Search : Exclude Header attributes of entities from the response > -- > > Key: ATLAS-4671 > URL: https://issues.apache.org/jira/browse/ATLAS-4671 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Labels: BasicSearch > > *Issue* : Basic search has AtlasEntityHeader of each entity in the response. > AtlasEntityHeader has many attributes including classification and terms. > hence for each attribute, it will request janusgraph to get all the header > attributes. > *Approach* : To overcome, we can add a flag to exclude other attributes and > add only selected attributes from 'attributes' field in the response -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4671) Basic Search : Exclude Header attributes of entities from the response
[ https://issues.apache.org/jira/browse/ATLAS-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609991#comment-17609991 ] ASF subversion and git services commented on ATLAS-4671: Commit 37c242755cdf5320c2eafce925d613061e584e6a in atlas's branch refs/heads/master from Pinal Shah [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=37c242755 ] ATLAS-4671: Basic Search : Exclude Header attributes of entities from the response Signed-off-by: Pinal Shah > Basic Search : Exclude Header attributes of entities from the response > -- > > Key: ATLAS-4671 > URL: https://issues.apache.org/jira/browse/ATLAS-4671 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Labels: BasicSearch > > *Issue* : Basic search has AtlasEntityHeader of each entity in the response. > AtlasEntityHeader has many attributes including classification and terms. > hence for each attribute, it will request janusgraph to get all the header > attributes. > *Approach* : To overcome, we can add a flag to exclude other attributes and > add only selected attributes from 'attributes' field in the response -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4679) Indexing of deleted relationship edges prolongs entity update time
[ https://issues.apache.org/jira/browse/ATLAS-4679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608678#comment-17608678 ] ASF subversion and git services commented on ATLAS-4679: Commit 226a034b59d124608a5b269c97d723b4312ff327 in atlas's branch refs/heads/branch-2.0 from Sheetal Shah [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=226a034b5 ] ATLAS-4679: Improving entity updates by not including deleted edges Signed-off-by: Pinal Shah (cherry picked from commit e3a6d238e3e0358b1f397968b1db1355c4818768) > Indexing of deleted relationship edges prolongs entity update time > -- > > Key: ATLAS-4679 > URL: https://issues.apache.org/jira/browse/ATLAS-4679 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: VINAYAK MARRAIYA >Assignee: Jayendra Parab >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4679) Indexing of deleted relationship edges prolongs entity update time
[ https://issues.apache.org/jira/browse/ATLAS-4679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608677#comment-17608677 ] ASF subversion and git services commented on ATLAS-4679: Commit e3a6d238e3e0358b1f397968b1db1355c4818768 in atlas's branch refs/heads/master from Sheetal Shah [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e3a6d238e ] ATLAS-4679: Improving entity updates by not including deleted edges Signed-off-by: Pinal Shah > Indexing of deleted relationship edges prolongs entity update time > -- > > Key: ATLAS-4679 > URL: https://issues.apache.org/jira/browse/ATLAS-4679 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: VINAYAK MARRAIYA >Assignee: Jayendra Parab >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4677) Atlas - Upgrade commons-configuration to 2.8.0
[ https://issues.apache.org/jira/browse/ATLAS-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17606568#comment-17606568 ] ASF subversion and git services commented on ATLAS-4677: Commit b11bd866fc6a4f834db0d1297d0aacc9dd9ecbd2 in atlas's branch refs/heads/branch-2.0 from chaitali borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b11bd866f ] ATLAS-4677 : Upgrade commons-configuration to 2.8.0 Signed-off-by: Pinal Shah (cherry picked from commit 33a7b45f7e641810a4e03c56f8d6cad229a58392) > Atlas - Upgrade commons-configuration to 2.8.0 > -- > > Key: ATLAS-4677 > URL: https://issues.apache.org/jira/browse/ATLAS-4677 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Current version for commons-configuration2 is 2.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4677) Atlas - Upgrade commons-configuration to 2.8.0
[ https://issues.apache.org/jira/browse/ATLAS-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17606567#comment-17606567 ] ASF subversion and git services commented on ATLAS-4677: Commit 33a7b45f7e641810a4e03c56f8d6cad229a58392 in atlas's branch refs/heads/master from chaitali borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=33a7b45f7 ] ATLAS-4677 : Upgrade commons-configuration to 2.8.0 Signed-off-by: Pinal Shah > Atlas - Upgrade commons-configuration to 2.8.0 > -- > > Key: ATLAS-4677 > URL: https://issues.apache.org/jira/browse/ATLAS-4677 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Current version for commons-configuration2 is 2.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4673) Atlas UI- Upgrade jquery-ui to 1.13.2
[ https://issues.apache.org/jira/browse/ATLAS-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605347#comment-17605347 ] ASF subversion and git services commented on ATLAS-4673: Commit d15946baf6a754e9bf1d57261cde1da168403a69 in atlas's branch refs/heads/branch-2.0 from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d15946baf ] ATLAS-4673 : (UI) Upgrade jquery-ui to 1.13.2 Signed-off-by: Pinal Shah (cherry picked from commit 146835ef03158d87defa1ef082decf9e05becbb0) > Atlas UI- Upgrade jquery-ui to 1.13.2 > - > > Key: ATLAS-4673 > URL: https://issues.apache.org/jira/browse/ATLAS-4673 > Project: Atlas > Issue Type: Improvement >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: 0001-ATLAS-4673-UI-Upgrade-jquery-ui-to-1.13.2.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4673) Atlas UI- Upgrade jquery-ui to 1.13.2
[ https://issues.apache.org/jira/browse/ATLAS-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605345#comment-17605345 ] ASF subversion and git services commented on ATLAS-4673: Commit 146835ef03158d87defa1ef082decf9e05becbb0 in atlas's branch refs/heads/master from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=146835ef0 ] ATLAS-4673 : (UI) Upgrade jquery-ui to 1.13.2 Signed-off-by: Pinal Shah > Atlas UI- Upgrade jquery-ui to 1.13.2 > - > > Key: ATLAS-4673 > URL: https://issues.apache.org/jira/browse/ATLAS-4673 > Project: Atlas > Issue Type: Improvement >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: 0001-ATLAS-4673-UI-Upgrade-jquery-ui-to-1.13.2.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4660) UI: Deleting businesss metadata attribute values with spaces in their key names results in unexpected behaviour
[ https://issues.apache.org/jira/browse/ATLAS-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602130#comment-17602130 ] ASF subversion and git services commented on ATLAS-4660: Commit c7496ffcd8122fa0f5ecd47f962b7b71fd7f3c52 in atlas's branch refs/heads/branch-2.0 from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=c7496ffcd ] ATLAS-4660 : (UI)Deleting businesss metadata attribute values with spaces in their key names results in unexpected behaviour Signed-off-by: Pinal Shah (cherry picked from commit 18aa87c0cffbe8e32483f8b88aae0cd9a11d2476) > UI: Deleting businesss metadata attribute values with spaces in their key > names results in unexpected behaviour > --- > > Key: ATLAS-4660 > URL: https://issues.apache.org/jira/browse/ATLAS-4660 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4660-UI-Deleting-businesss-metadata-attribute-.patch > > > # Create a business metadata with an attribute such that it has a space in > its name. (eg: 'testBusinessMetadata' with attribute 'test attribute1'). > Create at least two more attributes for the business metadata. > # Go to the entity details page for that entity with these business metadata > attributes and assign values to the above attributes. > # After the page refreshes, pick that attribute with the space with its name > and delete its value. > You will notice that on clicking the delete button for the first time, > nothing happens. When the delete button is clicked again,then all of the > other assigned values are wiped out along with the targeted attribute. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4660) UI: Deleting businesss metadata attribute values with spaces in their key names results in unexpected behaviour
[ https://issues.apache.org/jira/browse/ATLAS-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602129#comment-17602129 ] ASF subversion and git services commented on ATLAS-4660: Commit 18aa87c0cffbe8e32483f8b88aae0cd9a11d2476 in atlas's branch refs/heads/master from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=18aa87c0c ] ATLAS-4660 : (UI)Deleting businesss metadata attribute values with spaces in their key names results in unexpected behaviour Signed-off-by: Pinal Shah > UI: Deleting businesss metadata attribute values with spaces in their key > names results in unexpected behaviour > --- > > Key: ATLAS-4660 > URL: https://issues.apache.org/jira/browse/ATLAS-4660 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4660-UI-Deleting-businesss-metadata-attribute-.patch > > > # Create a business metadata with an attribute such that it has a space in > its name. (eg: 'testBusinessMetadata' with attribute 'test attribute1'). > Create at least two more attributes for the business metadata. > # Go to the entity details page for that entity with these business metadata > attributes and assign values to the above attributes. > # After the page refreshes, pick that attribute with the space with its name > and delete its value. > You will notice that on clicking the delete button for the first time, > nothing happens. When the delete button is clicked again,then all of the > other assigned values are wiped out along with the targeted attribute. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4669) Atlas - Upgrade Junit to 4.13.2
[ https://issues.apache.org/jira/browse/ATLAS-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17601804#comment-17601804 ] ASF subversion and git services commented on ATLAS-4669: Commit 83e7d6279c884e479aaaebac8e25f4d68c778a6f in atlas's branch refs/heads/branch-2.0 from chaitali borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=83e7d6279 ] ATLAS-4669 : Upgrade Junit to 4.13.2 Signed-off-by: Pinal Shah (cherry picked from commit 12fe912180ed9d98734a1ed1583c3e3f5f615b28) > Atlas - Upgrade Junit to 4.13.2 > --- > > Key: ATLAS-4669 > URL: https://issues.apache.org/jira/browse/ATLAS-4669 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 2.0.0, 3.0.0 > > > currently Junit version is 4.13.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4669) Atlas - Upgrade Junit to 4.13.2
[ https://issues.apache.org/jira/browse/ATLAS-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17601803#comment-17601803 ] ASF subversion and git services commented on ATLAS-4669: Commit 12fe912180ed9d98734a1ed1583c3e3f5f615b28 in atlas's branch refs/heads/master from chaitali borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=12fe91218 ] ATLAS-4669 : Upgrade Junit to 4.13.2 Signed-off-by: Pinal Shah > Atlas - Upgrade Junit to 4.13.2 > --- > > Key: ATLAS-4669 > URL: https://issues.apache.org/jira/browse/ATLAS-4669 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 2.0.0, 3.0.0 > > > currently Junit version is 4.13.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4627) Delete Existing entity in Atlas which are not present in Hive, DB wise through Import-hive command.
[ https://issues.apache.org/jira/browse/ATLAS-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17601728#comment-17601728 ] ASF subversion and git services commented on ATLAS-4627: Commit 4ac9ae6b2a2a858f811713aa7a268c81fe53471e in atlas's branch refs/heads/branch-2.0 from pareshD [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4ac9ae6b2 ] ATLAS-4627 : Delete Existing entity in Atlas which are not present in Hive, DB wise through Import-hive command. Signed-off-by: Pinal Shah (cherry picked from commit 3a98f1fc98dfcfabf9a19b5d43c8d61e8e696390) > Delete Existing entity in Atlas which are not present in Hive, DB wise > through Import-hive command. > --- > > Key: ATLAS-4627 > URL: https://issues.apache.org/jira/browse/ATLAS-4627 > Project: Atlas > Issue Type: Bug >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > PROBLEM STATEMENT > Created a DB_1 and DB_2 in Hive and disable the Atlas hook from hive and > hive_tez. > Created tables with 10 record in DB_1 and DB_2 . > In Atlas UI we checked it has no entity created, so we ran import-hive.sh > bash import-hive.sh -d DB_1 -t table_1, so this command will only create one > entity in atlas. > bash import-hive.sh -d DB_1, so this command will create all entity in atlas. > Drop table_1 from DB_1 and DB_2 in Hive, but will be present in atlas as > hooks are disable, so we will ran import-hive command to delete from atlas . > bash import-hive.sh -d DB_1 -t table_1 -deleteNonExisting, this command will > delete all the table from all DB which are present in Atlas and dropped from > Hive. > As we have mention -d and -t argument in command for DB and table wise > deleting, but still it ran for all DB and Tables. > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4627) Delete Existing entity in Atlas which are not present in Hive, DB wise through Import-hive command.
[ https://issues.apache.org/jira/browse/ATLAS-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17601727#comment-17601727 ] ASF subversion and git services commented on ATLAS-4627: Commit 3a98f1fc98dfcfabf9a19b5d43c8d61e8e696390 in atlas's branch refs/heads/master from pareshD [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3a98f1fc9 ] ATLAS-4627 : Delete Existing entity in Atlas which are not present in Hive, DB wise through Import-hive command. Signed-off-by: Pinal Shah > Delete Existing entity in Atlas which are not present in Hive, DB wise > through Import-hive command. > --- > > Key: ATLAS-4627 > URL: https://issues.apache.org/jira/browse/ATLAS-4627 > Project: Atlas > Issue Type: Bug >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > PROBLEM STATEMENT > Created a DB_1 and DB_2 in Hive and disable the Atlas hook from hive and > hive_tez. > Created tables with 10 record in DB_1 and DB_2 . > In Atlas UI we checked it has no entity created, so we ran import-hive.sh > bash import-hive.sh -d DB_1 -t table_1, so this command will only create one > entity in atlas. > bash import-hive.sh -d DB_1, so this command will create all entity in atlas. > Drop table_1 from DB_1 and DB_2 in Hive, but will be present in atlas as > hooks are disable, so we will ran import-hive command to delete from atlas . > bash import-hive.sh -d DB_1 -t table_1 -deleteNonExisting, this command will > delete all the table from all DB which are present in Atlas and dropped from > Hive. > As we have mention -d and -t argument in command for DB and table wise > deleting, but still it ran for all DB and Tables. > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4611) Atlas UI: Add text-editor for string attribute value of Business Metadata and for "description" field while creating Classification and Business Metadata.
[ https://issues.apache.org/jira/browse/ATLAS-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17585284#comment-17585284 ] ASF subversion and git services commented on ATLAS-4611: Commit 8bc54fd196bd6b6c6136b48258402eb4463315e7 in atlas's branch refs/heads/branch-2.0 from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8bc54fd19 ] ATLAS-4611 : (UI)Add text-editor for string attribute value of Business Metadata and for description field while creating Classification and Business Metadata Signed-off-by: Pinal Shah (cherry picked from commit d034bad23188f4292ee9befb2414d621b5be8945) > Atlas UI: Add text-editor for string attribute value of Business Metadata and > for "description" field while creating Classification and Business Metadata. > -- > > Key: ATLAS-4611 > URL: https://issues.apache.org/jira/browse/ATLAS-4611 > Project: Atlas > Issue Type: Improvement >Reporter: Prasad P. Pawar >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4611-UI-Add-text-editor-for-string-attribute-v.patch > > > 1) Business Metadata ( Entity Detail Page) > String attribute value should have text editor. > 2) Classification and Business Metadata > The "Description" field should have text editor as it has been implemented > for the Glossary section. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4611) Atlas UI: Add text-editor for string attribute value of Business Metadata and for "description" field while creating Classification and Business Metadata.
[ https://issues.apache.org/jira/browse/ATLAS-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17585283#comment-17585283 ] ASF subversion and git services commented on ATLAS-4611: Commit d034bad23188f4292ee9befb2414d621b5be8945 in atlas's branch refs/heads/master from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d034bad23 ] ATLAS-4611 : (UI)Add text-editor for string attribute value of Business Metadata and for description field while creating Classification and Business Metadata Signed-off-by: Pinal Shah > Atlas UI: Add text-editor for string attribute value of Business Metadata and > for "description" field while creating Classification and Business Metadata. > -- > > Key: ATLAS-4611 > URL: https://issues.apache.org/jira/browse/ATLAS-4611 > Project: Atlas > Issue Type: Improvement >Reporter: Prasad P. Pawar >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4611-UI-Add-text-editor-for-string-attribute-v.patch > > > 1) Business Metadata ( Entity Detail Page) > String attribute value should have text editor. > 2) Classification and Business Metadata > The "Description" field should have text editor as it has been implemented > for the Glossary section. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4662) Upgrade POI to 5.2.2
[ https://issues.apache.org/jira/browse/ATLAS-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583548#comment-17583548 ] ASF subversion and git services commented on ATLAS-4662: Commit 71b6bf783bf7bb999ea30965f7e9d381803f7f28 in atlas's branch refs/heads/branch-2.0 from chaitali borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=71b6bf783 ] ATLAS-4662 : Upgrade POI to 5.2.2 Signed-off-by: Pinal Shah (cherry picked from commit 7ee310bd34fc7cbe7899d42f4dc563ef676cd046) > Upgrade POI to 5.2.2 > > > Key: ATLAS-4662 > URL: https://issues.apache.org/jira/browse/ATLAS-4662 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > POI and POI-ooxml version is 4.1.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4662) Upgrade POI to 5.2.2
[ https://issues.apache.org/jira/browse/ATLAS-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583545#comment-17583545 ] ASF subversion and git services commented on ATLAS-4662: Commit 7ee310bd34fc7cbe7899d42f4dc563ef676cd046 in atlas's branch refs/heads/master from chaitali borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=7ee310bd3 ] ATLAS-4662 : Upgrade POI to 5.2.2 Signed-off-by: Pinal Shah > Upgrade POI to 5.2.2 > > > Key: ATLAS-4662 > URL: https://issues.apache.org/jira/browse/ATLAS-4662 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > POI and POI-ooxml version is 4.1.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4648) Upgrade Netty version to 4.1.78.Final
[ https://issues.apache.org/jira/browse/ATLAS-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582766#comment-17582766 ] ASF subversion and git services commented on ATLAS-4648: Commit 519afa57c7ee632e55e575818d4838a7c70a4ef2 in atlas's branch refs/heads/branch-2.0 from chaitali borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=519afa57c ] ATLAS-4648: Upgrade Netty Project to 4.1.78.Final Signed-off-by: Pinal Shah (cherry picked from commit 11ae4308a148a355193514f8fd4e04baf712) > Upgrade Netty version to 4.1.78.Final > - > > Key: ATLAS-4648 > URL: https://issues.apache.org/jira/browse/ATLAS-4648 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > current version for Netty to 4.1.77.Final -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4648) Upgrade Netty version to 4.1.78.Final
[ https://issues.apache.org/jira/browse/ATLAS-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582765#comment-17582765 ] ASF subversion and git services commented on ATLAS-4648: Commit 11ae4308a148a355193514f8fd4e04baf712 in atlas's branch refs/heads/master from chaitali borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=11ae43000 ] ATLAS-4648: Upgrade Netty Project to 4.1.78.Final Signed-off-by: Pinal Shah > Upgrade Netty version to 4.1.78.Final > - > > Key: ATLAS-4648 > URL: https://issues.apache.org/jira/browse/ATLAS-4648 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > current version for Netty to 4.1.77.Final -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4647) Upgrade Spring Security to 5.7.2
[ https://issues.apache.org/jira/browse/ATLAS-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581143#comment-17581143 ] ASF subversion and git services commented on ATLAS-4647: Commit 05e240173b4365445a08becb93030d6c52089a0b in atlas's branch refs/heads/branch-2.0 from chaitali borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=05e240173 ] ATLAS-4647 : Upgrade Spring Security to 5.7.2 Signed-off-by: Pinal Shah (cherry picked from commit ba5cf4046472272ccf51077f8deff8977d7730f5) > Upgrade Spring Security to 5.7.2 > > > Key: ATLAS-4647 > URL: https://issues.apache.org/jira/browse/ATLAS-4647 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > Current version for spring-security is 5.7.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4647) Upgrade Spring Security to 5.7.2
[ https://issues.apache.org/jira/browse/ATLAS-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581141#comment-17581141 ] ASF subversion and git services commented on ATLAS-4647: Commit ba5cf4046472272ccf51077f8deff8977d7730f5 in atlas's branch refs/heads/master from chaitali borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ba5cf4046 ] ATLAS-4647 : Upgrade Spring Security to 5.7.2 Signed-off-by: Pinal Shah > Upgrade Spring Security to 5.7.2 > > > Key: ATLAS-4647 > URL: https://issues.apache.org/jira/browse/ATLAS-4647 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > Current version for spring-security is 5.7.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4619) Refactor Atlas webapp module to remove Kafka core dependency
[ https://issues.apache.org/jira/browse/ATLAS-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581133#comment-17581133 ] ASF subversion and git services commented on ATLAS-4619: Commit 5ed088b4a6192d2f15656870e6522fdaa37d46f3 in atlas's branch refs/heads/branch-2.0 from Patrik Marton [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5ed088b4a ] ATLAS-4619: Refactor Atlas webapp module to remove Kafka core dependency Change-Id: Ie3422851cb711da4e7c4d0845319db6c3f65 Signed-off-by: Pinal Shah (cherry picked from commit 3c7d8c072055c246200a5617488ace5a1d64ae57) > Refactor Atlas webapp module to remove Kafka core dependency > > > Key: ATLAS-4619 > URL: https://issues.apache.org/jira/browse/ATLAS-4619 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Patrik Márton >Assignee: Patrik Márton >Priority: Major > > Goal is to break the strong coupling between Atlas components and Kafka. > These dependencies include using server side libraries of Kafka (this couples > the Scala version and other non-public interfaces of Kafka). Any code using > server side libraries of Kafka should be refactored. > Since atlas webapp module uses the ShutdownableThread from core kafka, it > should be refactored in a way to eliminate this dependency. > https://github.com/apache/atlas/blob/master/webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java#L526 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4649) Upgrade Spring Framework to 4.3.30.RELEASE/5.3.21
[ https://issues.apache.org/jira/browse/ATLAS-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581132#comment-17581132 ] ASF subversion and git services commented on ATLAS-4649: Commit 148fa540bdfa6d6b3f5b404266595ef3443ff232 in atlas's branch refs/heads/branch-2.0 from chaitali borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=148fa540b ] ATLAS-4649 Upgrade Spring Framework to 5.3.21 Signed-off-by: Pinal Shah (cherry picked from commit c1daaa44c3833be31c006753a2cf2f6f2e476cdc) > Upgrade Spring Framework to 4.3.30.RELEASE/5.3.21 > - > > Key: ATLAS-4649 > URL: https://issues.apache.org/jira/browse/ATLAS-4649 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > current version for Spring Framework is 5.3.20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4619) Refactor Atlas webapp module to remove Kafka core dependency
[ https://issues.apache.org/jira/browse/ATLAS-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581131#comment-17581131 ] ASF subversion and git services commented on ATLAS-4619: Commit 3c7d8c072055c246200a5617488ace5a1d64ae57 in atlas's branch refs/heads/master from Patrik Marton [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3c7d8c072 ] ATLAS-4619: Refactor Atlas webapp module to remove Kafka core dependency Change-Id: Ie3422851cb711da4e7c4d0845319db6c3f65 Signed-off-by: Pinal Shah > Refactor Atlas webapp module to remove Kafka core dependency > > > Key: ATLAS-4619 > URL: https://issues.apache.org/jira/browse/ATLAS-4619 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Patrik Márton >Assignee: Patrik Márton >Priority: Major > > Goal is to break the strong coupling between Atlas components and Kafka. > These dependencies include using server side libraries of Kafka (this couples > the Scala version and other non-public interfaces of Kafka). Any code using > server side libraries of Kafka should be refactored. > Since atlas webapp module uses the ShutdownableThread from core kafka, it > should be refactored in a way to eliminate this dependency. > https://github.com/apache/atlas/blob/master/webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java#L526 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4649) Upgrade Spring Framework to 4.3.30.RELEASE/5.3.21
[ https://issues.apache.org/jira/browse/ATLAS-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17577407#comment-17577407 ] ASF subversion and git services commented on ATLAS-4649: Commit c1daaa44c3833be31c006753a2cf2f6f2e476cdc in atlas's branch refs/heads/master from chaitali borole [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=c1daaa44c ] ATLAS-4649 Upgrade Spring Framework to 5.3.21 Signed-off-by: Pinal Shah > Upgrade Spring Framework to 4.3.30.RELEASE/5.3.21 > - > > Key: ATLAS-4649 > URL: https://issues.apache.org/jira/browse/ATLAS-4649 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 3.0.0 > > > current version for Spring Framework is 5.3.20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4600) UI: Add classification button appears for deleted hive_columns in Schema Tab of hive_table entity details page.
[ https://issues.apache.org/jira/browse/ATLAS-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17576528#comment-17576528 ] ASF subversion and git services commented on ATLAS-4600: Commit 9344ee3b6973efe987a3d1ba29615b91e3a72044 in atlas's branch refs/heads/branch-2.0 from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9344ee3b6 ] ATLAS-4600 : (UI)Add classification button appears for deleted hive_columns in Schema Tab of hive_table entity details page. Signed-off-by: Pinal Shah (cherry picked from commit 28cf092a8afe15e55d3a3d73918437caab600bbb) > UI: Add classification button appears for deleted hive_columns in Schema Tab > of hive_table entity details page. > --- > > Key: ATLAS-4600 > URL: https://issues.apache.org/jira/browse/ATLAS-4600 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: > 0001-ATLAS-4600-UI-Add-classification-button-appears-for-.patch, > image-2022-05-06-11-11-37-012.png > > > As you can see from the screenshot below, if you navigate to a deleted > hive_table entity's Schema tab, it is possible to get an 'add classification' > button. > > !image-2022-05-06-11-11-37-012.png|width=762,height=465! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4600) UI: Add classification button appears for deleted hive_columns in Schema Tab of hive_table entity details page.
[ https://issues.apache.org/jira/browse/ATLAS-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17576527#comment-17576527 ] ASF subversion and git services commented on ATLAS-4600: Commit 28cf092a8afe15e55d3a3d73918437caab600bbb in atlas's branch refs/heads/master from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=28cf092a8 ] ATLAS-4600 : (UI)Add classification button appears for deleted hive_columns in Schema Tab of hive_table entity details page. Signed-off-by: Pinal Shah > UI: Add classification button appears for deleted hive_columns in Schema Tab > of hive_table entity details page. > --- > > Key: ATLAS-4600 > URL: https://issues.apache.org/jira/browse/ATLAS-4600 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: > 0001-ATLAS-4600-UI-Add-classification-button-appears-for-.patch, > image-2022-05-06-11-11-37-012.png > > > As you can see from the screenshot below, if you navigate to a deleted > hive_table entity's Schema tab, it is possible to get an 'add classification' > button. > > !image-2022-05-06-11-11-37-012.png|width=762,height=465! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4607) UI improvements to support Atlas Lineage fetch on-demand
[ https://issues.apache.org/jira/browse/ATLAS-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572285#comment-17572285 ] ASF subversion and git services commented on ATLAS-4607: Commit ec00895d6b887fa4f482680982c32d38a3c87caa in atlas's branch refs/heads/branch-2.0 from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ec00895d6 ] ATLAS-4607: UI improvements to support Atlas Lineage fetch on-demand Signed-off-by: Pinal Shah (cherry picked from commit 6a1f2ef5c1cdcbc001c6ea74f5cbcfdf9c98f448) > UI improvements to support Atlas Lineage fetch on-demand > > > Key: ATLAS-4607 > URL: https://issues.apache.org/jira/browse/ATLAS-4607 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 3.0.0, 2.3.0 >Reporter: Radhika Kundam >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4607-UI-improvements-to-support-Atlas-Lineage-.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4607) UI improvements to support Atlas Lineage fetch on-demand
[ https://issues.apache.org/jira/browse/ATLAS-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572284#comment-17572284 ] ASF subversion and git services commented on ATLAS-4607: Commit 6a1f2ef5c1cdcbc001c6ea74f5cbcfdf9c98f448 in atlas's branch refs/heads/master from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=6a1f2ef5c ] ATLAS-4607: UI improvements to support Atlas Lineage fetch on-demand Signed-off-by: Pinal Shah > UI improvements to support Atlas Lineage fetch on-demand > > > Key: ATLAS-4607 > URL: https://issues.apache.org/jira/browse/ATLAS-4607 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 3.0.0, 2.3.0 >Reporter: Radhika Kundam >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4607-UI-improvements-to-support-Atlas-Lineage-.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4606) Improve Atlas Lineage API performance (fetch on-demand)
[ https://issues.apache.org/jira/browse/ATLAS-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572245#comment-17572245 ] ASF subversion and git services commented on ATLAS-4606: Commit 33d16202e5d67976eb71524c296a83ea10ae1808 in atlas's branch refs/heads/branch-2.0 from Radhika Kundam [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=33d16202e ] ATLAS-4606: Improve Atlas Lineage API performance (fetch on-demand) Signed-off-by: radhikakundam (cherry picked from commit 7ba5f191c5701f6fa850d18895951df6d20ab812) > Improve Atlas Lineage API performance (fetch on-demand) > --- > > Key: ATLAS-4606 > URL: https://issues.apache.org/jira/browse/ATLAS-4606 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Radhika Kundam >Assignee: Radhika Kundam >Priority: Major > > Atlas lineage for an entity returns all the entities connected in a single > call, this is expensive if lineage is long and has multi-level. Lineage API > response is large and UI fails to render the response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4606) Improve Atlas Lineage API performance (fetch on-demand)
[ https://issues.apache.org/jira/browse/ATLAS-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572244#comment-17572244 ] ASF subversion and git services commented on ATLAS-4606: Commit 7ba5f191c5701f6fa850d18895951df6d20ab812 in atlas's branch refs/heads/master from Radhika Kundam [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=7ba5f191c ] ATLAS-4606: Improve Atlas Lineage API performance (fetch on-demand) Signed-off-by: radhikakundam > Improve Atlas Lineage API performance (fetch on-demand) > --- > > Key: ATLAS-4606 > URL: https://issues.apache.org/jira/browse/ATLAS-4606 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Radhika Kundam >Assignee: Radhika Kundam >Priority: Major > > Atlas lineage for an entity returns all the entities connected in a single > call, this is expensive if lineage is long and has multi-level. Lineage API > response is large and UI fails to render the response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4642) remove unnecessary static members from plugin class loaders
[ https://issues.apache.org/jira/browse/ATLAS-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17569750#comment-17569750 ] ASF subversion and git services commented on ATLAS-4642: Commit 218dd81db9f3ea87f75833bee6acee1c70e2b1df in atlas's branch refs/heads/master from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=218dd81db ] ATLAS-4642: replace use of static volatile member from plugin classloader > remove unnecessary static members from plugin class loaders > --- > > Key: ATLAS-4642 > URL: https://issues.apache.org/jira/browse/ATLAS-4642 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: ATLAS-4642.patch > > > Plugin class loader uses static class member, which can/should be replaced > with non-static equivalent. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-3422) Cassandra Audit Repository not able to connect to Authenticated Cassandra Cluster
[ https://issues.apache.org/jira/browse/ATLAS-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17569260#comment-17569260 ] ASF subversion and git services commented on ATLAS-3422: Commit 19a09f72e60f08dce48e32bc796aaef58420554d in atlas's branch refs/heads/branch-2.0 from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=19a09f72e ] ATLAS-3422: fixed Atlas startup failure due to recently added configurations storage.username and storage.password - #2 (cherry picked from commit 2949b11627bc42dd32dc08737a970c31f0070c33) > Cassandra Audit Repository not able to connect to Authenticated Cassandra > Cluster > - > > Key: ATLAS-3422 > URL: https://issues.apache.org/jira/browse/ATLAS-3422 > Project: Atlas > Issue Type: Bug >Reporter: Arun >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Time Spent: 40m > Remaining Estimate: 0h > > When we chose Cassandra Audit Repository the Cassandra Connection details > does not take the credentails (username, password). > Following error is thrown when trying to connect to a Cassandra Cluster which > is Authenticated. > > Exception encountered during context initialization - cancelling refresh > attempt: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'services': Invocation of init method failed; nested > exception is java.lang.RuntimeException: org.apache.atlas.AtlasException: > com.datastax.driver.core.exceptions.AuthenticationException: Authentication > error on host /xx.x.xxx.xxx:9042: Host /xx.x.xxx.xxx:9042 requires > authentication, but no authenticator found in Cluster configuration -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-3422) Cassandra Audit Repository not able to connect to Authenticated Cassandra Cluster
[ https://issues.apache.org/jira/browse/ATLAS-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17569259#comment-17569259 ] ASF subversion and git services commented on ATLAS-3422: Commit 2949b11627bc42dd32dc08737a970c31f0070c33 in atlas's branch refs/heads/master from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2949b1162 ] ATLAS-3422: fixed Atlas startup failure due to recently added configurations storage.username and storage.password - #2 > Cassandra Audit Repository not able to connect to Authenticated Cassandra > Cluster > - > > Key: ATLAS-3422 > URL: https://issues.apache.org/jira/browse/ATLAS-3422 > Project: Atlas > Issue Type: Bug >Reporter: Arun >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Time Spent: 40m > Remaining Estimate: 0h > > When we chose Cassandra Audit Repository the Cassandra Connection details > does not take the credentails (username, password). > Following error is thrown when trying to connect to a Cassandra Cluster which > is Authenticated. > > Exception encountered during context initialization - cancelling refresh > attempt: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'services': Invocation of init method failed; nested > exception is java.lang.RuntimeException: org.apache.atlas.AtlasException: > com.datastax.driver.core.exceptions.AuthenticationException: Authentication > error on host /xx.x.xxx.xxx:9042: Host /xx.x.xxx.xxx:9042 requires > authentication, but no authenticator found in Cluster configuration -- This message was sent by Atlassian Jira (v8.20.10#820010)
