[jira] [Created] (ATLAS-1103) UI: Search type list is not refreshed
Shwetha G S created ATLAS-1103: -- Summary: UI: Search type list is not refreshed Key: ATLAS-1103 URL: https://issues.apache.org/jira/browse/ATLAS-1103 Project: Atlas Issue Type: Bug Reporter: Shwetha G S The list of types fetched for DSL search is done on main page rendering and not when the drop down is clicked. So, if a type is created after the main UI page is opened, the type list is not refreshed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1104) Get outgoing edges by label doesn't work in some cases
Shwetha G S created ATLAS-1104: -- Summary: Get outgoing edges by label doesn't work in some cases Key: ATLAS-1104 URL: https://issues.apache.org/jira/browse/ATLAS-1104 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Assignee: Shwetha G S Priority: Critical In one of the concurrent API scenario of add trait APIs and search API, the edge for add trait was added, but get edge by label doesn't return the edge. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1104) Get outgoing edges by label doesn't work in some cases
[ https://issues.apache.org/jira/browse/ATLAS-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1104: --- Attachment: ATLAS-1104.patch This looks like a titan issue. The patch attached traverses all the edges for now. I will follow up with titan community > Get outgoing edges by label doesn't work in some cases > -- > > Key: ATLAS-1104 > URL: https://issues.apache.org/jira/browse/ATLAS-1104 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S >Priority: Critical > Attachments: ATLAS-1104.patch > > > In one of the concurrent API scenario of add trait APIs and search API, the > edge for add trait was added, but get edge by label doesn't return the edge. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-1104) Get outgoing edges by label doesn't work in some cases
[ https://issues.apache.org/jira/browse/ATLAS-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411658#comment-15411658 ] Shwetha G S edited comment on ATLAS-1104 at 8/8/16 11:00 AM: - This looks like a titan issue. The patch attached traverses all the edges for now. I will follow up with titan community with an example was (Author: shwethags): This looks like a titan issue. The patch attached traverses all the edges for now. I will follow up with titan community > Get outgoing edges by label doesn't work in some cases > -- > > Key: ATLAS-1104 > URL: https://issues.apache.org/jira/browse/ATLAS-1104 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S >Priority: Critical > Fix For: 0.8-incubating > > Attachments: ATLAS-1104.patch > > > In one of the concurrent API scenario of add trait APIs and search API, the > edge for add trait was added, but get edge by label doesn't return the edge. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1104) Get outgoing edges by label doesn't work in some cases
[ https://issues.apache.org/jira/browse/ATLAS-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1104: --- Attachment: ATLAS-1104.patch > Get outgoing edges by label doesn't work in some cases > -- > > Key: ATLAS-1104 > URL: https://issues.apache.org/jira/browse/ATLAS-1104 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S >Priority: Critical > Fix For: 0.8-incubating > > Attachments: ATLAS-1104.patch > > > In one of the concurrent API scenario of add trait APIs and search API, the > edge for add trait was added, but get edge by label doesn't return the edge. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-967) Remove unused logo file and footer.
[ https://issues.apache.org/jira/browse/ATLAS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356895#comment-15356895 ] Shwetha G S commented on ATLAS-967: --- Can you also remove 'Hortonworks' in dashboardv2/package.json? > Remove unused logo file and footer. > --- > > Key: ATLAS-967 > URL: https://issues.apache.org/jira/browse/ATLAS-967 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Hemanth Yamijala >Assignee: Keval Bhatt >Priority: Blocker > Fix For: 0.7-incubating > > > There is an unused footer and icon dashboardv2/public/img/logo-green.png. > This is not used in the UI and hence should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-967) Remove unused logo file and footer.
[ https://issues.apache.org/jira/browse/ATLAS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356902#comment-15356902 ] Shwetha G S commented on ATLAS-967: --- Can you also remove any images not used, don't see any reference to graph.png. > Remove unused logo file and footer. > --- > > Key: ATLAS-967 > URL: https://issues.apache.org/jira/browse/ATLAS-967 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Hemanth Yamijala >Assignee: Keval Bhatt >Priority: Blocker > Fix For: 0.7-incubating > > Attachments: ATLAS-967.patch > > > There is an unused footer and icon dashboardv2/public/img/logo-green.png. > This is not used in the UI and hence should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-962) Include Apache Incubator disclaimer text on website.
[ https://issues.apache.org/jira/browse/ATLAS-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15355260#comment-15355260 ] Shwetha G S commented on ATLAS-962: --- +1 > Include Apache Incubator disclaimer text on website. > > > Key: ATLAS-962 > URL: https://issues.apache.org/jira/browse/ATLAS-962 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > Fix For: 0.7-incubating > > Attachments: ATLAS-962.patch > > > The Apache Incubator disclaimer is required to be included in the website on > the main page as per requirements of the Apache incubation process. Filing > this to make the change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-962) Include Apache Incubator disclaimer text on website.
[ https://issues.apache.org/jira/browse/ATLAS-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15355261#comment-15355261 ] Shwetha G S commented on ATLAS-962: --- +1 > Include Apache Incubator disclaimer text on website. > > > Key: ATLAS-962 > URL: https://issues.apache.org/jira/browse/ATLAS-962 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > Fix For: 0.7-incubating > > Attachments: ATLAS-962.patch > > > The Apache Incubator disclaimer is required to be included in the website on > the main page as per requirements of the Apache incubation process. Filing > this to make the change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (ATLAS-962) Include Apache Incubator disclaimer text on website.
[ https://issues.apache.org/jira/browse/ATLAS-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-962: -- Comment: was deleted (was: +1) > Include Apache Incubator disclaimer text on website. > > > Key: ATLAS-962 > URL: https://issues.apache.org/jira/browse/ATLAS-962 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Hemanth Yamijala > Fix For: 0.7-incubating > > Attachments: ATLAS-962.patch > > > The Apache Incubator disclaimer is required to be included in the website on > the main page as per requirements of the Apache incubation process. Filing > this to make the change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-964) Cleanup NOTICE and LICENSE
Shwetha G S created ATLAS-964:
-
Summary: Cleanup NOTICE and LICENSE
Key: ATLAS-964
URL: https://issues.apache.org/jira/browse/ATLAS-964
Project: Atlas
Issue Type: Bug
Reporter: Shwetha G S
Assignee: Shwetha G S
Priority: Blocker
Fix For: 0.7-incubating
{noformat}
Hi,
We have removed the glyphicons fonts, updated the license and notice to
match the source contents. Will you be able to do a quick check to see if
we are missing anything here:
https://github.com/apache/incubator-atlas/tree/0.7-incubating?
License looks good to me only two very minor things I can see you / may not
want to change:
- No need for the quotes around MIT license or the like. I've seen this done
elsewhere but can't think of a reason for doing so. Rabbit ears / scare quotes
[1] can imply that it's actually not the correct license or that it's a MIT
like license.
- Why not legally required I include the a pointer to the public domain text.
Notice is a bit odd, why have the section "Titan also includes software from
other open source projects including..."? Are these things bundled or just
dependancies? If they are just dependancies there is no need to mention then in
NOTICE, move them to a DEPENDENCIES files if you think it is useful information
to tell the user of the software.
(Feel free to post this to the list for discussion if you want)
Thanks,
Justin
1. https://en.wikipedia.org/wiki/Scare_quotes
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-964) Cleanup NOTICE and LICENSE
[
https://issues.apache.org/jira/browse/ATLAS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-964:
--
Attachment: ATLAS-964.patch
> Cleanup NOTICE and LICENSE
> --
>
> Key: ATLAS-964
> URL: https://issues.apache.org/jira/browse/ATLAS-964
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-964.patch
>
>
> {noformat}
> Hi,
> We have removed the glyphicons fonts, updated the license and notice to
> match the source contents. Will you be able to do a quick check to see if
> we are missing anything here:
> https://github.com/apache/incubator-atlas/tree/0.7-incubating?
> License looks good to me only two very minor things I can see you / may not
> want to change:
> - No need for the quotes around MIT license or the like. I've seen this done
> elsewhere but can't think of a reason for doing so. Rabbit ears / scare
> quotes [1] can imply that it's actually not the correct license or that it's
> a MIT like license.
> - Why not legally required I include the a pointer to the public domain text.
> Notice is a bit odd, why have the section "Titan also includes software from
> other open source projects including..."? Are these things bundled or just
> dependancies? If they are just dependancies there is no need to mention then
> in NOTICE, move them to a DEPENDENCIES files if you think it is useful
> information to tell the user of the software.
> (Feel free to post this to the list for discussion if you want)
> Thanks,
> Justin
> 1. https://en.wikipedia.org/wiki/Scare_quotes
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-961) DataSetLineageJerseyResourceIT.setUp fails
Shwetha G S created ATLAS-961:
-
Summary: DataSetLineageJerseyResourceIT.setUp fails
Key: ATLAS-961
URL: https://issues.apache.org/jira/browse/ATLAS-961
Project: Atlas
Issue Type: Bug
Reporter: Shwetha G S
Assignee: Shwetha G S
mvn clean install -rf :atlas-webapp -Dit.test=DataSetLineageJerseyResourceIT
-DskipUTs
{noformat}
Tests run: 9, Failures: 1, Errors: 0, Skipped: 8, Time elapsed: 3.716 sec <<<
FAILURE! - in org.apache.atlas.web.resources.DataSetLineageJerseyResourceIT
setUp(org.apache.atlas.web.resources.DataSetLineageJerseyResourceIT) Time
elapsed: 3.666 sec <<< FAILURE!
org.apache.atlas.AtlasServiceException: Metadata service API CREATE_ENTITY
failed with status 400(Bad Request) Response Body ({"error":"Unknown datatype:
Fact","stackTrace":"org.apache.atlas.typesystem.exception.TypeNotFoundException:
Unknown datatype: Fact\n\tat
org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:178)\n\tat
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.getDataType(TypeSystem.java:649)\n\tat
org.apache.atlas.typesystem.types.ClassType.createInstanceWithTraits(ClassType.java:182)\n\tat
org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:125)\n\tat
org.apache.atlas.services.DefaultMetadataService.getTypedReferenceableInstance(DefaultMetadataService.java:374)\n\tat
org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:350)\n\tat
org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:331)\n\tat
org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
java.lang.reflect.Method.invoke(Method.java:606)\n\tat
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\tat
com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)\n\tat
com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)\n\tat
com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)\n\tat
com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)\n\tat
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)\n\tat
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)\n\tat
[jira] [Created] (ATLAS-916) Return system attributes in get entity definition
Shwetha G S created ATLAS-916: - Summary: Return system attributes in get entity definition Key: ATLAS-916 URL: https://issues.apache.org/jira/browse/ATLAS-916 Project: Atlas Issue Type: Improvement Reporter: Shwetha G S Atlas should maintain system attributes created time, last modified time, created by user and last modified by user for every entity. This information should be returned in get entity definition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-881) UI: not displaying multiple taxonomies
[
https://issues.apache.org/jira/browse/ATLAS-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-881:
--
Fix Version/s: (was: 0.7-incubating)
> UI: not displaying multiple taxonomies
> --
>
> Key: ATLAS-881
> URL: https://issues.apache.org/jira/browse/ATLAS-881
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Keval Bhatt
>Priority: Critical
>
> UI: not displaying multiple taxonomies
> API response returns multiple taxonomies
> {noformat}
> curl 'http://localhost:21000/api/atlas/v1/taxonomies/' -H 'Cookie:
> JSESSIONID=19eplhd4dz8mueh7466qcbjwf' -H 'Accept-Encoding: gzip, deflate,
> sdch' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: Mozilla/5.0
> (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko)
> Chrome/50.0.2661.102 Safari/537.36' -H 'Accept: application/json,
> text/javascript, */*; q=0.01' -H 'Referer: http://localhost:21000/index.html'
> -H 'X-Requested-With: XMLHttpRequest' -H 'Connection: keep-alive'
> --compressed | python -m json.tool
> % Total% Received % Xferd Average Speed TimeTime Time
> Current
> Dload Upload Total SpentLeft Speed
> 100 3310 3310 0 4096 0 --:--:-- --:--:-- --:--:-- 4137
> [
> {
> "href": "http://localhost:21000/api/atlas/v1/taxonomies/empty;,
> "name": "empty"
> },
> {
> "href": "http://localhost:21000/api/atlas/v1/taxonomies/tax1;,
> "name": "tax1"
> },
> {
> "href": "http://localhost:21000/api/atlas/v1/taxonomies/default;,
> "name": "default"
> }
> ]
> {noformat}
> UI snapshot: https://monosnap.com/file/1M6dOB8D08IPMqkqj3LsCr8VYvXWJG
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-879) Business catalog: Terms are audited as tags.
[ https://issues.apache.org/jira/browse/ATLAS-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-879: -- Fix Version/s: (was: 0.7-incubating) > Business catalog: Terms are audited as tags. > > > Key: ATLAS-879 > URL: https://issues.apache.org/jira/browse/ATLAS-879 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Ayub Khan > > Is there a need to differentiate terms from tags from an audit perspective? > From a implementation point of view, terms are modelled as tags. But from an > end user perspective, terms are different from tags. In auditing, terms audit > logs are displayed as tag audit. > UI Snapshot: https://monosnap.com/file/560YS5CRHRioAoRbdDpRSP7Alm8o2B -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-855) Atlas logs contain stale transaction eviction message
[
https://issues.apache.org/jira/browse/ATLAS-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-855:
--
Fix Version/s: (was: 0.7-incubating)
> Atlas logs contain stale transaction eviction message
> -
>
> Key: ATLAS-855
> URL: https://issues.apache.org/jira/browse/ATLAS-855
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Priority: Critical
> Attachments: application.log.tar.gz
>
>
> In situations that are hard to replicate, we are getting a message in the
> Atlas server logs as follows:
> {code}
> Evicted [16@c0a801069313-hemanthijalambp-home1] from cache but waiting too
> long for transactions to close. Stale transaction alert on:
> [standardtitantx[null]] (ManagementLogger:189)
> {code}
> I started seeing this a lot more often with the business catalog delete
> functionality (ATLAS-793), although it is not consistent with this.
> This jira is to track down the cause and fix it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-819) All user defined types should have a set of common attributes
[ https://issues.apache.org/jira/browse/ATLAS-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-819: -- Attachment: ATLAS-819.patch Added base type for attributes name, description and owner. Will create another jira for returning system attributes > All user defined types should have a set of common attributes > - > > Key: ATLAS-819 > URL: https://issues.apache.org/jira/browse/ATLAS-819 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Shwetha G S > Fix For: 0.7-incubating > > Attachments: ATLAS-819.patch > > > It would be very convenient if all user defined types have a conventional set > of common attributes including: > * name > * description > * owner > * created at > * modified at -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-647) entityText property should be prefixed with __
[ https://issues.apache.org/jira/browse/ATLAS-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S reassigned ATLAS-647: - Assignee: Shwetha G S > entityText property should be prefixed with __ > -- > > Key: ATLAS-647 > URL: https://issues.apache.org/jira/browse/ATLAS-647 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > > All internal properties for the vertex in the repository are prefixed with __ > to avoid conflicts with user defined attribute names. Looks like entityText > is missed out -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-882) with multiple taxonomies, UI does not allow associating terms with entities. "Add Terms" drop down shows all the taxonomies
[ https://issues.apache.org/jira/browse/ATLAS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-882: -- Fix Version/s: (was: 0.7-incubating) > with multiple taxonomies, UI does not allow associating terms with entities. > "Add Terms" drop down shows all the taxonomies > --- > > Key: ATLAS-882 > URL: https://issues.apache.org/jira/browse/ATLAS-882 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Ayub Khan >Assignee: Keval Bhatt > Attachments: Screen Shot 2016-06-08 at 4.20.45 PM.png > > > with multiple taxonomies, UI does not allow associating terms with entities. > "Add Terms" drop down shows all the taxonomies > Attaching UI snapshot. > Create multiple taxonomies with terms and try associating terms to entities, > UI does not allow it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-815) Authentication error message
[
https://issues.apache.org/jira/browse/ATLAS-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-815:
--
Fix Version/s: (was: 0.7-incubating)
> Authentication error message
>
>
> Key: ATLAS-815
> URL: https://issues.apache.org/jira/browse/ATLAS-815
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>
> Currently, UI maps username/password errors to invalid credentials. But even
> REST APIs should return 'invalid credentials'
> {noformat}
> apache-atlas-0.7-incubating-SNAPSHOT$ curl -u admin2:admin
> http://localhost:21000/api/atlas/admin/version
>
>
>
> Error 401 Username not found.admin2
>
> HTTP ERROR 401
> Problem accessing /api/atlas/admin/version. Reason:
> Username not found.admin2Powered by
> Jetty://
>
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-836) Add timeout for kafka notifications
[ https://issues.apache.org/jira/browse/ATLAS-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-836: -- Fix Version/s: (was: 0.7-incubating) > Add timeout for kafka notifications > --- > > Key: ATLAS-836 > URL: https://issues.apache.org/jira/browse/ATLAS-836 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Vimal Sharma > > In atlas conf, we don't have timeout for calls to kafka and have seen cases > where the kafka calls get stuck for a long time. We should have reasonable > timeouts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-827) Add audit implementation for non-hbase environment
[ https://issues.apache.org/jira/browse/ATLAS-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-827: -- Fix Version/s: (was: 0.7-incubating) > Add audit implementation for non-hbase environment > -- > > Key: ATLAS-827 > URL: https://issues.apache.org/jira/browse/ATLAS-827 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > > Currently there is HBaseBasedAuditRepository which is hbase based > implementation for audit store. In the case that hbase is not used for titan, > there is no alternative implementation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-639) Exception for lineage request
[
https://issues.apache.org/jira/browse/ATLAS-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-639:
--
Priority: Critical (was: Major)
> Exception for lineage request
> -
>
> Key: ATLAS-639
> URL: https://issues.apache.org/jira/browse/ATLAS-639
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Khan
>Priority: Critical
> Fix For: trunk
>
>
> Exception in log for lineage request
> Steps to repro:
> create table j13 (col4 String);
> create table j14 (col5 String);
> insert into table j13 select * from j14;
> insert into table j14 select * from j13;
> Query for lineage of any of the above two entities..(also keep querying for
> any other request along with this). Lineage request is timed-out and below
> error messages are observed in the application log. The below messages are
> seen continously.(Clean the data dir and manual restart will fix this).
> Environment: Atlas running in embedded mode on local setup.
> {noformat}
> 2016-04-06 11:41:45,112 DEBUG - [qtp1936542270-298 -
> fecc3aa7-f4cf-4f6d-89a2-d973c05bc06f:] ~ graph commit
> (GraphTransactionInterceptor:44)
> 2016-04-06 11:41:45,112 DEBUG - [qtp1936542270-298 -
> fecc3aa7-f4cf-4f6d-89a2-d973c05bc06f:] ~ graph commit
> (GraphTransactionInterceptor:44)
> 2016-04-06 11:41:48,935 INFO - [main-SendThread(localhost:9026):] ~ Client
> session timed out, have not heard from server in 1669ms for sessionid
> 0x153ea2cd8da002b, closing socket connection and attempting reconnect
> (ClientCnxn:1096)
> 2016-04-06 11:41:48,935 INFO - [SessionTracker:] ~ Expiring session
> 0x153ea2cd8da002a, timeout of 1000ms exceeded (ZooKeeperServer:347)
> 2016-04-06 11:41:48,935 INFO - [main-SendThread(localhost:9026):] ~ Client
> session timed out, have not heard from server in 1917ms for sessionid
> 0x153ea2cd8da002a, closing socket connection and attempting reconnect
> (ClientCnxn:1096)
> 2016-04-06 11:41:48,935 INFO - [SessionTracker:] ~ Expiring session
> 0x153ea2cd8da002b, timeout of 1000ms exceeded (ZooKeeperServer:347)
> 2016-04-06 11:41:48,935 WARN -
> [NIOServerCxn.Factory:localhost/127.0.0.1:9026:] ~ caught end of stream
> exception (NIOServerCnxn:357)
> EndOfStreamException: Unable to read additional data from client sessionid
> 0x153ea2cd8da002b, likely client has closed socket
> at
> org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
> at
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
> at java.lang.Thread.run(Thread.java:745)
> 2016-04-06 11:41:48,935 INFO - [ProcessThread(sid:0 cport:-1)::] ~ Processed
> session termination for sessionid: 0x153ea2cd8da002a
> (PrepRequestProcessor:494)
> 2016-04-06 11:41:48,936 INFO - [ProcessThread(sid:0 cport:-1)::] ~ Processed
> session termination for sessionid: 0x153ea2cd8da002b
> (PrepRequestProcessor:494)
> 2016-04-06 11:41:48,936 INFO -
> [NIOServerCxn.Factory:localhost/127.0.0.1:9026:] ~ Closed socket connection
> for client /127.0.0.1:51657 which had sessionid 0x153ea2cd8da002b
> (NIOServerCnxn:1007)
> 2016-04-06 11:41:48,936 WARN -
> [NIOServerCxn.Factory:localhost/127.0.0.1:9026:] ~ caught end of stream
> exception (NIOServerCnxn:357)
> EndOfStreamException: Unable to read additional data from client sessionid
> 0x153ea2cd8da002a, likely client has closed socket
> at
> org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
> at
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
> at java.lang.Thread.run(Thread.java:745)
> 2016-04-06 11:41:48,936 INFO -
> [NIOServerCxn.Factory:localhost/127.0.0.1:9026:] ~ Closed socket connection
> for client /127.0.0.1:51652 which had sessionid 0x153ea2cd8da002a
> (NIOServerCnxn:1007)
> 2016-04-06 11:41:49,040 INFO - [main-EventThread:] ~ zookeeper state changed
> (Disconnected) (ZkClient:711)
> 2016-04-06 11:41:49,040 INFO - [main-EventThread:] ~ zookeeper state changed
> (Disconnected) (ZkClient:711)
> 2016-04-06 11:41:58,894 INFO - [main-SendThread(localhost:9026):] ~ Opening
> socket connection to server localhost/127.0.0.1:9026. Will not attempt to
> authenticate using SASL (unknown error) (ClientCnxn:975)
> 2016-04-06 11:41:58,894 INFO -
> [Curator-Framework-0-SendThread(localhost:9026):] ~ Client session timed out,
> have not heard from server in 11587ms for sessionid 0x153ea2cd8da0025,
> closing socket connection and attempting reconnect (ClientCnxn:1096)
> 2016-04-06 11:41:58,894 INFO - [main-SendThread(localhost:9026):] ~ Socket
> connection established to localhost/127.0.0.1:9026, initiating session
> (ClientCnxn:852)
> 2016-04-06 11:41:58,894 INFO - [main-SendThread(localhost:9026):] ~ Opening
> socket connection
[jira] [Resolved] (ATLAS-456) Loader of all Ui functionality until the api response, On Esc stop loader
[ https://issues.apache.org/jira/browse/ATLAS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-456. --- Resolution: Not A Problem > Loader of all Ui functionality until the api response, On Esc stop loader > - > > Key: ATLAS-456 > URL: https://issues.apache.org/jira/browse/ATLAS-456 > Project: Atlas > Issue Type: Task >Reporter: Anilsg >Assignee: Anilsg >Priority: Critical > > Loader for all the api call's from UI, > The loader to be shown until the backend Api is response is success or failure > If the Api is taking to long time to respond, On User Esc button press Loader > to be stopped. > This need's to implemented through out application, in frame work level > We need to show loader until the Api call is responded, > By block the screen for any other click's. > So that user will no be allowed to click any other button's, Only "Esc" to > stop the loade -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-170) Result of search based on attributes of a Traits is not displayed correctly
[
https://issues.apache.org/jira/browse/ATLAS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-170:
--
Assignee: (was: Rohit)
> Result of search based on attributes of a Traits is not displayed correctly
> ---
>
> Key: ATLAS-170
> URL: https://issues.apache.org/jira/browse/ATLAS-170
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
> Environment: HDP2.3.1
>Reporter: Herman Yu
>Priority: Blocker
> Labels: ATLAS-UI-BUGS
> Attachments: screenshot-1.png
>
>
> when search based on an attribute of a trait, it returns the correct # of
> entities found, but list of matched entities are not shown.
> for example, a traits ("mytrait") is defined with an attribute (myTraitAttr).
> then associate this trait to an entity with "myvalue" as the value of the
> attribute. When search with "mytrait.myTraitAttr="myvalue"", it returns 1
> record matched, but doesn't show the entity in the list.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ATLAS-655) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/ATLAS-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S reassigned ATLAS-655: - Assignee: Shwetha G S > Please delete old releases from mirroring system > > > Key: ATLAS-655 > URL: https://issues.apache.org/jira/browse/ATLAS-655 > Project: Atlas > Issue Type: Bug > Environment: > https://dist.apache.org/repos/dist/release/incubator/atlas/ >Reporter: Sebb >Assignee: Shwetha G S > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1119) Add retries for edge label creation
[
https://issues.apache.org/jira/browse/ATLAS-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1119:
---
Attachment: ATLAS-1119.2.patch
Committed to master. Thanks Suma
> Add retries for edge label creation
> ---
>
> Key: ATLAS-1119
> URL: https://issues.apache.org/jira/browse/ATLAS-1119
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1119.2.patch, ATLAS-1119.patch
>
>
> Concurrent operations will fail when trying to create edge label which tries
> to define a new property key for the edge label if it doesnt exist.
> {noformat}
> 2016-08-15 04:08:28,475 DEBUG - [pool-8-thread-1:] ~ Adding a new trait=PII
> for entity=b1630277-e8dc-4fcf-94af-c0c8b0b51c09
> (GraphBackedMetadataRepository:222)
> 2016-08-15 04:08:28,476 DEBUG - [pool-8-thread-2:] ~ Adding a new trait=PII
> for entity=5e335fed-4a74-496d-8521-1678caf85813
> (GraphBackedMetadataRepository:222)
> 2016-08-15 04:08:28,477 DEBUG - [pool-8-thread-1:] ~ Finding vertex with
> __guid = b1630277-e8dc-4fcf-94af-c0c8b0b51c09, (GraphHelper:182)
> 2016-08-15 04:08:28,477 DEBUG - [pool-8-thread-2:] ~ Finding vertex with
> __guid = 5e335fed-4a74-496d-8521-1678caf85813, (GraphHelper:182)
> 2016-08-15 04:08:28,477 DEBUG - [pool-8-thread-3:] ~ Executing dsl
> query=hive_table (GraphBackedDiscoveryService:133)
> 2016-08-15 04:08:28,483 DEBUG - [pool-8-thread-2:] ~ Found a vertex
> vertex[id=8704 type=hive_database guid=5e335fed-4a74-496d-8521-1678caf85813]
> with __guid = 5e335fed-4a74-496d-8521-1678caf85813, (GraphHelper:192)
> 2016-08-15 04:08:28,484 DEBUG - [pool-8-thread-2:] ~ Creating vertex for type
> PII id null (GraphHelper:97)
> 2016-08-15 04:08:28,485 DEBUG - [pool-8-thread-2:] ~ Setting property
> __typeName = "PII" to vertex[id=8960 type=null guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,487 DEBUG - [pool-8-thread-2:] ~ Set property __typeName
> = "PII" to vertex[id=8960 type=null guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,487 DEBUG - [pool-8-thread-2:] ~ Setting property __state
> = "ACTIVE" to vertex[id=8960 type=PII guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,488 DEBUG - [pool-8-thread-2:] ~ Set property __state =
> "ACTIVE" to vertex[id=8960 type=PII guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,488 DEBUG - [pool-8-thread-1:] ~ Found a vertex
> vertex[id=8448 type=hive_database guid=b1630277-e8dc-4fcf-94af-c0c8b0b51c09]
> with __guid = b1630277-e8dc-4fcf-94af-c0c8b0b51c09, (GraphHelper:192)
> 2016-08-15 04:08:28,488 DEBUG - [pool-8-thread-2:] ~ Setting property
> __timestamp = "1471234108488" to vertex[id=8960 type=PII guid=null]
> (GraphHelper:290)
> 2016-08-15 04:08:28,489 DEBUG - [pool-8-thread-1:] ~ Creating vertex for type
> PII id null (GraphHelper:97)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-2:] ~ Set property __timestamp
> = "1471234108488" to vertex[id=8960 type=PII guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-2:] ~ Setting property
> __modificationTimestamp = "1471234108488" to vertex[id=8960 type=PII
> guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-1:] ~ Setting property
> __typeName = "PII" to vertex[id=9216 type=null guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-2:] ~ Set property
> __modificationTimestamp = "1471234108488" to vertex[id=8960 type=PII
> guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,491 DEBUG - [pool-8-thread-2:] ~ created vertex
> vertex[id=8960 type=PII guid=null] for trait PII
> (TypedInstanceToGraphMapper:665)
> 2016-08-15 04:08:28,492 DEBUG - [pool-8-thread-2:] ~ Mapping instance
> struct[type=PII] to vertex vertex[id=8960 type=PII guid=null]
> (TypedInstanceToGraphMapper:181)
> 2016-08-15 04:08:28,492 DEBUG - [pool-8-thread-2:] ~ Setting property
> __modificationTimestamp = "1471234108488" to vertex[id=8960 type=PII
> guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,492 DEBUG - [pool-8-thread-2:] ~ Finding edges for
> vertex[id=8960 type=PII guid=null] with label hive_database.PII
> (GraphHelper:201)
> 2016-08-15 04:08:28,493 DEBUG - [pool-8-thread-2:] ~ Adding edge for
> vertex[id=8704 type=hive_database guid=5e335fed-4a74-496d-8521-1678caf85813]
> -> label hive_database.PII -> vertex[id=8960 type=PII guid=null]
> (GraphHelper:122)
> 2016-08-15 04:08:28,493 DEBUG - [pool-8-thread-1:] ~ Set property __typeName
> = "PII" to vertex[id=9216 type=null guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,494 DEBUG - [pool-8-thread-1:] ~ Setting property __state
> = "ACTIVE" to vertex[id=9216 type=PII guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,495 DEBUG - [pool-8-thread-3:] ~ Query =
[jira] [Updated] (ATLAS-1119) Add retries for edge label creation
[
https://issues.apache.org/jira/browse/ATLAS-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1119:
---
Attachment: (was: ATLAS-1119.patch)
> Add retries for edge label creation
> ---
>
> Key: ATLAS-1119
> URL: https://issues.apache.org/jira/browse/ATLAS-1119
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1119.2.patch, ATLAS-1119.patch
>
>
> Concurrent operations will fail when trying to create edge label which tries
> to define a new property key for the edge label if it doesnt exist.
> {noformat}
> 2016-08-15 04:08:28,475 DEBUG - [pool-8-thread-1:] ~ Adding a new trait=PII
> for entity=b1630277-e8dc-4fcf-94af-c0c8b0b51c09
> (GraphBackedMetadataRepository:222)
> 2016-08-15 04:08:28,476 DEBUG - [pool-8-thread-2:] ~ Adding a new trait=PII
> for entity=5e335fed-4a74-496d-8521-1678caf85813
> (GraphBackedMetadataRepository:222)
> 2016-08-15 04:08:28,477 DEBUG - [pool-8-thread-1:] ~ Finding vertex with
> __guid = b1630277-e8dc-4fcf-94af-c0c8b0b51c09, (GraphHelper:182)
> 2016-08-15 04:08:28,477 DEBUG - [pool-8-thread-2:] ~ Finding vertex with
> __guid = 5e335fed-4a74-496d-8521-1678caf85813, (GraphHelper:182)
> 2016-08-15 04:08:28,477 DEBUG - [pool-8-thread-3:] ~ Executing dsl
> query=hive_table (GraphBackedDiscoveryService:133)
> 2016-08-15 04:08:28,483 DEBUG - [pool-8-thread-2:] ~ Found a vertex
> vertex[id=8704 type=hive_database guid=5e335fed-4a74-496d-8521-1678caf85813]
> with __guid = 5e335fed-4a74-496d-8521-1678caf85813, (GraphHelper:192)
> 2016-08-15 04:08:28,484 DEBUG - [pool-8-thread-2:] ~ Creating vertex for type
> PII id null (GraphHelper:97)
> 2016-08-15 04:08:28,485 DEBUG - [pool-8-thread-2:] ~ Setting property
> __typeName = "PII" to vertex[id=8960 type=null guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,487 DEBUG - [pool-8-thread-2:] ~ Set property __typeName
> = "PII" to vertex[id=8960 type=null guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,487 DEBUG - [pool-8-thread-2:] ~ Setting property __state
> = "ACTIVE" to vertex[id=8960 type=PII guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,488 DEBUG - [pool-8-thread-2:] ~ Set property __state =
> "ACTIVE" to vertex[id=8960 type=PII guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,488 DEBUG - [pool-8-thread-1:] ~ Found a vertex
> vertex[id=8448 type=hive_database guid=b1630277-e8dc-4fcf-94af-c0c8b0b51c09]
> with __guid = b1630277-e8dc-4fcf-94af-c0c8b0b51c09, (GraphHelper:192)
> 2016-08-15 04:08:28,488 DEBUG - [pool-8-thread-2:] ~ Setting property
> __timestamp = "1471234108488" to vertex[id=8960 type=PII guid=null]
> (GraphHelper:290)
> 2016-08-15 04:08:28,489 DEBUG - [pool-8-thread-1:] ~ Creating vertex for type
> PII id null (GraphHelper:97)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-2:] ~ Set property __timestamp
> = "1471234108488" to vertex[id=8960 type=PII guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-2:] ~ Setting property
> __modificationTimestamp = "1471234108488" to vertex[id=8960 type=PII
> guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-1:] ~ Setting property
> __typeName = "PII" to vertex[id=9216 type=null guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-2:] ~ Set property
> __modificationTimestamp = "1471234108488" to vertex[id=8960 type=PII
> guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,491 DEBUG - [pool-8-thread-2:] ~ created vertex
> vertex[id=8960 type=PII guid=null] for trait PII
> (TypedInstanceToGraphMapper:665)
> 2016-08-15 04:08:28,492 DEBUG - [pool-8-thread-2:] ~ Mapping instance
> struct[type=PII] to vertex vertex[id=8960 type=PII guid=null]
> (TypedInstanceToGraphMapper:181)
> 2016-08-15 04:08:28,492 DEBUG - [pool-8-thread-2:] ~ Setting property
> __modificationTimestamp = "1471234108488" to vertex[id=8960 type=PII
> guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,492 DEBUG - [pool-8-thread-2:] ~ Finding edges for
> vertex[id=8960 type=PII guid=null] with label hive_database.PII
> (GraphHelper:201)
> 2016-08-15 04:08:28,493 DEBUG - [pool-8-thread-2:] ~ Adding edge for
> vertex[id=8704 type=hive_database guid=5e335fed-4a74-496d-8521-1678caf85813]
> -> label hive_database.PII -> vertex[id=8960 type=PII guid=null]
> (GraphHelper:122)
> 2016-08-15 04:08:28,493 DEBUG - [pool-8-thread-1:] ~ Set property __typeName
> = "PII" to vertex[id=9216 type=null guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,494 DEBUG - [pool-8-thread-1:] ~ Setting property __state
> = "ACTIVE" to vertex[id=9216 type=PII guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,495 DEBUG - [pool-8-thread-3:] ~ Query = hive_table limit
> 10 offset 0
[jira] [Updated] (ATLAS-1119) Add retries for edge label creation
[
https://issues.apache.org/jira/browse/ATLAS-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1119:
---
Attachment: ATLAS-1119.patch
Added another test and fixed a log statement. +1 for the patch
> Add retries for edge label creation
> ---
>
> Key: ATLAS-1119
> URL: https://issues.apache.org/jira/browse/ATLAS-1119
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1119.patch, ATLAS-1119.patch
>
>
> Concurrent operations will fail when trying to create edge label which tries
> to define a new property key for the edge label if it doesnt exist.
> {noformat}
> 2016-08-15 04:08:28,475 DEBUG - [pool-8-thread-1:] ~ Adding a new trait=PII
> for entity=b1630277-e8dc-4fcf-94af-c0c8b0b51c09
> (GraphBackedMetadataRepository:222)
> 2016-08-15 04:08:28,476 DEBUG - [pool-8-thread-2:] ~ Adding a new trait=PII
> for entity=5e335fed-4a74-496d-8521-1678caf85813
> (GraphBackedMetadataRepository:222)
> 2016-08-15 04:08:28,477 DEBUG - [pool-8-thread-1:] ~ Finding vertex with
> __guid = b1630277-e8dc-4fcf-94af-c0c8b0b51c09, (GraphHelper:182)
> 2016-08-15 04:08:28,477 DEBUG - [pool-8-thread-2:] ~ Finding vertex with
> __guid = 5e335fed-4a74-496d-8521-1678caf85813, (GraphHelper:182)
> 2016-08-15 04:08:28,477 DEBUG - [pool-8-thread-3:] ~ Executing dsl
> query=hive_table (GraphBackedDiscoveryService:133)
> 2016-08-15 04:08:28,483 DEBUG - [pool-8-thread-2:] ~ Found a vertex
> vertex[id=8704 type=hive_database guid=5e335fed-4a74-496d-8521-1678caf85813]
> with __guid = 5e335fed-4a74-496d-8521-1678caf85813, (GraphHelper:192)
> 2016-08-15 04:08:28,484 DEBUG - [pool-8-thread-2:] ~ Creating vertex for type
> PII id null (GraphHelper:97)
> 2016-08-15 04:08:28,485 DEBUG - [pool-8-thread-2:] ~ Setting property
> __typeName = "PII" to vertex[id=8960 type=null guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,487 DEBUG - [pool-8-thread-2:] ~ Set property __typeName
> = "PII" to vertex[id=8960 type=null guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,487 DEBUG - [pool-8-thread-2:] ~ Setting property __state
> = "ACTIVE" to vertex[id=8960 type=PII guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,488 DEBUG - [pool-8-thread-2:] ~ Set property __state =
> "ACTIVE" to vertex[id=8960 type=PII guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,488 DEBUG - [pool-8-thread-1:] ~ Found a vertex
> vertex[id=8448 type=hive_database guid=b1630277-e8dc-4fcf-94af-c0c8b0b51c09]
> with __guid = b1630277-e8dc-4fcf-94af-c0c8b0b51c09, (GraphHelper:192)
> 2016-08-15 04:08:28,488 DEBUG - [pool-8-thread-2:] ~ Setting property
> __timestamp = "1471234108488" to vertex[id=8960 type=PII guid=null]
> (GraphHelper:290)
> 2016-08-15 04:08:28,489 DEBUG - [pool-8-thread-1:] ~ Creating vertex for type
> PII id null (GraphHelper:97)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-2:] ~ Set property __timestamp
> = "1471234108488" to vertex[id=8960 type=PII guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-2:] ~ Setting property
> __modificationTimestamp = "1471234108488" to vertex[id=8960 type=PII
> guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-1:] ~ Setting property
> __typeName = "PII" to vertex[id=9216 type=null guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-2:] ~ Set property
> __modificationTimestamp = "1471234108488" to vertex[id=8960 type=PII
> guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,491 DEBUG - [pool-8-thread-2:] ~ created vertex
> vertex[id=8960 type=PII guid=null] for trait PII
> (TypedInstanceToGraphMapper:665)
> 2016-08-15 04:08:28,492 DEBUG - [pool-8-thread-2:] ~ Mapping instance
> struct[type=PII] to vertex vertex[id=8960 type=PII guid=null]
> (TypedInstanceToGraphMapper:181)
> 2016-08-15 04:08:28,492 DEBUG - [pool-8-thread-2:] ~ Setting property
> __modificationTimestamp = "1471234108488" to vertex[id=8960 type=PII
> guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,492 DEBUG - [pool-8-thread-2:] ~ Finding edges for
> vertex[id=8960 type=PII guid=null] with label hive_database.PII
> (GraphHelper:201)
> 2016-08-15 04:08:28,493 DEBUG - [pool-8-thread-2:] ~ Adding edge for
> vertex[id=8704 type=hive_database guid=5e335fed-4a74-496d-8521-1678caf85813]
> -> label hive_database.PII -> vertex[id=8960 type=PII guid=null]
> (GraphHelper:122)
> 2016-08-15 04:08:28,493 DEBUG - [pool-8-thread-1:] ~ Set property __typeName
> = "PII" to vertex[id=9216 type=null guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,494 DEBUG - [pool-8-thread-1:] ~ Setting property __state
> = "ACTIVE" to vertex[id=9216 type=PII guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,495 DEBUG -
[jira] [Updated] (ATLAS-1120) Add a set-up script to pre-create required tables
[ https://issues.apache.org/jira/browse/ATLAS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1120: --- Attachment: ATLAS-1120.patch Patch in progress. Need to test with secure environment > Add a set-up script to pre-create required tables > - > > Key: ATLAS-1120 > URL: https://issues.apache.org/jira/browse/ATLAS-1120 > Project: Atlas > Issue Type: Task >Reporter: Shwetha G S >Assignee: Shwetha G S > Attachments: ATLAS-1120.patch > > > Add a set-up script to pre-create required tables for graph db and audit > repository. In secure setup, the set-up scripts are required as the set up > needs to be done using admin user, not same as atlas server user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1125) Enable compression on hbase audit table
[ https://issues.apache.org/jira/browse/ATLAS-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423999#comment-15423999 ] Shwetha G S commented on ATLAS-1125: With the patch, hbase table size (hbase on local fs) with 10K hive tables imported default$ du -sh * 8.0Kapache_atlas_entity_audit 9.9Mapache_atlas_titan > Enable compression on hbase audit table > --- > > Key: ATLAS-1125 > URL: https://issues.apache.org/jira/browse/ATLAS-1125 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1125.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1129) Remove notification failed logs on retry and add sleep between retries
[ https://issues.apache.org/jira/browse/ATLAS-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428129#comment-15428129 ] Shwetha G S commented on ATLAS-1129: The patch looks good otherwise > Remove notification failed logs on retry and add sleep between retries > -- > > Key: ATLAS-1129 > URL: https://issues.apache.org/jira/browse/ATLAS-1129 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1129.patch > > > Atlas notification interface logs the exception if it cannot send the message > successfully. Further, the retries are attempted immediately. > Remove the exception logs for individual retry and add sleep between retries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1129) Remove notification failed logs on retry and add sleep between retries
[ https://issues.apache.org/jira/browse/ATLAS-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427998#comment-15427998 ] Shwetha G S commented on ATLAS-1129: In NotificationHookConsumer, move log of sleeping before Thread.sleep > Remove notification failed logs on retry and add sleep between retries > -- > > Key: ATLAS-1129 > URL: https://issues.apache.org/jira/browse/ATLAS-1129 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1129.patch > > > Atlas notification interface logs the exception if it cannot send the message > successfully. Further, the retries are attempted immediately. > Remove the exception logs for individual retry and add sleep between retries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1120) Add a set-up script to pre-create required tables
[ https://issues.apache.org/jira/browse/ATLAS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1120: --- Summary: Add a set-up script to pre-create required tables (was: 1Add a set-up script to pre-create required tables) > Add a set-up script to pre-create required tables > - > > Key: ATLAS-1120 > URL: https://issues.apache.org/jira/browse/ATLAS-1120 > Project: Atlas > Issue Type: Task >Reporter: Shwetha G S >Assignee: Shwetha G S > > Add a set-up script to pre-create required tables for graph db and audit > repository. In secure setup, the set-up scripts are required as the set up > needs to be done using admin user, not same as atlas server user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1120) 1Add a set-up script to pre-create required tables
Shwetha G S created ATLAS-1120: -- Summary: 1Add a set-up script to pre-create required tables Key: ATLAS-1120 URL: https://issues.apache.org/jira/browse/ATLAS-1120 Project: Atlas Issue Type: Task Reporter: Shwetha G S Assignee: Shwetha G S Add a set-up script to pre-create required tables for graph db and audit repository. In secure setup, the set-up scripts are required as the set up needs to be done using admin user, not same as atlas server user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1125) Enable compression on hbase audit table
Shwetha G S created ATLAS-1125: -- Summary: Enable compression on hbase audit table Key: ATLAS-1125 URL: https://issues.apache.org/jira/browse/ATLAS-1125 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Assignee: Shwetha G S Attachments: ATLAS-1125.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1125) Enable compression on hbase audit table
[ https://issues.apache.org/jira/browse/ATLAS-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1125: --- Attachment: ATLAS-1125.patch > Enable compression on hbase audit table > --- > > Key: ATLAS-1125 > URL: https://issues.apache.org/jira/browse/ATLAS-1125 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Attachments: ATLAS-1125.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1147) UI: column name doesn't show up in schema tab for hive table
[ https://issues.apache.org/jira/browse/ATLAS-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1147: --- Attachment: Screen Shot 2016-08-30 at 9.21.07 PM.png > UI: column name doesn't show up in schema tab for hive table > > > Key: ATLAS-1147 > URL: https://issues.apache.org/jira/browse/ATLAS-1147 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > Attachments: Screen Shot 2016-08-30 at 9.21.07 PM.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1146) Hive lineage with falcon doesn't depict correctly
Shwetha G S created ATLAS-1146: -- Summary: Hive lineage with falcon doesn't depict correctly Key: ATLAS-1146 URL: https://issues.apache.org/jira/browse/ATLAS-1146 Project: Atlas Issue Type: Bug Reporter: Shwetha G S With the lineage, process1 -> output feed1 and feed1 maps to hive table table1. Showing lineage for tabl1 doesn't show inputs of process1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1146) Hive lineage with falcon doesn't depict correctly
[ https://issues.apache.org/jira/browse/ATLAS-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1146: --- Description: With the lineage, process1 -> output feed1 and feed1 maps to hive table table1. Showing lineage for table1 doesn't show inputs of process1, need to click on feed1 to get process1 inputs which doesn't look right (was: With the lineage, process1 -> output feed1 and feed1 maps to hive table table1. Showing lineage for tabl1 doesn't show inputs of process1) > Hive lineage with falcon doesn't depict correctly > - > > Key: ATLAS-1146 > URL: https://issues.apache.org/jira/browse/ATLAS-1146 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > > With the lineage, process1 -> output feed1 and feed1 maps to hive table > table1. Showing lineage for table1 doesn't show inputs of process1, need to > click on feed1 to get process1 inputs which doesn't look right -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1148) Business taxonomy: search for assets under taxonomy shows the root taxonomy as well
[ https://issues.apache.org/jira/browse/ATLAS-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1148: --- Attachment: Screen Shot 2016-08-30 at 9.50.47 PM.png > Business taxonomy: search for assets under taxonomy shows the root taxonomy > as well > --- > > Key: ATLAS-1148 > URL: https://issues.apache.org/jira/browse/ATLAS-1148 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > Attachments: Screen Shot 2016-08-30 at 9.50.47 PM.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1148) Business taxonomy: search for assets under taxonomy shows the root taxonomy as well
Shwetha G S created ATLAS-1148: -- Summary: Business taxonomy: search for assets under taxonomy shows the root taxonomy as well Key: ATLAS-1148 URL: https://issues.apache.org/jira/browse/ATLAS-1148 Project: Atlas Issue Type: Bug Reporter: Shwetha G S -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1145) Storm hook with kafka topic and hive bolt picks wrong hive table name
Shwetha G S created ATLAS-1145: -- Summary: Storm hook with kafka topic and hive bolt picks wrong hive table name Key: ATLAS-1145 URL: https://issues.apache.org/jira/browse/ATLAS-1145 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Storm hook with kafka topic and hive bolt picks kafka topic name as hive table name -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1149) Changes to UI to sort the hive table schema based on "position" attribute of hive_column
[ https://issues.apache.org/jira/browse/ATLAS-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483537#comment-15483537 ] Shwetha G S commented on ATLAS-1149: The UI shouldn't do the sort. Instead we should modify the query used for this (atlas.lineage.schema.query.hive_table=hive_table where __guid='%s'\, columns) to sort by position, so that all clients have the same info. Also, the query should filter deleted columns > Changes to UI to sort the hive table schema based on "position" attribute of > hive_column > > > Key: ATLAS-1149 > URL: https://issues.apache.org/jira/browse/ATLAS-1149 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Sarath Subramanian >Assignee: Kalyani Kashikar > Labels: ui > Attachments: ATLAS-1149.patch, attach1.json, attach2.json > > > This is related to ATLAS-772, hive column needs to be sorted based on its > original column order. New attribute "position" has been added to hive_column > type which maintains the column order number. UI needs to use this > information to sort the column based on this attribute -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1098) Atlas allows creation of tag with name "isa" which causes exceptions during search
[ https://issues.apache.org/jira/browse/ATLAS-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483468#comment-15483468 ] Shwetha G S commented on ATLAS-1098: Sorry for the late review as I was away last few days. I have added comments on reviewboard, can you address them? > Atlas allows creation of tag with name "isa" which causes exceptions during > search > -- > > Key: ATLAS-1098 > URL: https://issues.apache.org/jira/browse/ATLAS-1098 > Project: Atlas > Issue Type: Bug >Reporter: Sharmadha Sainath >Assignee: Apoorv Naik > > Created a tag with name "isa". DSL query "Table where Table isa isa" throws > exception . Search in Tag tab also throws exception. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1154) Errors in Eclipse with web.xml
[
https://issues.apache.org/jira/browse/ATLAS-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1154:
---
Description:
I have set up a development environment in Eclipse. I notice that the project
atlas-webapp has 2 errors like this :
The content of element type "web-app" must match
"(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-
mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-
ref*,ejb-local-ref*)".
The reason for the error is that the xml elements were filter, filter mapping,
filter, filter mapping. This does not match the DTD element order (which
Eclipse seems to be policing). If I move the elements so all the filters are
next to each other - there are no errors.
Like this :
{noformat}
springSecurityFilterChain
org.springframework.web.filter.DelegatingFilterProxy
guiceFilter
com.google.inject.servlet.GuiceFilter
springSecurityFilterChain
/*
guiceFilter
/*
{noformat}
was:
I have set up a development environment in Eclipse. I notice that the project
atlas-webapp has 2 errors like this :
The content of element type "web-app" must match
"(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-
mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-
ref*,ejb-local-ref*)".
The reason for the error is that the xml elements were filter, filter mapping,
filter, filter mapping. This does not match the DTD element order (which
Eclipse seems to be policing). If I move the elements so all the filters are
next to each other - there are no errors.
Like this :
springSecurityFilterChain
org.springframework.web.filter.DelegatingFilterProxy
guiceFilter
com.google.inject.servlet.GuiceFilter
springSecurityFilterChain
/*
guiceFilter
/*
> Errors in Eclipse with web.xml
> --
>
> Key: ATLAS-1154
> URL: https://issues.apache.org/jira/browse/ATLAS-1154
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: David Radley
>Assignee: David Radley
> Fix For: 0.8-incubating
>
> Attachments: atlas1154.patch
>
>
> I have set up a development environment in Eclipse. I notice that the project
> atlas-webapp has 2 errors like this :
> The content of element type "web-app" must match
> "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-
>
> mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-
> ref*,ejb-local-ref*)".
> The reason for the error is that the xml elements were filter, filter
> mapping, filter, filter mapping. This does not match the DTD element order
> (which Eclipse seems to be policing). If I move the elements so all the
> filters are next to each other - there are no errors.
> Like this :
> {noformat}
>
> springSecurityFilterChain
>
> org.springframework.web.filter.DelegatingFilterProxy
>
>
> guiceFilter
> com.google.inject.servlet.GuiceFilter
>
>
> springSecurityFilterChain
> /*
>
>
> guiceFilter
> /*
>
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1154) Errors in Eclipse with web.xml
[ https://issues.apache.org/jira/browse/ATLAS-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1154: --- Assignee: David Radley > Errors in Eclipse with web.xml > -- > > Key: ATLAS-1154 > URL: https://issues.apache.org/jira/browse/ATLAS-1154 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: David Radley >Assignee: David Radley > Fix For: 0.8-incubating > > Attachments: atlas1154.patch > > > I have set up a development environment in Eclipse. I notice that the project > atlas-webapp has 2 errors like this : > The content of element type "web-app" must match > "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet- > > mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb- > ref*,ejb-local-ref*)". > The reason for the error is that the xml elements were filter, filter > mapping, filter, filter mapping. This does not match the DTD element order > (which Eclipse seems to be policing). If I move the elements so all the > filters are next to each other - there are no errors. > Like this : > > springSecurityFilterChain > > org.springframework.web.filter.DelegatingFilterProxy > > > guiceFilter > com.google.inject.servlet.GuiceFilter > > > springSecurityFilterChain > /* > > > guiceFilter > /* > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-1098) Atlas allows creation of tag with name "isa" which causes exceptions during search
[ https://issues.apache.org/jira/browse/ATLAS-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483078#comment-15483078 ] Shwetha G S edited comment on ATLAS-1098 at 9/12/16 8:23 AM: - [~apoorvnaik], please link the review board request to the jira and add the patch in the jira for your future patches. Thanks was (Author: shwethags): [~apoorvnaik], please link the review board request to the jira for your future patches. Thanks > Atlas allows creation of tag with name "isa" which causes exceptions during > search > -- > > Key: ATLAS-1098 > URL: https://issues.apache.org/jira/browse/ATLAS-1098 > Project: Atlas > Issue Type: Bug >Reporter: Sharmadha Sainath >Assignee: Apoorv Naik > > Created a tag with name "isa". DSL query "Table where Table isa isa" throws > exception . Search in Tag tab also throws exception. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1098) Atlas allows creation of tag with name "isa" which causes exceptions during search
[ https://issues.apache.org/jira/browse/ATLAS-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483078#comment-15483078 ] Shwetha G S commented on ATLAS-1098: [~apoorvnaik], please link the review board request to the jira for your future patches. Thanks > Atlas allows creation of tag with name "isa" which causes exceptions during > search > -- > > Key: ATLAS-1098 > URL: https://issues.apache.org/jira/browse/ATLAS-1098 > Project: Atlas > Issue Type: Bug >Reporter: Sharmadha Sainath >Assignee: Apoorv Naik > > Created a tag with name "isa". DSL query "Table where Table isa isa" throws > exception . Search in Tag tab also throws exception. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1161) Tags should be bound to an object's name and remain bound to all incarnations of that name
[
https://issues.apache.org/jira/browse/ATLAS-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487402#comment-15487402
]
Shwetha G S commented on ATLAS-1161:
{quote}
In the current Atlas world, if I create TableA again, Tag1 and Tag2 need to be
re-applied to TableA
{quote}
I think it makes sense to not carry over the tags from old entity. The new
entity, even though has the same name as old entity, might have been derived in
a different way and mean something else. Even I think rule based classification
would be a better fit here.
{quote}
By effectively deleting the binding of Tag1 and Tag2 to the name TableA
whenever TableA is deleted, Atlas ceases to be a book of record for tags
associated with TableA, as those tags would need to be applied again.
{quote}
By default, entity deletes are soft deletes. So, when TableA is deleted, its
just marked as deleted and all the tag associations still remain and search
retrieves the deleted entities as well. When TableA is re-created, atlas
creates another entity(with new guid) and with no tags. So, both the old and
new entity exists and its possible to look at both of them for audit.
Additionally, each entity has audit trail that records tag associations, that
can be viewed for both active and deleted entities
> Tags should be bound to an object's name and remain bound to all incarnations
> of that name
> --
>
> Key: ATLAS-1161
> URL: https://issues.apache.org/jira/browse/ATLAS-1161
> Project: Atlas
> Issue Type: Improvement
>Affects Versions: trunk, 0.7-incubating
>Reporter: Dan Markwat
>
> As a user I would like tags I ascribe to an object in Atlas carry to the next
> incarnation of that object. In effect, tags would be ascribed to a
> fully-qualified object name and all incarnations of that name would have the
> tags apply to it. (Not unlike Ranger and the way it applies policies to
> objects).
> Example: I create a Hive table, TableA. I tag TableA with tags, Tag1 and
> Tag2. I drop TableA.
> In the current Atlas world, if I create TableA again, Tag1 and Tag2 need to
> be re-applied to TableA. In the ideal governance/security world, if I
> re-create TableA I should not have to re-tag it with Tag1 and Tag2; instead,
> I should be required to *untag* TableA if I desire TableA to be clean and
> untagged. This effectively functions like a light switch: user turns on
> light, just because the bulb is swapped out doesn't mean the switch turned
> off - the user must explicitly turn the switch off, just as they did to turn
> it on. Think also about Ranger: just because I deleted an object doesn't
> mean that policy goes away.
> By effectively deleting the binding of Tag1 and Tag2 to the name TableA
> whenever TableA is deleted, Atlas ceases to be a book of record for tags
> associated with TableA, as those tags would need to be applied again. This
> is bad in a world where creating/dropping objects and tagging objects are
> part of 2 independent and asynchronous processes - one carried out by an
> engineer, the other carried out by a governance/security administrator. The
> issue is compounded by the fact that tags can have security policies
> associated with them in Ranger; and any object missing its tag at re-creation
> of that object now is missing security policies previously attached to it.
> This is an especially annoying issue for organizations that have large
> ingestion pipelines where tables are sometimes deleted or modified in ways
> not easily accomplished through updating table metadata. Not to mention,
> (probably a new feature: ) easily-accessible records of what was tagged with
> what - even if the object has been dropped or deleted - is especially
> important for organizations that require auditing or have security controls
> based on tag-based policies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1098) Atlas allows creation of tag with name "isa" which causes exceptions during search
[
https://issues.apache.org/jira/browse/ATLAS-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1098:
---
Attachment: ATLAS-1098.patch
The attached patch fixes the queryparser. The query {{Table isa `isa`}} works
with this patch and returns the right results
> Atlas allows creation of tag with name "isa" which causes exceptions during
> search
> --
>
> Key: ATLAS-1098
> URL: https://issues.apache.org/jira/browse/ATLAS-1098
> Project: Atlas
> Issue Type: Bug
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
> Attachments: ATLAS-1098.patch
>
>
> Created a tag with name "isa". DSL query "Table where Table isa isa" throws
> exception . Search in Tag tab also throws exception.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ATLAS-961) DataSetLineageJerseyResourceIT.setUp fails
[
https://issues.apache.org/jira/browse/ATLAS-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S resolved ATLAS-961.
---
Resolution: Duplicate
> DataSetLineageJerseyResourceIT.setUp fails
> --
>
> Key: ATLAS-961
> URL: https://issues.apache.org/jira/browse/ATLAS-961
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>
> mvn clean install -rf :atlas-webapp -Dit.test=DataSetLineageJerseyResourceIT
> -DskipUTs
> {noformat}
> Tests run: 9, Failures: 1, Errors: 0, Skipped: 8, Time elapsed: 3.716 sec <<<
> FAILURE! - in org.apache.atlas.web.resources.DataSetLineageJerseyResourceIT
> setUp(org.apache.atlas.web.resources.DataSetLineageJerseyResourceIT) Time
> elapsed: 3.666 sec <<< FAILURE!
> org.apache.atlas.AtlasServiceException: Metadata service API CREATE_ENTITY
> failed with status 400(Bad Request) Response Body ({"error":"Unknown
> datatype:
> Fact","stackTrace":"org.apache.atlas.typesystem.exception.TypeNotFoundException:
> Unknown datatype: Fact\n\tat
> org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:178)\n\tat
>
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.getDataType(TypeSystem.java:649)\n\tat
>
> org.apache.atlas.typesystem.types.ClassType.createInstanceWithTraits(ClassType.java:182)\n\tat
>
> org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:125)\n\tat
> org.apache.atlas.services.DefaultMetadataService.getTypedReferenceableInstance(DefaultMetadataService.java:374)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:350)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:331)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:606)\n\tat
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\tat
> com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)\n\tat
> com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)\n\tat
> com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)\n\tat
>
[jira] [Commented] (ATLAS-197) Add build instructions in top level dir
[ https://issues.apache.org/jira/browse/ATLAS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551084#comment-15551084 ] Shwetha G S commented on ATLAS-197: --- Yes, makes sense to add local reference or give minimal build instructions at README and add link as well for detailed instructions > Add build instructions in top level dir > --- > > Key: ATLAS-197 > URL: https://issues.apache.org/jira/browse/ATLAS-197 > Project: Atlas > Issue Type: Wish >Affects Versions: trunk >Reporter: Nigel Jones >Priority: Minor > > In early Atlas code we had a file (names something like Installation Steps) > in the top level directory which directed the developer who'd downloaded the > code from github as to how to build. > However since the docs are now in twiki those build instructions are only > found several layers deep, and with twiki markup > jonesn@jonesn-ThinkPad-W530:~/atlas/incubator-atlas$ find . -type f -print | > xargs -n50 grep -y "mvn clean install" > ./docs/src/site/twiki/InstallationSteps.twiki:export MAVEN_OPTS="-Xmx1024m > -XX:MaxPermSize=256m" && mvn clean install > A pointer to the user to read this file, or a quick summary should be added > to the root -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1208) DSL query optimisation
[
https://issues.apache.org/jira/browse/ATLAS-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1208:
---
Assignee: (was: Shwetha G S)
> DSL query optimisation
> --
>
> Key: ATLAS-1208
> URL: https://issues.apache.org/jira/browse/ATLAS-1208
> Project: Atlas
> Issue Type: Bug
>Reporter: Sharmadha Sainath
> Fix For: 0.8-incubating
>
>
> DSL queries always have the type. The DSL query is transformed into gremlin
> of the form: {{g.V().has(type, ).has(name, )}}. This is not
> efficient as the first has clause returns many vertices. Instead, if we
> generate the gremlin query as {{g.V().has(name, ).has(type, )}},
> the query should execute faster as the first predicate will filter more
> vertices
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-1207) Dataset exists query in lineage APIs takes longer
Shwetha G S created ATLAS-1207:
--
Summary: Dataset exists query in lineage APIs takes longer
Key: ATLAS-1207
URL: https://issues.apache.org/jira/browse/ATLAS-1207
Project: Atlas
Issue Type: Bug
Reporter: Sharmadha Sainath
Assignee: Shwetha G S
Fix For: 0.8-incubating
Hive_column now extends DataSet. Lineage Service uses the DSL query Dataset
where __guid = which maps to the gremlin query g.V().has(supertype,
Dataset).has(__guid, ). Since the first filter is on type which returns
many vertices, this query is slow. Supertypes is a list property and not sure
how adding combined index will work. This can be replaced with graph query
directly like
{code}
titanGraph.query().has(Constants.GUID_PROPERTY_KEY, guid)
.has(Constants.SUPER_TYPES_PROPERTY_KEY,
AtlasClient.DATA_SET_SUPER_TYPE)
{code}
Thanks [~ssainath] for helping to test this
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-1208) DSL query optimisation
Shwetha G S created ATLAS-1208:
--
Summary: DSL query optimisation
Key: ATLAS-1208
URL: https://issues.apache.org/jira/browse/ATLAS-1208
Project: Atlas
Issue Type: Bug
Reporter: Sharmadha Sainath
Fix For: 0.8-incubating
DSL queries always have the type. The DSL query is transformed into gremlin of
the form: {{g.V().has(type, ).has(name, )}}. This is not efficient
as the first has clause returns many vertices. Instead, if we generate the
gremlin query as {{g.V().has(name, ).has(type, )}}, the query
should execute faster as the first predicate will filter more vertices
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ATLAS-1216) Please delete this issue - JIRA is sooooo weird to use
[ https://issues.apache.org/jira/browse/ATLAS-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-1216. Resolution: Invalid > Please delete this issue - JIRA is so weird to use > -- > > Key: ATLAS-1216 > URL: https://issues.apache.org/jira/browse/ATLAS-1216 > Project: Atlas > Issue Type: Task >Reporter: Ronald Feicht >Priority: Trivial > > I cannot find the button where I may delete my own issue, so, sorry for one > of you guys having to do it for me. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1182) Hive Column level lineage docs
[ https://issues.apache.org/jira/browse/ATLAS-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554214#comment-15554214 ] Shwetha G S commented on ATLAS-1182: Can you also add details of hive version that column level lineage works with (hive 1.2.x + hive patch)? > Hive Column level lineage docs > -- > > Key: ATLAS-1182 > URL: https://issues.apache.org/jira/browse/ATLAS-1182 > Project: Atlas > Issue Type: Improvement >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-1182.patch, column_lineage_ex1.png > > > Add column level lineage details to Atlas documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1183) UI: help link should point to atlas website
Shwetha G S created ATLAS-1183: -- Summary: UI: help link should point to atlas website Key: ATLAS-1183 URL: https://issues.apache.org/jira/browse/ATLAS-1183 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Fix For: 0.8-incubating Help link points to https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=ATLAS=Atlas+Home which requires login. Instead, link to http://atlas.incubator.apache.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1184) ReservedTypesRegistrar checks for existence of 1st class type
Shwetha G S created ATLAS-1184: -- Summary: ReservedTypesRegistrar checks for existence of 1st class type Key: ATLAS-1184 URL: https://issues.apache.org/jira/browse/ATLAS-1184 Project: Atlas Issue Type: Bug Reporter: Shwetha G S ReservedTypesRegistrar registers the models for supported integrations like hive, falcon, sqoop and storm. ReservedTypesRegistrar reads the model files and registers the types defined in the model file. The check thats done to verify if the model is already registered - checks for existence of first class type. This will not work if we add more class types to the existing model or modify the existing type to add optional attributes. ReservedTypesRegistrar should check for every type in the model file. Also, ReservedTypesRegistrar should do type update which does create if not exists, and update if exists -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1185) UI: columns attribute displayed for all entities
Shwetha G S created ATLAS-1185: -- Summary: UI: columns attribute displayed for all entities Key: ATLAS-1185 URL: https://issues.apache.org/jira/browse/ATLAS-1185 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Attachments: Screen Shot 2016-09-21 at 5.06.29 PM.png In the entity details page, columns attribute is displayed without any value. Looks like this is shown for all entity types -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1185) UI: columns attribute displayed for all entities
[ https://issues.apache.org/jira/browse/ATLAS-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1185: --- Attachment: Screen Shot 2016-09-21 at 5.06.29 PM.png > UI: columns attribute displayed for all entities > > > Key: ATLAS-1185 > URL: https://issues.apache.org/jira/browse/ATLAS-1185 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > Attachments: Screen Shot 2016-09-21 at 5.06.29 PM.png > > > In the entity details page, columns attribute is displayed without any value. > Looks like this is shown for all entity types -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1142) Lineage UI Improvement.
[ https://issues.apache.org/jira/browse/ATLAS-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492574#comment-15492574 ] Shwetha G S commented on ATLAS-1142: Build fails in rat check: Unapproved licenses: /Users/sshivalingamurthy/git/atlas-clone/dashboardv2/public/js/jquery-ui/jquery-ui.min.css /Users/sshivalingamurthy/git/atlas-clone/dashboardv2/public/js/jquery-ui/jquery-ui.min.js > Lineage UI Improvement. > --- > > Key: ATLAS-1142 > URL: https://issues.apache.org/jira/browse/ATLAS-1142 > Project: Atlas > Issue Type: Improvement >Reporter: Nixon Rodrigues >Assignee: Keval Bhatt >Priority: Minor > Attachments: ATLAS-1142.patch > > > Following improvement to be done in Lineage UI & entity detail page > * Lineage UI should be resizable. > * All the nodes to be shown in format *name (typename)* -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1173) Doc: Minor editorial bug in the example given for property atlas.server.ha.zookeeper.auth
[
https://issues.apache.org/jira/browse/ATLAS-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492556#comment-15492556
]
Shwetha G S commented on ATLAS-1173:
+1
> Doc: Minor editorial bug in the example given for property
> atlas.server.ha.zookeeper.auth
> -
>
> Key: ATLAS-1173
> URL: https://issues.apache.org/jira/browse/ATLAS-1173
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Minor
> Attachments: ATLAS-1173.patch
>
>
> In {{Configuration.twiki}}, we have specified the example for Zookeeper
> security configs as follows (under the High Availability Properties).
> {code}
> atlas.server.ha.zookeeper.acl=auth:sasl:cli...@comany.com
> {code}
> The auth: prefix in the value is incorrect and should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-1142) Lineage UI Improvement.
[ https://issues.apache.org/jira/browse/ATLAS-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492559#comment-15492559 ] Shwetha G S commented on ATLAS-1142: The js file mentions its MIT license. Can you replace jQuery Foundation License with MIT License in the following lines: +This product bundles jQuery-ui.js, which is available under +jQuery Foundation License. For details, see 3party-licenses/jQuery-ui-LICENSE > Lineage UI Improvement. > --- > > Key: ATLAS-1142 > URL: https://issues.apache.org/jira/browse/ATLAS-1142 > Project: Atlas > Issue Type: Improvement >Reporter: Nixon Rodrigues >Assignee: Keval Bhatt >Priority: Minor > Attachments: ATLAS-1142.patch > > > Following improvement to be done in Lineage UI & entity detail page > * Lineage UI should be resizable. > * All the nodes to be shown in format *name (typename)* -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1184) ReservedTypesRegistrar checks for existence of 1st class type
[ https://issues.apache.org/jira/browse/ATLAS-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15509686#comment-15509686 ] Shwetha G S commented on ATLAS-1184: Looks like ReservedTypesRegistrar uses internal APIs directly. It should just be a utility which uses rest APIs so that its audited > ReservedTypesRegistrar checks for existence of 1st class type > - > > Key: ATLAS-1184 > URL: https://issues.apache.org/jira/browse/ATLAS-1184 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Vimal Sharma > > ReservedTypesRegistrar registers the models for supported integrations like > hive, falcon, sqoop and storm. ReservedTypesRegistrar reads the model files > and registers the types defined in the model file. The check thats done to > verify if the model is already registered - checks for existence of first > class type. This will not work if we add more class types to the existing > model or modify the existing type to add optional attributes. > ReservedTypesRegistrar should check for every type in the model file. Also, > ReservedTypesRegistrar should do type update which does create if not exists, > and update if exists -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1134) Full text search for "id" shows the blank screen in some case
[ https://issues.apache.org/jira/browse/ATLAS-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492818#comment-15492818 ] Shwetha G S commented on ATLAS-1134: I got the screen with 'No Record found!'. When does this issue happen? > Full text search for "id" shows the blank screen in some case > - > > Key: ATLAS-1134 > URL: https://issues.apache.org/jira/browse/ATLAS-1134 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1134.patch > > > Step to reproduce - > 1.Search for "id" in full text. > 2.In case of entity Id is null, it doesn't shows the result, loader is > display on screen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1142) Lineage UI Improvement.
[ https://issues.apache.org/jira/browse/ATLAS-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1142: --- Attachment: Screen Shot 2016-09-15 at 2.16.57 PM.png [~aahn], the patch adds asset type with the asset name(see the attached screenshot). In the header and lineage, asset type like hive table, mysql table, hbase table is displayed along with the actual table name. Does that look fine? > Lineage UI Improvement. > --- > > Key: ATLAS-1142 > URL: https://issues.apache.org/jira/browse/ATLAS-1142 > Project: Atlas > Issue Type: Improvement >Reporter: Nixon Rodrigues >Assignee: Keval Bhatt >Priority: Minor > Attachments: ATLAS-1142.patch, Screen Shot 2016-09-15 at 2.16.57 > PM.png > > > Following improvement to be done in Lineage UI & entity detail page > * Lineage UI should be resizable. > * All the nodes to be shown in format *name (typename)* -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1179) Hive hook test failure
Shwetha G S created ATLAS-1179:
--
Summary: Hive hook test failure
Key: ATLAS-1179
URL: https://issues.apache.org/jira/browse/ATLAS-1179
Project: Atlas
Issue Type: Bug
Reporter: Shwetha G S
The build fails:
{noformat}
HiveHookIT.testAlterTableDropColumn:996 expected:<1> but was:<2>
HiveHookIT.testCreateExternalTable:218->HiveITBase.assertTableIsRegistered:154->HiveITBase.assertEntityIsRegistered:160->HiveITBase.waitFor:204
Assertions failed. Failing after waiting for timeout 8 msecs
HiveHookIT.testInsertIntoTempTable:690->validateProcess:518->validateProcess:498->assertProcessIsRegistered:1662->HiveITBase.assertEntityIsRegistered:160->HiveITBase.waitFor:204
Assertions failed. Failing after waiting for timeout 8 msecs
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ATLAS-1179) Hive hook test failure
[
https://issues.apache.org/jira/browse/ATLAS-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S reassigned ATLAS-1179:
--
Assignee: Shwetha G S
> Hive hook test failure
> --
>
> Key: ATLAS-1179
> URL: https://issues.apache.org/jira/browse/ATLAS-1179
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Critical
>
> The build fails:
> {noformat}
> HiveHookIT.testAlterTableDropColumn:996 expected:<1> but was:<2>
>
> HiveHookIT.testCreateExternalTable:218->HiveITBase.assertTableIsRegistered:154->HiveITBase.assertEntityIsRegistered:160->HiveITBase.waitFor:204
> Assertions failed. Failing after waiting for timeout 8 msecs
>
> HiveHookIT.testInsertIntoTempTable:690->validateProcess:518->validateProcess:498->assertProcessIsRegistered:1662->HiveITBase.assertEntityIsRegistered:160->HiveITBase.waitFor:204
> Assertions failed. Failing after waiting for timeout 8 msecs
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-1155) Errors in Eclipse when I bring in the latest code
[ https://issues.apache.org/jira/browse/ATLAS-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502363#comment-15502363 ] Shwetha G S commented on ATLAS-1155: +1 > Errors in Eclipse when I bring in the latest code > - > > Key: ATLAS-1155 > URL: https://issues.apache.org/jira/browse/ATLAS-1155 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: David Radley >Assignee: David Radley > Fix For: 0.8-incubating > > Attachments: atlas1155.patch > > > I have brought the latest atlas code into an Eclipse environment and see an > error in GraphBackedDiscoveryService, > line 154 > scala.collection.immutable.List.empty()); it says method empty is ambiguous. > if I replace this expression with null it complies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-1142) Lineage UI Improvement.
[ https://issues.apache.org/jira/browse/ATLAS-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502454#comment-15502454 ] Shwetha G S edited comment on ATLAS-1142 at 9/19/16 6:27 AM: - +1, Committed to master. Thanks Keval was (Author: shwethags): Committed to master. Thanks Keval > Lineage UI Improvement. > --- > > Key: ATLAS-1142 > URL: https://issues.apache.org/jira/browse/ATLAS-1142 > Project: Atlas > Issue Type: Improvement >Reporter: Nixon Rodrigues >Assignee: Keval Bhatt >Priority: Minor > Fix For: 0.8-incubating > > Attachments: ATLAS-1142.1.patch, ATLAS-1142.patch, Screen Shot > 2016-09-15 at 2.16.57 PM.png > > > Following improvement to be done in Lineage UI & entity detail page > * Lineage UI should be resizable. > * All the nodes to be shown in format *name (typename)* -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-712) Support getTrait() API
[ https://issues.apache.org/jira/browse/ATLAS-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-712. --- Resolution: Fixed Fix Version/s: 0.8-incubating Committed to master. Thanks Vimal for the patch, thanks Suma for the review > Support getTrait() API > -- > > Key: ATLAS-712 > URL: https://issues.apache.org/jira/browse/ATLAS-712 > Project: Atlas > Issue Type: Improvement >Reporter: Suma Shivaprasad >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-712-v2.patch, ATLAS-712-v3.patch, > ATLAS-712-v4.patch, ATLAS-712.patch > > > Given entity id and trait name, support rest API that returns the trait > instance for the entity. Currently, the other way of getting it is > getEntity() which returns full entity with all trait instances -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-712) Support getTrait() API
[ https://issues.apache.org/jira/browse/ATLAS-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-712: -- Attachment: ATLAS-712-v4.patch Attached patch with the minor fix for commit > Support getTrait() API > -- > > Key: ATLAS-712 > URL: https://issues.apache.org/jira/browse/ATLAS-712 > Project: Atlas > Issue Type: Improvement >Reporter: Suma Shivaprasad >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-712-v2.patch, ATLAS-712-v3.patch, > ATLAS-712-v4.patch, ATLAS-712.patch > > > Given entity id and trait name, support rest API that returns the trait > instance for the entity. Currently, the other way of getting it is > getEntity() which returns full entity with all trait instances -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1145) Storm hook with kafka topic and hive bolt picks wrong hive table name
[ https://issues.apache.org/jira/browse/ATLAS-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15505532#comment-15505532 ] Shwetha G S commented on ATLAS-1145: Hemanth has one - https://github.com/yhemanth/storm-samples > Storm hook with kafka topic and hive bolt picks wrong hive table name > -- > > Key: ATLAS-1145 > URL: https://issues.apache.org/jira/browse/ATLAS-1145 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Sarath Subramanian > > Storm hook with kafka topic and hive bolt picks kafka topic name as hive > table name -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1175) Type updates should allow removal of optional attributes
[ https://issues.apache.org/jira/browse/ATLAS-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15509085#comment-15509085 ] Shwetha G S commented on ATLAS-1175: Removing the optional attribute is not an issue as it doesn't surface in entity definition. The issue is if the user adds the removed attribute again - in this case, the entities which had the values for old attribute will re-surface again, which is not right. > Type updates should allow removal of optional attributes > > > Key: ATLAS-1175 > URL: https://issues.apache.org/jira/browse/ATLAS-1175 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Suma Shivaprasad >Assignee: Sarath Subramanian > > Currently optional attributes are not allowed to be removed from a given > type. This should be allowed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1122) Change trait edge labels to have trait name alone
[
https://issues.apache.org/jira/browse/ATLAS-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1122:
---
Description: Currently when traits are added to classes they are added with
{{typeName.traitName}} and this is causing edge label creation to fail when
concurrent threads are running transactions. Event though adding retries
mitigates the issue to some extent in ATLAS-1119 and lets the transactions
succeed, there is lesser chance of them failing with edge label creation due to
concurrent transactions with the proposed change since this is a one time
operation that is done once per trait when it is added the first time to any
entity. Also this could potentially be moved to type creation phase when the
trait is created. (was: Currently when traits are added to classes they are
added with {typeName}.{traitName} and this is causing edge label creation to
fail when concurrent threads are running transactions. Event though adding
retries mitigates the issue to some extent in ATLAS-1119 and lets the
transactions succeed, there is lesser chance of them failing with edge label
creation due to concurrent transactions with the proposed change since this is
a one time operation that is done once per trait when it is added the first
time to any entity. Also this could potentially be moved to type creation phase
when the trait is created.)
> Change trait edge labels to have trait name alone
> -
>
> Key: ATLAS-1122
> URL: https://issues.apache.org/jira/browse/ATLAS-1122
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1122.patch
>
>
> Currently when traits are added to classes they are added with
> {{typeName.traitName}} and this is causing edge label creation to fail when
> concurrent threads are running transactions. Event though adding retries
> mitigates the issue to some extent in ATLAS-1119 and lets the transactions
> succeed, there is lesser chance of them failing with edge label creation due
> to concurrent transactions with the proposed change since this is a one time
> operation that is done once per trait when it is added the first time to any
> entity. Also this could potentially be moved to type creation phase when the
> trait is created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1122) Change trait edge labels to have trait name alone
[
https://issues.apache.org/jira/browse/ATLAS-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1122:
---
Attachment: ATLAS-1122.2.patch
Have fixed the test. +1 for the patch
> Change trait edge labels to have trait name alone
> -
>
> Key: ATLAS-1122
> URL: https://issues.apache.org/jira/browse/ATLAS-1122
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1122.2.patch, ATLAS-1122.patch
>
>
> Currently when traits are added to classes they are added with
> {{typeName.traitName}} and this is causing edge label creation to fail when
> concurrent threads are running transactions. Event though adding retries
> mitigates the issue to some extent in ATLAS-1119 and lets the transactions
> succeed, there is lesser chance of them failing with edge label creation due
> to concurrent transactions with the proposed change since this is a one time
> operation that is done once per trait when it is added the first time to any
> entity. Also this could potentially be moved to type creation phase when the
> trait is created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1120) Add a set-up script to pre-create required tables
[ https://issues.apache.org/jira/browse/ATLAS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1120: --- Assignee: (was: Shwetha G S) > Add a set-up script to pre-create required tables > - > > Key: ATLAS-1120 > URL: https://issues.apache.org/jira/browse/ATLAS-1120 > Project: Atlas > Issue Type: Task >Reporter: Shwetha G S > > Add a set-up script to pre-create required tables for graph db and audit > repository. In secure setup, the set-up scripts are required as the set up > needs to be done using admin user, not same as atlas server user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (ATLAS-1120) Add a set-up script to pre-create required tables
[ https://issues.apache.org/jira/browse/ATLAS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1120: --- Comment: was deleted (was: Patch in progress. Need to test with secure environment) > Add a set-up script to pre-create required tables > - > > Key: ATLAS-1120 > URL: https://issues.apache.org/jira/browse/ATLAS-1120 > Project: Atlas > Issue Type: Task >Reporter: Shwetha G S > > Add a set-up script to pre-create required tables for graph db and audit > repository. In secure setup, the set-up scripts are required as the set up > needs to be done using admin user, not same as atlas server user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1120) Add a set-up script to pre-create required tables
[ https://issues.apache.org/jira/browse/ATLAS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1120: --- Attachment: (was: ATLAS-1120.patch) > Add a set-up script to pre-create required tables > - > > Key: ATLAS-1120 > URL: https://issues.apache.org/jira/browse/ATLAS-1120 > Project: Atlas > Issue Type: Task >Reporter: Shwetha G S > > Add a set-up script to pre-create required tables for graph db and audit > repository. In secure setup, the set-up scripts are required as the set up > needs to be done using admin user, not same as atlas server user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1125) Enable compression on hbase audit table
[ https://issues.apache.org/jira/browse/ATLAS-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425895#comment-15425895 ] Shwetha G S commented on ATLAS-1125: Thanks [~suma.shivaprasad] for suggesting this change > Enable compression on hbase audit table > --- > > Key: ATLAS-1125 > URL: https://issues.apache.org/jira/browse/ATLAS-1125 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1125.1.patch, ATLAS-1125.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-674) Falcon Hook should use timestamps instead of long
[ https://issues.apache.org/jira/browse/ATLAS-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426111#comment-15426111 ] Shwetha G S commented on ATLAS-674: --- There are no timestamps in falcon model. The patch here changes an internal variable which is not used anywhere. Can you just remove the variable instead of changing the variable type.? > Falcon Hook should use timestamps instead of long > - > > Key: ATLAS-674 > URL: https://issues.apache.org/jira/browse/ATLAS-674 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Suma Shivaprasad >Assignee: Ayub Khan > Fix For: trunk > > Attachments: ATLAS-674-1.patch, ATLAS-674.patch > > > For eg: TIMESTAMP attribute is of type LONG. should be of type Date. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1126) Fix NPE in getSchema calls
[ https://issues.apache.org/jira/browse/ATLAS-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1126: --- Attachment: ATLAS-1126.2.patch +1 for the patch. Updated patch with the test fixed, renamed hbase audit table columns, Changed supertype for hive_column > Fix NPE in getSchema calls > --- > > Key: ATLAS-1126 > URL: https://issues.apache.org/jira/browse/ATLAS-1126 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: Suma Shivaprasad >Assignee: Suma Shivaprasad > Fix For: 0.8-incubating > > Attachments: ATLAS-1126.2.patch, ATLAS-1126.patch > > > Lineage /schema API results in NPE when the config entry for a entity without > schema query is not found. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1138) UI: Show entity type with the entity name
Shwetha G S created ATLAS-1138: -- Summary: UI: Show entity type with the entity name Key: ATLAS-1138 URL: https://issues.apache.org/jira/browse/ATLAS-1138 Project: Atlas Issue Type: Bug Reporter: Shwetha G S When atlas has entities from different components like mysql table, hdfs path, hie table, the entity names may be same as they represent the same data. In lineage graph and entity details page, all these show up with same name and its confusing for the user. Displaying entity type with name will make it less confusing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-694) Update Atlas code to use abstraction layer
[ https://issues.apache.org/jira/browse/ATLAS-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-694: -- Attachment: ATLAS-694.patch re-based patch > Update Atlas code to use abstraction layer > -- > > Key: ATLAS-694 > URL: https://issues.apache.org/jira/browse/ATLAS-694 > Project: Atlas > Issue Type: Sub-task >Reporter: Jeffrey Hagelberg >Assignee: Jeffrey Hagelberg > Attachments: ATLAS-694.patch, rb47810.patch > > > In this task, we will update Atlas to replace the direct usage of titan > classes with usage of the equivalent interfaces in the abstraction layer. At > this point, there will be no options to configure the abstraction layer > implementation that gets used. Atlas will be hard-coded to use the titan > 0.5.4 implementation. It will also continue to have a compile time > dependency on the titan 0.5.4 graph database implementation. When this task > is complete, Atlas will only be accessing titan through the abstraction layer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1174) Framework to apply updates to types in the type-system
[
https://issues.apache.org/jira/browse/ATLAS-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528662#comment-15528662
]
Shwetha G S commented on ATLAS-1174:
Committing this now, don't see the patch file for position attribute that you
added earlier. You can file a jira for it
> Framework to apply updates to types in the type-system
> --
>
> Key: ATLAS-1174
> URL: https://issues.apache.org/jira/browse/ATLAS-1174
> Project: Atlas
> Issue Type: New Feature
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Labels: feature, patch
> Attachments: ATLAS-1174.patch
>
>
> 1. Introduce "version" attribute to all types in the type-system, this helps
> to track changes made to the default types (hive, sqoop, falcon and storm
> types) and user created types. If version is not mentioned during creation of
> a type, default version "1.0" is assigned (optional attribute).
> 2. Using the version attributed for types, introduce a patch framework for
> type system. This framework applies patches to a type using its version
> number and can be used during upgrade - add new attributes to an existing
> types and it will be run during atlas startup.
> The sequence of steps:
> a. During atlas startup, check $ATLAS_HOME/models/patches directory for
> any available patch files (json files). If there any patch files handle them.
> b. Sample patch json file looks like:
> {
> "patches": [
> {
> "action": "ADD_ATTRIBUTE",
> "typeName": "hive_column",
> "applyToVersion": "1.0",
> "updateToVersion": "2.0",
> "actionParams": [
> { "name": "position",
> "dataTypeName": "int",
> "multiplicity": "optional",
> "isComposite": false,
> "isUnique": false,
> "isIndexable": false,
> "reverseAttributeName": null
> } ]
> } ]
> }
> c. The framework updates the type in "typeName" for the matching version
> number and after applying the patch, update the version to the one mentioned
> in "updateToVersion"
> d. The json file can have more than one action (array of actions).
> e. There can be multiple patch json files in the directory and are
> applied in the sort order of the filename. eg:
> 001-hive_column_add_position.json
> 002-hive_column_add_anotherattribute.json
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-1183) UI: help link should point to atlas website
[ https://issues.apache.org/jira/browse/ATLAS-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528663#comment-15528663 ] Shwetha G S commented on ATLAS-1183: +1 > UI: help link should point to atlas website > --- > > Key: ATLAS-1183 > URL: https://issues.apache.org/jira/browse/ATLAS-1183 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Keval Bhatt > Fix For: 0.8-incubating > > Attachments: ATLAS-1183.patch > > > Help link points to > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=ATLAS=Atlas+Home > which requires login. Instead, link to http://atlas.incubator.apache.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1199) Atlas UI not loading after fresh build due jquery-asBreadcrumbs plugin changes.
[ https://issues.apache.org/jira/browse/ATLAS-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529300#comment-15529300 ] Shwetha G S commented on ATLAS-1199: Is this issue after ATLAS-1142 commit? > Atlas UI not loading after fresh build due jquery-asBreadcrumbs plugin > changes. > --- > > Key: ATLAS-1199 > URL: https://issues.apache.org/jira/browse/ATLAS-1199 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Keval Bhatt >Priority: Blocker > Fix For: 0.7-incubating > > > Atlas UI not loading after fresh build due jquery-asBreadcrumbs plugin > changes. > Found following error in browser console > Overrides.js:22 Uncaught TypeError: Cannot set property > 'generateChildrenInfo' of undefined > GET http://localhost:21000/js/libs/jquery-asBreadcrumbs/css/asBreadcrumbs.css > 404 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1183) UI: help link should point to atlas website
[ https://issues.apache.org/jira/browse/ATLAS-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529316#comment-15529316 ] Shwetha G S commented on ATLAS-1183: Couldn't verify because of issue detailed ATLAS-1199. Will commit post ATLAS-1199 fix > UI: help link should point to atlas website > --- > > Key: ATLAS-1183 > URL: https://issues.apache.org/jira/browse/ATLAS-1183 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Keval Bhatt > Fix For: 0.8-incubating > > Attachments: ATLAS-1183.patch > > > Help link points to > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=ATLAS=Atlas+Home > which requires login. Instead, link to http://atlas.incubator.apache.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1178) APIs in DefaultMetadataService should return POJOs
[ https://issues.apache.org/jira/browse/ATLAS-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522127#comment-15522127 ] Shwetha G S commented on ATLAS-1178: DefaultMetadataService is the API internal to the service. server-api module has only the server side APIs and not exposed to clients. So, lets leave DefaultMetadataService in server-api DefaultMetadataService handles both type and entities related APIs, and hence the name MetadataService Yes, the plan is to remove json awareness from MetadataService, and the serialisation/deserialisation should be transparent to even the rest APIs and should be handled by jersey automatically. Yes, this is to avoid the extra json processing. EntityResult is already a POJO > APIs in DefaultMetadataService should return POJOs > -- > > Key: ATLAS-1178 > URL: https://issues.apache.org/jira/browse/ATLAS-1178 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > > DefaultMetadataService APIs accept/return json strings and the rest APIs end > up serialising and deserialising everytime. DefaultMetadataService APIs are > internal APIs and should accept/return POJOs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1205) Improve atlas build time
[ https://issues.apache.org/jira/browse/ATLAS-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1205: --- Attachment: ATLAS-1205.patch 1. Moved copy jars to dist profile as the copied jars are required only for atlas package. Atlas package is built only in dist profile, and copying jars is not useful otherwise 2. Moved scala plugin to specific modules 3. Removed building zip package, as there is already tag.gz package built > Improve atlas build time > > > Key: ATLAS-1205 > URL: https://issues.apache.org/jira/browse/ATLAS-1205 > Project: Atlas > Issue Type: Improvement >Reporter: Shwetha G S >Assignee: Shwetha G S >Priority: Minor > Fix For: 0.8-incubating > > Attachments: ATLAS-1205.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1205) Improve atlas build time
Shwetha G S created ATLAS-1205: -- Summary: Improve atlas build time Key: ATLAS-1205 URL: https://issues.apache.org/jira/browse/ATLAS-1205 Project: Atlas Issue Type: Improvement Reporter: Shwetha G S Assignee: Shwetha G S Priority: Minor Fix For: 0.8-incubating -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1203) 'Invalid type definition' error during startup
[
https://issues.apache.org/jira/browse/ATLAS-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15540307#comment-15540307
]
Shwetha G S commented on ATLAS-1203:
+1
> 'Invalid type definition' error during startup
> --
>
> Key: ATLAS-1203
> URL: https://issues.apache.org/jira/browse/ATLAS-1203
> Project: Atlas
> Issue Type: Bug
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Attachments: ATLAS-1203.patch
>
>
> After the fix for ATLAS-1184, following exception/error is seen in Atlas
> server logs during startup:
> {code}
> 2016-10-01 05:55:27,437 INFO - [main:] ~ Initializing type system for the
> first time. (DefaultMetadataService:165)
> 2016-10-01 05:55:27,751 ERROR - [main:] ~ Unable to deserialize json={
> "enumTypes":[
> ],
> "structTypes":[
> ],
> "traitTypes":[
> ],
> "classTypes":[
> ]
> } (DefaultMetadataService:286)
> java.lang.IllegalArgumentException: Invalid type definition
> at
> org.apache.atlas.services.DefaultMetadataService.validateTypeDefinition(DefaultMetadataService.java:282)
> at
> org.apache.atlas.services.DefaultMetadataService.createOrUpdateTypes(DefaultMetadataService.java:244)
> at
> org.apache.atlas.services.DefaultMetadataService.createType(DefaultMetadataService.java:239)
> at
> org.apache.atlas.services.ReservedTypesRegistrar.registerType(ReservedTypesRegistrar.java:124)
> at
> org.apache.atlas.services.ReservedTypesRegistrar.registerTypes(ReservedTypesRegistrar.java:69)
> at
> org.apache.atlas.services.DefaultMetadataService.restoreTypeSystem(DefaultMetadataService.java:170)
> at
> org.apache.atlas.services.DefaultMetadataService.(DefaultMetadataService.java:153)
> at
> org.apache.atlas.services.DefaultMetadataService.(DefaultMetadataService.java:118)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> ...
> ...
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:93)
> at org.apache.atlas.Atlas.main(Atlas.java:118)
> 2016-10-01 05:55:27,762 INFO - [main:] ~ Restoring type system from the
> store (DefaultMetadataService:162)
> 2016-10-01 05:55:27,770 INFO - [main:] ~ Restoring type CLASS.fs_path.null
> (GraphBackedTypeStore:243)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1203) 'Invalid type definition' due to no new types to be created at startup
[
https://issues.apache.org/jira/browse/ATLAS-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1203:
---
Summary: 'Invalid type definition' due to no new types to be created at
startup (was: 'Invalid type definition' error during startup)
> 'Invalid type definition' due to no new types to be created at startup
> --
>
> Key: ATLAS-1203
> URL: https://issues.apache.org/jira/browse/ATLAS-1203
> Project: Atlas
> Issue Type: Bug
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Attachments: ATLAS-1203.patch
>
>
> After the fix for ATLAS-1184, following exception/error is seen in Atlas
> server logs during startup:
> {code}
> 2016-10-01 05:55:27,437 INFO - [main:] ~ Initializing type system for the
> first time. (DefaultMetadataService:165)
> 2016-10-01 05:55:27,751 ERROR - [main:] ~ Unable to deserialize json={
> "enumTypes":[
> ],
> "structTypes":[
> ],
> "traitTypes":[
> ],
> "classTypes":[
> ]
> } (DefaultMetadataService:286)
> java.lang.IllegalArgumentException: Invalid type definition
> at
> org.apache.atlas.services.DefaultMetadataService.validateTypeDefinition(DefaultMetadataService.java:282)
> at
> org.apache.atlas.services.DefaultMetadataService.createOrUpdateTypes(DefaultMetadataService.java:244)
> at
> org.apache.atlas.services.DefaultMetadataService.createType(DefaultMetadataService.java:239)
> at
> org.apache.atlas.services.ReservedTypesRegistrar.registerType(ReservedTypesRegistrar.java:124)
> at
> org.apache.atlas.services.ReservedTypesRegistrar.registerTypes(ReservedTypesRegistrar.java:69)
> at
> org.apache.atlas.services.DefaultMetadataService.restoreTypeSystem(DefaultMetadataService.java:170)
> at
> org.apache.atlas.services.DefaultMetadataService.(DefaultMetadataService.java:153)
> at
> org.apache.atlas.services.DefaultMetadataService.(DefaultMetadataService.java:118)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> ...
> ...
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:93)
> at org.apache.atlas.Atlas.main(Atlas.java:118)
> 2016-10-01 05:55:27,762 INFO - [main:] ~ Restoring type system from the
> store (DefaultMetadataService:162)
> 2016-10-01 05:55:27,770 INFO - [main:] ~ Restoring type CLASS.fs_path.null
> (GraphBackedTypeStore:243)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ATLAS-1116) Performance monitoring of backend methods in API requests
[ https://issues.apache.org/jira/browse/ATLAS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S reassigned ATLAS-1116: -- Assignee: Shwetha G S (was: Vimal Sharma) > Performance monitoring of backend methods in API requests > - > > Key: ATLAS-1116 > URL: https://issues.apache.org/jira/browse/ATLAS-1116 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1116.patch > > > Time taken by methods used in API calls for add/update/delete entities and > traits need to be monitored for performance -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1246) Upgrade versions of dependencies
Shwetha G S created ATLAS-1246: -- Summary: Upgrade versions of dependencies Key: ATLAS-1246 URL: https://issues.apache.org/jira/browse/ATLAS-1246 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Assignee: Shwetha G S Attachments: ATLAS-1246.patch 1. Expose variables for setting zookeeper version 2. Upgrade the versions of libraries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1246) Upgrade versions of dependencies
[ https://issues.apache.org/jira/browse/ATLAS-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1246: --- Attachment: ATLAS-1246.patch > Upgrade versions of dependencies > > > Key: ATLAS-1246 > URL: https://issues.apache.org/jira/browse/ATLAS-1246 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Attachments: ATLAS-1246.patch > > > 1. Expose variables for setting zookeeper version > 2. Upgrade the versions of libraries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1247) Support for hive 2.x
[ https://issues.apache.org/jira/browse/ATLAS-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15610942#comment-15610942 ] Shwetha G S commented on ATLAS-1247: Did the atlas hive hook work with hive 2.1.0? If it didn't work, you can try to figure out the issues. Another is to change hive.version in hive-bridge/pom.xml to 2.1.0 and make sure the tests pass. Vimal had an initial patch, attaching here > Support for hive 2.x > > > Key: ATLAS-1247 > URL: https://issues.apache.org/jira/browse/ATLAS-1247 > Project: Atlas > Issue Type: Improvement >Reporter: Shwetha G S >Assignee: Vimal Sharma > Attachments: hive2_atlas.patch > > > Atlas hive hook works only with hive 1.x. Need support for hive 2.x -- This message was sent by Atlassian JIRA (v6.3.4#6332)
