[jira] [Commented] (ATLAS-360) Secure cluster Atlas-solr integration instructions
[
https://issues.apache.org/jira/browse/ATLAS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059674#comment-15059674
]
Suma Shivaprasad commented on ATLAS-360:
[~tbeerbower]
Can you pls remove the following and refer to the section which has the same
steps in InstallationSyeps.twiki to avoid copies? If theres anything missing
there , pls add to it
{noformat}
+ * Run the following commands from SOLR_HOME directory to create collections
in Solr corresponding to the indexes that Atlas uses. In the case that the
ATLAS and SOLR instance are on 2 different hosts, first copy the required
configuration files from ATLAS_HOME/conf/solr on the ATLAS instance host to the
Solr instance host. SOLR_CONF in the below mentioned commands refer to the
directory where the solr configuration files have been copied to on Solr host:
+
+
+ $SOLR_INSTALL_HOME/bin/solr create -c vertex_index -d $SOLR_CONF -shards
-replicationFactor
+ $SOLR_INSTALL_HOME/bin/solr create -c edge_index -d $SOLR_CONF -shards
-replicationFactor
+ $SOLR_INSTALL_HOME/bin/solr create -c fulltext_index -d $SOLR_CONF -shards
-replicationFactor
+
+
+ Note: If numShards and replicationFactor are not specified, they default to
1 which suffices if you are trying out solr with ATLAS on a single node
instance. Otherwise specify numShards according to the number of hosts that
are in the Solr cluster and the maxShardsPerNode configuration. The number of
shards cannot exceed the total number of Solr nodes in your SolrCloud cluster
+
+ * Change ATLAS configuration to point to the Solr instance setup. Please
make sure the following configurations are set to the below values in
ATLAS_HOME//conf/application.properties
+
+
+ atlas.graph.index.search.backend=solr5
+ atlas.graph.index.search.solr.mode=cloud
+ atlas.graph.index.search.solr.zookeeper-url= eg: 10.1.6.4:2181,10.1.6.5:2181
+
{noformat}
> Secure cluster Atlas-solr integration instructions
> --
>
> Key: ATLAS-360
> URL: https://issues.apache.org/jira/browse/ATLAS-360
> Project: Atlas
> Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: ATLAS-360.patch
>
>
> Kerberized secure cluster solr configuration instructions for Atlas.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-263) Searching for a multi word trait always returns empty result
[
https://issues.apache.org/jira/browse/ATLAS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059678#comment-15059678
]
Suma Shivaprasad commented on ATLAS-263:
+1
> Searching for a multi word trait always returns empty result
>
>
> Key: ATLAS-263
> URL: https://issues.apache.org/jira/browse/ATLAS-263
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Ayub Khan
>Assignee: Girish Ramachandran
>Priority: Blocker
> Fix For: trunk
>
> Attachments: multi_word_trait_changes.patch, types_query_fix.patch
>
>
> Searching for a multi word trait always returns empty result..
> 1. Create a trait name with multiple words..
> Example:
> {noformat}
> curl 'http://localhost:21000/api/atlas/types' -H 'Origin:
> http://localhost:21000' -H 'Content-Type: application/json;charset=UTF-8'
> --data-binary
> '{"enumTypes":[],"traitTypes":[{"superTypes":[],"typeName":"multi word
> trait","attributeDefinitions":[],"hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType"}],"structTypes":[],"classTypes":[]}'
> --compressed
> {noformat}
> 2. Attach the tag with an entity
> Example:
> {noformat}
> curl -v
> 'http://localhost:21000/api/atlas/entity/803f5bdd-28f9-49e1-8c21-3dc0f9fd5c61/traits'
> -H 'Content-Type: application/json;charset=UTF-8' --data-binary
> '{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct","typeName":"multi
> word trait","values":{}}' --compressed
> {noformat}
> 3. Now try to get all the entities associated with the tag
> Example:
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/discovery/search?query=multi+word+trait'
> {noformat}
>
> Result of the above is always empty because the above query is
> triggered as "full text" and it always returns empty result even if you have
> associated entites to the tag.
>
> This is a big issue from an end user's perspective. marking this as a blocker
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-385) Support for Lineage for entities with SuperType as DataSet
[ https://issues.apache.org/jira/browse/ATLAS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-385: Attachment: ATLAS-385-v1.patch > Support for Lineage for entities with SuperType as DataSet > --- > > Key: ATLAS-385 > URL: https://issues.apache.org/jira/browse/ATLAS-385 > Project: Atlas > Issue Type: Improvement >Affects Versions: trunk >Reporter: Rishabh Bhardwaj >Assignee: Anilsg > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385-v1.patch, ATLAS-385.patch, > feed_enhancements.txt, lineage.png, sample_graph_api_output.txt > > > Currently from the trunk code,the lineage only comes to type "Table" while > previously It used to come when `superType` is "DataSet" for the entities. > Due to this change now lineage only comes for the entities of type "Table" > and not for custom entities with superType 'DataSet'. > Can we get this support for DataSet back ? > Or is there any workaround for the same ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-383) hive-import seems broken in Atlas trunk and 0.6 release candidate.
[
https://issues.apache.org/jira/browse/ATLAS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suma Shivaprasad updated ATLAS-383:
---
Attachment: ATLAS-383.patch
This has been fixed as part of ATLAS-386 but unit tests for the change were
missing. Have added that here.
> hive-import seems broken in Atlas trunk and 0.6 release candidate.
> --
>
> Key: ATLAS-383
> URL: https://issues.apache.org/jira/browse/ATLAS-383
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating, trunk
>Reporter: Hemanth Yamijala
>Priority: Blocker
> Fix For: 0.6-incubating, trunk
>
> Attachments: ATLAS-383.patch, hive_import_rc_bug.txt
>
>
> I ran hive-import on both trunk and the release candidate, and both failed
> with a stack trace. My hive had a simple table with 2 columns - but I think
> it is immaterial.
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata
> service API CREATE_ENTITY failed with status 400(Bad Request) Response Body
> ({"error":"Cannot convert value '{Id='(type: hive_storagedesc, id:
> d85dcf0f-8e42-4416-ae47-7a20acfbeb7b)', traits=[], values={}}' to datatype
> hive_storagedesc","stackTrace":"org.apache.atlas.typesystem.types.ValueConversionException:
> Cannot convert value '{Id='(type: hive_storagedesc, id:
> d85dcf0f-8e42-4416-ae47-7a20acfbeb7b)', traits=[], values={}}' to datatype
> hive_storagedesc\n\tat
> org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:145)\n\tat
> org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:43)\n\tat
> org.apache.atlas.typesystem.persistence.StructInstance.set(StructInstance.java:122)\n\tat
>
> org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:143)\n\tat
> org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:307)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:280)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:114)\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:288)\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:1469)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)\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:67)\n\tat
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\
[jira] [Updated] (ATLAS-383) hive-import seems broken in Atlas trunk and 0.6 release candidate.
[
https://issues.apache.org/jira/browse/ATLAS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suma Shivaprasad updated ATLAS-383:
---
Fix Version/s: trunk
0.6-incubating
> hive-import seems broken in Atlas trunk and 0.6 release candidate.
> --
>
> Key: ATLAS-383
> URL: https://issues.apache.org/jira/browse/ATLAS-383
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating, trunk
>Reporter: Hemanth Yamijala
>Assignee: Suma Shivaprasad
>Priority: Blocker
> Fix For: 0.6-incubating, trunk
>
> Attachments: ATLAS-383.patch, hive_import_rc_bug.txt
>
>
> I ran hive-import on both trunk and the release candidate, and both failed
> with a stack trace. My hive had a simple table with 2 columns - but I think
> it is immaterial.
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata
> service API CREATE_ENTITY failed with status 400(Bad Request) Response Body
> ({"error":"Cannot convert value '{Id='(type: hive_storagedesc, id:
> d85dcf0f-8e42-4416-ae47-7a20acfbeb7b)', traits=[], values={}}' to datatype
> hive_storagedesc","stackTrace":"org.apache.atlas.typesystem.types.ValueConversionException:
> Cannot convert value '{Id='(type: hive_storagedesc, id:
> d85dcf0f-8e42-4416-ae47-7a20acfbeb7b)', traits=[], values={}}' to datatype
> hive_storagedesc\n\tat
> org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:145)\n\tat
> org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:43)\n\tat
> org.apache.atlas.typesystem.persistence.StructInstance.set(StructInstance.java:122)\n\tat
>
> org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:143)\n\tat
> org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:307)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:280)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:114)\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:288)\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:1469)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)\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:67)\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.GuiceFilt
[jira] [Assigned] (ATLAS-383) hive-import seems broken in Atlas trunk and 0.6 release candidate.
[
https://issues.apache.org/jira/browse/ATLAS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suma Shivaprasad reassigned ATLAS-383:
--
Assignee: Suma Shivaprasad
> hive-import seems broken in Atlas trunk and 0.6 release candidate.
> --
>
> Key: ATLAS-383
> URL: https://issues.apache.org/jira/browse/ATLAS-383
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating, trunk
>Reporter: Hemanth Yamijala
>Assignee: Suma Shivaprasad
>Priority: Blocker
> Fix For: 0.6-incubating, trunk
>
> Attachments: ATLAS-383.patch, hive_import_rc_bug.txt
>
>
> I ran hive-import on both trunk and the release candidate, and both failed
> with a stack trace. My hive had a simple table with 2 columns - but I think
> it is immaterial.
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata
> service API CREATE_ENTITY failed with status 400(Bad Request) Response Body
> ({"error":"Cannot convert value '{Id='(type: hive_storagedesc, id:
> d85dcf0f-8e42-4416-ae47-7a20acfbeb7b)', traits=[], values={}}' to datatype
> hive_storagedesc","stackTrace":"org.apache.atlas.typesystem.types.ValueConversionException:
> Cannot convert value '{Id='(type: hive_storagedesc, id:
> d85dcf0f-8e42-4416-ae47-7a20acfbeb7b)', traits=[], values={}}' to datatype
> hive_storagedesc\n\tat
> org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:145)\n\tat
> org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:43)\n\tat
> org.apache.atlas.typesystem.persistence.StructInstance.set(StructInstance.java:122)\n\tat
>
> org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:143)\n\tat
> org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:307)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:280)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:114)\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:288)\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:1469)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)\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:67)\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
[jira] [Updated] (ATLAS-385) Support for Lineage for entities with SuperType as DataSet
[ https://issues.apache.org/jira/browse/ATLAS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-385: Attachment: ATLAS-385-v2.patch > Support for Lineage for entities with SuperType as DataSet > --- > > Key: ATLAS-385 > URL: https://issues.apache.org/jira/browse/ATLAS-385 > Project: Atlas > Issue Type: Improvement >Affects Versions: trunk >Reporter: Rishabh Bhardwaj >Assignee: Anilsg > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385-v1.patch, ATLAS-385-v2.patch, ATLAS-385.patch, > feed_enhancements.txt, lineage.png, sample_graph_api_output.txt > > > Currently from the trunk code,the lineage only comes to type "Table" while > previously It used to come when `superType` is "DataSet" for the entities. > Due to this change now lineage only comes for the entities of type "Table" > and not for custom entities with superType 'DataSet'. > Can we get this support for DataSet back ? > Or is there any workaround for the same ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-381) HiveMetaStoreBridge will not connect to a kerberized hive metastore
[ https://issues.apache.org/jira/browse/ATLAS-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059817#comment-15059817 ] Tom Beerbower commented on ATLAS-381: - [~dossett], Could you attach your /etc/atlas/conf/client.properties? > HiveMetaStoreBridge will not connect to a kerberized hive metastore > --- > > Key: ATLAS-381 > URL: https://issues.apache.org/jira/browse/ATLAS-381 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Aaron Dossett >Assignee: Aaron Dossett > > Running the HiveMetaStoreBridge on a kerberized cluster gives the error > below, because it does not do any authentication for kerberos. > 2015-12-09 13:07:37,880 ERROR - [main:] ~ SASL negotiation failure > (TSaslTransport:315) > javax.security.sasl.SaslException: GSS initiate failed [Caused by > GSSException: No valid credentials provided (Mechanism level: Failed to find > any Kerberos tgt)] > at > com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:212) > at > org.apache.thrift.transport.TSaslClientTransport.handleSaslStartMessage(TSaslClientTransport.java:94) > at > org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:271) > at > org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37) > at > org.apache.hadoop.hive.thrift.client.TUGIAssumingTransport$1.run(TUGIAssumingTransport.java:52) > at > org.apache.hadoop.hive.thrift.client.TUGIAssumingTransport$1.run(TUGIAssumingTransport.java:49) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:415) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657) > at > org.apache.hadoop.hive.thrift.client.TUGIAssumingTransport.open(TUGIAssumingTransport.java:49) > at > org.apache.hadoop.hive.metastore.HiveMetaStoreClient.open(HiveMetaStoreClient.java:420) > at > org.apache.hadoop.hive.metastore.HiveMetaStoreClient.(HiveMetaStoreClient.java:236) > at > org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient.(SessionHiveMetaStoreClient.java:74) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at > org.apache.hadoop.hive.metastore.MetaStoreUtils.newInstance(MetaStoreUtils.java:1521) > at > org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.(RetryingMetaStoreClient.java:86) > at > org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.getProxy(RetryingMetaStoreClient.java:132) > at > org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.getProxy(RetryingMetaStoreClient.java:104) > at > org.apache.hadoop.hive.ql.metadata.Hive.createMetaStoreClient(Hive.java:3005) > at org.apache.hadoop.hive.ql.metadata.Hive.getMSC(Hive.java:3024) > at > org.apache.hadoop.hive.ql.metadata.Hive.getAllDatabases(Hive.java:1234) > at > org.apache.hadoop.hive.ql.metadata.Hive.reloadFunctions(Hive.java:174) > at org.apache.hadoop.hive.ql.metadata.Hive.(Hive.java:166) > at > org.apache.atlas.hive.bridge.HiveMetaStoreBridge.(HiveMetaStoreBridge.java:80) > at > org.apache.atlas.hive.bridge.HiveMetaStoreBridge.(HiveMetaStoreBridge.java:70) > at > org.apache.atlas.hive.bridge.HiveMetaStoreBridge.main(HiveMetaStoreBridge.java:494) > Caused by: GSSException: No valid credentials provided (Mechanism level: > Failed to find any Kerberos tgt) > at > sun.security.jgss.krb5.Krb5InitCredential.getInstance(Krb5InitCredential.java:147) > at > sun.security.jgss.krb5.Krb5MechFactory.getCredentialElement(Krb5MechFactory.java:121) > at > sun.security.jgss.krb5.Krb5MechFactory.getMechanismContext(Krb5MechFactory.java:187) > at > sun.security.jgss.GSSManagerImpl.getMechanismContext(GSSManagerImpl.java:223) > at > sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:212) > at > sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:179) > at > com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:193) > ... 28 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-360) Secure cluster Atlas-solr integration instructions
[ https://issues.apache.org/jira/browse/ATLAS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Beerbower updated ATLAS-360: Attachment: ATLAS-360.patch > Secure cluster Atlas-solr integration instructions > -- > > Key: ATLAS-360 > URL: https://issues.apache.org/jira/browse/ATLAS-360 > Project: Atlas > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > Attachments: ATLAS-360.patch > > > Kerberized secure cluster solr configuration instructions for Atlas. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-360) Secure cluster Atlas-solr integration instructions
[ https://issues.apache.org/jira/browse/ATLAS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Beerbower updated ATLAS-360: Attachment: (was: ATLAS-360.patch) > Secure cluster Atlas-solr integration instructions > -- > > Key: ATLAS-360 > URL: https://issues.apache.org/jira/browse/ATLAS-360 > Project: Atlas > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > Attachments: ATLAS-360.patch > > > Kerberized secure cluster solr configuration instructions for Atlas. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-360) Secure cluster Atlas-solr integration instructions
[ https://issues.apache.org/jira/browse/ATLAS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059979#comment-15059979 ] Tom Beerbower commented on ATLAS-360: - [~suma.shivaprasad], Thanks for the review! I've made the suggested change to remove the text and instead link to the installation steps. I've also made a number of clean up changes in the InstallationSteps.twiki. I've uploaded a new patch here and on the review board. > Secure cluster Atlas-solr integration instructions > -- > > Key: ATLAS-360 > URL: https://issues.apache.org/jira/browse/ATLAS-360 > Project: Atlas > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > Attachments: ATLAS-360.patch > > > Kerberized secure cluster solr configuration instructions for Atlas. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-181) Integrate storm topology metadata into Atlas
[ https://issues.apache.org/jira/browse/ATLAS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060146#comment-15060146 ] Sriharsha Chintalapani commented on ATLAS-181: -- [~svenkat] [~yhemanth] Yes extlib is the right dir. > Integrate storm topology metadata into Atlas > > > Key: ATLAS-181 > URL: https://issues.apache.org/jira/browse/ATLAS-181 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Venkatesh Seetharam > Fix For: 0.6-incubating > > Attachments: ATLAS-181.patch, > ApacheStormIntegrationWithApacheAtlas.pdf > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-20) Rename env variables from METADATA to ATLAS
[ https://issues.apache.org/jira/browse/ATLAS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060370#comment-15060370 ] John Speidel commented on ATLAS-20: --- [~suma.shivaprasad] The changes to environment variable names in the patch will require changes in Ambari since Ambari sets these env vars such as "METADATA_CONF", etc. Without these Ambari changes, Ambari will be unable to start Atlas after the env var name changes. > Rename env variables from METADATA to ATLAS > --- > > Key: ATLAS-20 > URL: https://issues.apache.org/jira/browse/ATLAS-20 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.5-incubating >Reporter: Venkatesh Seetharam >Assignee: Rishabh Bhardwaj > Attachments: ATLAS-20.patch, ATLAS-20.v2.patch, ATLAS-20.v3.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-106) Store createTimestamp and modified timestamp separately for an entity
[ https://issues.apache.org/jira/browse/ATLAS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Kantor updated ATLAS-106: --- Attachment: (was: ATLAS-106-v5.patch) > Store createTimestamp and modified timestamp separately for an entity > - > > Key: ATLAS-106 > URL: https://issues.apache.org/jira/browse/ATLAS-106 > Project: Atlas > Issue Type: Improvement >Reporter: Suma Shivaprasad >Assignee: David Kantor > Attachments: ATLAS-106-v6.patch > > > Currently we store only the Create timestamp in atlas. Would be better to > separate to track create and modified time separately , in cases where we > want to support search queries give all entities which have been modified in > the past 1 day etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-106) Store createTimestamp and modified timestamp separately for an entity
[ https://issues.apache.org/jira/browse/ATLAS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060836#comment-15060836 ] David Kantor commented on ATLAS-106: [~suma.shivaprasad] Thanks for reviewing the code. I have addressed your comments and attached an updated patch which contains all changes. Please let me know if there is anything further needed for this enhancement. > Store createTimestamp and modified timestamp separately for an entity > - > > Key: ATLAS-106 > URL: https://issues.apache.org/jira/browse/ATLAS-106 > Project: Atlas > Issue Type: Improvement >Reporter: Suma Shivaprasad >Assignee: David Kantor > Attachments: ATLAS-106-v6.patch > > > Currently we store only the Create timestamp in atlas. Would be better to > separate to track create and modified time separately , in cases where we > want to support search queries give all entities which have been modified in > the past 1 day etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-106) Store createTimestamp and modified timestamp separately for an entity
[ https://issues.apache.org/jira/browse/ATLAS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Kantor updated ATLAS-106: --- Attachment: ATLAS-106-v6.patch > Store createTimestamp and modified timestamp separately for an entity > - > > Key: ATLAS-106 > URL: https://issues.apache.org/jira/browse/ATLAS-106 > Project: Atlas > Issue Type: Improvement >Reporter: Suma Shivaprasad >Assignee: David Kantor > Attachments: ATLAS-106-v6.patch > > > Currently we store only the Create timestamp in atlas. Would be better to > separate to track create and modified time separately , in cases where we > want to support search queries give all entities which have been modified in > the past 1 day etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-360) Secure cluster Atlas-solr integration instructions
[ https://issues.apache.org/jira/browse/ATLAS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061368#comment-15061368 ] Chethana commented on ATLAS-360: The solr changes look good > Secure cluster Atlas-solr integration instructions > -- > > Key: ATLAS-360 > URL: https://issues.apache.org/jira/browse/ATLAS-360 > Project: Atlas > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > Attachments: ATLAS-360.patch > > > Kerberized secure cluster solr configuration instructions for Atlas. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-360) Secure cluster Atlas-solr integration instructions
[ https://issues.apache.org/jira/browse/ATLAS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061368#comment-15061368 ] Chethana edited comment on ATLAS-360 at 12/17/15 2:50 AM: -- The solr changes for secure cluster looks good was (Author: ckrishnakumar): The solr changes look good > Secure cluster Atlas-solr integration instructions > -- > > Key: ATLAS-360 > URL: https://issues.apache.org/jira/browse/ATLAS-360 > Project: Atlas > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > Attachments: ATLAS-360.patch > > > Kerberized secure cluster solr configuration instructions for Atlas. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-392) Rename application.properties to atlas-application.properties
[ https://issues.apache.org/jira/browse/ATLAS-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishabh Bhardwaj reassigned ATLAS-392: -- Assignee: Rishabh Bhardwaj > Rename application.properties to atlas-application.properties > - > > Key: ATLAS-392 > URL: https://issues.apache.org/jira/browse/ATLAS-392 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Rishabh Bhardwaj > > Atlas conf needs to be included in other components for hooks. The name > resolution can conflict and hence use properties filename should be atlas > specific -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-393) Upgrade to kafka 0.9
Shwetha G S created ATLAS-393: - Summary: Upgrade to kafka 0.9 Key: ATLAS-393 URL: https://issues.apache.org/jira/browse/ATLAS-393 Project: Atlas Issue Type: Improvement Reporter: Shwetha G S Kafka security is available with 0.9. Atlas doesn't compile with 0.9 kafka, need some changes in atlas. 0.9 kafka client should be compatible with 0.8.x kafka server, but we should test is once -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-385) Support for Lineage for entities with SuperType as DataSet
[ https://issues.apache.org/jira/browse/ATLAS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061504#comment-15061504 ] Hemanth Yamijala commented on ATLAS-385: I tested the patch and while overall it seems fine, there is one issue that I do observe and want to be sure its not an issue before I certify. The first time I search for an entity - the graph service queries are not fired and the lineage does not show. I seem to have to search for one of the entities for which lineage was always working like a hive_table to activate this and after that all works fine.. Can you please try and test this scenario? Thanks Hemanth > Support for Lineage for entities with SuperType as DataSet > --- > > Key: ATLAS-385 > URL: https://issues.apache.org/jira/browse/ATLAS-385 > Project: Atlas > Issue Type: Improvement >Affects Versions: trunk >Reporter: Rishabh Bhardwaj >Assignee: Anilsg > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385-v1.patch, ATLAS-385-v2.patch, ATLAS-385.patch, > feed_enhancements.txt, lineage.png, sample_graph_api_output.txt > > > Currently from the trunk code,the lineage only comes to type "Table" while > previously It used to come when `superType` is "DataSet" for the entities. > Due to this change now lineage only comes for the entities of type "Table" > and not for custom entities with superType 'DataSet'. > Can we get this support for DataSet back ? > Or is there any workaround for the same ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-394) Fix BaseResourceIT.waitForNotification()
Shwetha G S created ATLAS-394: - Summary: Fix BaseResourceIT.waitForNotification() Key: ATLAS-394 URL: https://issues.apache.org/jira/browse/ATLAS-394 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Assignee: Shwetha G S EntityNotificationConsumer sets entityNotification to the last read notification waitForNotification returns with the last read notification which may not be the expected one. waitForNotification() should accept a predicate instead -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-385) Support for Lineage for entities with SuperType as DataSet
[ https://issues.apache.org/jira/browse/ATLAS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061640#comment-15061640 ] Darshan Kumar commented on ATLAS-385: - Thanks [~yhemanth] Will update the patch with this fix please let me know if anything. Thanks > Support for Lineage for entities with SuperType as DataSet > --- > > Key: ATLAS-385 > URL: https://issues.apache.org/jira/browse/ATLAS-385 > Project: Atlas > Issue Type: Improvement >Affects Versions: trunk >Reporter: Rishabh Bhardwaj >Assignee: Anilsg > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385-v1.patch, ATLAS-385-v2.patch, ATLAS-385.patch, > feed_enhancements.txt, lineage.png, sample_graph_api_output.txt > > > Currently from the trunk code,the lineage only comes to type "Table" while > previously It used to come when `superType` is "DataSet" for the entities. > Due to this change now lineage only comes for the entities of type "Table" > and not for custom entities with superType 'DataSet'. > Can we get this support for DataSet back ? > Or is there any workaround for the same ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-385) Support for Lineage for entities with SuperType as DataSet
[ https://issues.apache.org/jira/browse/ATLAS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-385: Attachment: ATLAS-385-v4.patch > Support for Lineage for entities with SuperType as DataSet > --- > > Key: ATLAS-385 > URL: https://issues.apache.org/jira/browse/ATLAS-385 > Project: Atlas > Issue Type: Improvement >Affects Versions: trunk >Reporter: Rishabh Bhardwaj >Assignee: Anilsg > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385-v1.patch, ATLAS-385-v2.patch, > ATLAS-385-v4.patch, ATLAS-385.patch, feed_enhancements.txt, lineage.png, > sample_graph_api_output.txt > > > Currently from the trunk code,the lineage only comes to type "Table" while > previously It used to come when `superType` is "DataSet" for the entities. > Due to this change now lineage only comes for the entities of type "Table" > and not for custom entities with superType 'DataSet'. > Can we get this support for DataSet back ? > Or is there any workaround for the same ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-385) Support for Lineage for entities with SuperType as DataSet
[ https://issues.apache.org/jira/browse/ATLAS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-385: Attachment: ATLAS-385-v3.patch > Support for Lineage for entities with SuperType as DataSet > --- > > Key: ATLAS-385 > URL: https://issues.apache.org/jira/browse/ATLAS-385 > Project: Atlas > Issue Type: Improvement >Affects Versions: trunk >Reporter: Rishabh Bhardwaj >Assignee: Anilsg > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385-v1.patch, ATLAS-385-v2.patch, > ATLAS-385-v3.patch, ATLAS-385.patch, feed_enhancements.txt, lineage.png, > sample_graph_api_output.txt > > > Currently from the trunk code,the lineage only comes to type "Table" while > previously It used to come when `superType` is "DataSet" for the entities. > Due to this change now lineage only comes for the entities of type "Table" > and not for custom entities with superType 'DataSet'. > Can we get this support for DataSet back ? > Or is there any workaround for the same ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-385) Support for Lineage for entities with SuperType as DataSet
[ https://issues.apache.org/jira/browse/ATLAS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-385: Attachment: (was: ATLAS-385-v4.patch) > Support for Lineage for entities with SuperType as DataSet > --- > > Key: ATLAS-385 > URL: https://issues.apache.org/jira/browse/ATLAS-385 > Project: Atlas > Issue Type: Improvement >Affects Versions: trunk >Reporter: Rishabh Bhardwaj >Assignee: Anilsg > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-385-v1.patch, ATLAS-385-v2.patch, > ATLAS-385-v3.patch, ATLAS-385.patch, feed_enhancements.txt, lineage.png, > sample_graph_api_output.txt > > > Currently from the trunk code,the lineage only comes to type "Table" while > previously It used to come when `superType` is "DataSet" for the entities. > Due to this change now lineage only comes for the entities of type "Table" > and not for custom entities with superType 'DataSet'. > Can we get this support for DataSet back ? > Or is there any workaround for the same ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
