[jira] [Commented] (ATLAS-297) KafkaNotificationTest.testSendReceiveMessage fails when atlas-server is running on the same machine

2015-11-10 Thread Hemanth Yamijala (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1457#comment-1457
 ] 

Hemanth Yamijala commented on ATLAS-297:


The failure is because the running Atlas server also binds its sockets to the 
same ports as what the test needs - at least for Zookeeper server (port 9026)



> KafkaNotificationTest.testSendReceiveMessage fails when atlas-server is 
> running on the same machine 
> 
>
> Key: ATLAS-297
> URL: https://issues.apache.org/jira/browse/ATLAS-297
> Project: Atlas
>  Issue Type: Bug
> Environment: Dev environment 
>Reporter: Hemanth Yamijala
>Priority: Minor
>
> Start the atlas-server on local machine. Then execute mvn 
> -Dtest=KafkaNotificationTest -DfailIfNoTests=false test
> Get the following stack trace and test failure:
> Running org.apache.atlas.kafka.KafkaNotificationTest
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 1.262 sec <<< 
> FAILURE! - in org.apache.atlas.kafka.KafkaNotificationTest
> setUp(org.apache.atlas.kafka.KafkaNotificationTest)  Time elapsed: 0.88 sec  
> <<< FAILURE!
> org.apache.atlas.AtlasException: Failed to start embedded kafka
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Net.java:463)
>   at sun.nio.ch.Net.bind(Net.java:455)
>   at 
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
>   at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>   at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
>   at 
> org.apache.zookeeper.server.NIOServerCnxnFactory.configure(NIOServerCnxnFactory.java:95)
>   at 
> org.apache.zookeeper.server.ServerCnxnFactory.createFactory(ServerCnxnFactory.java:126)
>   at 
> org.apache.atlas.kafka.KafkaNotification.startZk(KafkaNotification.java:140)
>   at 
> org.apache.atlas.kafka.KafkaNotification.start(KafkaNotification.java:170)
>   at 
> org.apache.atlas.kafka.KafkaNotificationTest.setUp(KafkaNotificationTest.java:40)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (ATLAS-297) KafkaNotificationTest.testSendReceiveMessage fails when atlas-server is running on the same machine

2015-11-10 Thread Hemanth Yamijala (JIRA)
Hemanth Yamijala created ATLAS-297:
--

 Summary: KafkaNotificationTest.testSendReceiveMessage fails when 
atlas-server is running on the same machine 
 Key: ATLAS-297
 URL: https://issues.apache.org/jira/browse/ATLAS-297
 Project: Atlas
  Issue Type: Bug
 Environment: Dev environment 
Reporter: Hemanth Yamijala
Priority: Minor


Start the atlas-server on local machine. Then execute mvn 
-Dtest=KafkaNotificationTest -DfailIfNoTests=false test

Get the following stack trace and test failure:

Running org.apache.atlas.kafka.KafkaNotificationTest
Tests run: 3, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 1.262 sec <<< 
FAILURE! - in org.apache.atlas.kafka.KafkaNotificationTest
setUp(org.apache.atlas.kafka.KafkaNotificationTest)  Time elapsed: 0.88 sec  
<<< FAILURE!
org.apache.atlas.AtlasException: Failed to start embedded kafka
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:463)
at sun.nio.ch.Net.bind(Net.java:455)
at 
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
at 
org.apache.zookeeper.server.NIOServerCnxnFactory.configure(NIOServerCnxnFactory.java:95)
at 
org.apache.zookeeper.server.ServerCnxnFactory.createFactory(ServerCnxnFactory.java:126)
at 
org.apache.atlas.kafka.KafkaNotification.startZk(KafkaNotification.java:140)
at 
org.apache.atlas.kafka.KafkaNotification.start(KafkaNotification.java:170)
at 
org.apache.atlas.kafka.KafkaNotificationTest.setUp(KafkaNotificationTest.java:40)




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (ATLAS-224) Left Navigation search results do not show name for each GUID

2015-11-10 Thread Suma Shivaprasad (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad resolved ATLAS-224.

Resolution: Fixed

> Left Navigation search results do not show name for each GUID
> -
>
> Key: ATLAS-224
> URL: https://issues.apache.org/jira/browse/ATLAS-224
> Project: Atlas
>  Issue Type: Bug
>Reporter: Darshan Kumar
>Assignee: Anilsg
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-224_v1.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (ATLAS-296) IllegalArgumentException during hive HiveHookIT integration tests.

2015-11-10 Thread Tom Beerbower (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999898#comment-14999898
 ] 

Tom Beerbower commented on ATLAS-296:
-

[~shwethags], could you review the attached patch?

Thanks!


> IllegalArgumentException during hive HiveHookIT integration tests.
> --
>
> Key: ATLAS-296
> URL: https://issues.apache.org/jira/browse/ATLAS-296
> Project: Atlas
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: ATLAS-296.patch
>
>
> In the hive-bridge tests (HiveHookIT), the following stacktrace is printed. 
> The tests succeed though.
> Introduced with patch for entity notification.  ATLAS-158.
> {code}
> 127.0.0.1 - - [10/Nov/2015:04:31:24 +] "OPTIONS 
> /api/atlas/entities?user.name=sshivalingamurthy HTTP/1.1" 200 3317 "-" 
> "Java/1.7.0_79"
> 2015-11-10 10:01:24.622:WARN:oejs.ServletHandler:qtp276244868-27: 
> /api/atlas/entities
> java.lang.IllegalArgumentException: Input String cannot be null cannot be null
> at org.apache.atlas.ParamChecker.notNull(ParamChecker.java:34)
> at org.apache.atlas.web.util.Servlets.escapeJsonString(Servlets.java:146)
> at org.apache.atlas.web.util.Servlets.getErrorResponse(Servlets.java:125)
> at org.apache.atlas.web.util.Servlets.getErrorResponse(Servlets.java:107)
> at 
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:136)
> at sun.reflect.GeneratedMethodAccessor119.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
> at 
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
> at 
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
> at 
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
> at org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:67)
> at 
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
> at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
> at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
> at 
> com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
> at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
> at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
> at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
> at 
> org.eclipse.jetty.servlet.ServletHandler

[jira] [Updated] (ATLAS-296) IllegalArgumentException during hive HiveHookIT integration tests.

2015-11-10 Thread Tom Beerbower (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tom Beerbower updated ATLAS-296:

Attachment: ATLAS-296.patch

> IllegalArgumentException during hive HiveHookIT integration tests.
> --
>
> Key: ATLAS-296
> URL: https://issues.apache.org/jira/browse/ATLAS-296
> Project: Atlas
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: ATLAS-296.patch
>
>
> In the hive-bridge tests (HiveHookIT), the following stacktrace is printed. 
> The tests succeed though.
> Introduced with patch for entity notification.  ATLAS-158.
> {code}
> 127.0.0.1 - - [10/Nov/2015:04:31:24 +] "OPTIONS 
> /api/atlas/entities?user.name=sshivalingamurthy HTTP/1.1" 200 3317 "-" 
> "Java/1.7.0_79"
> 2015-11-10 10:01:24.622:WARN:oejs.ServletHandler:qtp276244868-27: 
> /api/atlas/entities
> java.lang.IllegalArgumentException: Input String cannot be null cannot be null
> at org.apache.atlas.ParamChecker.notNull(ParamChecker.java:34)
> at org.apache.atlas.web.util.Servlets.escapeJsonString(Servlets.java:146)
> at org.apache.atlas.web.util.Servlets.getErrorResponse(Servlets.java:125)
> at org.apache.atlas.web.util.Servlets.getErrorResponse(Servlets.java:107)
> at 
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:136)
> at sun.reflect.GeneratedMethodAccessor119.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
> at 
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
> at 
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
> at 
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
> at org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:67)
> at 
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
> at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
> at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
> at 
> com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
> at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
> at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
> at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
> at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
> at 
> org.eclipse.jetty.server.session.SessionH

[jira] [Created] (ATLAS-296) IllegalArgumentException during hive HiveHookIT integration tests.

2015-11-10 Thread Tom Beerbower (JIRA)
Tom Beerbower created ATLAS-296:
---

 Summary: IllegalArgumentException during hive HiveHookIT 
integration tests.
 Key: ATLAS-296
 URL: https://issues.apache.org/jira/browse/ATLAS-296
 Project: Atlas
  Issue Type: Bug
Reporter: Tom Beerbower
Assignee: Tom Beerbower


In the hive-bridge tests (HiveHookIT), the following stacktrace is printed. The 
tests succeed though.

Introduced with patch for entity notification.  ATLAS-158.

{code}

127.0.0.1 - - [10/Nov/2015:04:31:24 +] "OPTIONS 
/api/atlas/entities?user.name=sshivalingamurthy HTTP/1.1" 200 3317 "-" 
"Java/1.7.0_79"
2015-11-10 10:01:24.622:WARN:oejs.ServletHandler:qtp276244868-27: 
/api/atlas/entities
java.lang.IllegalArgumentException: Input String cannot be null cannot be null
at org.apache.atlas.ParamChecker.notNull(ParamChecker.java:34)
at org.apache.atlas.web.util.Servlets.escapeJsonString(Servlets.java:146)
at org.apache.atlas.web.util.Servlets.getErrorResponse(Servlets.java:125)
at org.apache.atlas.web.util.Servlets.getErrorResponse(Servlets.java:107)
at 
org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:136)
at sun.reflect.GeneratedMethodAccessor119.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
at 
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
at 
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
at 
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
at org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:67)
at 
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
at com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
at 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:1

[jira] [Updated] (ATLAS-294) Select queries(ex: from DB select DB.name) response contains column names as "_col_x" instead of the actual names requested in the query.

2015-11-10 Thread Erik Bergenholtz (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik Bergenholtz updated ATLAS-294:
---
Assignee: (was: Erik Bergenholtz)

> Select queries(ex: from DB select DB.name) response contains column names as 
> "_col_x" instead of the actual names requested in the query.
> -
>
> Key: ATLAS-294
> URL: https://issues.apache.org/jira/browse/ATLAS-294
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Ayub Khan
> Fix For: 0.6-incubating
>
>
> Select queries(ex: from DB select DB.name) response contains column names as 
> "_col_x" instead of the actual names requested in the query.
> For example: 
> {noformat}
> curl 
> 'http://52.27.169.250:3208/api/atlas/discovery/search?query=from+DB+select+DB.name,+DB.locationUri,+DB.owner,+DB.description'
>  -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' 
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: 
> http://52.27.169.250:3208/' -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/46.0.2490.80 Safari/537.36' 
> --compressed | python -m json.tool
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  Speed
> 100  13180  13180 0643  0 --:--:--  0:00:02 --:--:--   643
> {
> "count": 2,
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> },
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_1",
> "reverseAttributeName": null
> },
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_2",
> "reverseAttributeName": null
> },
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_3",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct892"
> },
> "query": "from DB select DB.name, DB.locationUri, DB.owner, 
> DB.description",
> "queryType": "dsl",
> "requestId": "qtp1879648991-168 - 4f2f4de0-e57a-4283-8dbb-8c2ad3ce00e8",
> "results": [
> {
> "$typeName$": "__tempQueryResultStruct892",
> "_col_0": "Sales",
> "_col_1": "hdfs://host:8000/apps/warehouse/sales",
> "_col_2": "John ETL",
> "_col_3": "Sales Database"
> },
> {
> "$typeName$": "__tempQueryResultStruct892",
> "_col_0": "Reporting",
> "_col_1": "hdfs://host:8000/apps/warehouse/reporting",
> "_col_2": "Jane BI",
> "_col_3": "reporting database"
> }
> ]
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (ATLAS-239) UI: Tag screen should make it possible to specify parent tag

2015-11-10 Thread Erik Bergenholtz (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999432#comment-14999432
 ] 

Erik Bergenholtz commented on ATLAS-239:


The addition to the Create Tag screen should be "Parent" and allow to specify 
an existing tag as the parent tag.

> UI: Tag screen should make it possible to specify parent tag
> 
>
> Key: ATLAS-239
> URL: https://issues.apache.org/jira/browse/ATLAS-239
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Rohit
> Fix For: 0.6-incubating
>
>
> From the tag screen there should be a drop down below the "Tag Name" that 
> lists all of the available Tags. The default should be blank. However, a user 
> should be able to select another tag and if the user selects a named parent 
> tag then when constructing the Trait, the selected Tag should be used as the 
> super class in the definition as follows (where PII is the parent tag name):
> {code}
> ...],
>   "traitTypes":[
> {
>   "superTypes":[
>   “PII"
>   ],
>   
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType",
>   "typeName": ...
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (ATLAS-158) Provide Atlas Entity Change Notification

2015-11-10 Thread Shwetha G S (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998803#comment-14998803
 ] 

Shwetha G S commented on ATLAS-158:
---

You can run individual IT - but some tests are not idempotent and required 
cleaning graph DB which is in target. 
https://maven.apache.org/surefire/maven-failsafe-plugin/examples/single-test.html

> Provide Atlas Entity Change Notification
> 
>
> Key: ATLAS-158
> URL: https://issues.apache.org/jira/browse/ATLAS-158
> Project: Atlas
>  Issue Type: Task
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-158-13.patch, ATLAS-158.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (ATLAS-158) Provide Atlas Entity Change Notification

2015-11-10 Thread Shwetha G S (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shwetha G S updated ATLAS-158:
--
Attachment: ATLAS-158-13.patch

Attaching the latest patch

+1, committed to master. Thanks Tom. [~tbeerbower], can you file jiras for 
adding more ITs and the stacktrace in hive-bridge tests. Thanks

> Provide Atlas Entity Change Notification
> 
>
> Key: ATLAS-158
> URL: https://issues.apache.org/jira/browse/ATLAS-158
> Project: Atlas
>  Issue Type: Task
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-158-13.patch, ATLAS-158.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (ATLAS-160) Move UI plugins from webapp to dashboard module

2015-11-10 Thread Shwetha G S (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shwetha G S resolved ATLAS-160.
---
Resolution: Duplicate

Fixed in ATLAS-159

> Move UI plugins from webapp to dashboard module
> ---
>
> Key: ATLAS-160
> URL: https://issues.apache.org/jira/browse/ATLAS-160
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>
> Currently, the UI plugins are defined in webapp's pom.xml. They should be 
> executed as part of dashboard module instead - new pom can be created in 
> dashboard and plugins can be moved there



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Assigned] (ATLAS-279) UI not displaying results for certain successful "select" search queries

2015-11-10 Thread Darshan Kumar (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Darshan Kumar reassigned ATLAS-279:
---

Assignee: Darshan Kumar  (was: Anilsg)

> UI not displaying results for certain successful "select" search queries
> 
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Darshan Kumar
>  Labels: patch-available
> Attachments: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI. 
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl 
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
>  -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' 
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: 
> http://localhost:21000/' -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/46.0.2490.80 Safari/537.36' --compressed | python -m 
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Reopened] (ATLAS-279) UI not displaying results for certain successful "select" search queries

2015-11-10 Thread Darshan Kumar (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Darshan Kumar reopened ATLAS-279:
-

> UI not displaying results for certain successful "select" search queries
> 
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
>  Labels: patch-available
> Attachments: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI. 
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl 
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
>  -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' 
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: 
> http://localhost:21000/' -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/46.0.2490.80 Safari/537.36' --compressed | python -m 
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (ATLAS-279) UI not displaying results for certain successful "select" search queries

2015-11-10 Thread Anilsg (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anilsg updated ATLAS-279:
-
Labels: patch-available  (was: )

> UI not displaying results for certain successful "select" search queries
> 
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
>  Labels: patch-available
> Attachments: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI. 
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl 
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
>  -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' 
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: 
> http://localhost:21000/' -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/46.0.2490.80 Safari/537.36' --compressed | python -m 
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (ATLAS-279) UI not displaying results for certain successful "select" search queries

2015-11-10 Thread Anilsg (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998345#comment-14998345
 ] 

Anilsg commented on ATLAS-279:
--

 Patch for ATLAS-279,268,244,264 are in one patch available in ATLAS-279 [ 
http://52.27.169.250:3208/#!/search] Please review

> UI not displaying results for certain successful "select" search queries
> 
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Attachments: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI. 
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl 
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
>  -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' 
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: 
> http://localhost:21000/' -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/46.0.2490.80 Safari/537.36' --compressed | python -m 
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (ATLAS-279) UI not displaying results for certain successful "select" search queries

2015-11-10 Thread Darshan Kumar (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Darshan Kumar updated ATLAS-279:

Flags: Patch

> UI not displaying results for certain successful "select" search queries
> 
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Attachments: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI. 
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl 
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
>  -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' 
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: 
> http://localhost:21000/' -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/46.0.2490.80 Safari/537.36' --compressed | python -m 
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (ATLAS-279) UI not displaying results for certain successful "select" search queries

2015-11-10 Thread Darshan Kumar (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Darshan Kumar updated ATLAS-279:

Attachment: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch

> UI not displaying results for certain successful "select" search queries
> 
>
> Key: ATLAS-279
> URL: https://issues.apache.org/jira/browse/ATLAS-279
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Anilsg
> Attachments: ATLAS-279-ATLAS-268-ATLAS-244-ATLAS-264_v0.patch
>
>
> UI not displaying results for certain successful "select" search queries
> For example: Below search query returns 6 results but none are shown on UI. 
> Link for UI snapshot: https://monosnap.com/file/1yNz13MGbe3t6vPvDNqrKqurW6K3Es
> {noformat}
> curl 
> 'http://localhost:21000/api/atlas/discovery/search?query=from+Table+select+Table.name'
>  -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' 
> -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: 
> http://localhost:21000/' -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/46.0.2490.80 Safari/537.36' --compressed | python -m 
> json.tool
> {
> "count": 6,
> "query": "from Table select Table.name",
> "queryType": "dsl",
> "requestId": "qtp1946331169-37253 - 4d068946-1df3-4c60-8671-584e2901c9ee",
> "results": {
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "string",
> "isComposite": false,
> "isIndexable": true,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "_col_0",
> "reverseAttributeName": null
> }
> ],
> "typeName": "__tempQueryResultStruct625"
> },
> "query": "Table as _src1 select _src1.name as _col_0",
> "rows": [
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "product_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "customer_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "time_dim"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_daily_mv"
> },
> {
> "$typeName$": "__tempQueryResultStruct625",
> "_col_0": "sales_fact_monthly_mv"
> }
> ]
> }
> }
> {noformat}
> Other such successful queries which are not displayed on UI are:
> http://localhost:21000/api/atlas/discovery/search?query=Column+select+Column.name
> http://localhost:21000/api/atlas/discovery/search?query=from+DB+select+DB.name



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (ATLAS-114) Upgrade hbase client to 1.1.1

2015-11-10 Thread Shwetha G S (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998290#comment-14998290
 ] 

Shwetha G S commented on ATLAS-114:
---

1. Can't we use storage.hbase.compat-class 
config(http://s3.thinkaurelius.com/docs/titan/current/titan-config-ref.html#_storage_hbase)
 to add 1.1 implementation? 
2. With the current approach, is it safer to use new hbase implementation of 
titan 1.x with titan core 0.5.4? Can you check in the hbase community?
3. Can you update Configuration twiki?

> Upgrade hbase client to 1.1.1
> -
>
> Key: ATLAS-114
> URL: https://issues.apache.org/jira/browse/ATLAS-114
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Attachments: ATLAS-114.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)