[jira] [Assigned] (ATLAS-4434) Atlas - Upgrade jetty to 9.4.43 or to later version.
[ https://issues.apache.org/jira/browse/ATLAS-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain reassigned ATLAS-4434: -- Assignee: (was: Mayank Jain) > Atlas - Upgrade jetty to 9.4.43 or to later version. > > > Key: ATLAS-4434 > URL: https://issues.apache.org/jira/browse/ATLAS-4434 > Project: Atlas > Issue Type: Improvement >Reporter: Mayank Jain >Priority: Major > > Upgrade jetty to 9.4.43 or to later version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4433) ATLAS - upgrade elastic search to 6.8.17
[ https://issues.apache.org/jira/browse/ATLAS-4433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-4433: --- Description: Upgrade elastic search to 6.8.17 > ATLAS - upgrade elastic search to 6.8.17 > > > Key: ATLAS-4433 > URL: https://issues.apache.org/jira/browse/ATLAS-4433 > Project: Atlas > Issue Type: Improvement >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > > Upgrade elastic search to 6.8.17 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4433) ATLAS - upgrade elastic search to 6.8.17
[ https://issues.apache.org/jira/browse/ATLAS-4433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-4433: --- Description: Upgrade elastic search jars to 6.8.17 (was: Upgrade elastic search to 6.8.17) > ATLAS - upgrade elastic search to 6.8.17 > > > Key: ATLAS-4433 > URL: https://issues.apache.org/jira/browse/ATLAS-4433 > Project: Atlas > Issue Type: Improvement >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > > Upgrade elastic search jars to 6.8.17 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4434) Atlas - Upgrade jetty to 9.4.43 or to later version.
Mayank Jain created ATLAS-4434: -- Summary: Atlas - Upgrade jetty to 9.4.43 or to later version. Key: ATLAS-4434 URL: https://issues.apache.org/jira/browse/ATLAS-4434 Project: Atlas Issue Type: Improvement Reporter: Mayank Jain Assignee: Mayank Jain Upgrade jetty to 9.4.43 or to later version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4433) ATLAS - upgrade elastic search to 6.8.17
Mayank Jain created ATLAS-4433: -- Summary: ATLAS - upgrade elastic search to 6.8.17 Key: ATLAS-4433 URL: https://issues.apache.org/jira/browse/ATLAS-4433 Project: Atlas Issue Type: Improvement Reporter: Mayank Jain Assignee: Mayank Jain -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ATLAS-3651) Metrics API: Count of entities for a type doesn't include entities of sub type
[ https://issues.apache.org/jira/browse/ATLAS-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain closed ATLAS-3651. -- > Metrics API: Count of entities for a type doesn't include entities of sub type > -- > > Key: ATLAS-3651 > URL: https://issues.apache.org/jira/browse/ATLAS-3651 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > Attachments: ATLAS-3651-Metrics-API-Count-of-entities-for-a-type-and > subType updation-8.patch > > > DataSet count shown in Basic/DSL Search doesn't include the count of entities > of its subtypes. If an entity is created as a DataSet then the count is > updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ATLAS-4296) [Atlas: Debug Metrics] Min Time , Max Time and Average Time in UI are not matching the api response values
[
https://issues.apache.org/jira/browse/ATLAS-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain closed ATLAS-4296.
--
> [Atlas: Debug Metrics] Min Time , Max Time and Average Time in UI are not
> matching the api response values
> --
>
> Key: ATLAS-4296
> URL: https://issues.apache.org/jira/browse/ATLAS-4296
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
> Attachments:
> 0001-ATLAS-UI-ATLAS-4296-ATLAS-4298-ATLAS-4299-Debug-Metr.patch,
> ATLAS-4296-1.patch, Screenshot 2021-05-21 at 4.18.34 PM.png, Screenshot
> 2021-05-21 at 4.18.34 PM.png
>
>
> Scenario: Enable debug Metrics
> !Screenshot 2021-05-21 at 4.18.34 PM.png|width=646,height=322!
> Eg: Consider the above highlighted example. *GlossaryREST_deleteGlossary*
> Here
> Min Time : 1.920 (seconds)
> Max Time : 5.530 (seconds) and
> Average Time : 5.530 (seconds)
> *Api response:*
> {code:java}
> "GlossaryREST_deleteGlossary": {
> "name": "GlossaryREST_deleteGlossary",
> "numops": 6,
> "minTime": 192,
> "maxTime": 553,
> "stdDevTime": 21.556128,
> "avgTime": 532
> } {code}
>
> 1.92 (seconds) has to be 1920 if the value is response is stored in
> milliseconds but it appears as 192
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (ATLAS-4391) NoSuchFileException for ${atlas.log.dir}/atlas-metrics.out
[
https://issues.apache.org/jira/browse/ATLAS-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain closed ATLAS-4391.
--
> NoSuchFileException for ${atlas.log.dir}/atlas-metrics.out
> ---
>
> Key: ATLAS-4391
> URL: https://issues.apache.org/jira/browse/ATLAS-4391
> Project: Atlas
> Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Mayank Jain
>Priority: Critical
> Attachments: ATLAS-4391-1.patch
>
>
> Atlas startup logs NoSuchFileException for ${atlas.log.dir}/atlas-metrics.out:
> 2021-08-05 07:54:07,353 WARN - [main:] ~ Error creating sink
> 'atlas-debug-metrics-context' (MetricsSystemImpl:508)
> org.apache.hadoop.metrics2.impl.MetricsConfigException: Error creating
> plugin: org.apache.hadoop.metrics2.sink.FileSink
> at
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:210)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.newSink(MetricsSystemImpl.java:531)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configureSinks(MetricsSystemImpl.java:503)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configure(MetricsSystemImpl.java:479)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:188)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.init(MetricsSystemImpl.java:163)
> at
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.init(DefaultMetricsSystem.java:62)
> at
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.initialize(DefaultMetricsSystem.java:58)
> at
> org.apache.atlas.web.service.DebugMetricsWrapper.init(DebugMetricsWrapper.java:43)
> ...
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:72)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:110)
> at org.apache.atlas.Atlas.main(Atlas.java:133)
> Caused by: org.apache.hadoop.metrics2.MetricsException: Error creating
> ${atlas.log.dir}/atlas-metrics.out
> at org.apache.hadoop.metrics2.sink.FileSink.init(FileSink.java:53)
> at
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:207)
> ... 63 more
> Caused by: java.nio.file.NoSuchFileException:
> ${atlas.log.dir}/atlas-metrics.out
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> at
> sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
> at
> java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)
> at java.nio.file.Files.newOutputStream(Files.java:216)
> at org.apache.hadoop.metrics2.sink.FileSink.init(FileSink.java:50)
> ... 64 more
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (ATLAS-3768) Business Metadata import issue with extra commas csv file
[
https://issues.apache.org/jira/browse/ATLAS-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain closed ATLAS-3768.
--
> Business Metadata import issue with extra commas csv file
> -
>
> Key: ATLAS-3768
> URL: https://issues.apache.org/jira/browse/ATLAS-3768
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Mayank Jain
>Priority: Minor
> Attachments: ATLAS-3768-1.patch
>
>
> If a csv file contains an extra comma(which gets inserted automatically at
> the end of the file after editing and saving the file in a program like
> Libreoffice Calc) and is then imported, it throws the error
> {code:java}
> "Provided UniqueAttributeValue is not valid.at line #1"{code}
> which is an invalid error message and doesn't inform the user as to what the
> error actually is.
> It should point to the extra comma in the error message, or the extra comma
> should be handled.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (ATLAS-4315) [Atlas: Debug Metrics] An entity when updated via REST api, is not reflected in debug metrics.
[ https://issues.apache.org/jira/browse/ATLAS-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain closed ATLAS-4315. -- > [Atlas: Debug Metrics] An entity when updated via REST api, is not reflected > in debug metrics. > -- > > Key: ATLAS-4315 > URL: https://issues.apache.org/jira/browse/ATLAS-4315 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > Attachments: ATLAS-4315-1.patch > > > Create a type (say type_entity) > Create an entity of type 'type_entity' > Update the entity > This should update the entry *EntityREST_createOrUpdate* in metrics data but > its not updated currently -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4297) [Atlas: Debug Metrics] Old data is lost when the feature is re-enabled
[ https://issues.apache.org/jira/browse/ATLAS-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain reassigned ATLAS-4297: -- Assignee: Mayank Jain > [Atlas: Debug Metrics] Old data is lost when the feature is re-enabled > -- > > Key: ATLAS-4297 > URL: https://issues.apache.org/jira/browse/ATLAS-4297 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mayank Jain >Priority: Major > > Enable the feature debug metrics by setting *atlas.debug.metrics.enabled=true* > Data will be collected > Now turn the feature off by setting *atlas.debug.metrics.enabled=false* > Re-enable the feature *atlas.debug.metrics.enabled=true* > This will be the data collected fresh and all the old data collected will be > lost > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ATLAS-4297) [Atlas: Debug Metrics] Old data is lost when the feature is re-enabled
[ https://issues.apache.org/jira/browse/ATLAS-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain closed ATLAS-4297. -- > [Atlas: Debug Metrics] Old data is lost when the feature is re-enabled > -- > > Key: ATLAS-4297 > URL: https://issues.apache.org/jira/browse/ATLAS-4297 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mayank Jain >Priority: Major > > Enable the feature debug metrics by setting *atlas.debug.metrics.enabled=true* > Data will be collected > Now turn the feature off by setting *atlas.debug.metrics.enabled=false* > Re-enable the feature *atlas.debug.metrics.enabled=true* > This will be the data collected fresh and all the old data collected will be > lost > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4297) [Atlas: Debug Metrics] Old data is lost when the feature is re-enabled
[ https://issues.apache.org/jira/browse/ATLAS-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain resolved ATLAS-4297. Resolution: Not A Bug > [Atlas: Debug Metrics] Old data is lost when the feature is re-enabled > -- > > Key: ATLAS-4297 > URL: https://issues.apache.org/jira/browse/ATLAS-4297 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mayank Jain >Priority: Major > > Enable the feature debug metrics by setting *atlas.debug.metrics.enabled=true* > Data will be collected > Now turn the feature off by setting *atlas.debug.metrics.enabled=false* > Re-enable the feature *atlas.debug.metrics.enabled=true* > This will be the data collected fresh and all the old data collected will be > lost > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4297) [Atlas: Debug Metrics] Old data is lost when the feature is re-enabled
[ https://issues.apache.org/jira/browse/ATLAS-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17392987#comment-17392987 ] Mayank Jain commented on ATLAS-4297: [~dharshmk] , This is not a bug, since by design the metrics shown on UI are maintained in-memory, so after restart the data gets reset. Using appropriate Sink implementation, we can persist it to storage like graphite, etc. For reference : [Hadoop Metrcis Sink Implementation Support|[https://hadoop.apache.org/docs/r3.1.0/api/org/apache/hadoop/metrics2/sink/RollingFileSystemSink.html]] > [Atlas: Debug Metrics] Old data is lost when the feature is re-enabled > -- > > Key: ATLAS-4297 > URL: https://issues.apache.org/jira/browse/ATLAS-4297 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mayank Jain >Priority: Major > > Enable the feature debug metrics by setting *atlas.debug.metrics.enabled=true* > Data will be collected > Now turn the feature off by setting *atlas.debug.metrics.enabled=false* > Re-enable the feature *atlas.debug.metrics.enabled=true* > This will be the data collected fresh and all the old data collected will be > lost > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4291) [Atlas: Debug Metrics] The Average time calculated for some endpoints/methods are incorrect
[ https://issues.apache.org/jira/browse/ATLAS-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain resolved ATLAS-4291. Resolution: Not A Bug > [Atlas: Debug Metrics] The Average time calculated for some endpoints/methods > are incorrect > --- > > Key: ATLAS-4291 > URL: https://issues.apache.org/jira/browse/ATLAS-4291 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mayank Jain >Priority: Major > Attachments: Screenshot 2021-05-20 at 6.58.22 PM.png > > > The average time calculated for some of the requests are incorrect > !Screenshot 2021-05-20 at 6.58.22 PM.png|width=461,height=223! > *Repro steps:* > Enable debug metrics by setting *atlas.debug.metrics.enabled=true* > Perform some operations create/delete glossary/entity or any other operation > Open the REST API metrics page > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ATLAS-4292) [Atlas: Debug Metrics] com.sun.jersey.api.MessageException thrown while fetching debug metrics via browser
[
https://issues.apache.org/jira/browse/ATLAS-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain closed ATLAS-4292.
--
> [Atlas: Debug Metrics] com.sun.jersey.api.MessageException thrown while
> fetching debug metrics via browser
> --
>
> Key: ATLAS-4292
> URL: https://issues.apache.org/jira/browse/ATLAS-4292
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
> Attachments: ATLAS-4292-1.patch, Screenshot 2021-05-20 at 7.44.34
> PM.png, Screenshot 2021-05-20 at 8.03.07 PM.png
>
>
> While fetching the data via browser, the following exception is thrown
> {code:java}
> 2021-05-20 13:47:32,150 INFO -
> [etp522553046-44:HTTP:GET/api/atlas/admin/metrics] ~ Request from
> authenticated user: HTTP, URL=/api/atlas/admin/metrics
> (AtlasAuthenticationFilter$KerberosFilterChainWrapper:739)
> 2021-05-20 13:47:50,657 ERROR - [etp522553046-269 -
> 41f0e041-f379-4389-b998-62bb43cafd88:] ~ Error handling a request:
> 58173f6d7e3447db (ExceptionMapperUtil:32)at
> com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:284)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1510)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1452)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:791)
> at
> org.eclipse.jetty.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1626)
> at
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:106)
> at
> org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193)
> at
> org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1601)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
> at
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:127)
> at
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:91)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:114)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:137)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:111)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.apache.atlas.web.filters.AtlasCSRFPreventionFilter$ServletFilterHttpInteraction.proceed(AtlasCSRFPreventionFilter.java:235)
> at
> org.apache.atlas.web.filters.AtlasCSRFPreventionFilter.handleHttpInteraction(AtlasCSRFPreventionFilter.java:177)
> at
> org.apache.atlas.web.filters.AtlasCSRFPreventionFilter.doFilter(AtlasCSRFPreventionFilter.java:190)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.apache.atlas.web.filters.AtlasAuthenticationFilter.doFilter(AtlasAuthenticationFilter.java:358)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:170)
> at
>
[jira] [Closed] (ATLAS-4291) [Atlas: Debug Metrics] The Average time calculated for some endpoints/methods are incorrect
[ https://issues.apache.org/jira/browse/ATLAS-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain closed ATLAS-4291. -- > [Atlas: Debug Metrics] The Average time calculated for some endpoints/methods > are incorrect > --- > > Key: ATLAS-4291 > URL: https://issues.apache.org/jira/browse/ATLAS-4291 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mayank Jain >Priority: Major > Attachments: Screenshot 2021-05-20 at 6.58.22 PM.png > > > The average time calculated for some of the requests are incorrect > !Screenshot 2021-05-20 at 6.58.22 PM.png|width=461,height=223! > *Repro steps:* > Enable debug metrics by setting *atlas.debug.metrics.enabled=true* > Perform some operations create/delete glossary/entity or any other operation > Open the REST API metrics page > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4291) [Atlas: Debug Metrics] The Average time calculated for some endpoints/methods are incorrect
[ https://issues.apache.org/jira/browse/ATLAS-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain reassigned ATLAS-4291: -- Assignee: Mayank Jain > [Atlas: Debug Metrics] The Average time calculated for some endpoints/methods > are incorrect > --- > > Key: ATLAS-4291 > URL: https://issues.apache.org/jira/browse/ATLAS-4291 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mayank Jain >Priority: Major > Attachments: Screenshot 2021-05-20 at 6.58.22 PM.png > > > The average time calculated for some of the requests are incorrect > !Screenshot 2021-05-20 at 6.58.22 PM.png|width=461,height=223! > *Repro steps:* > Enable debug metrics by setting *atlas.debug.metrics.enabled=true* > Perform some operations create/delete glossary/entity or any other operation > Open the REST API metrics page > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4291) [Atlas: Debug Metrics] The Average time calculated for some endpoints/methods are incorrect
[ https://issues.apache.org/jira/browse/ATLAS-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17392985#comment-17392985 ] Mayank Jain commented on ATLAS-4291: @ [~dharshmk], The Average Time which is actually the avgTime for the last interval i.e the API which is being monitored has if been accessed in the last interval then the avg time is calculated for the last interval only and not from the time since the atlas application started. > [Atlas: Debug Metrics] The Average time calculated for some endpoints/methods > are incorrect > --- > > Key: ATLAS-4291 > URL: https://issues.apache.org/jira/browse/ATLAS-4291 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mayank Jain >Priority: Major > Attachments: Screenshot 2021-05-20 at 6.58.22 PM.png > > > The average time calculated for some of the requests are incorrect > !Screenshot 2021-05-20 at 6.58.22 PM.png|width=461,height=223! > *Repro steps:* > Enable debug metrics by setting *atlas.debug.metrics.enabled=true* > Perform some operations create/delete glossary/entity or any other operation > Open the REST API metrics page > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ATLAS-4312) [Atlas: Debug Metrics] When an entity is created via hive EntityREST_createOrUpdate metrics does not capture it
[ https://issues.apache.org/jira/browse/ATLAS-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain closed ATLAS-4312. -- > [Atlas: Debug Metrics] When an entity is created via hive > EntityREST_createOrUpdate metrics does not capture it > --- > > Key: ATLAS-4312 > URL: https://issues.apache.org/jira/browse/ATLAS-4312 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mayank Jain >Priority: Major > Attachments: ATLAS-4315-1.pacth > > > When debug metrics is enabled, all the debug data are captured. > When an entity is created by hitting the /entity endpoint, then the > *EntityREST_createOrUpdate* is created/updated. > But if a hive table is created, this entry is not created/updated > *Steps to repro:* > # Restart Atlas > # Create a hive table after restart > # Fetch debug metrics > > Expectation: > EntityREST_createOrUpdate should be created in debug_audit_response > Observation: > The response is empty -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4312) [Atlas: Debug Metrics] When an entity is created via hive EntityREST_createOrUpdate metrics does not capture it
[ https://issues.apache.org/jira/browse/ATLAS-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain reassigned ATLAS-4312: -- Assignee: Mayank Jain > [Atlas: Debug Metrics] When an entity is created via hive > EntityREST_createOrUpdate metrics does not capture it > --- > > Key: ATLAS-4312 > URL: https://issues.apache.org/jira/browse/ATLAS-4312 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Dharshana M Krishnamoorthy >Assignee: Mayank Jain >Priority: Major > > When debug metrics is enabled, all the debug data are captured. > When an entity is created by hitting the /entity endpoint, then the > *EntityREST_createOrUpdate* is created/updated. > But if a hive table is created, this entry is not created/updated > *Steps to repro:* > # Restart Atlas > # Create a hive table after restart > # Fetch debug metrics > > Expectation: > EntityREST_createOrUpdate should be created in debug_audit_response > Observation: > The response is empty -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4315) [Atlas: Debug Metrics] An entity when updated via REST api, is not reflected in debug metrics.
[ https://issues.apache.org/jira/browse/ATLAS-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-4315: --- Summary: [Atlas: Debug Metrics] An entity when updated via REST api, is not reflected in debug metrics. (was: [Atlas: Debug Metrics] When an entity is updated via REST api, its not reflected in metrics) > [Atlas: Debug Metrics] An entity when updated via REST api, is not reflected > in debug metrics. > -- > > Key: ATLAS-4315 > URL: https://issues.apache.org/jira/browse/ATLAS-4315 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > > Create a type (say type_entity) > Create an entity of type 'type_entity' > Update the entity > This should update the entry *EntityREST_createOrUpdate* in metrics data but > its not updated currently -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4315) [Atlas: Debug Metrics] When an entity is updated via REST api, its not reflected in metrics
[ https://issues.apache.org/jira/browse/ATLAS-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-4315: --- Issue Type: Bug (was: New Feature) > [Atlas: Debug Metrics] When an entity is updated via REST api, its not > reflected in metrics > --- > > Key: ATLAS-4315 > URL: https://issues.apache.org/jira/browse/ATLAS-4315 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > > Create a type (say type_entity) > Create an entity of type 'type_entity' > Update the entity > This should update the entry *EntityREST_createOrUpdate* in metrics data but > its not updated currently -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4315) [Atlas: Debug Metrics] When an entity is updated via REST api, its not reflected in metrics
Mayank Jain created ATLAS-4315: -- Summary: [Atlas: Debug Metrics] When an entity is updated via REST api, its not reflected in metrics Key: ATLAS-4315 URL: https://issues.apache.org/jira/browse/ATLAS-4315 Project: Atlas Issue Type: New Feature Reporter: Mayank Jain Assignee: Mayank Jain Create a type (say type_entity) Create an entity of type 'type_entity' Update the entity This should update the entry *EntityREST_createOrUpdate* in metrics data but its not updated currently -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4296) [Atlas: Debug Metrics] Min Time , Max Time and Average Time in UI are not matching the api response values
[
https://issues.apache.org/jira/browse/ATLAS-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-4296:
--
Assignee: Mayank Jain
> [Atlas: Debug Metrics] Min Time , Max Time and Average Time in UI are not
> matching the api response values
> --
>
> Key: ATLAS-4296
> URL: https://issues.apache.org/jira/browse/ATLAS-4296
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
> Attachments: Screenshot 2021-05-21 at 4.18.34 PM.png, Screenshot
> 2021-05-21 at 4.18.34 PM.png
>
>
> Scenario: Enable debug Metrics
> !Screenshot 2021-05-21 at 4.18.34 PM.png|width=646,height=322!
> Eg: Consider the above highlighted example. *GlossaryREST_deleteGlossary*
> Here
> Min Time : 1.920 (seconds)
> Max Time : 5.530 (seconds) and
> Average Time : 5.530 (seconds)
> *Api response:*
> {code:java}
> "GlossaryREST_deleteGlossary": {
> "name": "GlossaryREST_deleteGlossary",
> "numops": 6,
> "minTime": 192,
> "maxTime": 553,
> "stdDevTime": 21.556128,
> "avgTime": 532
> } {code}
>
> 1.92 (seconds) has to be 1920 if the value is response is stored in
> milliseconds but it appears as 192
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4292) [Atlas: Debug Metrics] com.sun.jersey.api.MessageException thrown while fetching debug metrics via browser
[
https://issues.apache.org/jira/browse/ATLAS-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-4292:
--
Assignee: Mayank Jain
> [Atlas: Debug Metrics] com.sun.jersey.api.MessageException thrown while
> fetching debug metrics via browser
> --
>
> Key: ATLAS-4292
> URL: https://issues.apache.org/jira/browse/ATLAS-4292
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
> Attachments: Screenshot 2021-05-20 at 7.44.34 PM.png, Screenshot
> 2021-05-20 at 8.03.07 PM.png
>
>
> While fetching the data via browser, the following exception is thrown
> {code:java}
> 2021-05-20 13:47:32,150 INFO -
> [etp522553046-44:HTTP:GET/api/atlas/admin/metrics] ~ Request from
> authenticated user: HTTP, URL=/api/atlas/admin/metrics
> (AtlasAuthenticationFilter$KerberosFilterChainWrapper:739)
> 2021-05-20 13:47:50,657 ERROR - [etp522553046-269 -
> 41f0e041-f379-4389-b998-62bb43cafd88:] ~ Error handling a request:
> 58173f6d7e3447db (ExceptionMapperUtil:32)at
> com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:284)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1510)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1452)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:791)
> at
> org.eclipse.jetty.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1626)
> at
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:106)
> at
> org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193)
> at
> org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1601)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
> at
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:127)
> at
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:91)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:114)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:137)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:111)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.apache.atlas.web.filters.AtlasCSRFPreventionFilter$ServletFilterHttpInteraction.proceed(AtlasCSRFPreventionFilter.java:235)
> at
> org.apache.atlas.web.filters.AtlasCSRFPreventionFilter.handleHttpInteraction(AtlasCSRFPreventionFilter.java:177)
> at
> org.apache.atlas.web.filters.AtlasCSRFPreventionFilter.doFilter(AtlasCSRFPreventionFilter.java:190)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.apache.atlas.web.filters.AtlasAuthenticationFilter.doFilter(AtlasAuthenticationFilter.java:358)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:170)
> at
>
[jira] [Assigned] (ATLAS-4273) [Atlas: Glossary Term Bulk Import] When there is only 1 term imported via bulk import and if it fails, no proper reason is mentioned in response
[
https://issues.apache.org/jira/browse/ATLAS-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-4273:
--
Assignee: Sidharth Kumar Mishra (was: Mayank Jain)
> [Atlas: Glossary Term Bulk Import] When there is only 1 term imported via
> bulk import and if it fails, no proper reason is mentioned in response
>
>
> Key: ATLAS-4273
> URL: https://issues.apache.org/jira/browse/ATLAS-4273
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> The following fails as we do not support @ in term name
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_l,term_@_1 {code}
> But the failure is
> {code:java}
> {"errorCode":"ATLAS-409-00-011","errorMessage":"Glossary import failed"}
> {code}
> The code is 409 which mean a conflict but the reason is different
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4275) [Atlas: Glossary Term Bulk Import] When there an incorrect data in preferred term column, it is not considered while importing
[
https://issues.apache.org/jira/browse/ATLAS-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-4275:
--
Assignee: Sidharth Kumar Mishra (was: Mayank Jain)
> [Atlas: Glossary Term Bulk Import] When there an incorrect data in preferred
> term column, it is not considered while importing
> --
>
> Key: ATLAS-4275
> URL: https://issues.apache.org/jira/browse/ATLAS-4275
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> When there is an error in the PreferredTerms of the input, error is not
> considered
> Consider the following input. Here the provided term "abcd:efgh" does not
> exists in the system.
> The error is thrown when it is provided as an input for "*PreferredToTerms*"
> column but not for "*PreferredTerms*" column
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> dharsh,term_1,"short desc","long description", "Example", "G1", "Usage",
> "glossary:100%","abcd:efgh"
> dharsh,term_2,"short desc","long description", "Example", "G1", "Usage",
> "glossary:100%""abcd:efgh", {code}
>
> *Expectation:*
> 2 failed message info should be thrown one for term_1(incorrect
> PreferredTerms) and the other for term_2(incorrect PreferredToTerms), but
> only 1 is thrown
>
> *Current output:*
> {code:java}
> {
> "failedImportInfoList": [
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_2",
> "importStatus": "FAILED",
> "remarks": "The provided Reference efgh@abcd does not exist at Atlas
> referred at record with TermName : term_2 and GlossaryName : dharsh"
> }
> ],
> "successImportInfoList": [
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_1",
> "importStatus": "SUCCESS",
> "remarks":
> "{\"termGuid\":\"284fe9a7-911c-423a-90bf-adf8231afb27\",\"qualifiedName\":\"term_1@dharsh\"}"
> },
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_2",
> "importStatus": "SUCCESS",
> "remarks":
> "{\"termGuid\":\"29a51c8a-ce92-4988-8fca-feaf683c58dd\",\"qualifiedName\":\"term_2@dharsh\"}"
> }
> ]
> } {code}
>
> *Expected output:*
> {code:java}
> {
> "failedImportInfoList": [
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_1",
> "importStatus": "FAILED",
> "remarks": "The provided Reference efgh@abcd does not exist at Atlas
> referred at record with TermName : term_1 and GlossaryName : dharsh"
> },
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_2",
> "importStatus": "FAILED",
> "remarks": "The provided Reference efgh@abcd does not exist at Atlas
> referred at record with TermName : term_2 and GlossaryName : dharsh"
> }
> ],
> "successImportInfoList": [
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_1",
> "importStatus": "SUCCESS",
> "remarks":
> "{\"termGuid\":\"284fe9a7-911c-423a-90bf-adf8231afb27\",\"qualifiedName\":\"term_1@dharsh\"}"
> },
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_2",
> "importStatus": "SUCCESS",
> "remarks":
> "{\"termGuid\":\"29a51c8a-ce92-4988-8fca-feaf683c58dd\",\"qualifiedName\":\"term_2@dharsh\"}"
> }
> ]
> } {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4276) [Atlas: Glossary Term Bulk Import] Unhandled exception java.lang.ArrayIndexOutOfBoundsException thrown, when related terms are not provided in the right format
[
https://issues.apache.org/jira/browse/ATLAS-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-4276:
--
Assignee: Sidharth Kumar Mishra (was: Mayank Jain)
> [Atlas: Glossary Term Bulk Import] Unhandled exception
> java.lang.ArrayIndexOutOfBoundsException thrown, when related terms are not
> provided in the right format
> ---
>
> Key: ATLAS-4276
> URL: https://issues.apache.org/jira/browse/ATLAS-4276
> Project: Atlas
> Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-4274_2.patch
>
>
> Input:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> dharsh,term_1,"short desc","long description", "Example", "G1", "Usage",
> "glossary:100%""abcd", {code}
> Here term is provided as "abcd" instead of glossary@term format
> The following exception is thrown, which is an Internal server error
> {code:java}
> 2021-05-07 06:31:39,080 ERROR - [etp1770642014-187 -
> 11bce930-c6b9-4eec-a353-a553450425bb:] ~ Error handling a request:
> a2e852df89225e3a (ExceptionMapperUtil:32)2021-05-07 06:31:39,080 ERROR -
> [etp1770642014-187 - 11bce930-c6b9-4eec-a353-a553450425bb:] ~ Error handling
> a request: a2e852df89225e3a
> (ExceptionMapperUtil:32)java.lang.ArrayIndexOutOfBoundsException: 1 at
> org.apache.atlas.glossary.GlossaryTermUtils.getAtlasRelatedTermHeaderSet(GlossaryTermUtils.java:718)
> at
> org.apache.atlas.glossary.GlossaryTermUtils.populateGlossaryTermObject(GlossaryTermUtils.java:778)
> at
> org.apache.atlas.glossary.GlossaryTermUtils.getGlossaryTermDataWithRelations(GlossaryTermUtils.java:610)
> at
> org.apache.atlas.glossary.GlossaryService.importGlossaryData(GlossaryService.java:1134)
> at
> org.apache.atlas.glossary.GlossaryService$$FastClassBySpringCGLIB$$e1f893e0.invoke()
> at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:668)
> at
> org.apache.atlas.glossary.GlossaryService$$EnhancerBySpringCGLIB$$3c19046e.importGlossaryData()
> at
> org.apache.atlas.web.rest.GlossaryREST.importGlossaryData(GlossaryREST.java:1021)
> at
> org.apache.atlas.web.rest.GlossaryREST$$FastClassBySpringCGLIB$$29dc059.invoke()
> at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:737)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
> at
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:84)
> at
> org.apache.atlas.web.service.TimedAspectInterceptor.timerAdvice(TimedAspectInterceptor.java:46)
> at sun.reflect.GeneratedMethodAccessor208.invoke(Unknown Source) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:627)
> at
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:616)
> at
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:70)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:168)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:672)
> at
> org.apache.atlas.web.rest.GlossaryREST$$EnhancerBySpringCGLIB$$d1d409d6.importGlossaryData()
> at sun.reflect.GeneratedMethodAccessor331.invoke(Unknown Source) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
>
[jira] [Assigned] (ATLAS-4277) [Atlas: Glossary Term Bulk Import] [Regression] Unable to create term term_1 under glossary glossary_1 via bulk import
[
https://issues.apache.org/jira/browse/ATLAS-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-4277:
--
Assignee: Sidharth Kumar Mishra (was: Mayank Jain)
> [Atlas: Glossary Term Bulk Import] [Regression] Unable to create term term_1
> under glossary glossary_1 via bulk import
> --
>
> Key: ATLAS-4277
> URL: https://issues.apache.org/jira/browse/ATLAS-4277
> Project: Atlas
> Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Unable to create term *term_1* under glossary *glossary_1* the cluster with
> latest bits
> Import input:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1
> glossary_1,term_2{code}
> Current result:
> {code:java}
> {
> "failedImportInfoList":[
> {
> "parentObjectName":"glossary_1",
> "childObjectName":"term_1",
> "importStatus":"FAILED",
> "remarks":"Glossary term with qualifiedName term_1@glossary_1 already
> exists"
> }
> ],
> "successImportInfoList":[
> {
> "parentObjectName":"glossary_1",
> "childObjectName":"term_2",
> "importStatus":"SUCCESS",
>
> "remarks":"{\"termGuid\":\"8fe9a26a-aa14-4ed4-9a37-ef6db69ec29b\",\"qualifiedName\":\"term_2@glossary_1\"}"
> }
> ]
> } {code}
> Even though there is no glossary with name glossary_1 and you are creating it
> for the first time, this error is thrown.
> This was working fine on the older bits
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4273) [Atlas: Glossary Term Bulk Import] When there is only 1 term imported via bulk import and if it fails, no proper reason is mentioned in response
[
https://issues.apache.org/jira/browse/ATLAS-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-4273:
--
Assignee: Mayank Jain
> [Atlas: Glossary Term Bulk Import] When there is only 1 term imported via
> bulk import and if it fails, no proper reason is mentioned in response
>
>
> Key: ATLAS-4273
> URL: https://issues.apache.org/jira/browse/ATLAS-4273
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
>
> The following fails as we do not support @ in term name
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_l,term_@_1 {code}
> But the failure is
> {code:java}
> {"errorCode":"ATLAS-409-00-011","errorMessage":"Glossary import failed"}
> {code}
> The code is 409 which mean a conflict but the reason is different
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4275) [Atlas: Glossary Term Bulk Import] When there an incorrect data in preferred term column, it is not considered while importing
[
https://issues.apache.org/jira/browse/ATLAS-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-4275:
--
Assignee: Mayank Jain
> [Atlas: Glossary Term Bulk Import] When there an incorrect data in preferred
> term column, it is not considered while importing
> --
>
> Key: ATLAS-4275
> URL: https://issues.apache.org/jira/browse/ATLAS-4275
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
>
> When there is an error in the PreferredTerms of the input, error is not
> considered
> Consider the following input. Here the provided term "abcd:efgh" does not
> exists in the system.
> The error is thrown when it is provided as an input for "*PreferredToTerms*"
> column but not for "*PreferredTerms*" column
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> dharsh,term_1,"short desc","long description", "Example", "G1", "Usage",
> "glossary:100%","abcd:efgh"
> dharsh,term_2,"short desc","long description", "Example", "G1", "Usage",
> "glossary:100%""abcd:efgh", {code}
>
> *Expectation:*
> 2 failed message info should be thrown one for term_1(incorrect
> PreferredTerms) and the other for term_2(incorrect PreferredToTerms), but
> only 1 is thrown
>
> *Current output:*
> {code:java}
> {
> "failedImportInfoList": [
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_2",
> "importStatus": "FAILED",
> "remarks": "The provided Reference efgh@abcd does not exist at Atlas
> referred at record with TermName : term_2 and GlossaryName : dharsh"
> }
> ],
> "successImportInfoList": [
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_1",
> "importStatus": "SUCCESS",
> "remarks":
> "{\"termGuid\":\"284fe9a7-911c-423a-90bf-adf8231afb27\",\"qualifiedName\":\"term_1@dharsh\"}"
> },
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_2",
> "importStatus": "SUCCESS",
> "remarks":
> "{\"termGuid\":\"29a51c8a-ce92-4988-8fca-feaf683c58dd\",\"qualifiedName\":\"term_2@dharsh\"}"
> }
> ]
> } {code}
>
> *Expected output:*
> {code:java}
> {
> "failedImportInfoList": [
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_1",
> "importStatus": "FAILED",
> "remarks": "The provided Reference efgh@abcd does not exist at Atlas
> referred at record with TermName : term_1 and GlossaryName : dharsh"
> },
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_2",
> "importStatus": "FAILED",
> "remarks": "The provided Reference efgh@abcd does not exist at Atlas
> referred at record with TermName : term_2 and GlossaryName : dharsh"
> }
> ],
> "successImportInfoList": [
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_1",
> "importStatus": "SUCCESS",
> "remarks":
> "{\"termGuid\":\"284fe9a7-911c-423a-90bf-adf8231afb27\",\"qualifiedName\":\"term_1@dharsh\"}"
> },
> {
> "parentObjectName": "dharsh",
> "childObjectName": "term_2",
> "importStatus": "SUCCESS",
> "remarks":
> "{\"termGuid\":\"29a51c8a-ce92-4988-8fca-feaf683c58dd\",\"qualifiedName\":\"term_2@dharsh\"}"
> }
> ]
> } {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4276) [Atlas: Glossary Term Bulk Import] Unhandled exception java.lang.ArrayIndexOutOfBoundsException thrown, when related terms are not provided in the right format
[
https://issues.apache.org/jira/browse/ATLAS-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-4276:
--
Assignee: Mayank Jain
> [Atlas: Glossary Term Bulk Import] Unhandled exception
> java.lang.ArrayIndexOutOfBoundsException thrown, when related terms are not
> provided in the right format
> ---
>
> Key: ATLAS-4276
> URL: https://issues.apache.org/jira/browse/ATLAS-4276
> Project: Atlas
> Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
>
> Input:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> dharsh,term_1,"short desc","long description", "Example", "G1", "Usage",
> "glossary:100%""abcd", {code}
> Here term is provided as "abcd" instead of glossary@term format
> The following exception is thrown, which is an Internal server error
> {code:java}
> 2021-05-07 06:31:39,080 ERROR - [etp1770642014-187 -
> 11bce930-c6b9-4eec-a353-a553450425bb:] ~ Error handling a request:
> a2e852df89225e3a (ExceptionMapperUtil:32)2021-05-07 06:31:39,080 ERROR -
> [etp1770642014-187 - 11bce930-c6b9-4eec-a353-a553450425bb:] ~ Error handling
> a request: a2e852df89225e3a
> (ExceptionMapperUtil:32)java.lang.ArrayIndexOutOfBoundsException: 1 at
> org.apache.atlas.glossary.GlossaryTermUtils.getAtlasRelatedTermHeaderSet(GlossaryTermUtils.java:718)
> at
> org.apache.atlas.glossary.GlossaryTermUtils.populateGlossaryTermObject(GlossaryTermUtils.java:778)
> at
> org.apache.atlas.glossary.GlossaryTermUtils.getGlossaryTermDataWithRelations(GlossaryTermUtils.java:610)
> at
> org.apache.atlas.glossary.GlossaryService.importGlossaryData(GlossaryService.java:1134)
> at
> org.apache.atlas.glossary.GlossaryService$$FastClassBySpringCGLIB$$e1f893e0.invoke()
> at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:668)
> at
> org.apache.atlas.glossary.GlossaryService$$EnhancerBySpringCGLIB$$3c19046e.importGlossaryData()
> at
> org.apache.atlas.web.rest.GlossaryREST.importGlossaryData(GlossaryREST.java:1021)
> at
> org.apache.atlas.web.rest.GlossaryREST$$FastClassBySpringCGLIB$$29dc059.invoke()
> at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:737)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
> at
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:84)
> at
> org.apache.atlas.web.service.TimedAspectInterceptor.timerAdvice(TimedAspectInterceptor.java:46)
> at sun.reflect.GeneratedMethodAccessor208.invoke(Unknown Source) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:627)
> at
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:616)
> at
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:70)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:168)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:672)
> at
> org.apache.atlas.web.rest.GlossaryREST$$EnhancerBySpringCGLIB$$d1d409d6.importGlossaryData()
> at sun.reflect.GeneratedMethodAccessor331.invoke(Unknown Source) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at
>
[jira] [Assigned] (ATLAS-4277) [Atlas: Glossary Term Bulk Import] [Regression] Unable to create term term_1 under glossary glossary_1 via bulk import
[
https://issues.apache.org/jira/browse/ATLAS-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-4277:
--
Assignee: Mayank Jain
> [Atlas: Glossary Term Bulk Import] [Regression] Unable to create term term_1
> under glossary glossary_1 via bulk import
> --
>
> Key: ATLAS-4277
> URL: https://issues.apache.org/jira/browse/ATLAS-4277
> Project: Atlas
> Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
>
> Unable to create term *term_1* under glossary *glossary_1* the cluster with
> latest bits
> Import input:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1
> glossary_1,term_2{code}
> Current result:
> {code:java}
> {
> "failedImportInfoList":[
> {
> "parentObjectName":"glossary_1",
> "childObjectName":"term_1",
> "importStatus":"FAILED",
> "remarks":"Glossary term with qualifiedName term_1@glossary_1 already
> exists"
> }
> ],
> "successImportInfoList":[
> {
> "parentObjectName":"glossary_1",
> "childObjectName":"term_2",
> "importStatus":"SUCCESS",
>
> "remarks":"{\"termGuid\":\"8fe9a26a-aa14-4ed4-9a37-ef6db69ec29b\",\"qualifiedName\":\"term_2@glossary_1\"}"
> }
> ]
> } {code}
> Even though there is no glossary with name glossary_1 and you are creating it
> for the first time, this error is thrown.
> This was working fine on the older bits
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4225) Support for Chinese character in entity data.
Mayank Jain created ATLAS-4225: -- Summary: Support for Chinese character in entity data. Key: ATLAS-4225 URL: https://issues.apache.org/jira/browse/ATLAS-4225 Project: Atlas Issue Type: New Feature Reporter: Mayank Jain Assignee: Mayank Jain Currently we only allow English characters to be used to adding entity data that is labels , Custom Attributes and Business-Metadata. We need to support for Chinese and other languages as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4174) [Atlas: Glossary Term Bulk Import] When the file size is large (5 mb) bulk import times out
[ https://issues.apache.org/jira/browse/ATLAS-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain reassigned ATLAS-4174: -- Assignee: Mayank Jain > [Atlas: Glossary Term Bulk Import] When the file size is large (5 mb) bulk > import times out > --- > > Key: ATLAS-4174 > URL: https://issues.apache.org/jira/browse/ATLAS-4174 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Mayank Jain >Priority: Major > Attachments: Screen Recording 2021-02-23 at 2.33.42 PM.mov, > only_names.csv > > > When file size is large bulk import times out. > Attached a sample input for which the bulk import times out > Sample input: [^only_names.csv] > Video: [^Screen Recording 2021-02-23 at 2.33.42 PM.mov] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4130) [Atlas: Glossary Term Bulk Import] Need a way to know if the import was fully success or partial success or failure
[
https://issues.apache.org/jira/browse/ATLAS-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-4130:
--
Assignee: Mayank Jain
> [Atlas: Glossary Term Bulk Import] Need a way to know if the import was fully
> success or partial success or failure
> ---
>
> Key: ATLAS-4130
> URL: https://issues.apache.org/jira/browse/ATLAS-4130
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
> Attachments: Screenshot 2021-01-28 at 11.46.10 AM.png
>
>
> When there are partial success the response need to convey the details
> clearly to the user
> Partial import example:
> While importing bulk glossaries via bulk import feature, if one of the rows
> has a fault, it throws exception and creates only glossary names for the rest
> of the input without creating the associated terms
> Consider the following input
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> gloss_1,term_1
> gloss_1,term_1
> gloss_2,term_2
> gloss_3,term_3
> {code}
> Here we are creating gloss_1 and term_1 twice.
> The first time succeeds, the second time it throws the right exception as
> follows
> {code:java}
> {"errorCode":"ATLAS-500-00-016", "errorMessage":"Error occurred while
> creating glossary term: \{0}
> ",
> "errorCause":"Glossary term with qualifiedName term_1@gloss_1 already
> exists"}{code}
>
> But for the remaining rows, it creates only the glossaries without creating
> the terms
> The import call fails but still data is populated which leads to confusion.
> There is no way to know if the import was fully success or partial success or
> failure
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4129) [Atlas: Glossary Term Bulk Import] Only glossaries are created when there is faulty input in one of the rows during bulk import of glossaries
[
https://issues.apache.org/jira/browse/ATLAS-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-4129:
--
Assignee: Mayank Jain
> [Atlas: Glossary Term Bulk Import] Only glossaries are created when there is
> faulty input in one of the rows during bulk import of glossaries
> -
>
> Key: ATLAS-4129
> URL: https://issues.apache.org/jira/browse/ATLAS-4129
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
> Attachments: Screenshot 2021-01-28 at 11.46.10 AM.png
>
>
> While importing bulk glossaries via bulk import feature, if one of the rows
> has a fault, it throws exception and creates only glossary names for the rest
> of the input.
> Consider the following input
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> gloss_1,term_1
> gloss_1,term_1
> gloss_2,term_2
> gloss_3,term_3
> {code}
> Here we are creating gloss_1 and term_1 twice.
> The first time succeeds, the second time it throws the right exception as
> follows
> {code:java}
> {"errorCode":"ATLAS-500-00-016", "errorMessage":"Error occurred while
> creating glossary term: \{0}
> ",
> "errorCause":"Glossary term with qualifiedName term_1@gloss_1 already
> exists"}{code}
>
> But for the remaining rows, it creates only the glossaries without creating
> the terms
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4128) [Atlas: Glossary Term Bulk Import]Bulk import glossary terms should not allow creation of blank/empty glossaries
[
https://issues.apache.org/jira/browse/ATLAS-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-4128:
--
Assignee: Mayank Jain
> [Atlas: Glossary Term Bulk Import]Bulk import glossary terms should not allow
> creation of blank/empty glossaries
>
>
> Key: ATLAS-4128
> URL: https://issues.apache.org/jira/browse/ATLAS-4128
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
> Attachments: Screenshot 2021-01-25 at 6.13.59 PM.png, Screenshot
> 2021-01-28 at 11.25.14 AM.png
>
>
> Currently via bulk import glossary term, we allow creation of blank/empty
> glossaries.
> We should not allow these
> Response of : "api/atlas/v2/glossary" api
> {code:java}
> [
> {
> "guid": "34bf4540-5909-4a8e-84f0-1ff310870730",
> "qualifiedName": "glossary_1",
> "name": "glossary_1",
> "terms": [
> {
> "termGuid": "1ccaa2a2-f663-43ee-8cbc-f20c0ac95af0",
> "relationGuid": "b255b30e-be93-44e4-93bf-3d2d11a512d4",
> "displayText": "term_1"
> }
> ]
> },
> {
> "guid": "8834a901-0fde-4123-8d82-06e655ccf231",
> "qualifiedName": " ",
> "name": " ",
> "terms": [
> {
> "termGuid": "ac3f05d9-16d4-4ac5-be9c-bc5034af02d8",
> "relationGuid": "9c2ef8dd-522c-4d07-a338-093f39bceb93",
> "displayText": "no name term"
> }
> ]
> },
> {
> "guid": "29950f59-e863-42e2-a3f8-a070e706a934",
> "terms": [
> {
> "termGuid": "9e504d8d-8be2-4518-821a-cad3d86dfa6d",
> "relationGuid": "75f8f3d0-258a-4428-bb6c-08e59da90ee3",
> "displayText": "empty_term"
> }
> ]
> }
> ]
> {code}
> As seen above there exists a glossary with name " " and with no name.
> Not sure of the implication of such a glossary
> Though the request fails with right exception it ends up creating blank
> glossary
> Payload used:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> " ", " ",{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4160) [Atlas: Glossary Term Bulk Import]: Bulk import fails with AtlasBaseException
[
https://issues.apache.org/jira/browse/ATLAS-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-4160:
--
Assignee: Mayank Jain
> [Atlas: Glossary Term Bulk Import]: Bulk import fails with AtlasBaseException
> -
>
> Key: ATLAS-4160
> URL: https://issues.apache.org/jira/browse/ATLAS-4160
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
>
> h4. Description
> Bulk import fails with error message:
> *org.apache.atlas.exception.AtlasBaseException: Glossary term with
> qualifiedName brZd_1@gloss_123_1 already exists*
> though, there is no such term already present
> {code:java}
> 2021-02-17 08:25:55,036 ERROR - [etp823723302-197 -
> 997d7198-a7af-4cf1-97ae-93b7bfec07b8:] ~ Error handling a request:
> 6981164eb7efbced (ExceptionMapperUtil:32)
> org.apache.atlas.exception.AtlasBaseException: Error occurred while creating
> glossary term: {0}
> at
> org.apache.atlas.glossary.GlossaryService.createGlossaryTerms(GlossaryService.java:1107)
> at
> org.apache.atlas.glossary.GlossaryService.importGlossaryData(GlossaryService.java:1092)
> at
> org.apache.atlas.glossary.GlossaryService$$FastClassBySpringCGLIB$$e1f893e0.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:668)
> at
> org.apache.atlas.glossary.GlossaryService$$EnhancerBySpringCGLIB$$f33e53e3.importGlossaryData()
> at
> org.apache.atlas.web.rest.GlossaryREST.importGlossaryData(GlossaryREST.java:988)
> at sun.reflect.GeneratedMethodAccessor643.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.eclipse.jetty.servlet.ServletHolder$NotAsyncServlet.service(ServletHolder.java:1411)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:763)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1651)
> at
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:106)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1638)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
> at
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:127)
> at
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:91)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
>
[jira] [Assigned] (ATLAS-4131) [Atlas: Glossary Term Bulk Import] Incorrect input has to be reported as Client side error instead of server side error
[
https://issues.apache.org/jira/browse/ATLAS-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-4131:
--
Assignee: Mayank Jain
> [Atlas: Glossary Term Bulk Import] Incorrect input has to be reported as
> Client side error instead of server side error
> ---
>
> Key: ATLAS-4131
> URL: https://issues.apache.org/jira/browse/ATLAS-4131
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
> Attachments: Screenshot 2021-01-28 at 11.55.36 AM.png
>
>
> In the below payload, incorrect input is given and ideally it has to be
> reported as 400 bad input error [Client error], but it is thrown as 500 error
> [Server error]
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> gloss_1,term_1
> gloss_1,term_1
> gloss_2,term_2
> gloss_3,term_3 {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4106) Adding Debug metrics to atlas.
Mayank Jain created ATLAS-4106: -- Summary: Adding Debug metrics to atlas. Key: ATLAS-4106 URL: https://issues.apache.org/jira/browse/ATLAS-4106 Project: Atlas Issue Type: New Feature Reporter: Mayank Jain Assignee: Mayank Jain This is a new feature added to atlas to create a ease for keeping track of certain highly used api's in atlas , so at the time of evaluating the performance of certain API we could have our data ready. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3359) Relationships : Unique attribute in a relationship is not honored
[ https://issues.apache.org/jira/browse/ATLAS-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain reassigned ATLAS-3359: -- Assignee: Mayank Jain (was: Radhika Kundam) > Relationships : Unique attribute in a relationship is not honored > - > > Key: ATLAS-3359 > URL: https://issues.apache.org/jira/browse/ATLAS-3359 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Nixon Rodrigues >Assignee: Mayank Jain >Priority: Major > Fix For: 2.2.0 > > Attachments: > ATLAS-3359-Relationships-Unique-attribute-in-a-relat-3.patch > > > 1.Created a relationship typedef between type1 & type2 with attribute "attr1" > which is unique (set "IsUnique" to true). > 2. Created entity1 (type1) and entity2(type2) and created a relationship > instance between them with "attr1" value , say "value1". > 3. Created entity3 (type1) and entity4(type2) and created a relationship > instance between them with "attr1" value with the same value "value1". > Expected the relationship creation between entity3 and entity4 would fail > because a relationship with "attr1 " with "value1" is already created between > entity1 and entity2. But request passed and the relationship is created > successfully. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3359) Relationships : Unique attribute in a relationship is not honored
[ https://issues.apache.org/jira/browse/ATLAS-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3359: --- Attachment: ATLAS-3359-Relationships-Unique-attribute-in-a-relat-3.patch > Relationships : Unique attribute in a relationship is not honored > - > > Key: ATLAS-3359 > URL: https://issues.apache.org/jira/browse/ATLAS-3359 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Nixon Rodrigues >Assignee: Radhika Kundam >Priority: Major > Fix For: 2.2.0 > > Attachments: > ATLAS-3359-Relationships-Unique-attribute-in-a-relat-3.patch > > > 1.Created a relationship typedef between type1 & type2 with attribute "attr1" > which is unique (set "IsUnique" to true). > 2. Created entity1 (type1) and entity2(type2) and created a relationship > instance between them with "attr1" value , say "value1". > 3. Created entity3 (type1) and entity4(type2) and created a relationship > instance between them with "attr1" value with the same value "value1". > Expected the relationship creation between entity3 and entity4 would fail > because a relationship with "attr1 " with "value1" is already created between > entity1 and entity2. But request passed and the relationship is created > successfully. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3920) Harmonize joda-time to version 2.10.latest
Mayank Jain created ATLAS-3920: -- Summary: Harmonize joda-time to version 2.10.latest Key: ATLAS-3920 URL: https://issues.apache.org/jira/browse/ATLAS-3920 Project: Atlas Issue Type: Bug Reporter: Mayank Jain Atlas currently uses outdated joda-time versions, which can cause issues. To avoid issue we need to update it to the latest version of joda-time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3853) Error while creating enum Attribute with special characters.
[
https://issues.apache.org/jira/browse/ATLAS-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain updated ATLAS-3853:
---
Description:
_The issue :_
The enumValue which we assigned ">" has double quotes in it.the
janusgraph's class SystemTypeManager.java has RESERVED_CHARS = new char[]{'
{', '}
', '"', '\u001e'}; into it.
_How to reproduce it ? Steps to reproduce :_
Step 1 : Create an enum e.g enumXSS.
Step 2 : create a classification with some attribute of type enumXSS.
Step 3 : Assign a value for this attribute with ">"Now this will result into an error with
500 saying "Something went wrong"
_Approach for resolving this :_
As the janusgraph has this check for special characters and our enumValue has
that double quotes in it it throws an illelagalArgumentException.
Now at Atlas end we are not handling the unexpected exception so we just have
to catch the Exception and throw it with proper error code and error-message
which helps user to understand the issue properly.And for that i have provided
the patch on RR.
Stack-trace:-
{noformat}
2020-06-19 17:05:32,390 ERROR - [pool-2-thread-7 -
37492d4b-63b4-4189-89c3-329b0566ae74:]
~ graph rollback due to exception (GraphTransactionInterceptor:167)
java.lang.IllegalArgumentException: Name contains reserved character ":
__type.edge.classitest.">
at
com.google.common.base.Preconditions.checkArgument(Preconditions.java:163)
at
org.janusgraph.graphdb.types.system.SystemTypeManager.throwIfSystemName(SystemTypeManager.java:74)
at
org.janusgraph.graphdb.types.StandardRelationTypeMaker.name(StandardRelationTypeMaker.java:181)
at
org.janusgraph.graphdb.types.StandardRelationTypeMaker.(StandardRelationTypeMaker.java:53)
at
org.janusgraph.graphdb.types.StandardEdgeLabelMaker.(StandardEdgeLabelMaker.java:41)
at
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.makeEdgeLabel(StandardJanusGraphTx.java:1052)
at
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.getOrCreateEdgeLabel(StandardJanusGraphTx.java:1038)
at
org.janusgraph.graphdb.vertices.AbstractVertex.addEdge(AbstractVertex.java:167)
at
org.janusgraph.graphdb.vertices.AbstractVertex.addEdge(AbstractVertex.java:37)
at
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.addEdge(AtlasJanusGraph.java:147)
at
org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.addEdge(AtlasTypeDefGraphStoreV2.java:395)
at
org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.getOrCreateEdge(AtlasTypeDefGraphStoreV2.java:387)
at
org.apache.atlas.repository.store.graph.v2.AtlasStructDefStoreV2.addReferencesForAttribute(AtlasStructDefStoreV2.java:523)
at
org.apache.atlas.repository.store.graph.v2.AtlasStructDefStoreV2.updateVertexAddReferences(AtlasStructDefStoreV2.java:471)
at
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.updateVertexAddReferences(AtlasClassificationDefStoreV2.java:338)
at
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.updateByGuid(AtlasClassificationDefStoreV2.java:254)
at
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.update(AtlasClassificationDefStoreV2.java:183)
at
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.update(AtlasClassificationDefStoreV2.java:48)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateGraphStore(AtlasTypeDefGraphStore.java:1029)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateTypesDef(AtlasTypeDefGraphStore.java:481)
{noformat}
was:
The issue :
The enumValue which we assigned ">" has double quotes in it.the
janusgraph's class SystemTypeManager.java has RESERVED_CHARS = new char[]\{'{',
'}', '"', '\u001e'}; into it.
How to reproduce it ? Steps to reproduce :
Step 1 : Create an enum e.g enumXSS.Step 2 : create a classification with some
attribute of type enumXSS.Step 3 : Assign a value for this attribute with
">"Now this will result into an
error with 500 saying "Something went wrong"
Approach for resolving this :
As the janusgraph has this check for special characters and our enumValue has
that double quotes in it it throws an illelagalArgumentException.
Now at Atlas end we are not handling the unexpected exception so we just have
to catch the Exception and throw it with proper error code and error-message
which helps user to understand the issue properly.And for that i have provided
the patch on RR.
Stack-trace:-
{noformat}
2020-06-19 17:05:32,390 ERROR - [pool-2-thread-7 -
37492d4b-63b4-4189-89c3-329b0566ae74:]
~ graph rollback due to exception (GraphTransactionInterceptor:167)
java.lang.IllegalArgumentException: Name contains reserved character ":
__type.edge.classitest.">
[jira] [Updated] (ATLAS-3853) Error while creating enum Attribute with special characters.
[
https://issues.apache.org/jira/browse/ATLAS-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain updated ATLAS-3853:
---
Description:
The issue :
The enumValue which we assigned ">" has double quotes in it.the
janusgraph's class SystemTypeManager.java has RESERVED_CHARS = new char[]\{'{',
'}', '"', '\u001e'}; into it.
How to reproduce it ? Steps to reproduce :
Step 1 : Create an enum e.g enumXSS.Step 2 : create a classification with some
attribute of type enumXSS.Step 3 : Assign a value for this attribute with
">"Now this will result into an
error with 500 saying "Something went wrong"
Approach for resolving this :
As the janusgraph has this check for special characters and our enumValue has
that double quotes in it it throws an illelagalArgumentException.
Now at Atlas end we are not handling the unexpected exception so we just have
to catch the Exception and throw it with proper error code and error-message
which helps user to understand the issue properly.And for that i have provided
the patch on RR.
Stack-trace:-
{noformat}
2020-06-19 17:05:32,390 ERROR - [pool-2-thread-7 -
37492d4b-63b4-4189-89c3-329b0566ae74:]
~ graph rollback due to exception (GraphTransactionInterceptor:167)
java.lang.IllegalArgumentException: Name contains reserved character ":
__type.edge.classitest.">
at
com.google.common.base.Preconditions.checkArgument(Preconditions.java:163)
at
org.janusgraph.graphdb.types.system.SystemTypeManager.throwIfSystemName(SystemTypeManager.java:74)
at
org.janusgraph.graphdb.types.StandardRelationTypeMaker.name(StandardRelationTypeMaker.java:181)
at
org.janusgraph.graphdb.types.StandardRelationTypeMaker.(StandardRelationTypeMaker.java:53)
at
org.janusgraph.graphdb.types.StandardEdgeLabelMaker.(StandardEdgeLabelMaker.java:41)
at
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.makeEdgeLabel(StandardJanusGraphTx.java:1052)
at
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.getOrCreateEdgeLabel(StandardJanusGraphTx.java:1038)
at
org.janusgraph.graphdb.vertices.AbstractVertex.addEdge(AbstractVertex.java:167)
at
org.janusgraph.graphdb.vertices.AbstractVertex.addEdge(AbstractVertex.java:37)
at
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.addEdge(AtlasJanusGraph.java:147)
at
org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.addEdge(AtlasTypeDefGraphStoreV2.java:395)
at
org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.getOrCreateEdge(AtlasTypeDefGraphStoreV2.java:387)
at
org.apache.atlas.repository.store.graph.v2.AtlasStructDefStoreV2.addReferencesForAttribute(AtlasStructDefStoreV2.java:523)
at
org.apache.atlas.repository.store.graph.v2.AtlasStructDefStoreV2.updateVertexAddReferences(AtlasStructDefStoreV2.java:471)
at
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.updateVertexAddReferences(AtlasClassificationDefStoreV2.java:338)
at
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.updateByGuid(AtlasClassificationDefStoreV2.java:254)
at
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.update(AtlasClassificationDefStoreV2.java:183)
at
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.update(AtlasClassificationDefStoreV2.java:48)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateGraphStore(AtlasTypeDefGraphStore.java:1029)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateTypesDef(AtlasTypeDefGraphStore.java:481)
{noformat}
was:
I had created an enum with some value in it, and a classification
ClassificationTest1, now while i was adding an attribute to my
ClassificationTest1 the value i assigne the enumValue was
">
and instead of throwing some kind of error message the application threw
"Something went wrong" with 500 error code.
The end user in such scenario won't be able to identify what exactly went wrong.
Stacktrace:-
{noformat}
2020-06-19 17:05:32,390 ERROR - [pool-2-thread-7 -
37492d4b-63b4-4189-89c3-329b0566ae74:]
~ graph rollback due to exception (GraphTransactionInterceptor:167)
java.lang.IllegalArgumentException: Name contains reserved character ":
__type.edge.classitest.">
at
com.google.common.base.Preconditions.checkArgument(Preconditions.java:163)
at
org.janusgraph.graphdb.types.system.SystemTypeManager.throwIfSystemName(SystemTypeManager.java:74)
at
org.janusgraph.graphdb.types.StandardRelationTypeMaker.name(StandardRelationTypeMaker.java:181)
at
org.janusgraph.graphdb.types.StandardRelationTypeMaker.(StandardRelationTypeMaker.java:53)
at
org.janusgraph.graphdb.types.StandardEdgeLabelMaker.(StandardEdgeLabelMaker.java:41)
at
[jira] [Updated] (ATLAS-3853) Error while creating enum Attribute with special characters.
[ https://issues.apache.org/jira/browse/ATLAS-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3853: --- Attachment: errorStackTrace.txt > Error while creating enum Attribute with special characters. > > > Key: ATLAS-3853 > URL: https://issues.apache.org/jira/browse/ATLAS-3853 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > Attachments: errorStackTrace.txt > > > I had created an enum with some value in it, and a classification > ClassificationTest1, now while i was adding an attribute to my > ClassificationTest1 the value i assigne the enumValue was > "> > and instead of throwing some kind of error message the application threw > "Something went wrong" with 500 error code. > The end user in such scenario won't be able to identify what exactly went > wrong. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3853) Error while creating enum Attribute with special characters.
[ https://issues.apache.org/jira/browse/ATLAS-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3853: --- Description: I had created an enum with some value in it, and a classification ClassificationTest1, now while i was adding an attribute to my ClassificationTest1 the value i assigne the enumValue was "> and instead of throwing some kind of error message the application threw "Something went wrong" with 500 error code. The end user in such scenario won't be able to identify what exactly went wrong. was:While trying to assign an enum as attribute for a classification in Atlas the Application threw Something went wrong. > Error while creating enum Attribute with special characters. > > > Key: ATLAS-3853 > URL: https://issues.apache.org/jira/browse/ATLAS-3853 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > > I had created an enum with some value in it, and a classification > ClassificationTest1, now while i was adding an attribute to my > ClassificationTest1 the value i assigne the enumValue was > "> > and instead of throwing some kind of error message the application threw > "Something went wrong" with 500 error code. > The end user in such scenario won't be able to identify what exactly went > wrong. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3853) Error while creating enum Attribute with special characters.
[ https://issues.apache.org/jira/browse/ATLAS-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain reassigned ATLAS-3853: -- Assignee: Mayank Jain > Error while creating enum Attribute with special characters. > > > Key: ATLAS-3853 > URL: https://issues.apache.org/jira/browse/ATLAS-3853 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > > While trying to assign an enum as attribute for a classification in Atlas the > Application threw Something went wrong. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3853) Error while creating enum Attribute with special characters.
Mayank Jain created ATLAS-3853: -- Summary: Error while creating enum Attribute with special characters. Key: ATLAS-3853 URL: https://issues.apache.org/jira/browse/ATLAS-3853 Project: Atlas Issue Type: Bug Reporter: Mayank Jain While trying to assign an enum as attribute for a classification in Atlas the Application threw Something went wrong. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3784) Issues with Import business metadata
[ https://issues.apache.org/jira/browse/ATLAS-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain reassigned ATLAS-3784: -- Assignee: Mayank Jain > Issues with Import business metadata > > > Key: ATLAS-3784 > URL: https://issues.apache.org/jira/browse/ATLAS-3784 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Mayank Jain >Priority: Major > > 1. It is possible to to assign BM values to deleted entities by specifying > the qualified name of the deleted entity in the imported file > 2. Import through xls/xlsx doesn't work, getting an > java.lang.IllegalStateException: Cannot get a STRING value from a NUMERIC > cell in application.log > 3. If a multi-valued attribute is assigned the string '|', the attribute is > assigned a blank value (ideally in this scenario, Atlas should throw an error) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3768) Business Metadata import issue with extra commas csv file
[
https://issues.apache.org/jira/browse/ATLAS-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-3768:
--
Assignee: Mayank Jain
> Business Metadata import issue with extra commas csv file
> -
>
> Key: ATLAS-3768
> URL: https://issues.apache.org/jira/browse/ATLAS-3768
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Mayank Jain
>Priority: Minor
>
> If a csv file contains an extra comma(which gets inserted automatically at
> the end of the file after editing and saving the file in a program like
> Libreoffice Calc) and is then imported, it throws the error
> {code:java}
> "Provided UniqueAttributeValue is not valid.at line #1"{code}
> which is an invalid error message and doesn't inform the user as to what the
> error actually is.
> It should point to the extra comma in the error message, or the extra comma
> should be handled.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-3779) Inmemory JAASConfig issue in Atlas
[
https://issues.apache.org/jira/browse/ATLAS-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-3779:
--
Assignee: Mayank Jain
> Inmemory JAASConfig issue in Atlas
> --
>
> Key: ATLAS-3779
> URL: https://issues.apache.org/jira/browse/ATLAS-3779
> Project: Atlas
> Issue Type: Bug
>Reporter: Mayank Jain
>Assignee: Mayank Jain
>Priority: Major
>
> Spark uses Kafka as source and sink in secure cluster. The test creates a
> JAAS file like this:
> {code:java}
> KafkaClient {
> com.sun.security.auth.module.Krb5LoginModule required
> debug=true
> useKeyTab=true
> storeKey=true
> keyTab="/xxx/keytabs/systest.keytab"
> useTicketCache=false
> serviceName="kafka"
> principal="syst...@gce.example.com";
> };
> {code}
> As one can see serviceName is set properly.
> Then the test pass the JAAS file to Spark's driver + executor as well:
> {code:java}
> "--conf
> \"spark.driver.extraJavaOptions=-Djava.security.auth.login.config=./kafka_source_jaas.conf..."
> "--conf
> \"spark.executor.extraJavaOptions=-Djava.security.auth.login.config=./kafka_source_jaas.conf..."
> {code}
> Later on SAC + atlas makes some magic in the background with the Jvm JAAS
> configuration. As a result Spark is not able to create consumer for
> processing data:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: No serviceName defined in
> either JAAS or Kafka config
> {code}
> When I've turned off SAC then all the problem gone away.
> Atlas replaces the JVM global JAAS configuration with
> InMemoryJAASConfiguration once Atlas configuration is initialized.
> InMemoryJAASConfiguration has an old JAAS config as "parent" but Atlas config
> takes precedence which is unexpected.
> We never want to let Atlas to overwrite existing JAAS configuration if
> there's a conflict. (I believe most endpoints using Atlas client as a library
> would agree with this.) This may be achieved via swapping precedence for
> "parent" vs "Atlas config" in InMemoryJAASConfiguration, but I have no idea
> the change would be safe to Atlas side. In any way, Atlas should at least
> provide a config to let "parent" take precedence for the conflict.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-3779) Inmemory JAASConfig issue in Atlas
Mayank Jain created ATLAS-3779:
--
Summary: Inmemory JAASConfig issue in Atlas
Key: ATLAS-3779
URL: https://issues.apache.org/jira/browse/ATLAS-3779
Project: Atlas
Issue Type: Bug
Reporter: Mayank Jain
Spark uses Kafka as source and sink in secure cluster. The test creates a JAAS
file like this:
{code:java}
KafkaClient {
com.sun.security.auth.module.Krb5LoginModule required
debug=true
useKeyTab=true
storeKey=true
keyTab="/cdep/keytabs/systest.keytab"
useTicketCache=false
serviceName="kafka"
principal="syst...@gce.cloudera.com";
};
{code}
As one can see serviceName is set properly.
Then the test pass the JAAS file to Spark's driver + executor as well:
{code:java}
"--conf
\"spark.driver.extraJavaOptions=-Djava.security.auth.login.config=./kafka_source_jaas.conf..."
"--conf
\"spark.executor.extraJavaOptions=-Djava.security.auth.login.config=./kafka_source_jaas.conf..."
{code}
Later on SAC + atlas makes some magic in the background with the Jvm JAAS
configuration. As a result Spark is not able to create consumer for processing
data:
{code:java}
Caused by: java.lang.IllegalArgumentException: No serviceName defined in either
JAAS or Kafka config
{code}
When I've turned off SAC then all the problem gone away.
Atlas replaces the JVM global JAAS configuration with InMemoryJAASConfiguration
once Atlas configuration is initialized. InMemoryJAASConfiguration has an old
JAAS config as "parent" but Atlas config takes precedence which is unexpected.
We never want to let Atlas to overwrite existing JAAS configuration if there's
a conflict. (I believe most endpoints using Atlas client as a library would
agree with this.) This may be achieved via swapping precedence for "parent" vs
"Atlas config" in InMemoryJAASConfiguration, but I have no idea the change
would be safe to Atlas side. In any way, Atlas should at least provide a config
to let "parent" take precedence for the conflict.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-3698) Update Response for Bulk import's in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain reassigned ATLAS-3698: -- Assignee: Mayank Jain > Update Response for Bulk import's in Atlas > -- > > Key: ATLAS-3698 > URL: https://issues.apache.org/jira/browse/ATLAS-3698 > Project: Atlas > Issue Type: Improvement >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > > This Jira is regarding an improvement in providing response for Bulk imports > in Atlas , > the basic idea was to create the response more user friendly by providing > appropriate and understandable response to the end user. > E.g : If the user uploads a csv/excel file with 15 records out of which 10 > records got updated and 5 didn't then we tend to maintain a separate list for > both successful as well as Failed records. > Also the Failed records would have the msgs addressing why the records didn't > got uploaded i.e what exactly went wrong using which the user can make > appropriate changes and do a re-upload. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3698) Update Response for Bulk import's in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3698: --- Description: This Jira is regarding an improvement in providing response for Bulk imports in Atlas , the basic idea was to create the response more user friendly by providing appropriate and understandable response to the end user. E.g : If the user uploads a csv/excel file with 15 records out of which 10 records got updated and 5 didn't then we tend to maintain a separate list for both successful as well as Failed records. Also the Failed records would have the msgs addressing why the records didn't got uploaded i.e what exactly went wrong using which the user can make appropriate changes and do a re-upload. > Update Response for Bulk import's in Atlas > -- > > Key: ATLAS-3698 > URL: https://issues.apache.org/jira/browse/ATLAS-3698 > Project: Atlas > Issue Type: Improvement >Reporter: Mayank Jain >Priority: Major > > This Jira is regarding an improvement in providing response for Bulk imports > in Atlas , > the basic idea was to create the response more user friendly by providing > appropriate and understandable response to the end user. > E.g : If the user uploads a csv/excel file with 15 records out of which 10 > records got updated and 5 didn't then we tend to maintain a separate list for > both successful as well as Failed records. > Also the Failed records would have the msgs addressing why the records didn't > got uploaded i.e what exactly went wrong using which the user can make > appropriate changes and do a re-upload. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3698) Update Response for Bulk import's in Atlas
Mayank Jain created ATLAS-3698: -- Summary: Update Response for Bulk import's in Atlas Key: ATLAS-3698 URL: https://issues.apache.org/jira/browse/ATLAS-3698 Project: Atlas Issue Type: Improvement Reporter: Mayank Jain -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3423) Import Glossary Terms CSV into a Glossary
[ https://issues.apache.org/jira/browse/ATLAS-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17065316#comment-17065316 ] Mayank Jain commented on ATLAS-3423: Updated the patch for Test cases Fix. > Import Glossary Terms CSV into a Glossary > - > > Key: ATLAS-3423 > URL: https://issues.apache.org/jira/browse/ATLAS-3423 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: Nixon Rodrigues >Assignee: Mayank Jain >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3423-1-Test-Cases-Fix.patch, ATLAS-3423-22.patch > > > As a data steward, I would like to be able to glossary terms in bulk from an > appropriately formatted CSV/XLS template (which includes all the relevant > properties pertaining to a glossary term) and import it into Atlas directly > from Atlas UI. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3423) Import Glossary Terms CSV into a Glossary
[ https://issues.apache.org/jira/browse/ATLAS-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3423: --- Attachment: ATLAS-3423-1-Test-Cases-Fix.patch > Import Glossary Terms CSV into a Glossary > - > > Key: ATLAS-3423 > URL: https://issues.apache.org/jira/browse/ATLAS-3423 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: Nixon Rodrigues >Assignee: Mayank Jain >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3423-1-Test-Cases-Fix.patch, ATLAS-3423-22.patch > > > As a data steward, I would like to be able to glossary terms in bulk from an > appropriately formatted CSV/XLS template (which includes all the relevant > properties pertaining to a glossary term) and import it into Atlas directly > from Atlas UI. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3423) Import Glossary Terms CSV into a Glossary
[ https://issues.apache.org/jira/browse/ATLAS-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3423: --- Attachment: (was: ATLAS-3423-19.patch) > Import Glossary Terms CSV into a Glossary > - > > Key: ATLAS-3423 > URL: https://issues.apache.org/jira/browse/ATLAS-3423 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: Nixon Rodrigues >Assignee: Mayank Jain >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3423-1-Test-Cases-Fix.patch, ATLAS-3423-22.patch > > > As a data steward, I would like to be able to glossary terms in bulk from an > appropriately formatted CSV/XLS template (which includes all the relevant > properties pertaining to a glossary term) and import it into Atlas directly > from Atlas UI. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3679) Bulk import Business Metadata attribute assignment to entities
[ https://issues.apache.org/jira/browse/ATLAS-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain reassigned ATLAS-3679: -- Assignee: Mayank Jain > Bulk import Business Metadata attribute assignment to entities > -- > > Key: ATLAS-3679 > URL: https://issues.apache.org/jira/browse/ATLAS-3679 > Project: Atlas > Issue Type: Improvement >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3679) Bulk import Business Metadata attribute assignment to entities
Mayank Jain created ATLAS-3679: -- Summary: Bulk import Business Metadata attribute assignment to entities Key: ATLAS-3679 URL: https://issues.apache.org/jira/browse/ATLAS-3679 Project: Atlas Issue Type: Improvement Reporter: Mayank Jain -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3423) Import Glossary Terms CSV into a Glossary
[ https://issues.apache.org/jira/browse/ATLAS-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3423: --- Attachment: ATLAS-3423-19.patch > Import Glossary Terms CSV into a Glossary > - > > Key: ATLAS-3423 > URL: https://issues.apache.org/jira/browse/ATLAS-3423 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Affects Versions: 3.0.0 >Reporter: Nixon Rodrigues >Assignee: Mayank Jain >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3423-19.patch > > > As a data steward, I would like to be able to glossary terms in bulk from an > appropriately formatted CSV/XLS template (which includes all the relevant > properties pertaining to a glossary term) and import it into Atlas directly > from Atlas UI. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3423) Import Glossary Terms CSV into a Glossary
[ https://issues.apache.org/jira/browse/ATLAS-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3423: --- Attachment: (was: ATLAS-3423-7.patch) > Import Glossary Terms CSV into a Glossary > - > > Key: ATLAS-3423 > URL: https://issues.apache.org/jira/browse/ATLAS-3423 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Affects Versions: 3.0.0 >Reporter: Nixon Rodrigues >Assignee: Mayank Jain >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3423-19.patch > > > As a data steward, I would like to be able to glossary terms in bulk from an > appropriately formatted CSV/XLS template (which includes all the relevant > properties pertaining to a glossary term) and import it into Atlas directly > from Atlas UI. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3423) Import Glossary Terms CSV into a Glossary
[ https://issues.apache.org/jira/browse/ATLAS-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3423: --- Attachment: (was: ATLAS-3423-1.patch) > Import Glossary Terms CSV into a Glossary > - > > Key: ATLAS-3423 > URL: https://issues.apache.org/jira/browse/ATLAS-3423 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Affects Versions: 3.0.0 >Reporter: Nixon Rodrigues >Assignee: Mayank Jain >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3423-7.patch > > > As a data steward, I would like to be able to glossary terms in bulk from an > appropriately formatted CSV/XLS template (which includes all the relevant > properties pertaining to a glossary term) and import it into Atlas directly > from Atlas UI. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3647) System attribute search : isIncomplete attribute has 1,null as values
[ https://issues.apache.org/jira/browse/ATLAS-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3647: --- Attachment: ATLAS-3467-2.patch > System attribute search : isIncomplete attribute has 1,null as values > - > > Key: ATLAS-3647 > URL: https://issues.apache.org/jira/browse/ATLAS-3647 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > Attachments: ATLAS-3467-2.patch > > > In entity definition , > isIncomplete is null when is entity is complete > isIncomplete is 1 when is entity is incomplete (shell/ghost entities) > when isIncomplete = false is expected to return all complete entities > (non-shell entities) but since isIncomplete is null , it doesn't return any > entity. > In system attributes search, > isIncomplete takes conditions =, != , not null , null with values true , > false. > IMHO , it could have only = , != with true,false > Hence issues are : > 1. Backend : IsIncomplete to have value as 0 when the entity is complete. > 2. UI : Search attribute for IsIncomplete to remove "is null" and "is not > null" checks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3651) Metrics API: Count of entities for a type doesn't include entities of sub type
[ https://issues.apache.org/jira/browse/ATLAS-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain reassigned ATLAS-3651: -- Assignee: Mayank Jain > Metrics API: Count of entities for a type doesn't include entities of sub type > -- > > Key: ATLAS-3651 > URL: https://issues.apache.org/jira/browse/ATLAS-3651 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > > DataSet count shown in Basic/DSL Search doesn't include the count of entities > of its subtypes. If an entity is created as a DataSet then the count is > updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3651) Metrics API: Count of entities for a type doesn't include entities of sub type
Mayank Jain created ATLAS-3651: -- Summary: Metrics API: Count of entities for a type doesn't include entities of sub type Key: ATLAS-3651 URL: https://issues.apache.org/jira/browse/ATLAS-3651 Project: Atlas Issue Type: Bug Reporter: Mayank Jain DataSet count shown in Basic/DSL Search doesn't include the count of entities of its subtypes. If an entity is created as a DataSet then the count is updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3647) System attribute search : isIncomplete attribute has 1,null as values
[ https://issues.apache.org/jira/browse/ATLAS-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain reassigned ATLAS-3647: -- Assignee: Mayank Jain > System attribute search : isIncomplete attribute has 1,null as values > - > > Key: ATLAS-3647 > URL: https://issues.apache.org/jira/browse/ATLAS-3647 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > > In entity definition , > isIncomplete is null when is entity is complete > isIncomplete is 1 when is entity is incomplete (shell/ghost entities) > when isIncomplete = false is expected to return all complete entities > (non-shell entities) but since isIncomplete is null , it doesn't return any > entity. > In system attributes search, > isIncomplete takes conditions =, != , not null , null with values true , > false. > IMHO , it could have only = , != with true,false > Hence issues are : > 1. Backend : IsIncomplete to have value as 0 when the entity is complete. > 2. UI : Search attribute for IsIncomplete to remove "is null" and "is not > null" checks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3647) System attribute search : isIncomplete attribute has 1,null as values
Mayank Jain created ATLAS-3647: -- Summary: System attribute search : isIncomplete attribute has 1,null as values Key: ATLAS-3647 URL: https://issues.apache.org/jira/browse/ATLAS-3647 Project: Atlas Issue Type: Bug Reporter: Mayank Jain In entity definition , isIncomplete is null when is entity is complete isIncomplete is 1 when is entity is incomplete (shell/ghost entities) when isIncomplete = false is expected to return all complete entities (non-shell entities) but since isIncomplete is null , it doesn't return any entity. In system attributes search, isIncomplete takes conditions =, != , not null , null with values true , false. IMHO , it could have only = , != with true,false Hence issues are : 1. Backend : IsIncomplete to have value as 0 when the entity is complete. 2. UI : Search attribute for IsIncomplete to remove "is null" and "is not null" checks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3600) The System Attribute feature does not support Classification search in it.
[ https://issues.apache.org/jira/browse/ATLAS-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3600: --- Summary: The System Attribute feature does not support Classification search in it. (was: The System Attribute enhancement does not support Classification search in it.) > The System Attribute feature does not support Classification search in it. > -- > > Key: ATLAS-3600 > URL: https://issues.apache.org/jira/browse/ATLAS-3600 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Priority: Major > > The new enhancement of System Attributes does not support's following 4 > search , > # classification search > # Propogated Classification Search > # User-Defined Attributes > # Labels -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3600) The System Attribute enhancement doest not support's Classification search in it.
[ https://issues.apache.org/jira/browse/ATLAS-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3600: --- Description: The new enhancement of System Attributes does not support's following 4 search , # classification search # Propogated Classification Search # User-Defined Attributes # Labels was: The new enhancement of System Attributes does not support's following 4 search , 1. classification search > The System Attribute enhancement doest not support's Classification search in > it. > - > > Key: ATLAS-3600 > URL: https://issues.apache.org/jira/browse/ATLAS-3600 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Priority: Major > > The new enhancement of System Attributes does not support's following 4 > search , > # classification search > # Propogated Classification Search > # User-Defined Attributes > # Labels -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3600) The System Attribute enhancement does not support Classification search in it.
[ https://issues.apache.org/jira/browse/ATLAS-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3600: --- Summary: The System Attribute enhancement does not support Classification search in it. (was: The System Attribute enhancement doest not support's Classification search in it.) > The System Attribute enhancement does not support Classification search in it. > -- > > Key: ATLAS-3600 > URL: https://issues.apache.org/jira/browse/ATLAS-3600 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Priority: Major > > The new enhancement of System Attributes does not support's following 4 > search , > # classification search > # Propogated Classification Search > # User-Defined Attributes > # Labels -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3600) The System Attribute enhancement doest not support's Classification search in it.
Mayank Jain created ATLAS-3600: -- Summary: The System Attribute enhancement doest not support's Classification search in it. Key: ATLAS-3600 URL: https://issues.apache.org/jira/browse/ATLAS-3600 Project: Atlas Issue Type: Bug Reporter: Mayank Jain The new enhancement of System Attributes does not support's following 4 search , 1. classification search -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3254) Atlas entity with large array of refs causes performance issues for lineage
[ https://issues.apache.org/jira/browse/ATLAS-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16998035#comment-16998035 ] Mayank Jain commented on ATLAS-3254: @Team, [^entity_auto_create.sh] I was unable to reproduce the issue as there were no such issues occurring mentioned above,The steps which i followed are mentioned below # Created a cluster with 3 instance and then followed the above mentioned steps . I used a script to create 200k+ entities in a bucket and it took 3 days for its creation and after that if we try to load the bucket and the properties it initially takes time of approx 1 hr 18 mins but after loading the properties were getting loaded properly and did'nt found errors in log or NotificationHookConsumer error as stated above. I have the script file which i used fo creating 200k entitites. Kindly let me know in case i have missed out some thing. > Atlas entity with large array of refs causes performance issues for lineage > --- > > Key: ATLAS-3254 > URL: https://issues.apache.org/jira/browse/ATLAS-3254 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 1.0.0, 2.0.0 >Reporter: Adam Rempter >Assignee: Mayank Jain >Priority: Major > Labels: performance > Attachments: Screenshot 2019-11-28 at 21.18.44.png, > entity_auto_create.sh, example_create_entities.json, > rest_entity_get_pseudodir.json > > > We use “aws_s3_pseudo_dir” type from 3020-aws_s3_typedefs.json model. > It has following property: > "name": "s3Objects", > "typeName": "array" > > Now in AWS buckets you can have thousands of objects. This causes that > s3Objects array grows quite quickly, causing aws_s3_pseudo_dir entity Json to > rich easly few MBs. > > Then we start seeing problems like: > * UI is dying on displaying entity properties or lineage > * Error in logs: audit record too long: entityType=aws_s3_pseudo_dir, > guid=24398271-6ba0-4db5-adfa-38e432dc55ce, size=1053931; maxSize=1048576. > entity attribute values not stored in audit (EntityAuditListenerV2:234) > * Some errors with write to HBase (java.lang.IllegalArgumentException: > KeyValue size too large, as workaround we set hbase.client.keyvalue.maxsize > param to 0) > * kafka consumer errors (we can of course set some parameters on consumer, > but I think it is just workaround) > … > Exception in NotificationHookConsumer (NotificationHookConsumer:332) > org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be > completed since the group has already rebalanced and assigned the partitions > to another member. This means that the time between subsequen > t calls to poll() was longer than the configured max.poll.interval.ms, which > typically implies that the poll loop is spending too much time message > processing. You can address this either by increasing the sessio > n timeout or by reducing the maximum size of batches returned in poll() with > max.poll.records. > … > Specifying pseudo_dir is required for s3objects: > name": "pseudoDirectory", > "typeName": "aws_s3_pseudo_dir", > "cardinality": "SINGLE", > "isIndexable": false, > *"isOptional": false,* > "isUnique": false, > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3254) Atlas entity with large array of refs causes performance issues for lineage
[ https://issues.apache.org/jira/browse/ATLAS-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3254: --- Attachment: entity_auto_create.sh > Atlas entity with large array of refs causes performance issues for lineage > --- > > Key: ATLAS-3254 > URL: https://issues.apache.org/jira/browse/ATLAS-3254 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 1.0.0, 2.0.0 >Reporter: Adam Rempter >Assignee: Mayank Jain >Priority: Major > Labels: performance > Attachments: Screenshot 2019-11-28 at 21.18.44.png, > entity_auto_create.sh, example_create_entities.json, > rest_entity_get_pseudodir.json > > > We use “aws_s3_pseudo_dir” type from 3020-aws_s3_typedefs.json model. > It has following property: > "name": "s3Objects", > "typeName": "array" > > Now in AWS buckets you can have thousands of objects. This causes that > s3Objects array grows quite quickly, causing aws_s3_pseudo_dir entity Json to > rich easly few MBs. > > Then we start seeing problems like: > * UI is dying on displaying entity properties or lineage > * Error in logs: audit record too long: entityType=aws_s3_pseudo_dir, > guid=24398271-6ba0-4db5-adfa-38e432dc55ce, size=1053931; maxSize=1048576. > entity attribute values not stored in audit (EntityAuditListenerV2:234) > * Some errors with write to HBase (java.lang.IllegalArgumentException: > KeyValue size too large, as workaround we set hbase.client.keyvalue.maxsize > param to 0) > * kafka consumer errors (we can of course set some parameters on consumer, > but I think it is just workaround) > … > Exception in NotificationHookConsumer (NotificationHookConsumer:332) > org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be > completed since the group has already rebalanced and assigned the partitions > to another member. This means that the time between subsequen > t calls to poll() was longer than the configured max.poll.interval.ms, which > typically implies that the poll loop is spending too much time message > processing. You can address this either by increasing the sessio > n timeout or by reducing the maximum size of batches returned in poll() with > max.poll.records. > … > Specifying pseudo_dir is required for s3objects: > name": "pseudoDirectory", > "typeName": "aws_s3_pseudo_dir", > "cardinality": "SINGLE", > "isIndexable": false, > *"isOptional": false,* > "isUnique": false, > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3423) Import Glossary Terms CSV into a Glossary
[ https://issues.apache.org/jira/browse/ATLAS-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3423: --- Attachment: ATLAS-3423-7.patch > Import Glossary Terms CSV into a Glossary > - > > Key: ATLAS-3423 > URL: https://issues.apache.org/jira/browse/ATLAS-3423 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Affects Versions: 3.0.0 >Reporter: Nixon Rodrigues >Assignee: Mayank Jain >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3423-1.patch, ATLAS-3423-7.patch > > > As a data steward, I would like to be able to glossary terms in bulk from an > appropriately formatted CSV/XLS template (which includes all the relevant > properties pertaining to a glossary term) and import it into Atlas directly > from Atlas UI. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3254) Atlas entity with large array of refs causes performance issues for lineage
[ https://issues.apache.org/jira/browse/ATLAS-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988821#comment-16988821 ] Mayank Jain commented on ATLAS-3254: [~arempter] / [~bolke] can u please mention the steps to recreate this bug ? > Atlas entity with large array of refs causes performance issues for lineage > --- > > Key: ATLAS-3254 > URL: https://issues.apache.org/jira/browse/ATLAS-3254 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 1.0.0, 2.0.0 >Reporter: Adam Rempter >Assignee: Mayank Jain >Priority: Major > Labels: performance > Attachments: Screenshot 2019-11-28 at 21.18.44.png, > example_create_entities.json, rest_entity_get_pseudodir.json > > > We use “aws_s3_pseudo_dir” type from 3020-aws_s3_typedefs.json model. > It has following property: > "name": "s3Objects", > "typeName": "array" > > Now in AWS buckets you can have thousands of objects. This causes that > s3Objects array grows quite quickly, causing aws_s3_pseudo_dir entity Json to > rich easly few MBs. > > Then we start seeing problems like: > * UI is dying on displaying entity properties or lineage > * Error in logs: audit record too long: entityType=aws_s3_pseudo_dir, > guid=24398271-6ba0-4db5-adfa-38e432dc55ce, size=1053931; maxSize=1048576. > entity attribute values not stored in audit (EntityAuditListenerV2:234) > * Some errors with write to HBase (java.lang.IllegalArgumentException: > KeyValue size too large, as workaround we set hbase.client.keyvalue.maxsize > param to 0) > * kafka consumer errors (we can of course set some parameters on consumer, > but I think it is just workaround) > … > Exception in NotificationHookConsumer (NotificationHookConsumer:332) > org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be > completed since the group has already rebalanced and assigned the partitions > to another member. This means that the time between subsequen > t calls to poll() was longer than the configured max.poll.interval.ms, which > typically implies that the poll loop is spending too much time message > processing. You can address this either by increasing the sessio > n timeout or by reducing the maximum size of batches returned in poll() with > max.poll.records. > … > Specifying pseudo_dir is required for s3objects: > name": "pseudoDirectory", > "typeName": "aws_s3_pseudo_dir", > "cardinality": "SINGLE", > "isIndexable": false, > *"isOptional": false,* > "isUnique": false, > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3254) Atlas entity with large array of refs causes performance issues for lineage
[ https://issues.apache.org/jira/browse/ATLAS-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain reassigned ATLAS-3254: -- Assignee: Mayank Jain (was: Sarath Subramanian) > Atlas entity with large array of refs causes performance issues for lineage > --- > > Key: ATLAS-3254 > URL: https://issues.apache.org/jira/browse/ATLAS-3254 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 1.0.0, 2.0.0 >Reporter: Adam Rempter >Assignee: Mayank Jain >Priority: Major > Labels: performance > Attachments: Screenshot 2019-11-28 at 21.18.44.png, > example_create_entities.json, rest_entity_get_pseudodir.json > > > We use “aws_s3_pseudo_dir” type from 3020-aws_s3_typedefs.json model. > It has following property: > "name": "s3Objects", > "typeName": "array" > > Now in AWS buckets you can have thousands of objects. This causes that > s3Objects array grows quite quickly, causing aws_s3_pseudo_dir entity Json to > rich easly few MBs. > > Then we start seeing problems like: > * UI is dying on displaying entity properties or lineage > * Error in logs: audit record too long: entityType=aws_s3_pseudo_dir, > guid=24398271-6ba0-4db5-adfa-38e432dc55ce, size=1053931; maxSize=1048576. > entity attribute values not stored in audit (EntityAuditListenerV2:234) > * Some errors with write to HBase (java.lang.IllegalArgumentException: > KeyValue size too large, as workaround we set hbase.client.keyvalue.maxsize > param to 0) > * kafka consumer errors (we can of course set some parameters on consumer, > but I think it is just workaround) > … > Exception in NotificationHookConsumer (NotificationHookConsumer:332) > org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be > completed since the group has already rebalanced and assigned the partitions > to another member. This means that the time between subsequen > t calls to poll() was longer than the configured max.poll.interval.ms, which > typically implies that the poll loop is spending too much time message > processing. You can address this either by increasing the sessio > n timeout or by reducing the maximum size of batches returned in poll() with > max.poll.records. > … > Specifying pseudo_dir is required for s3objects: > name": "pseudoDirectory", > "typeName": "aws_s3_pseudo_dir", > "cardinality": "SINGLE", > "isIndexable": false, > *"isOptional": false,* > "isUnique": false, > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3540) Extra audit messages incase of insert/update/delete/truncate operations
[ https://issues.apache.org/jira/browse/ATLAS-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3540: --- Description: As Atlas specifically focuses on meta data and we are getting logs for insert/update/delete/truncate operations of hive tables in atlas which should not be happening. (was: As Atlas specifically focuses on meta data and we are here generating logs for insert/update/delete/truncate operations of hive tables in atlas which should not be happening.) > Extra audit messages incase of insert/update/delete/truncate operations > --- > > Key: ATLAS-3540 > URL: https://issues.apache.org/jira/browse/ATLAS-3540 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > > As Atlas specifically focuses on meta data and we are getting logs for > insert/update/delete/truncate operations of hive tables in atlas which should > not be happening. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3540) Extra audit messages incase of insert/update/delete/truncate operations
[ https://issues.apache.org/jira/browse/ATLAS-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain reassigned ATLAS-3540: -- Assignee: Mayank Jain > Extra audit messages incase of insert/update/delete/truncate operations > --- > > Key: ATLAS-3540 > URL: https://issues.apache.org/jira/browse/ATLAS-3540 > Project: Atlas > Issue Type: Bug >Reporter: Mayank Jain >Assignee: Mayank Jain >Priority: Major > > As Atlas specifically focuses on meta data and we are here generating logs > for insert/update/delete/truncate operations of hive tables in atlas which > should not be happening. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3540) Extra audit messages incase of insert/update/delete/truncate operations
Mayank Jain created ATLAS-3540: -- Summary: Extra audit messages incase of insert/update/delete/truncate operations Key: ATLAS-3540 URL: https://issues.apache.org/jira/browse/ATLAS-3540 Project: Atlas Issue Type: Bug Reporter: Mayank Jain As Atlas specifically focuses on meta data and we are here generating logs for insert/update/delete/truncate operations of hive tables in atlas which should not be happening. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3511) Relationship attributes not forming while creating entities using a bulk entity API request
[
https://issues.apache.org/jira/browse/ATLAS-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-3511:
--
Assignee: Mayank Jain
> Relationship attributes not forming while creating entities using a bulk
> entity API request
> ---
>
> Key: ATLAS-3511
> URL: https://issues.apache.org/jira/browse/ATLAS-3511
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Mayank Jain
>Priority: Major
> Attachments: entity_instance, entity_typedef_1, entity_typedef_2,
> relationship_typedef
>
>
> Steps:
> 1.Create 2 entity types based on the JSON structure (see attached file
> [^entity_typedef_1] and [^entity_typedef_2]) with relationship attributes as
> described in attached file [^relationship_typedef] through a POST request on
> the typedef API ({color:#505050}api/atlas/v2/types/typedefs{color}).
> 2. Create entities with relationship attributes for each of the entity types
> (as described in step 1) through a POST request on the bulk API (see attached
> file [^entity_instance] for reference) ([^relationship_typedef])
> You will observe that the definition of the attributes and the number of
> attributes varies for each of the entities. Hence we are not able to create
> relationship instances using bulk REST API call.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3423) Import Glossary Terms CSV into a Glossary
[ https://issues.apache.org/jira/browse/ATLAS-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3423: --- Fix Version/s: trunk > Import Glossary Terms CSV into a Glossary > - > > Key: ATLAS-3423 > URL: https://issues.apache.org/jira/browse/ATLAS-3423 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Affects Versions: 3.0.0 >Reporter: Nixon Rodrigues >Assignee: Mayank Jain >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3423-1.patch > > > As a data steward, I would like to be able to glossary terms in bulk from an > appropriately formatted CSV/XLS template (which includes all the relevant > properties pertaining to a glossary term) and import it into Atlas directly > from Atlas UI. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3423) Import Glossary Terms CSV into a Glossary
[ https://issues.apache.org/jira/browse/ATLAS-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3423: --- Attachment: ATLAS-3423-1.patch > Import Glossary Terms CSV into a Glossary > - > > Key: ATLAS-3423 > URL: https://issues.apache.org/jira/browse/ATLAS-3423 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Affects Versions: 3.0.0 >Reporter: Nixon Rodrigues >Assignee: Mayank Jain >Priority: Major > Attachments: ATLAS-3423-1.patch > > > As a data steward, I would like to be able to glossary terms in bulk from an > appropriately formatted CSV/XLS template (which includes all the relevant > properties pertaining to a glossary term) and import it into Atlas directly > from Atlas UI. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3383) Relationships : Atlas allows Relationship attributes of Atlas types.
Mayank Jain created ATLAS-3383: -- Summary: Relationships : Atlas allows Relationship attributes of Atlas types. Key: ATLAS-3383 URL: https://issues.apache.org/jira/browse/ATLAS-3383 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Mayank Jain Assignee: Mayank Jain Creation of Relationship typedef with an attribute of type hive_table passes. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (ATLAS-3206) Atlas REST API: Create new attribute in AtlasGlossaryTerm
[
https://issues.apache.org/jira/browse/ATLAS-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayank Jain reassigned ATLAS-3206:
--
Assignee: Mayank Jain
> Atlas REST API: Create new attribute in AtlasGlossaryTerm
> -
>
> Key: ATLAS-3206
> URL: https://issues.apache.org/jira/browse/ATLAS-3206
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: José Nilson dos Santos Júnior
>Assignee: Mayank Jain
>Priority: Major
> Fix For: 1.1.0
>
> Attachments: Create_with_custom_attr.png, POST_v2-glossary-term.txt,
> PUT_v2-glossary-term-termGuid.txt, PUT_v2-types-typedefs.txt,
> atlasglossaryterm-created.png, atlasglossaryterm-updated.png
>
>
> Hi experts,
>
> I have been working with Atlas REST API.
> [http://atlas.apache.org/api/v2/index.html]
>
> I created a new attribute in AtlasGlossaryTerm with the command: See
> {color:#33}*PUT_v2-types-typedefs.txt*{color}
>
> I can not update the values of this new attribute. I tried two ways:
>
> [1] I tried to create a new term with the command: See
> {color:#33}*POST_v2-glossary-term.txt.*{color}
>
> The term is created, however the display is empty. See
> *atlasglossaryterm-created.png*.
>
> [2] I also tried updating the term created: See
> {color:#33}*PUT_v2-glossary-term-termGuid.txt*. {color}
> {color:#33}See *atlasglossaryterm-updated.png*.{color}
>
> How can I solve this?
>
> Thank you.
> Best Regards.
>
> José Nilson
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
